CICS Business Event Publisher for MQSeries Modernization Guide

CICS Business Event Publisher for MQSeries automatically generates Websphere MQ messages when EXEC CICS commands are issued or database files are updated. It operates transparently to the application, enabling other programs or processes on any platform to be driven automatically from CICS processing.

The product integrates with CICS and Websphere MQ. It requires configuration to define which CICS events trigger the publication of MQ messages. Administration is performed via a Windows client.

The product allows users to define rules that map CICS events (such as the execution of specific EXEC CICS commands or updates to database files) to the content and format of MQ messages. This enables the automatic propagation of CICS events to other systems via MQ.

The product's architecture involves components within the CICS region that monitor for specified events. When an event occurs, the component formats and sends an MQ message to a designated queue. A Windows-based administration client is used for configuration and monitoring.

The product intercepts EXEC CICS commands and database updates. Configuration files define the mapping between these events and the MQ messages to be generated. Specific syntax for defining these mappings would be found in the product documentation.

The product likely uses MQI (Message Queue Interface) to interact with Websphere MQ. Specific API endpoint patterns and method names would be detailed in the product's API documentation. Integration is typically done using programming languages supported by both CICS and MQ, such as COBOL or PL/I.

The main components include the CICS event interceptor, the message formatter, and the MQ message sender. These components communicate through internal CICS mechanisms and MQ API calls. The product uses Websphere MQ for message storage and transport.

The administrative interface is a Windows client. User management is handled through CICS security. Configuration parameters define event mappings, MQ queue names, and message formats. Monitoring and logging capabilities are available through the Windows client and CICS logs.

By automating the generation of MQ messages from CICS events, the product enables real-time integration between CICS applications and other systems. This can improve business responsiveness, reduce manual intervention, and facilitate event-driven architectures.

The product allows businesses to extend the reach of their CICS applications by integrating them with other systems and platforms via MQ. This can enable new business processes and improve the efficiency of existing ones.

The product facilitates the creation of event-driven architectures by automatically publishing CICS events to MQ. This allows other systems to react to these events in real-time, enabling more agile and responsive business operations.

The product leverages CICS security for user authentication and authorization. Access control is likely based on CICS resource definitions and user profiles. Encryption is used for MQ message transport, typically using SSL/TLS.

The product integrates with CICS security to control access to event publishing functions. User roles and permissions within CICS determine which users can configure and manage event mappings.

The product supports encryption for MQ message transport, ensuring that sensitive data is protected as it moves between CICS and other systems. This typically involves configuring SSL/TLS for MQ channels.

The product provides monitoring and logging capabilities through the Windows client and CICS logs. These logs can be used to track event publishing activity, identify errors, and troubleshoot issues.

The product's operations involve configuring event mappings, monitoring MQ queue depths, and troubleshooting any errors that occur during event publishing. Regular maintenance of CICS and MQ is also required.

The product's health can be monitored by checking the status of CICS regions, MQ queues, and the event publishing process. The Windows client provides a graphical interface for monitoring these components.