Install WebSphere Portal on a managed node (secondary)

Install IBM WebSphere Portal on the secondary node. In this scenario, first install IBM WAS Network Deployment and IBM WebSphere Process Server, and then federate the secondary node to the deployment manager before installing WebSphere Portal on the managed node.

i5/OS users: WebSphere Portal installation is not supported on a federated node in an i5/OS environment. If you are building a cluster on i5/OS, use the instructions in the following section to install WebSphere Portal and then federate the node: Installing WebSphere Portal on an unmanaged node (secondary).

When you remove a node from a managed cell, the application server on that node reverts to the state it had at the time it was originally federated. Consequently, if you install WebSphere Portal on a node that has already been federated into a cell and then later remove that node from the cell, WebSphere Portal will not be usable on the resulting stand-alone server.

  1. Linux only: If we have not done so already, use the ulimit command to increase the number of files that can be open concurrently. Enter the following command: 

    ulimit -n 10240

  2. Install WAS Network Deployment with the customized installation package (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.

  3. Update the secondary node with required JAR files. These files are located on the Setup CD provided as part of the installation package for WebSphere Portal. Copy the following files from the dmgr_wmmjars directory on the Setup CD to the app_server_root/lib directory on the node:

    • wmm.jar

    • wmm.ejb.jar

    • wp.wire.jar

  4. Upgrade the WAS Network Deployment installation on the node by installing WebSphere Process Server with the customized installation package (CIP) provided with WebSphere Portal.

    Locate the disc for WebSphere Process Server for our 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 custom profile. Refer to the WebSphere Process Server information center for details:

    Creating a new WebSphere Process Server custom profile

    • Because security is already enabled in the managed cell, the Profile Creation Wizard cannot federate the custom node when you create a custom profile. Instead, choose to federate the profile later by using the addnode command with the appropriate security credentials. Do not include the -includeapps parameter. Refer to addNode command for command syntax and other information.

      • It is important not to use the -includeapps option. The applications will not be transferred as they are already in the deployment manager's master configuration.

      • Applications stored in the master configuration are still only assigned to the primary node. In order to share them with a secondary node, the node must be added to the cluster.

    • If you exit the installation wizard before launching the Profile Creation Wizard for WebSphere Process Server, follow the instructions in the above link to 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.

    • Ensure that you 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, we will not be able to use the business process integration function on the managed node after you install WebSphere Portal.

  5. Change the timeout request period for the Simple Object Access Protocol (SOAP) client. The default, in seconds, is 180. Edit the soap.client.props file for the custom profile in the was_profile_root/properties directory:

    Change the line to: 

    com.ibm.SOAP.requestTimeout=6000

  6. Install WebSphere Portal on the managed node.

    Execute from either the root directory of the Setup CD or from the directory where you downloaded the product code:

    • Windows:

      install.bat -W startPortalServerSequence.active=false

    • UNIX:

      ./install.sh -W startPortalServerSequence.active=false

    Installation notes:

    • The installation program detects that you are installing to a federated node and displays a panel that enables us to specify that this is the secondary node in the cell.

    • Enter the information requested by the installation program, including the following specific settings:

      • Select the Custom installation type.

      • When selecting the existing installation of WAS Network Deployment where we are installing, ensure that you also select the Install on a managed node check box.

      • Select Secondary Node to indicate that this is a secondary instance of WebSphere Portal in the cell. This will cause the installation program to install the server without any of its enterprise applications. After the node is added to the cluster, it will share the enterprise applications that were installed with the primary node.

      • Select the profile name for the managed node to which you want to install.

    Do not attempt to verify that WebSphere Portal is operational after installation. Because you installed as a secondary node without any enterprise applications or portlets, the WebSphere Portal instance on the secondary node will not be operational until it is added to the cluster.

  7. Windows and UNIX only: Update the database settings for the node in preparation for transferring the database from Cloudscape to the database being used by the primary node.

    These steps are preparatory to running the cluster-setup task. Although you are updating the properties files with the database information, actual connection to the database and creation of the datasources does not occur until you run the cluster-setup task, as instructed later in the installation process.

    1. Ensure that the database client software is installed on the secondary node using the same settings as the primary node and that we can connect to the remote database. It is not necessary to create databases or users when configuring secondary nodes.

      DB2 users: When using DB2, catalog the TCP/IP node and all databases used by WebSphere Portal on each secondary node. For more information, refer to Creating databases and users for DB2.

    2. The datasources for the secondary node must be made to point to the datasources for the primary node. Update the wpconfig_dbtype.properties and wpconfig_dbdomain.properties files to specify which remote database will be used. This information should match the database information used for the primary node installation. Refer to Configuring for WebSphere Portal for information on properties that are pertinent for database configuration.

      Tip: To simplify this process, we can make a backup copy of the wpconfig_dbdomain.properties file on the secondary node, and then copy the wpconfig_dbdomain.properties file from the primary node to the secondary node.

    3. Validate the database settings by running the following commands.

  8. i5/OS only: Specify database settings and complete the configuration of WebSphere Portal.

    1. Ensure that the following properties are uncommented.

      wpconfig.properties file:

      • PrimaryNode property: Because this node is a secondary node, set this property to false.

      • PortalAdminId property: specify the fully-qualified name of the WebSphere Portal administrator.

      wpconfig_dbtype.properties file:

      • DbSafeMode property: Set this property to true to prevent the database configuration from being changed.

      wpconfig_dbdomain.properties file:

      • domain.DbUser: Specify the administrator ID for the following domains in the WebSphere Portal database.

        • release

        • customization

        • community

        • wmm

        • jcr

        • feedback

        • likeminds

    2. Reconfigure the datasources for the secondary node to point to the datasources for the primary node. Update the wpconfig_dbtype.properties and wpconfig_dbdomain.properties files to specify which remote database will be used. This information should match the database information used for the primary node installation. Refer to Configuring for WebSphere Portal for information on properties that are pertinent for database configuration.

      When specifying property values for the remote database on a secondary node, ensure that you replace instances of *LOCAL/schema with primary_node_hostname/schema, as described in Creating schemas and users for DB2.

    3. Validate the database settings by running the following commands.

      where profile_root is the name of the WebSphere Application Server profile where WebSphere Portal is installed; for example, wp_profile.

    4. Set the DbSafeMode property to false in wpconfig_dbtype.properties.

  9. Optional: If you intend to use business process integration function, update the configuration for the task list by completing the steps in the following topic: Change the connection settings for the Human Task Manager .

  10. If you are using an LDAP user registry to provide security for the cluster, update the security configuration on the node.

 

Parent Topic

Installing and federating secondary nodes