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).
  1. Deploy the web service with the iogmgmt -deploy -w wsdl_file -r correlator_file command.
    The WSDL file can be either the file name, if the WSDL file is already in the server WSDL directory, or the fully qualified path to the WSDL file. The correlator file can be either the file name, if the correlator XML file is already in the server XML directory, or the fully qualified path to the correlator XML file.
    Tip: For ease of maintenance and support, it is recommended that you store your web service WSDL, XSD, and correlator files in a location other than the SOAP Gateway WSDL and XML directories. Deploy a web service by specifying the fully qualified path to these files.
  2. Verify that the web service is deployed.
    The SOAP Gateway management utility issues messages if it is unable to deploy the web service. You can verify that the service is deployed by issuing the iogmgmt -view -correlatorfile ALL command. Alternatively, use the SOAP Gateway administrative console.
    The correlator file for the newly deployed web service is displayed in the list of active correlator files in the runtime cache.
The web service is now deployed and can accept client application requests.