Output files generated in the WSDL2PLI scenario

Edit online

This topic describes the output files generated in the WSDL2PLI scenario.

In the WSDL2PLI scenario the following components interact to produce the output files:
  1. The batch processor.
  2. The WSDL2ELS component, which does common WSDL-to-programming-language processing.
  3. The WSDL2PLI component, which does WSDL-to-Enterprise-PL/I processing.
The sequence of processing is as follows:
  1. The batch processor invokes the WSDL2ELS component, passing to it the input parameters specified in the input properties files.
  2. The WSDL2ELS component invokes the WSDL2PLI component:
    • Together these two components produce a set of intermediate output files.
    • Control is then returned to the batch processor.
  3. The batch processor gathers the information in the intermediate output files, processes the information, and generates the final output files.
The intermediate output files generated by WSDL2ELS and WSDL2PLI components are as follows:
  • The mapping session files:
    • There are two mapping session files for each operation defined in the WSDL file: one mapping session file for the inbound message and one for the outbound message.
    • Each mapping session file contains:
      • Descriptions of the XML data structure and the programming language data structure that are the source and target of the mapping session.
      • A description of each the mapping of data between the source data structure and the target data structure.

  • A WSDL2ELS metadata file that is later used to generate the IMS application template file, the IMS correlator file, and the XML converter files.

  • A log file containing processing information. The name and location of file are specified in the targetLogFile parameter of the WSDL2ELSSpec element of the ServiceSpecification.xml input file.

The files generated by the batch processor are as follows:
  • The file containing the application template program:
    • This program is a working template of an application that uses the IMS Web service provider.
    • If the original WSDL file contains multiple operations then the template program is multioperation.
  • The file or files containing the drivers and converters.
    • There is one such file for each operation defined in the WSDL file.
    • Each file contains a driver, an inbound converter, and an outbound converter.
  • The IMS correlator file:
    • This file contains information about using IMS Connect.
    • If the WSDL file contains multiple operations then the correlator file is also multioperation.