Use the adapter tab to select an EP adapter that will emit
events for this event binding.

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
resource, or the adapter defined in the Adapter section of the Adapter
tab. For more information about a predefined EPADAPTER resource, see
the Event processing (EP) adapter configuration editor topic.
- 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® Business Events (WBE),
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 CICS-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 Business Events,
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 Business Events,
and IBM Business Monitor which
was formerly known as WebSphere Business Monitor.
The HTTP EP adapter does not support assured emission
of transactional events.

Note: Event bindings created using CICS TS v4.2 or higher no longer
include the eventDispatcherSpecification element.
When using the CICS event binding editor with CICS TS v4.2 you have the choice
of embedded or external EPADAPTER. You must use the embedded EPADAPTER
definition to be compatible with CICS TS
v4.1.
Installing an event binding into CICS TS v4.2 causes CICS to extract the EPADAPTER configuration
from the event binding and create it automatically.

- Advanced
- 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. 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.