MQ Authenticate User Security Exit (MQAUSX) is a solution that allows a company to fully authenticate a user who is accessing a WebSphere MQ resource. It verifies the user's user ID and password (and possibly domain name) against the server's native OS system (or domain controller) or a remote LDAP server. The security exit will operate with WebSphere MQ v6.0, v7.0, v7.1, or v7.5 in Windows, iSeries (OS/400), Unix, and Linux environments. It works with Server Connection, Client Connection, Sender, Receiver, Server, Requestor, Cluster-Sender, and Cluster-Receiver channels of WebSphere MQ queue manager. The MQ Authenticate User Security Exit solution is comprised of 2 components: client-side security exit and server-side security exit.
MQ Batch Toolkit allows users to manipulate, monitor, and manage messages in a queue of a WebSphere MQ (formally MQSeries) queue manager from a command-line or shell scripting environment. It is designed for developers, programmers, quality assurance testers, and production support personnel who want to do backup and recovery of messages, stress testing of applications, replaying of messages, searching a queue for a text string, etc.. It can run on any platform that supports Java v1.4 (or higher). It can connect to local queue managers or to any remote queue manager.
MQ Visual Browse allows users to view messages in a queue of a WebSphere MQ (formally MQSeries) queue manager and presents the data in a simplified format similar to a database utility or spreadsheet program. It is designed for application programmers, JMS developers, quality assurance testers, and production support personnel who do not need message editing capabilities. It can run on any platform that supports Java v1.4 (or higher). It can connect to local queue managers or to any remote queue manager.
MQ Visual Edit allows users to view, manipulate and manage messages in a queue of a WebSphere MQ (formally MQSeries) queue manager and presents the data in a simplified format similar to a database utility or spreadsheet program. It is designed for application programmers, JMS developers, quality assurance testers, and production support personnel. It can run on any platform that supports Java v1.4 (or higher). It can connect to local queue managers or to any remote queue manager.
Schedule::Cron is a Perl module that provides a simple but complete cron-like scheduler. It can be used for periodically executing Perl subroutines. The philosophy behind Schedule::Cron is to call subroutines periodically from within one single Perl program instead of letting cron trigger several (possibly different) Perl scripts. Everything under one roof. Furthermore, Schedule::Cron provides a mechanism to create crontab entries dynamically, which isn't that easy with cron. It knows about all extensions (at least all extensions the author is aware of, i.e those of "Vixie" cron) for crontab entries like ranges including 'steps', specification of month and days of the week by name, or coexistence of lists and ranges in the same field. It even supports a bit more (like lists and ranges with symbolic names). It has existed since 1999 on CPAN and is successfully used in many projects.
Pandora FMS is a software-monitoring tool created for all kinds of companies. It is specially designed for large environments, and works by first managing servers, applications, and communications, and then notifying clients of problems and failures before they occur. Pandora FMS also includes a configurable report system that evaluates and notifies the client on the level of fulfillment and compliance of their systems. It supports all kinds of technologies unifying the management tools of your system, such as performance monitoring, network monitoring, and availability management. Pandora FMS makes your company management more agile and improves your process performance.
GoAnywhere Services allows trading partners and employees to securely connect to your organization and easily download or upload files. Popular file transfer and encryption standards are supported without the need for proprietary client software. It supports FTP, SFTP, FTPS, HTTP, and HTTPS, provides a pure Web client for simple file transfers, includes event triggers based on user-defined conditions, generates detailed audit logs and alert messages, provides trading partners with account wizards and permission controls, features an intuitive browser-based interface for remote administration and monitoring, and requires no programming or special skills.
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.
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.