How does the product intercept CICS commands and translate them into MQ messages?

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.

What APIs does the product expose, and what programming languages are supported for integration?

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.

What are the main system components and how do they communicate?

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.

What administrative interfaces are available, and how is user management handled?

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.

What business value does the product provide?

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.

How does the product help businesses extend the reach of their CICS applications?

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.

How does the product facilitate the creation of event-driven architectures?

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.

What authentication methods are supported, and what access control model is used?

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.

How does the product control access to event publishing functions?

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.

What encryption is used and where?

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.

What monitoring and logging capabilities exist?

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.

What are the main operational tasks associated with the product?

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.

How can the health of the product be monitored?

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.

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

CICS Business Event Publisher for MQSeries

IBM Not Supported z/OS

MQ Messaging and SOA Networks and Communication Automation CICS

Vendor

IBM

Product Overview

CICS Business Event Publisher for MQSeries provided automated event-driven integration between CICS applications and other systems via Websphere MQ. The architecture comprised several key components: the CICS event interceptor, responsible for capturing EXEC CICS commands and database updates; the message formatter, which transformed event data into MQ message format; and the MQ message sender, which transmitted messages to designated MQ queues. Communication between components relied on internal CICS mechanisms and MQI calls.

Administration was performed through a Windows-based client, allowing configuration of event mappings and monitoring of system activity. Given the product's withdrawn status, organizations should consider migrating to alternative solutions. Native CICS event processing offers similar capabilities, while platforms like IBM MQ Event Bridge and Apache Kafka provide more modern and scalable architectures for event-driven integration.

Migration requires careful planning to replicate event mappings and ensure seamless transition of message flows.

Frequently Asked Questions

What is the primary function of CICS Business Event Publisher for MQSeries?

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.

What are the main integration points and dependencies of the product?

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.

How does the product enable the automatic generation of MQ messages from CICS events?

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.

Can you describe the high-level architecture of the product?

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.

Help Improve This Directory

Notice outdated information? Have insights about this product? Help the mainframe community stay informed with accurate, current data.

Report Issue Suggest Product Share Event

Are You a Vendor? Claim Your Listing

Take control of your product listings. Add verified information, showcase updates, and unlock a Claimed Vendor badge across the directory.

Claim Your Listing Now

Are You a Vendor? Claim Your Listing

CICS Business Event Publisher for MQSeries

Product Overview

Frequently Asked Questions

What is the primary function of CICS Business Event Publisher for MQSeries?

What are the main integration points and dependencies of the product?

How does the product enable the automatic generation of MQ messages from CICS events?

Can you describe the high-level architecture of the product?

How does the product intercept CICS commands and translate them into MQ messages?

What APIs does the product expose, and what programming languages are supported for integration?

What are the main system components and how do they communicate?

What administrative interfaces are available, and how is user management handled?

What business value does the product provide?

How does the product help businesses extend the reach of their CICS applications?

How does the product facilitate the creation of event-driven architectures?

What authentication methods are supported, and what access control model is used?

How does the product control access to event publishing functions?

What encryption is used and where?

What monitoring and logging capabilities exist?

What are the main operational tasks associated with the product?

How can the health of the product be monitored?

Related Products

More from IBM

Access 1

ACF/NCP

ACF/SSP

ACO SolutionPac

Ada/370

ADF II

Similar Products

_beta access monitor

$avers

2cIP

2cSNA

3270 SUPEROPTIMIZER/CICS

3770Link

Help Improve This Directory

Are You a Vendor? Claim Your Listing