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).
nxlog is a modular, multi-threaded, high-performance log management solution with multi-platform support. In concept, it is similar to syslog-ng or rsyslog, but is not limited to Unix/syslog only. It can collect logs from files in various formats, receive logs from the network remotely over UDP, TCP, or TLS/SSL on all supported platforms. It supports platform-specific sources such as the Windows Eventlog, Linux kernel logs, Android device logs, local syslog, etc. Writing and reading logs to/from databases is also supported for many database servers. The collected logs can be stored into files, databases, or forwarded to a remote log server using various protocols. The old BSD Syslog and the newer IETF syslog standard (RFC 3164 and RFC 5424-5426) are fully supported by nxlog in addition to XML, JSON, CSV, GELF, and other custom formats. A key concept in nxlog is to be able to handle and preserve structured logs so there is no need to convert everything to syslog and then parse these logs again at the other side. It has powerful message filtering, log rewrite, and conversion capabilities. Using a lightweight, modular, and multi-threaded architecture which can scale, nxlog can process hundreds of thousands of events per second.
Shinken is an advanced monitoring system that is based on Nagios, but redesigned and rewritten from scratch while maintaining compatibility. It can monitor all IT devices from systems to end user applications. In case of a failure, Shinken can alert the operation engineers so they can promptly repair it. It has the same capabilities as Nagios along with more advanced built-in facilities such as load balanced and high availability monitoring.
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.
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 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 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.
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.
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 v22.214.171.124 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.
RepoGuard is an advanced validation framework with built-in integrations for several common version control systems. The integration is carried out by utilizing the hook mechanisms each version control system provides. The user may provide configurations that are processed through inversion of control mechanisms. RepoGuard is completely written in the Python programming language, which allows for easy integration of other tools. An extensible command line tool for advanced usage is provided, which allows for comfortable administration.