Install WebSphere Portal on a managed node (primary)

 

+
Search Tips   |   Advanced Search

 

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

i5/OS users: Installation of WebSphere Portal 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 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 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 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. 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 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 following command: 

        ulimit -n 10240

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

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

    Locate the disc for WebSphere Process Server for the 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

    • By default, the Profile Creation wizard federates a custom node when you create a custom profile, so it is important that the deployment manager be running and available on the network when you are working with the wizard.

    • 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, you 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. 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 the 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 the changes and synchronize with the node.

    5. Restart the node agent.

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

    • UNIX:

      ./install.sh

    • i5/OS:

      /QOPT/cd_root/install.sh where cd_root is the root directory of the first WebSphere Portal 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 us 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 WAS 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 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.

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

  11. Verify that WebSphere Portal is operational after installation.

  12. 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 the changes and synchronize with the node.

    5. Restart the node agent.

  13. Configure the node to use a remote database.

    1. i5/OS only: Depending on the scaling topology you are using with the cluster, we can choose to use different database configurations. Refer to Setting up an i5/OS database in a cluster for more information before continuing.

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

    3. Transfer the database from IBM Cloudscape™ the default database to another database.

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

  14. Update the scheduler.ejb.reschedule property used by IWWCM ™.

    1. Stop the portal application server.

    2. Edit the SchedulerService.properties file, according to the 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 property: 

          scheduler.ejb.reschedule=true

    4. Save the changes.

    5. Restart the portal application server.

  15. 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 instance.

  16. Disable the scheduler.ejb.reschedule property.

    1. Edit the SchedulerService.properties file, according to the operating system.

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

    3. Save the changes.

    4. Restart the portal application server.

 

Parent Topic

Installing and federating the primary node