Install WebSphere Portal on AIX on the additional cluster nodes


Overview

Install WebSphere Portal on additional cluster nodes to create a highly available and scalable environment.


Prerequisites

  1. Installation methods, options, and sources
  2. WebSphere Portal detailed system requirements


Install WebSphere Portal

  1. Verify the fully qualified host name is configured...

      ping myserver.myco.com

  2. If you are installing with an existing WAS instance, ensure it is installed at the supported level and has the following features installed:

    • Application Server
    • Administration
      • Scripted Administration
      • Administrative Console
    • Ant and Deployment Tools
      • Deploy Tool
      • Ant Utilities

    WAS installations that have an existing WebSphere Portal v7.0 profile or that do not meet the correct software versions will not be included in the list of available, existing WAS instances.

    Besides ensuring that the existing WAS instance is at the supported level, verify that Apache Derby is installed at the supported level before installing WebSphere Portal.

  3. Optional. If you want to install WebSphere Portal using a non-root user:

    Although it is possible to install WAS as a non-root user, there are limitations to this option that can affect WebSphere Portal functionality, which is why you should install WAS as a root user.

    1. Install the current supported version of WAS as a root user.

    2. Create a non-root user and change ownership:

      1. Use the appropriate system commands to create a new group, to create a new user, and to add the new user to the new group.

      2. Run the following tasks to change the rights of the non-root user: 

          chmod -R g+rwx /opt/IBM
chgrp -R group_name /opt/IBM
chmod -R g+wr /tmp
chgrp -R group_name /tmp
chmod -R g+wr /var/tmp
chgrp -R group_name /var/tmp

      3. If you are also installing WAS as a non-root user, choose one of the following additional tasks based on the type of OS that you have:

        OS Additional task
        32-bit OS chmod -R g+rwx /OS_code-Setup
        chgrp -R group_name /OS_code-Setup
        64-bit OS chmod -R g+rwx /OS_code-Setup
        chgrp -R group_name /OS_code-Setup

        Enter the appropriate OS code letter, based on whether you have a 32-bit or 64-bit OS, where you see OS_code in the additional task:

        • AIX(32-bit and 64-bit) = A
        • Intel Linux (32-bit and 64-bit) = IL
        • PowerPC Linux (32-bit and 64-bit) = PL
        • zLinux (64-bit) = ZL
        • Solaris (32-bit and 64-bit) = SS
        • Solaris (64-bit) = SO

    3. Launch the installation program per the next step. During the installation, select the existing WAS using the non-root user and set the installation location to a unique location under the path where non-root permissions were granted.

  4. Choose one of the following installation commands:

    Type Task
    GUI ./install.sh -W defaults.isBinaryInstall=true
    Console mode ./install.sh -console -W defaults.isBinaryInstall=true
    Silent install ./install.sh -options "/path/to/installresponse.txt"

    Set the defaults.isBinaryInstall parameter to true in the response file.

    Do not place the response file in a path that contains a space and do not put a space in the file name.

After the installation of the additional cluster node, no application server exists because the defaults.isBinaryInstall parameter was set to true. The application server will be added when the new cluster member is created.


Parent

Prepare additional nodes on AIX


Next topic

Choose the type of additional node to create on AIX


Related

Data collection and symptom analysis
Create multiple profiles on AIX
Advanced installation parameters

 


+

Search Tips   |   Advanced Search