Install WebSphere Portal on Solaris on the additional nodes

Install WebSphere Portal on your secondary nodes to create a highly available and scalable environment. Review the Supported hardware and software requirements for your operating system and ensure that all hardware and software matches the minimum product level before installing WebSphere Portal. Review Installation methods, options, and sources before installing to determine your installation source location and installation method.

If you plan to use IBM WAS v7.0, purchase and install it before installing WebSphere Portal on the existing WAS v7.0 instance.

To install WebSphere Portal:

  1. Type ping on a command line to verify that your fully qualified host name is properly configured.

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

    Besides ensuring that the existing WAS instance is at the supported level, you will also need to ensure that Apache Derby is installed at the supported level before installing WebSphere Portal. See WebSphere Portal detailed system requirements for supported levels.

    • Application Server

    • Administration

      • Scripted Administration

      • Administrative Console

    • Ant and Deployment Tools

      • Deploy Tool

      • Ant Utilities

  3. Optional: Perform the following steps if you want to install WebSphere Portal using a non-root user:

    Restriction: 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. Open a command prompt and perform the following steps to create a non-root user and to 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...


        s 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. 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 based on the installation method you want to use to install WebSphere Portal; see Installation Methods for more information: Advance installation parameters: To customize your installation, you can add various parameters to your installation commands; for example, you can specify your port information. See Advanced installation parameters.

    When defining your installation path, the ONLY supported characters are ASCII letters [A-Z and a-z], numbers [0-9], slashes [/ or \, depending on your operating system], and the dash [-].

    Option Description
    GUI ./
    Console mode ./ -console
    Silent install ./ -options "path_to_file/response_filename", where path_to_file is the full path to the response file and response_filename is the name of the file. A sample install response file (installresponse.txt) and a sample uninstall response file (uninstallresponse.txt) are located in the setup CD root directory.

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

    If you have a Solaris 9 on Sun SPARC, you MUST either add the -W defaults.force32bit=true parameter to your installation command or install the 32-bit WAS product before installing WebSphere Portal to prevent the installer from automatically selecting a 64-bit environment.

  5. Verify your installation was successful; access WebSphere Portal using the http://yourserver:yourport/wps/portal format. Run...

      ./ list-server-ports -DWasPassword=password


      profile_root/ConfigEngine generate the profile_root/ConfigEngine/log/wp_PortMatrix.txt file that lists WebSphere Portal ports for your installation.

  6. Optional: Perform the following steps if change the ports for WAS or WebSphere Portal:

    1. Stop the server1 and WebSphere_Portal servers.

    2. Run one of the following commands for each server change:

      Method Task
      Starting port number ./ modify-ports-by-startport -DWasPassword=password -DModifyPortsServer=servername -DStartPort=starting port number
      Port file

      Sample port files are available on the Setup disc.

      ./ modify-ports-by-portsfile -DWasPassword=password -DModifyPortsServer=servername -DPortsFile=full path to ports fileThe following is an example of the information within a port file although the port values will be different based on your environment:


    3. Restart the server1 and WebSphere_Portal servers.

  7. To prevent Out of Memory errors, perform the following steps to set the MaxPermSize: Tip: If Maximum Heap Size is set to 2048 M or higher, set the MaxPermSize to a quarter of the value entered for the Maximum Heap Size; for example, if your Maximum Heap Size is 3000 M, set MaxPermSize to 7.0 M. If your Maximum Heap Size is less than 2048 M, set MaxPermSize to 512 M.

    1. Log in to the WAS Administration Console.

    2. Click Servers > Server Types > WebSphere appservers > WebSphere_Portal.

    3. Under Server Infrastructure, click Java and Process Management > Process Definitions > Additional Properties > Java Virtual Machine.

    4. In the Generic JVM arguments field, change the MaxPermSize value to -XX:MaxPermSize=numeric value, where numeric value is a quarter of the value entered for the Maximum Heap Size.

      If MaxPermSize does not exist in the Generic JVM arguments field, add it to the field but do not replace existing information in the Generic JVM arguments field with the MaxPermSize information.

    5. Click OK to save your changes.

    6. Click Save to save your changes to the master configuration.

    7. Log out of the WAS Administration Console.

    8. Restart the server1 and WebSphere_Portal servers.

  8. Perform the following steps if you migrated from a previous version of WebSphere Portal:

    1. Log on to the admin console.

    2. Navigate to Resources > Resource Environment > Resource Environment Providers.

    3. Click WP Identification.

    4. Click Custom properties.

    5. If applicable, note the location of the file.

    6. If the file exists on the primary node, copy the file to the same location on the secondary node.

Parent topic:

Prepare additional nodes on Solaris

Related concepts

Installation methods
IBM Support Assistant Lite for WebSphere Portal

Related reference

Advanced installation parameters