Deploying a web service to SOAP Gateway
A web service must be deployed to the SOAP Gateway server before it is available to client applications.
A web service in the provider scenario in SOAP Gateway has
three components:
- A WSDL file that describes the web service to client applications. The WSDL file can import additional XSD files.
- An entry in a correlator XML file that defines the transaction properties between web service requests and an IMS application.
- A connection bundle entry that defines connection and security properties between SOAP Gateway and IMS Connect.
Deploying a web service makes these artifacts active in the runtime configuration. The service WSDL file and any imported XSD files are bundled into the web service Axis ARchive file (AAR file), stored in the master configuration, and made available in the runtime configuration. The web service is then available for client applications.
Tip: The
correlator file and the WSDL file, when uploaded from a distributed platform, must be transferred in
BINARY mode from your local workstation. Binary transfers provide a bit-by-bit copy that preserves
the encoding on your system by instructing the FTP socket not to convert the encoding to the local
system encoding (EBCDIC).