Web Services for CICS project

Generate a Web service description and runtime-specific XML message processing from a high level language structure. You can use this option when you expose an application program as a service provider.

There are two conversion type choices available for this scenario and runtime combination. Either Compiled XML Conversion or Interpretive XML Conversion may be selected from the Web Service Runtime and Scenario Selection dialog. The choice of conversion type involves considering the benefits and cost of either technology. Use the following information when making a selection:

Compiled XML Conversion

XML conversion is accomplished using a suite of generated high-level language (HLL) programs. A driver program interacts with the runtime environment and invokes bundled programs to provide conversion of XML to and from language structures. The compiled XML conversion type provides more extensive support for language structure data types and constructs than the interpretive XML conversion type, however compilation of XML Converters is required and there are more artifacts to manage.

Interpretive XML Conversion

XML conversion is accomplished using generated metadata and an XML conversion component built into the runtime environment. While the Interpretive XML Conversion type has limited support for language structure data types and constructs its requires fewer artifacts and does not involve compilation of XML converters.

Generated artifacts (Interpretive XML Conversion)

Generated artifacts (Compiled XML Conversion)

Scenario: Map to an Existing Service Interface (meet-in-the-middle)

Define mappings between high level language structures and WSDL, XML, or XSD files. You can use this option to generate XML message processing based on the mappings. You use the Create Mappings wizard to define the mappings and create compiled converters. When the wizard closes the single-service mapping editor opens so that you can set the mappings.

Generated artifacts (Compiled XML Conversion)

Scenario: Create New Service Implementation (top-down) Web Services for CICS only

Generate a high level language structure and XML message processing from a Web service description. You can use this option to (1) Create a new service provider application program (2) Expose an existing application program as a service provider or (3) Construct a new service requester application program.

The Interpretive XML Conversion type is the only available conversion technology for this runtime environment and scenario combination. The top-down artifacts are generated through a wizard that allows you to specify the properties of the new service application. To assist in writing the new service application described by the Web service description, generation of a new service provider or service requester template is provided.

Generated Artifacts (Interpretive XML Conversion)

Scenario: Create New MTOM/XOP Service Interface (bottom-up)

Generate an MTOM/XOP compatible Web service description and runtime specific XML message processing from a high-level language data structure. You can use this option when you expose an application program as a service provider where language structures are transmitted in binary instead of an XML representation.

The conversion type choice available for this scenario is and runtime combination isInterpretive XML Conversion.

XML conversion is accomplished using generated metadata and an XML conversion component built into the runtime environment. While the Interpretive XML Conversion type has limited support for language structure data types and constructs its requires fewer artifacts and does not involve compilation of XML converters.

Generated artifacts (Interpretive XML Conversion)

For additoinal information, see Generate CICS MTOM/XOP Web Service (Bottom-Up)