Adapter tab

You can also provide advanced information that tells CICS® how to run the EP adapter. The tab consists of three sections.

Resource

In this section, you choose whether to use a predefined EPADAPTER or EPADAPTERSET resource, or the adapter defined in the Adapter section of the Adapter tab.

If you select Use a predefined EPADAPTER resource or Use a predefined EPADAPTERSET resource, enter the resource name in the Name field, or click Choose and use the dialog to select a resource. For more information about a predefined EPADAPTER resource, see Event processing (EP) adapter configuration editor. For more information about a predefined EPADAPTERSET resource, see Event processing (EP) adapter set editor.

Use Export Event Specifications to export descriptions for one or more event specifications in your event binding as a schema or copybook for use elsewhere. See Exporting event specifications.

Adapter

In this section, you choose the type of EP adapter and supply information required by your chosen EP adapter.

WebSphere MQ Queue

Emits events to an IBM® MQ message queue in an XML format for consumption by IBM Operational Decision Manager or IBM Business Monitor, or in binary CICS flattened event (CFE) format for consumption directly from IBM MQ.

For assured event emission, event delivery is assured when the WebSphere MQ Queue EP adapter is used in combination with persistent IBM MQ message queues.

Transaction Start

Emits events to a named CICS transaction. Data is passed to the transaction in a container-based event format. You can specify the CICS system to run the transaction. If the event data is not required, you can use an existing transaction.

The transaction start EP adapter does not support assured emission of events.

TS Queue

Emits events to a named CICS TS queue in one of the XML formats: Common Base Event, Common Base Event REST, Decision Server Insights Event, or WebSphere Business Events; or in a non-XML (CFE) format. Use this EP adapter to validate that the correct events are being captured with the correct data, and to emit events to any consumer that reads from a TS queue.

For assured event emission, synchronous transactional events need a recoverable TS queue; synchronous nontransactional events need an unrecoverable queue. Whether TS queues are recoverable depends on the settings of a matching TSMODEL; TS queues are recoverable only when there is a matching TSMODEL. When you use the TS queue adapter for synchronous transactional events, you cannot issue a DELETEQ TS command for the event TS queue in the unit of work that captures the event.

Custom (User Written)

Emits events in any format that you require. A custom EP adapter is a CICS program that you write to provide a combination of formatting and routing of an event that is not supported by the supplied EP adapters. The custom EP adapter must not carry out any other processing, such as consumption of the event.

For assured event emission, the custom EP adapter must conform to the recoverability requirements of the event. Consult the documentation for your custom EP adapter to see whether it supports transactional or nontransactional synchronous events.

HTTP

Emits events to an HTTP 1.1 compliant server using HTTP POST in XML format for consumption by products such as IBM Operational Decision Manager or IBM Business Monitor.

The HTTP EP adapter does not support assured emission of transactional events.

Note:

Event bindings created using CICS TS Version 4.2 or later no longer include the eventDispatcherSpecification element except when the adapter specification is embedded.

When you use the CICS event binding editor with CICS TS Version 4.2, you can choose the embedded or external EPADAPTER definition. To be compatible with CICS TS Version 4.1, you must use the embedded EPADAPTER definition.

Installing an event binding into CICS TS Version 4.2 or later causes CICS to extract the EPADAPTER configuration from the event binding and create it automatically.

Advanced options

Supplying information in this section is not required to complete the event binding. If you need to influence the way in which CICS runs the EP adapter, you can change the emission mode, priority, transactionality, user ID, transaction ID, and CICS system ID. Some options are not available for all EP adapter types. The section displays the correct set of options for your chosen EP adapter and message format.

For more information about the advanced settings you can choose, see Specifying EP adapter and dispatcher information.