Installing the gateway into an application server that is part of a deployment manager cell

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.

[Version 5.0.2 and later]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

  1. Start the application server.
  2. Clear your class path.
    You can use the following command:
    • (Windows systems): set CLASSPATH=
    • (UNIX and Linux systems): unset CLASSPATH
  3. Navigate to the WebSphere_DeployMgr_root/WSGW/scripts/install directory.
  4. Enter the command: WebSphere_DeployMgr_root/bin/wsadmin.ext -f setupWSGW.jacl parm1 ... parmN
    where:
    • parm1 is the WebSphere_DeployMgr_root directory
    • parm2 is the server name
    • parm3 is the node name (this is case sensitive)

    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

    After you run the setupWSGW.jacl command, system messages are displayed confirming that the following initial set of gateway applications have installed successfully:
    • The gateway (wsgw.ear).
    • Apache SOAP channel 1 (wsgwsoap1.ear).
    • [Version 5.0.2 and later]SOAP over HTTP channel 1 (wsgwsoaphttp1.ear).
  5. Install additional gateway applications. For example:
    • Apache SOAP channel 2 (wsgwsoap2.ear)
    • [Version 5.0.2 and later]SOAP over HTTP channel 2 (wsgwsoaphttp2.ear)

    To install additional gateway applications, complete the following steps:

    Note:

    1. Navigate to the WebSphere_DeployMgr_root/bin directory.
    2. Start the application server.
    3. Start the WebSphere administration program (by entering the command wsadmin.ext).
    4. For each additional Web services gateway enterprise application that you install, enter the following commands at the wsadmin> prompt:
      $AdminApp install path_to_ear_file {-appname application 
              -server your_server -node your_node_name}
      $AdminConfig save

      where:

      • application is the name of the enterprise application
      • path_to_ear_file is the name and location of the enterprise application EAR file
      • your_node_name is the node name (this value is case sensitive)

      For example (Windows systems):

      $AdminApp install 
          C:/Progra~1/WebSphere/DeploymentManager/installableApps/wsgwsoap2.ear 
          {-appname wsgwsoap2 -server server1 -node PHJ2}
      $AdminConfig save

    5. After you install all your additional Web services gateway enterprise applications, close the WebSphere administration program by entering quit or exit at the wsadmin> prompt.
  6. Stop then restart the application server.

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.


Related tasks
Web services gateway - Completing the installation
Installing the gateway into a stand-alone application server
Testing the Web services gateway installation
Troubleshooting the Web services gateway
Related reference
Web services gateway - prerequisites and constraints



Searchable topic ID:   twsg_install_nd
Last updated: Jun 21, 2007 4:55:42 PM CDT    WebSphere Application Server Network Deployment, Version 5.0.2
http://publib.boulder.ibm.com/infocenter/wasinfo/index.jsp?topic=/com.ibm.websphere.nd.doc/info/ae/ae/twsg_install_nd.html

Library | Support | Terms of Use | Feedback