Use this task to install the gateway into an application server that is part of a node of an existing deployment manager cell.
Before you begin
This topic assumes that you have completed the pre-installation steps described in Completing the installation and that the gateway application files are therefore available in directories under WebSphere_DeployMgr_root, where WebSphere_DeployMgr_root is the deployment manager root directory (by default WebSphere/DeploymentManager). This topic also assumes that you have already created or selected an application server that is part of a node in a deployment manager cell, and that this application server is not also part of a cluster.
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
To install the gateway into an application server that is part of a node in a deployment manager cell, complete the following steps:
Steps for this task
For example (Windows systems):
C:\Progra~1\WebSphere\DeploymentManager\bin\wsadmin.bat -f setupWSGW.jacl C:/Progra~1/WebSphere/DeploymentManager server1 PHJ2
Note: The use of forward slashes (/) is compulsory for this command, even on Windows systems.
Tip: If you create a symbolic link to the wsadmin.sh file, then you need not type the directory path to the wsadmin.sh file in the previous command. To create this symbolic link, issue the following command from within the WebSphere_DeployMgr_root/WSGW/scripts/install directory:
ln -s /bin/wsadmin.sh wsadmin.sh
To install additional gateway applications, complete the following steps:
Note:
$AdminApp install path_to_ear_file {-appname application -server your_server -node your_node_name} $AdminConfig save
where:
For example (Windows systems):
$AdminApp install C:/Progra~1/WebSphere/DeploymentManager/installableApps/wsgwsoap2.ear {-appname wsgwsoap2 -server server1 -node PHJ2} $AdminConfig save
What to do next
If you want more than one gateway installation (for example, to scale the Web services gateway), repeat the steps in this topic for another application server that is part of a node in a deployment manager cell.
You are now ready to test the installation. Run the test on every application server on which you installed the gateway.