Exporting event specifications

You can export descriptions for one or more event specifications in your event binding as a schema or copybook for use elsewhere.

Before you begin

You must have a CICS® bundle project that contains an event binding file.

About this task

If the data format specified by your chosen EP adapter or an EP adapter in your chosen EP adapter set is:

An XML format such as common base event, common base event REST, or WebSphere® Operational Decision Management format, then the exported file is an XML schema definition .xsd file. The TSQ EP adapter, WebSphere MQ EP adapter, and HTTP adapters can all emit events in XML character formats.
A non-XML format, that is, CICS flattened event format, then the exported file is a COBOL copybook .cpy file. The TSQ EP adapter and the WebSphere MQ EP adapter can emit events in CICS flattened event format.

Procedure

To export an event schema or copybook, perform the following steps:

From the Adapter tab in the CICS event binding editor, click Export Event Specifications. The Export Event Specifications window is displayed.
Select the event specifications that you want to export.
Specify a directory to which to export the event specifications in the To directory field.
Click Export.

Results

One or more files are created in the specified directory for each event specification that you selected.

For example, if you specify the WebSphere MQ EP adapter and the common base event format and select two event specifications that are called example1 and example2, two XML schema files are created: example1_CBE.xsd and example2_CBE.xsd. You can import these schema files to IBM® Business Monitor to help define an inbound event.

If you specify the WebSphere MQ EP adapter and the WebSphere Operational Decision Management (XML) format and select an event specification that is called example1, an XML schema file is created, called example1_WBE.xsd. You can use this schema file in the WebSphere Operational Decision Management Design Data tool to help define an event.

If you specify the TS Queue adapter and select two event specifications that are called example1 and example2, two COBOL copybooks are created: example1.cpy and example2.cpy. You can use these copybooks to process data in your own event consumer programs.

If you specify an EP adapter set that has a TS Queue adapter and the WebSphere MQ EP adapter (WebSphere Operational Decision Management - XML format), and you then select two event specifications that are called example1 and example2, four files are created with the name suffix that indicates the format: example1.cpy, example1_WBE.xsd, example2.cpy, and example2_WBE.xsd. You can use these files in your programs and in the WebSphere Operational Decision Management Design Data tool.

If you export an event specification, and then export the same event specification again to the same directory, the CICS event binding editor prompts you to either overwrite the existing file or cancel the export operation.