WebSphere Application Server Network Deployment is not a stand-alone
product for running enterprise applications. If you want to deploy the gateway
you also need to install the base WebSphere Application Server product. Although
it is not installed by default, a copy of the base WebSphere Application Server
product is packaged with WebSphere Application Server Network Deployment.
The
gateway is not fully integrated into the WebSphere Application Server Network
Deployment tooling:
When you install WebSphere
Application Server, or an upgrade or fix pack, the installation program does not install
the gateway. The installation program copies the gateway files into directories
within your application server directory structure, then you install the gateway
into your application server as a separate task.
- You cannot use the full power of the deployment manager tooling to automatically
install or update a set of gateways across all application servers in a cell.
- You cannot install the gateway into an application server that is part
of a WebSphere Application Server Network Deployment cluster.
For more information about these restrictions, see
Completing the installation.
If you want to enable gateway-level security,
you must do so before you install the gateway.
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 Troubleshooting the Web services gateway.
- Install the gateway application (wsgw.ear) before you install
channel and filter applications. If you need to reinstall the gateway application,
uninstall all channels and filters first, then reinstall them after the gateway
application.
The gateway does not support WSDL service definitions
that contain <soap:header> elements within the <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 behavior is correct . However, you also see
the following effects:
- The SOAP headers are not included in the WSDL that the gateway generates.
- If you set the "must understand" flag on the SOAP message, then you
get an error message.
![[5.0 only]](../../v50.gif)
The SOAP message format
must be Remote Procedure Call (RPC) style. The gateway does not support Document
style SOAP messages.
The Apache SOAP channel is deprecated and wholly
superseded by the SOAP over HTTP channel.
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 over HTTP channel, which supports both RPC style and
Document style SOAP messages.
You might also find it useful to enable trace for all gateway components:
- Set the WebSphere Application Server trace string to com.ibm.wsgw.*=all=enabled
- Write trace, stdout and stderr for the application server to a well-known
location.
For more information, see
Enabling trace.