Deploy a callout application to
SOAP Gateway with the SOAP Gateway management utility.
A callout application requires a valid correlator XML file with interaction properties for
the application, a valid WSDL file that describes the web service to clients, and a valid connection bundle
with connection properties for the application.
- Ensure that the required web service artifacts are located
in the SOAP Gateway installation
directory.
The correlator XML file and WSDL (or XSD) file
can either be in the XML and WSDL directories, or elsewhere in the
SOAP Gateway directory.
If the files are already located in the XML and WSDL directories when
you deploy the web service, you can provide the file name without
the fully qualified path to the file.
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).
Restriction: Nested XSD import
statements are supported only by Rational® Developer
for System z® Version
8.5.1 or later in its top-down support for COBOL data structure generation
for synchronous callout. Sharing of XSD schema files among callout
applications is not supported. See the -deploy command
reference for details.
- If you are not using the XML
adapter function in IMS Connect, update your correlator file by using
the SOAP Gateway management utility iogmgmt
-corr command and setting the
-a option
(adapter type) to No_Adapter. By
specifying the No_Adapter value, the adapterType
entry in the correlator is set to blank. By default, this entry is
set to IBM XML Adapter.
-
Issue the command to deploy the application to the server:
iogmgmt -deploy -w wsdl_file -r
correlator_file.
SOAP Gateway is configured to pass callout
requests to the target web service.