Generating the XML converter driver and the correlator file by using Rational Developer for System z : Mashup Center 2.0Added by IBM on November 20, 2009 | Version 1 (Original)
|No abstract provided. Tags: IMS transaction feeds, IMS transaction feeds, IMS transaction feeds, IMS transaction feeds, correlators, XML converter driver, IMS transaction feeds, IMS transaction feeds, IMS transaction feeds, execution timeout, timeouts, socket timeout, timeouts, transaction code, LTERM name, feeds, feeds, 2.0
Contents: MashupHub User and Administrator Guide : Mashup Center 2.0
Use the Enterprise Service Tools wizard in IBM®
Developer for System z®
to generate the artifacts that are needed to enable your IMS transaction to run as a feed.
Before you begin
To generate the XML converter driver and the correlator file, you must have a COBOL copybook that describes the format of the input and output messages for your IMS application.
About this task
The Enterprise Service Tools wizard in Rational Developer for System z guides you through the steps to create the XML converter driver and the correlator file. The following table describes the key information to specify.
Table 1. Information that the Enterprise Service Tools wizard gathers
|Your IMS application source file||The Enterprise Service Tools wizard parses the application source file to identify the language structures.|
|z/OS® as the platform that the application runs on||The platform selection impacts other platform information attributes, such as floating point format and endian, to default values that are appropriate for the z/OS platform.|
|Inbound language structure in your application||Based on the language structures from your application, the Enterprise Service Tools wizard needs to know which data structure is the input to invoke the application.|
|Outbound language structure in your application||Based on the language structures from your application, the Enterprise Service Tools wizard needs to know which data structure is the output from the application. |
|Prefix for the converter name||The Enterprise Service Tools wizard generates the converters based on the prefix. Because the Enterprise Service Tools wizard lets you generate separate converter files for inbound and outbound messages, it appends a different character to the prefix to create different converter files. |
|Character encodings||The code page to use for encoding the inbound and outbound XML messages, and the code page that is used by the z/OS host system.|
|Transaction code for your IMS application||The transaction code that is required to run the IMS application.|
|Socket timeout and execution timeout values||The amount of time the IMS transaction feed generator waits for a response from IMS Connect, and for IMS Connect to send a message to IMS and receive a response before timing out.|
Parent topic: Creating a feed from an IMS transaction : Mashup Center 2.0
Previous topic: Designing your feed from an IMS application : Mashup Center 2.0
Next topic: Deploying the XML converter driver to IMS Connect : Mashup Center 2.0