You can export descriptions for one or more event specifications in your event binding as a schema or copybook for use elsewhere.
If you are using the WebSphere MQ EP adapter and the common base event format or the WebSphere Business Events (XML) format, the exported file is an XML schema definition .xsd file.
If your chosen adapter and data format emit events to a system in a non-XML character format, the exported file is a COBOL copybook .cpy file. The TSQ EP adapter and the WebSphere MQ EP adapter using the CICS Flattened Event format emit events in a non-XML character format.
To export event schema or copybook, perform the following steps:
A file is 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 called example1 and example2, two XML schema files are created, example1.xsd and example2.xsd. You can import this schema file toIBM® Business Monitor to help define an inbound event.
If you specify the WebSphere MQ EP adapter and the WebSphere Business Events (XML) format and select an event specification called example1, an XML schema file is created, called example1.xsd. You can use this schema file in the WebSphere Business Events Design Data tool to help define an event.
If you specify the TS Queue adapter and select two event specifications 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 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.