Web services gateway - prerequisites and constraints
The gateway is an enterprise application that you can deploy
- to an appserver that is a node of a WAS Network Deployment cell.
- to a stand-alone appserver.
If you want to run a gateway cluster (for example to guarantee high availability) create the cluster (probably as a deployment manager cell) before you install the gateway on any machine in the cluster.
WAS Network Deployment is not a stand-alone product for running enterprise applications. So if you want to deploy the gateway you also need to install the base WAS product.
Although it is not installed by default, a copy of the base WAS product is packaged with the WAS Network Deployment product.
This version of the Web services gateway is also subject to the following constraints:
- WSDL definitions for target services must use XML Schema version 2001. For more information, see Web services gateway troubleshooting tips.
- The SOAP message format must be RPC style. The gateway does not support Document style SOAP messages.
- If you are using the Apache SOAP Channel, then the SOAP message format must be RPC style. To handle Document style SOAP messages, use the SOAP/HTTP channel (which supports both RPC style and Document style SOAP messages).
- The gateway application (wsgw.ear) must be installed before channel and filter applications. If the gateway application needs to be reinstalled, all channels and filters must be uninstalled first, then reinstalled after the gateway application.
- The gateway does not support WSDL service definitions that contain soap:header elements within their wsdl:definition element.
- If the WSDL for your service contains soap:header elements within the wsdl:definition element, then the gateway passes the SOAP headers through. This is correct behavior. However, you will also see the following effects:
- The SOAP headers will not be included in the WSDL that the gateway generates.
- If you set the "must understand" flag on the SOAP message, then you will get an error message.
You might also find it useful to enable trace for all gateway components: Set the WAS trace string to com.ibm.wsgw.*=all=enabled , and have trace, stdout and stderr for the appserver written to a well-known location. For information on how to do this, see Enabling trace.
Web services gateway - Completing the installation
Establishing requirements for using a database with the gateway
Installing the gateway into a deployment manager cell
Installing the gateway into a stand-alone appserver
Test the Web services gateway installation
Web services gateway troubleshooting tips