Install WAS Network Deployment on Windows and UNIX (with WebSphere Process Server)

 

+
Search Tips   |   Advanced Search

 

Overview

IBM WebSphere Portal provides a customized installation package (CIP) that includes...

Use the discs supplied with WebSphere Portal to install...

...on a dedicated machine.

To install a deployment manager for use when WebSphere Portal is installed with WebSphere Process Server, install, in order...

  1. WAS Network Deployment
  2. WebSphere Process Server

...before creating a deployment manager profile.

 

Windows Notes

Note that there is a known limitation with many Windows operating systems that limits path names to a maximum length of 259 characters. This can be a potential problem due to the depth of the WAS Network Deployment directory structure, particularly when deploying applications in a cluster. To avoid problems related to excessively long paths names, consider the following recommendations when installing WAS Network Deployment:

 

Linux Notes

Use the ulimit command to increase the number of files that can be open concurrently. Enter the following command: 

    ulimit -n 10240

 

Procedure

  1. Install WAS Network Deployment with the CIP provided with WebSphere Portal.

    We can install on a machine without WAS Network Deployment or use the CIP to upgrade an existing installation.

    Locate the disc for WAS Network Deployment for the operating system and install WAS Network Deployment by invoking the appropriate install command based on platform:

    • Windows:

      cd_root\windows\ia32\ifpackage\WAS\install.exe

    • UNIX:

      cd_root/operating_system/architecture/ifpackage/WAS/install

    ...where:

    cd_root root directory of the disc
    architecture processor architecture of the machine
    operating_system operating system name

    During installation, you are asked whether you want to create a profile at that time. If you intend to install WebSphere Process Server do not create a profile and instead wait to create the profile when you are installing WebSphere Process Server.

  2. Upgrade the WAS Network Deployment installation on the node by installing WebSphere Process Server with the CIP provided with WebSphere Portal.

    Locate the disc for WebSphere Process Server for the operating system and install it by invoking the appropriate install command based on platform:

    • Windows:

      cd_root\windows\ia32\WBI\install.bat

    • UNIX:

      cd_root/operating_system/architecture/WBI/install.sh

    At the end of the installation, select...

    Launch the Profile Creation Wizard

    ...to create a default deployment manager profile.

    • Windows only: As with installation path names, you should use a short directory path when specifying the location of the profile you are creating. For example, instead of using the path...

      C:\Program Files\IBM \WebSphere\AppServer\profiles

      ...use...

      C:\IBM \AppServer\profiles

      Note that it is not necessary that the installation path for the application server be the same directory path used for storing profile information.

    • If you exit the installation wizard before launching the...

      Profile Creation Wizard for WebSphere Process Server

      ...launch the wizard from the command line.

      This is required because the First Steps console is not one of the components of WebSphere Process Server that is included in the installation for WebSphere Portal.

    • Create the profile with the wizard for WebSphere Process Server rather than the wizard for WAS Network Deployment.

      If you create a profile using the wizard for WAS Network Deployment, you will not be able to use the business process integration function on the managed node after you install WebSphere Portal.

 

Parent Topic

Installing WAS Network Deployment on the deployment manager machine