Use this element of the ServiceSpecification.xml document
to implement a service provider or service requester from a web service description
(WSDL) file. Also use as a container for the required ServiceImplementationSpec
container and, optionally, for the ConnectionPropertyArray and the
ServicePropertyArray.
Attributes
Table 1 shows
the attributes for EISServiceImplementation.
Table 1. Attribute Specifications for EISServiceImplementation| Fields |
Description |
Attribute: runtime
Valid values: WEB_SERVICES_CICS | IMS_SOAP_GATEWAY
Required?: -
Default value: WEB_SERVICES_CICS
|
Specifies the subsystem (such as CICS®, IMS™,
TSO) for which the artifacts are generated:- WEB_SERVICES_CICS: The artifacts are deployable to a CICS TS 3.1+ Web services runtime environment.
- IMS_SOAP_GATEWAY: The artifacts are deployable
into IMS Enterprise
Suite SOAP Gateway and IMS Connect.
|
Attribute: type
Valid values: SERVICE_PROVIDER
| SERVICE_REQUESTOR
Required?: -
Default value: SERVICE_PROVIDER
|
Specifies whether to generate artifacts to implement
a Service Provider or Service Requester based on the input web service
description.Notes: - SERVICE_REQUESTOR mode is referred to as “callout” in IMS-related
scenarios.
- SERVICE_REQUESTOR mode is not supported when
the development scenario is top-down, the target runtime is IMS Enterprise Suite SOAP Gateway,
the conversion type is compiled, and the language is Enterprise PL/I
(see IMS Enterprise Suite SOAP Gateway project).
|
Example
<EISProject xmlns="http:///com/ibm/etools/xmlent/batch/emf/BatchProcessModel.ecore"
name="CICSTopDownSample">
<!-- Generate an implementation of a web service from a WSDL file -->
<EISServiceImplementation type="SERVICE_PROVIDER">
...
</EISServiceImplementation>
<!-- Generate a client to from a WSDL file -->
<EISServiceImplementation type="SERVICE_REQUESTOR">
...
</EISServiceImplementation>
</EISProject>