Use this task to install the gateway into an individual application server instance in your network space.
Before you begin
A stand-alone application server is an application server that is not part of a deployment manager cell. Before you install the gateway into a stand-alone application server, you should consider whether you might subsequently want to add the machine on which the application server is hosted as a node of a cell. If you do subsequently add the machine to a cell, then the installed gateway application will be deleted by the node synchronization process. You cannot install the gateway into a stand-alone application server that is 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.
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 ). Before you can install and run the gateway in a stand-alone application server, you must copy these files over to the application server by completing the following steps:
where stand-alone_install_root is the root directory for the installation of your target application server (by default WebSphere/AppServer).
Why and when to perform this task
To install the gateway into your stand-alone application server, complete the following steps:
Steps for this task
unset CLASSPATH
For example:
WebSphere/AppServer/bin/wsadmin.sh -f setupWSGW.jacl WebSphere/AppServer server1 PHJ2
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 (for example) the following command from within the WebSphere_DeployMgr_root/WSGW/scripts/install directory:
ln -s WebSphere/AppServer/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:
$AdminApp install WebSphere/AppServer/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 provided in this topic for another stand-alone application server.
You are now ready to test the installation. Run the test on every application server on which you installed the gateway.