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

 

+
Search Tips   |   Advanced Search

 

IBM WebSphere Portal provides a customized installation package (CIP) that includes IBM WAS Network Deployment and all required maintenance packages. Use the discs supplied with WebSphere Portal to install WAS Network Deployment on a dedicated machine.

Limitation for Windows: 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:

• Use a short installation path. For example, use C:\WebSphere instead of C:\Program Files\IBM \WebSphere.

• Specify short cell and node names. For example, you might use sm01cell instead of stonemillNode01cell.

 

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 is the root directory of the disc

   • architecture is the processor architecture of the machine

   • operating_system is the 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 to exploit business process integration function, do not create a profile and instead wait to create the profile when you are installing WebSphere Process Server.

2. Use the Profile Creation wizard to create a default deployment manager profile.

   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.

   Refer to the WAS Network Deployment information center for details:

   Creating a deployment manager profile

3. Linux only: If the deployment manager is running on a Linux system, increase the number of files that can be open concurrently. Enter the following command before starting the deployment manager process:

       ulimit -n 10240
   

4. Ensure the deployment manager is operating properly.

   On the WAS Network Deployment node, start the deployment manager by running the startManager script.

   • Windows:

     was_profile_root\bin\startManager.bat

   • UNIX:

     was_profile_root/bin/startManager.sh

   After the deployment manager starts, launch the administrative console...

   http://dmgr_hostname:9060/ibm/console

   ...where dmgr_hostname is the fully qualified host.name of the WAS Network Deployment node.

Security note: If you plan to add a secured WebSphere Portal node to the deployment manager cell, manually configure the deployment manager security settings to match the node security before adding the node to the cell. Refer to the Securing applications and their environment topic in the information center for details on how to configure security for WAS Network Deployment.

 

Parent Topic

Install WAS Network Deployment on the deployment manager machine

 

---