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.
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.
MQ Auditor is a solution that allows a company to audit and track all MQ API calls performed by MQ applications that are connected to a queue manager. The API Exit operates with WebSphere MQ v7.0, v7.1, or v7.5 in Windows, Unix, IBM i, and Linux environments. Under WMQ v5.3 and higher, MQA audits the following MQ API calls: MQCONN, MQCONNX, MQOPEN, MQGET, MQPUT, MQPUT1, MQINQ, MQSET, MQCLOSE, MQDISC, MQBACK, MQBEGIN, and MQCMIT. Under WMQ v184.108.40.206 and higher, MQA audits the above calls as well as the following calls: XASTART, XAEND, XAOPEN, XACLOSE, XACOMMIT, XACOMPLETE XAFORGET, XAPREPARE, XARECOVER, XAROLLBACK, AX_REG, and AX_UNREG. Under WMQ v7.0 and higher, MQA also audits the following additional MQ API calls: MQCALLBACK, MQCB, MQCTL, MQSTAT, MQSUB, and MQSUBRQ.
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 ReQuest for WebSphere MQ offers a set of unique functionality to enable extensive reporting, recovery, and replay functions for WebSphere MQ logs across multiple queue managers on multiple platforms. It supports linear and circular logging and can be driven from a GUI or command line interface. The recovery log can be accessed while the queue manager is running and all functions can be applied on defined 'applications', which are sets of local queues, across queue managers if neccessary. There is no application or queue manager overhead.
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.
Cressida CeQuest for WebSphere MQ utilizes the standard WMQ API Exit facility to collect message related information in a JDBC compliant database and allows users to filter and analyze the collected data. It provides message tracking, reporting, accounting, compliance, and auditing for both persistent and non-persistent messages. It can also concurrently capture message data to the screen, where messages may be filtered and analyzed by authorized users.
MQ Message Encryption (MQME) is a solution that provides encryption for WebSphere MQ message data while it resides in a queue and in the MQ logs. It uses AES and offers the ability to control who accesses protected queues. This control is obtained through the use of UserID grouping, and group files are similar to the Unix /etc/group file. It also has the ability to generate and validate messages using a SHA-2 digital signature.
Universal File Mover (UFM) manages the transfer of files. The user combines a series of Action commands to create the UFM Workflow XML file. These Action commands define which actions are to be taken, the order of the actions, and how errors are to be handled. UFM processes the Action commands as per the UFM Workflow XML file. UFM currently contains 41 Action commands. These action commands fall into five categories: WebSphere MQ Actions, Network Actions, File Actions, Control Actions, and Other Actions. UFM can transfer files in one of five ways, using WebSphere MQ, FTP, SFTP, SCP, or HTTP.