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.
MQ Standard Security Exit is a solution that allows a company to control and restrict who is accessing a WebSphere MQ resource. The security exit will operate with WebSphere MQ v6.0, v7.0, v7.1, or v7.5 in Windows, IBM i (OS/400), Unix, and Linux environments. It works with Server Connection, Receiver, Requestor, and Cluster-Receiver channels of WebSphere MQ queue manager. The MQ Standard Security Exit solution is comprised of a server-side security exit.
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.
MQWhat is a tool for documenting which MQ components are installed and active on a particular server. Since MQ component information is contained in various files and/or output by MQ programs, MQWhat is designed to collect and summarize the MQ information and present the information to the user's screen in a concise manner.
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.
PyMQI is a Python library for working with WebSphere MQ (formerly known as MQSeries) implementing MQI and PCF protocols. It allows one to connect to queues, put, browse, get messages, and to programmatically administer MQ objects. PyMQI has been used in production environments for several years and is known to work on Linux, Windows, Solaris, AIX, and HP-UX with queue managers running on Linux, Windows, Solarix, AIX, HP-UX, and z/OS mainframe.
Cressida SynQuest for WebSphere MQ is a highly optimized, production-strength replication and synchronization tool utilizing the MQI API exit facility. It is designed to keep the content of WMQ queues on separate queue managers synchronized by performing a MirrorQ type application. SynQuest provides a solution for maintaining disaster recovery backups of queue managers in those cases where a hardware solution (i.e. mirrored disks) is impractical due to distance or associated hardware costs.