+

Search Tips   |   Advanced Search


Install WebSphere Portal on Windows 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 yourserver.yourcompany.com 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. If you are installing on a server with a firewall enabled, disable the firewall before installing. If you do not disable the firewall and the installation program detects it, a warning message displays during the installation.

  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 install.bat
    Console mode install.bat -console
    Silent install install.bat -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.

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

      ConfigEngine.bat list-server-ports -DWasPassword=password

    ...from the profile_root/ConfigEngine directory to generate the profile_root/ConfigEngine\log\wp_PortMatrix.txt file that lists the 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 ConfigEngine.bat modify-ports-by-startport -DWasPassword=password -DModifyPortsServer=servername -DStartPort=starting port number
      Port file

      Sample port files are available on the Setup disc.

      		ConfigEngine.bat 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: 

      BOOTSTRAP_ADDRESS=10031 SOAP_CONNECTOR_ADDRESS=10033 SAS_SSL_SERVERAUTH_LISTENER_ADDRESS=10032 CSIV2_SSL_SERVERAUTH_LISTENER_ADDRESS=10025 CSIV2_SSL_MUTUALAUTH_LISTENER_ADDRESS=10036 WC_adminhost=10027 WC_defaulthost=33344 DCS_UNICAST_ADDRESS=10029 WC_adminhost_secure=10039 WC_defaulthost_secure=10035 SIB_ENDPOINT_ADDRESS=10026 SIB_ENDPOINT_SECURE_ADDRESS=10037 SIB_MQ_ENDPOINT_ADDRESS=10030 SIB_MQ_ENDPOINT_SECURE_ADDRESS=10028 ORB_LISTENER_ADDRESS=10034

    3. Restart the server1 and WebSphere_Portal servers.

  7. 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 LpidToGupidMapping.properties file.

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


Parent topic:

Prepare additional nodes on Windows


Related concepts


Installation methods
IBM Support Assistant Lite for WebSphere Portal


Related reference


Advanced installation parameters