Web services gateway: Post-install

 

Web services gateway bundled with the WAS Network Deployment, and is installed during a "typical install". Web services gateway files are copied into directories under:

/opt/WebSphere/DeploymentManager"

Here are the relevant files:

File name Purpose Location
wsgw.ear The Web services gateway application /installableApps
wsgwsoap1.ear The Apache SOAP channel application number 1 /installableApps
wsgwsoap2.ear The Apache SOAP channel application number 2 /installableApps
wsgwsoaphttp1.ear The SOAP/HTTP channel application number 1 /installableApps
wsgwsoaphttp2.ear The SOAP/HTTP channel application number 2 /installableApps
wsgwcorr.ear The application used to correlate any asynchronous reply messages /installableApps
wsgwauth.ear The Web service operation-level security application /installableApps
WSGWResourceBundles.jar System messages for the Web services gateway application /lib
Various install 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
Cloudscape directory tree Cloudscape database containing the Web services gateway tables and pre-loaded data needed to install a database to use with the gateway /bin/WSGWDB


If you want to run a gateway cluster (for example to guarantee high availability) create the cluster before you install the gateway on any machine in the cluster.

To complete the gateway installation, you have two choices:

For production use you will probably want to install the gateway into one or more nodes of a deployment manager cell. But for development or test purposes you might find it useful to install the gateway into a stand-alone appserver (that is, an application server that is not part of a deployment manager cell).

 

What to do next

To finish the Web services gateway installation, complete the following steps:

  1. Confirm that your system configuration complies with the Web services gateway prerequisites and constraints.

  2. Establish requirements for using a database with the gateway.

  3. Enable security if required.

  4. Either Install the gateway into a deployment manager cell, or Install the gateway into a stand-alone appserver.

  5. Test the installation.


Web services gateway: Enabling Web services
Web services gateway - prerequisites and constraints

 

IBM is a trademark of the IBM Corporation in the United States, other countries, or both.