Chandler is a standards-based "Note-to-Self Organizer" designed for personal and small-group task management and calendaring. It consists of a desktop application and Chandler Hub, a free sharing service and Web application. You can also download and run your own Chandler Server.
Jiplet Container (Java SIP Servlet) is a servlet-like development and runtime environment for SIP applications. The SIP protocol is widely used for voice services over IP networks. This product enables developers to create server-side SIP applications using a component-based model similar to that envisioned by the J2EE architecture. The Jiplet container runs as a standalone server as well as a JBOSS service.
OpenDMTP (Open Device Monitoring and Tracking Protocol) is a highly configurable and extensible protocol for communicating with mobile devices over high-latency/low-bandwidth networks. The protocol is particularly geared towards the transmission of GPS base location information and includes a full-featured reference implementation showcasing its capabilities.
The deepOfix Mail Server makes it possible for organizations with minimal technical expertise to have robust server infrastructure. deepOfix offers unprecented ease of use, doesn't require prior GNU/Linux experience and is backed by a full-time development and support team. deepOfix features LDAP-based directory services for user account management, email delivery, distribution lists, and addressbooks. It also includes built in tools for spam and virus control, webmail, and fetching email.
The POP and IMAP troubleshooter serves to diagnose and solve connection problems from client machines to email services. It reads the client configuration files (Outlook, Windows Mail, Thunderbird, etc.), checks the individual settings, and then attempts to create POP, IMAP, and SMTP connections using these settings. The troubleshooter is coded in C++ using the Qt environment. It can be used generically, or can be customized for the demands of a particular email service.
The Message Multiplexer (MMX) application will get a message from a WebSphere MQ queue and output it to one or more queues. Context information is maintained across the message put(s). MMX can move messages from a single source queue to (up to) 99 target queues. Messages put to each target queue are an exact replicate of the original message from the source queue (including the message's MQMD). MMX performs each MQGET and the subsequent "n" MQPUT(s) under a Unit of Work (UOW), so that message integrity is kept.
The Message Router (MRTR) application will move a message from a central WebSphere MQ queue to a specific application WebSphere MQ queue. The destination queue that the message will be placed into will be based on a keyword in the message. Context information is maintained. MRTR will look in the message for a Start Keyword and an End Keyword. The value between these two keywords is the Keyword Value (inifile Token). MRTR will search its ini file for that particular Keyword Value. The field value associated with the looked-up keyword value is the destination queue name. MRTR performs each MQGET and the subsequent MQPUT under a Unit of Work (UOW) so that message integrity is kept.