Before you begin
This task assumes that when you installed WebSphere Application Server Network Deployment you selected the Web services gateway either by accepting the "typical install" option, or by choosing the "custom install" option Web services > Web services gateway.
When you install WebSphere Application Server, or apply an upgrade or fix pack, the installation program does not install the gateway enterprise applications. When you run the installation program, and select the Web services gateway component, the files that are required for running the gateway are copied into directories under WebSphere_DeployMgr_root, where WebSphere_DeployMgr_root is the deployment manager root directory (by default WebSphere/DeploymentManager ). For example, if you install WebSphere Application Server and accept the default directory names, then the location of the installableApps directory is WebSphere/DeploymentManager/installableApps .
When you install the gateway into your application
server (by completing the steps described in this topic), any previously configured
gateway is replaced with an upgraded but empty gateway. If you want to preserve
an existing gateway configuration, you need to save the configuration before
you install the upgraded gateway, then restore the configuration after the
upgrade is installed. To save your gateway configuration before you complete
the installation of an upgraded gateway, see Preserving an existing gateway configuration.
Why and when to perform this task
The following table lists the gateway files, and the locations into which they are placed. The Location column shows the subdirectory under WebSphere_DeployMgr_root.
File name | Purpose | Location |
---|---|---|
wsgw.ear | The Web services gateway application | /installableApps |
wsgwsoap1.ear | The Apache SOAP channel 1 application | /installableApps |
wsgwsoap2.ear | The Apache SOAP channel 2 application | /installableApps |
wsgwsoaphttp1.ear | The SOAP over HTTP channel 1 application | /installableApps |
wsgwsoaphttp2.ear | The SOAP over HTTP channel 2 application | /installableApps |
wsgwauth.ear | The Web service operation-level security application | /installableApps |
WSGWResourceBundles.jar | System messages for the Web services gateway | /lib |
Installation scripts | Installation of the Web services gateway | /WSGW/scripts/install |
Authorization scripts | Generation of authorization beans for Web service operation-level security | /WSGW/scripts/auth |
To complete the gateway installation, you have two choices:
The gateway functions identically in either environment, but if you install the gateway into an application server that is part of a deployment manager cell, then you can use the deployment manager tooling for that cell to complete the gateway installation on any server within the cell, irrespective of where the server is physically hosted. Note however that the gateway is not fully integrated into the WebSphere Application Server Network Deployment tooling:
To achieve high availability and load
balancing, follow the steps described in Scaling
the Web services gateway. The gateways that you include in your load-balancing
group can be hosted on stand-alone application servers, or application servers
that are members of a deployment manager cell, or a mixture of the two.
To finish the Web services gateway installation, complete the following steps:
Steps for this task