WebSphere

 

Portal Express, Version 6.0
Operating systems: i5/OS, Linux, Windows

 

Install WebSphere Portal Express on a managed node (secondary)

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

i5/OS users: WebSphere Portal Express 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 Express and then federate the node: Installing WebSphere Portal Express 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 Express on a node that has already been federated into a cell and then later remove that node from the cell, WebSphere Portal Express will not be usable on the resulting stand-alone server.

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

  2. Install WebSphere Application Server Network Deployment with the customized installation package (CIP) provided with WebSphere Portal Express. You can install on a machine without WebSphere Application Server Network Deployment or use the CIP to upgrade an existing installation.Locate the disc for WebSphere Application Server Network Deployment for your operating system and install WebSphere Application Server Network Deployment by invoking the appropriate install command based on platform:

    • Windows:

      cd_root\windows\ia32\ifpackage\WAS\install.exe

    • Linux:

      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 your operating system name

  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 Express. 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. 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

    After changing the timeout request period on the custom profile, edit the soap.client.props file for the deployment manager profile in the was_profile_root/properties directory:

    Change the line to: com.ibm.SOAP.requestTimeout=6000

  5. Install WebSphere Portal Express on the managed node. Run the following command from either the PortalExpress directory of the Setup CD or from the PortalExpress directory where you downloaded the product code:

    • Windows:

      install.bat -W startPortalServerSequence.active=false

    • Linux:

      ./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 you 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 WebSphere Application Server Network Deployment where you 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 Express 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 Express is operational after installation. Because you installed as a secondary node without any enterprise applications or portlets, the WebSphere Portal Express instance on the secondary node will not be operational until it is added to the cluster.

  6. Windows and Linux only: Update the database settings for the node in preparation for transferring the database from the default 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 you 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 Express 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 Express for information on properties that are pertinent for database configuration.Tip: To simplify this process, you 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.

  7. After installing a secondary node portal in the managed profile, the profile must also be prepared to support the BPEL-based business processes, which are deployed as EAR files to the business process container, and especially to support the connection to the database used for the container. Access the Administrative Console and set the path to the database drivers by selecting the WebSphere Application Server variables and then specifying the scope to be the secondary node. Look for the needed variables in the path statements in the JDBC providers defined in the cluster scope of the portal cluster. If there are multiple JDBC providers defined, select the one which holds the datasource with the JNDI name jdbc/BPEDB.

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

    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 Express 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 Express 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 Express 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 Express is installed; for example, wp_profile.

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

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

    • If LDAP security is already enabled in the cluster, enable security on the secondary node with the enable-jcr-security configuration task. Before running the following configuration task, ensure that the wpconfig.properties file on the secondary node contains the same LDAP user registry information you used to configure the primary node.

      • Windows and Linux:

        Run the following command from the portal_server_root/config directory:

        • Windows:

          WPSconfig.bat enable-jcr-security -DPortalAdminId=portal_admin_id

        • Linux:

          ./WPSconfig.sh enable-jcr-security -DPortalAdminId=portal_admin_id

        where portal_admin_id is the fully qualified distinguished name (DN) of the portal administrator (for example, uid=wpsadmin,cn=users,dc=example,dc=com).

      • i5/OS:

        Run the following command from the portal_server_root_user/config directory: 

        WPSconfig.sh -profileName profile_root enable-jcr-security -DPortalAdminId=portal_admin_id
        where

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

        • portal_admin_id is the fully qualified distinguished name (DN) of the portal administrator (for example, uid=wpsadmin,cn=users,dc=example,dc=com

      The configuration task enable-jcr-security will fail if there is a space in the LDAP user's fully qualified distinguished name (DN). For more information refer to the detailed notes on using properties .

    • If you intend to use an LDAP user registry for security but have not yet performed that configuration, refer to Enabling LDAP security after cluster creation.

 

Parent topic:

Installing and federating secondary nodes