AtMail is a webmail client. The project aims to provide an elegant client for existing IMAP mailservers, with less bloat and a focus on an intuitive, simple user interface. Features include complete Webmail functionality, address-book support, video mail, an AJAX interface, drag'n'drop, and more.
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.
Cosmo is the OSAF calendar sharing server. With your favorite calendar program (Chandler, Apple iCal, Mozilla Sunbird, or any other WebDAV or CalDAV enabled client), you can share your calendar with other people by publishing it to Cosmo. Your shared calendars can be subscribed to and updated by anyone, even if they don't have an account on your server. Cosmo provides Atom feeds for shared calendars, so you can track updates in your favorite feed reader and integrate your calendar into your Web site or blog.
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.
The MQ Channel Monitor application is a software package designed to gather and to display the status of MQ channels of the queue manager. It displays 16 columns of channel status information. The display is automatically refreshed every 60 seconds (default value). The user can alter this refresh rate. By default, all of the channels of the queue manager that currently have a status will be displayed. The user can define filters so that only particular channels will have their status displayed. MQCM can connect to a queue manager in 3 possible ways: locally in binding mode; remotely using a Client Channel Definition Table (CCDT); and remotely using an MQ XML file. MQCM supports both forms of MQ security: SSL for connecting to remote queue managers, and 3rd party security exit for connecting to remote queue managers.
When a user inputs a hostname or an IP address, MQ Port Scan will scan a range of ports looking for a queue manager's MCA, using the standard (system default) channel names, in order to make a successful connection. It is very easy to use. It has the ability to search across a range of IP addresses and scan the port range for each IP address. Any time MQ Port Scan successfully connects to a queue manager, the information is written to a CSV file. The output will include the queue manager name, MQ version, channel name, hostname or an IP address, and port number.
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.