WebSphere

 

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

 

Install WebSphere Portal Express on a managed node (primary)

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

i5/OS users: Installation of WebSphere Portal Express 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 the portal and then federate the node: Installing WebSphere Portal Express on an unmanaged node (primary).

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 standalone server.

  1. Update the deployment manager machine 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 deployment manager machine:

    • wmm.jar

    • wmm.ejb.jar

    • wp.wire.jar

    If this is the first node you have installed in the cell, proceed to the next step and continue with the primary node installation. If you have already installed other managed nodes in the cell, also copy these JAR files to the app_server_root/lib directory on each node, regardless of whether you intend to install WebSphere Portal Express on the node.

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

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

  4. Add the node to the deployment manager cell by entering the addNode command. Ensure that you include the -includeapps parameter. Refer to addNode command for command syntax and other information.

  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

    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

  6. Change the timeout request period for the Java Management Extensions (JMX) connector.

    1. Log in to the administrative console for the deployment manager.

    2. Click System administration > Deployment Manager > Administration Services > JMX connectors > SOAPConnector > Custom Properties.

    3. Select the requestTimeout property, and increase the value from 600 to 6000.

    4. Save your configuration changes.

  7. Restart the deployment manager.

  8. Disable automatic synchronization between this node and the deployment manager.

    1. Log in to the administrative console for the deployment manager.

    2. Click System Administration > Node Agents > node > File Synchronization Service.

    3. Ensure that the Automatic Synchronization check box is not selected.

    4. Save your changes and synchronize with the node.

    5. Restart the node agent.

  9. Install WebSphere Portal Express on the managed node. Run the following command from the PortalExpress directory of the Quick Start Setup CD (if you are using the disc) or image (if you are using downloaded product code):

    • Windows:

      install.bat

    • Linux:

      ./install.sh

    • i5/OS:

      /QOPT/cd_root/PortalExpress/install.sh where cd_root is the root directory of the first WebSphere Portal Express Setup CD, for example WP-0.

    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 primary 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 Primary Node to indicate that this is the primary instance of WebSphere Portal Express in the cell. This will cause the installation program to update the deployment manager's master configuration with the server's enterprise applications.

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

    • Security is enabled during installation, and during installation, the security settings are applied to all nodes in the cell. Please ensure the node agents of other nodes in the cell are started before installing.

  10. Verify that WebSphere Portal Express is operational after installation.

  11. Optional: Re-enable automatic synchronization between this node and the deployment manager.

    1. Log in to the administrative console for the deployment manager.

    2. Click System Administration > Node Agents > node > File Synchronization Service.

    3. Select the Automatic Synchronization check box.

    4. Save your changes and synchronize with the node.

    5. Restart the node agent.

  12. Configure the node to use a remote database.

    i5/OS only: Depending on the scaling topology you are using with your cluster, you can choose to use different database configurations. Before continuing refer to the information in Setting up an i5/OS database in a cluster.

    1. Ensure that the remote database server is installed and operational.

    2. Transfer the database from the default database to another database.

    3. Verify that WebSphere Portal Express is operational with the new database configuration.

  13. Update the scheduler.ejb.reschedule property used by IBM Workplace Web Content Management™.

    1. Stop the portal application server.

    2. Edit the SchedulerService.properties file, according to your operating system.

    3. Set the value for the scheduler.ejb.reschedule property to true.

      If the scheduler.ejb.reschedule property is not present in the file, add the scheduler.ejb.reschedule=true property.

    4. Save your changes.

    5. Restart the portal application server.

    Make sure the node agent remains active to allow EAR expansion to complete.

  14. Once complete, the federated servers are visible in the deployment manager administrative console in the Servers > Application Servers view. Verify the operability of the WebSphere Portal Express profile.

  15. Disable the scheduler.ejb.reschedule property.

    1. Stop the portal application server.

    2. Edit the SchedulerService.properties file, according to your operating system.

    3. Set the value for the scheduler.ejb.reschedule property to false.

    4. Save your changes.

    5. Restart the portal application server.

 

Parent topic:

Installing and federating the primary node