EISService

Edit online

Use this element of the ServiceSpecification.xml document to provide information about the Web service and as a container for the required Operation containers and, optionally, for the ConnectionPropertyArray and the ServicePropertyArray.

If this service contains multiple Operations and it is implemented by the CICS® Web Services runtime environment, you can specify an optional WSBindSpec element. In that element, you can specify properties of the WSBind file representing multi-operation service. The WSBindSpec options provided on multiple Operations takes precedence over any WSBindSpec options that might be specified on individual Operations. That is, any WSBindSpec on individual Operations in multi-operation service is ignored.

Note: If you do not specify a WSBindSpec for the EISService with multiple operations, the default values for multiple Operations are used (seeWSBindSpec description for more information on the default WSBindSpec values for multiple Operations).

The following is a sample of specifying multiple operations:

<EISProject name="BankPrj">
  <EISService name="Bank">
        .....
    <Operation name="DepositFundsOperation">
     ....
    </Operation>
    <Operation name="WithdrawFundsOperation">
     ....
    </Operation>
  </EISService>
</EISProject>

The following rules apply when generating multiple Operations:

Operation names must not contain duplicates
Driver types must match on all operations
Target namespaces for types in message specifications must not contain duplicates across multiple operations
Output file specifications across multiple Operations must not have duplicate names.
For unwrapped SOAP messages (which is what the single-service projects GUI tools generate), top-level elements in the request messages have to be distinct for distinct operations.
Note: Not following these rules will cause the results of the generation process to be unpredictable.

When specifying multiple operations, keep in mind the following restrictions:

Program interface for the business program implementing multiple operations in CICS must be via CHANNEL (COMMAREA interfaces are not supported).
Business program name must be specified in the WSBindSpec element of the EISService container. Business program names of the DriverSpec elements in the individual operations are ignored.
Relying on default program names and file names may lead to unpredictable results when the different parameters come up identical values. For example service name with the name of "Bank" may lead to a default business program name of BANKSER. If you also specify the router name as BANKSER, you may have errors when building or using these programs.

Contained by

EISProject

Contains

Attributes

Table 1 shows the attributes for EISService.

Table 1. Attribute Specifications for EISService
Fields	Description
Attribute: name Valid values: See Description Required?: - Default value: See Description	Specifies the name of the Web service. The name of the Web Services Definition File (WSDL) that is generated uses this name. The default value: The default is taken from the xsebatch command line parameter -w.
Attribute: generateConverters Valid values: true \| false Required?: - Default value: false	Specifies whether to generate the converter set (request and response converters, driver).
Attribute: generateSeparateXSD Valid values: true \| false Required?: - Default value: false	Specifies whether to generate a separate set of XML schemas that define the message request and response). Note: The "false" setting of this attribute is meaningful only if generateWSDL is set to true. A value of false specifies that the service definition file contains an embedded schema.
Attribute: generateWSDL Valid values: true \| false Required?: - Default value: false	Specifies whether to generate a service definition.
Attribute: targetFilesURI Valid values: See Description Required?: - Default value: See Description	Specifies the URI of the location where the output files will be generated, relative to the top level project. The default value is: Value of targetNamespace, if specified. Otherwise it is set to file: //target.files
Attribute: targetNamespace Valid values: See Description Required?: - Default value: svcNS	Specifies the URL of the target namespace.
Attribute: type Valid values: CICS \| IMS Required?: - Default value: CICS	Specifies the relevant subsystem.

Example

Figure 1 is an example of the EISService element.

Figure 1. Example of EISService Element

<EISProject name="CICSSample">
     <EISService name="CustomerInfo" type="CICS" targetNamespace="http://cics.sample"
             targetFilesURI="file://my.files"
             generateConverters="true"
             generateSeparateXSD="false"
             generateWSDL="true" >

     </EISService>
</EISProject>