Use the EP adapter configuration editor to configure your EP adapter.
Adapter tab
Use the Adapter tab to select an EP adapter and choose your configuration settings.
Figure 1. EP adapter configuration editor example
- Adapter
- In this section, you choose the type of EP adapter and supply
information required by your chosen EP adapter.
- TS Queue
- Emits events to a named CICS® TS queue in one of the XML formats: Common Base Event, Common Base Event REST, or WebSphere® Operational Decision Management (WODM); 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.
- 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. You can use an existing transaction, if the event data is not required.
- The transaction start EP adapter does not support assured emission of events.
- 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.
- WebSphere Message Queue
- Emits events to a WebSphere message queue either in an XML format for consumption by WebSphere Operational Decision Management, the Common Base Event format for IBM® Business Monitor, or in a non-XML format.
- For assured event emission, event delivery is assured when the WebSphere MQ EP adapter is used in combination with persistent WebSphere message queues.
- HTTP
- Emits events to an HTTP 1.1 compliant server using HTTP POST in XML format for consumption by products such as WebSphere Operational Decision Management, and IBM Business Monitor.
- The HTTP EP adapter does not support assured emission of transactional events.
- Advanced options
- Supplying information in this section is not required to complete the EP adapter. 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. Not all these options are 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.