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.
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.
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 v126.96.36.199 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.
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 Channel Auto Creation Manager (MQCACM) is an MQ Channel Auto-Definition (MQ CHAD) exit which allows a company to control and restrict incoming connection requests to auto-create a channel. MQCACM is invoked when a request is received to start an undefined Receiver, Server-Connection, Cluster-Receiver, or Cluster-Sender channel. MQCACM can modify or clear the supplied default channel definition values for an instance of the channel, so there is no exit incompatibility (cross-platform or otherwise).
MQ Channel Encryption (MQCE) is a solution that provides AES encryption for message data flowing between WebSphere MQ (WMQ) resources. It operates with Sender, Receiver, Server, Requestor, Cluster-Sender, Cluster-Receiver, Server Connection, and Client Connection channels of the WMQ queue managers. It is a simple drop-in solution and can be configured as a queue manager channel message exit or as a channel sender/receive exit pair.
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.
The MQ File Mover application is a software package designed to move files using WebSphere MQ (aka MQSeries). MQFM processes “Action” commands, which are controlled through an MQFM Workflow XML file. The user combines a series of Action commands to create the MQFM Workflow XML file.
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.