+

Search Tips   |   Advanced Search

Additional node - Install portal

Author: Michael Pareene


Overview

This section covers adding the additional node to the Deployment Manager cell and adding a new WebSphere_Portal server as a horizontal dynamic cluster member to the previously created dynamic cluster. Once this section is completed, you will have a functional two-node horizontal dynamic cluster using the federated LDAP security.

  1. Install Installation Manager

  2. Add WAS v8.5.5 and WAS FP1 to Installation Manager repository...

    1. Run...

        cd /opt/IBM/InstallationManager/eclipse/tools
        ./imcl -c

      ...select...

        P. Preferences | 1. Repositories | D. Add Repository

    2. Set...

        /opt/IBM/Portal/media/WAS855/repository.config

    3. Add repository for WAS 8.5.5 FP 1

        /opt/IBM/Portal/media/WAS855_FP1/repository.config

    4. Select "Search service repositories during installation and updates" to remove the check mark.
      =====> IBM Installation Manager> Preferences> Repositories
      
      Repositories:
           1. [X] /opt/IBM/Portal/media/WAS855/repository.config
      
      Other Options:
           D. Add Repository
      
           S. [ ] Search service repositories during installation and updates
      
           R. Restore Defaults
           A. Apply Changes and Return to Preferences Menu
           P. Temporarily Keep Changes and Return to Preferences Menu
      

  3. Install WAS v8.5.5 binaries

    1. Start Installation Manager GUI...

        cd /opt/IBM/InstallationManager/eclipse
        ./IBMIM

    2. Select Install, then select Continue in pop-up panel.

    3. On the Install Packages screen, select...

        Create a new package group

      ...and for Installation Directory select...

        /opt/IBM/Portal/WAS1/AppServer

    4. Select defaults for remainder of panels, then on summary page, select Install

    5. On last screen, select None, then Finish

  4. Install Fixes

    1. Add repository for WAS 8.5.5 FP 1

        /opt/IBM/Portal/media/WAS855_FP1/repository.config

      MyCo has WCM license, which is different from WCM Standard Edition (fewer entitlements). We install...

        8.0.0-WP-Server-FP001
        8.0.0-WP-WCM-FP001

      Uncheck: "Search service repositories during installation and updates"

    2. On the main IIM page, select Update

    3. On the "Select a package group to find updates for", select first package group

    4. On the panel, "Select updates to install", verify V8.5.5.1 is selected

    5. On the panel, "Select the features to install", keep defaults, then select Next

    6. On the Summary panel, select Update

  5. Install Portal v8.0

    1. Add repository...

        /opt/IBM/Portal/media/Portal8/Setup/eimage/repository.config

    2. On Install Packages panel, select IBM WebSphere Portal Server

    3. Select "Create a new package group" and set Installation Directory to...

        /opt/IBM/Portal/WAS1/PortalServer

    4. For features, select only...

      • Config Engine
      • Portal Server Binary

    5. On the next screen, select "Existing WebSphere Application Server Root Directory"

        /opt/IBM/Portal/WAS1/AppServer

    6. On the Summary page, click install...

    7. Once the installation completes, click the radio button for None and click Finish to exit the installer.

  6. Upgrade Portal v8 with FP1

    1. Review: Update Portal v8 with FP1

    2. Add FP1 to Installation Manager repository

        /opt/IBM/Portal/media/Portal8_FP1/repository.config

    3. From Installation Manager select "Update"

    4. If you have more than one fix in your repository, it will try to install them all. To install just FP1, de-select "Show recommended only", then select only "v8.0.0.1"

    5. Ignore warnings about needing to update wps.properties. Unlike primary node, we did a binary only install of portal on this host, so don't need to update wps.properties

    6. After upgrade finishes, make tarball backup

  7. Upgrade Portal v8 with CF09

    1. Download CF09

    2. Add CF09 to Installation Manager repository

    3. Change class loader from parent first to parent last.

    4. Stop all WebSphere processes

    5. Because no profile has been created yet, we do not need to update wps.properties to include profile name and location

    6. Add CF09 to repository

    7. Use Installation Manager to install

      To install manually..

      1. Determine offering ID...

          $ cd /opt/IBM/InstallationManager/eclipse/tools
          $ ./imcl listAvailablePackages -repositories /opt/IBM/Portal/media/CF09/repository.config
          com.ibm.websphere.PORTAL.SERVER.v80_8.0.1.20131217_0755

      2. Install
        ./imcl install \
               com.ibm.websphere.PORTAL.SERVER.v80_8.0.1.20131217_0755 \
               -repositories /opt/IBM/Portal/media/CF09/repository.config \
               -installationDirectory /opt/IBM/Portal/WAS1/PortalServer \
               -sharedResourcesDirectory /opt/IBM/IMShared \
               -log /tmp/imcl.log  \
               -acceptLicense  
        

    8. Start Portal

    9. Make tarball backup


  8. Create profiles on secondary nodes

    Do this step only after configuring the portal primary node with DB2 and LDAP

    1. From primary node, copy profileTemplates.zip to secondary nodes. For example...

        cd /opt/IBM/Portal/WAS1/PortalServer/profileTemplates
        scp profileTemplates.zip user1@prdhost2.myco.com:/tmp
        scp profileTemplates.zip user1@prdhost3.myco.com:/tmp
        scp profileTemplates.zip user1@prdhost4.myco.com:/tmp

    2. On target node, unzip profileTemplates.zip

        cd /opt/IBM/Portal/WAS1/PortalServer/profileTemplates
        mv /tmp/profileTemplates.zip .
        unzip profileTemplates.zip

    3. Update permissions...

        cd /opt/IBM/Portal/WAS1/PortalServer/
        find profileTemplates -name \* -exec chmod 755 {} \;

    4. Execute...

        cd /opt/IBM/Portal/WAS1/PortalServer/profileTemplates
        ./installPortalTemplates.sh /opt/IBM/Portal/WAS1/AppServer

    5. On each WebSphere Portal additional node...
      cd /opt/IBM/Portal/WAS1/AppServer/bin/ 
      ./manageprofiles.sh -create  \
                          -templatePath /opt/IBM/Portal/WAS1/PortalServer/profileTemplates/managed.portal  \
                          -profileName wp_profile  \
                          -profilePath /opt/IBM/Portal/WAS1/wp_profile \
                          -cellName P1Cell02 \
                          -nodeName P1Node02 \
                          -hostName prdhost2.myco.com
      
      cd /opt/IBM/Portal/WAS1/AppServer/bin/ 
      ./manageprofiles.sh -create  \
                          -templatePath /opt/IBM/Portal/WAS1/PortalServer/profileTemplates/managed.portal  \
                          -profileName wp_profile  \
                          -profilePath /opt/IBM/Portal/WAS1/wp_profile \
                          -cellName P1Cell03 \
                          -nodeName P1Node03 \
                          -hostName prdhost3.myco.com
      
      cd /opt/IBM/Portal/WAS1/AppServer/bin/ 
      ./manageprofiles.sh -create  \
                          -templatePath /opt/IBM/Portal/WAS1/PortalServer/profileTemplates/managed.portal  \
                          -profileName wp_profile  \
                          -profilePath /opt/IBM/Portal/WAS1/wp_profile \
                          -cellName P1Cell04 \
                          -nodeName P1Node04 \
                          -hostName prdhost4.myco.com
      
      ...etc...
      

      Do NOT use the same node name as your primary node or any other node that may already be part of the DMGR cell. You will be unable to add this node to the DMGR cell if the node names are identical. Do NOT use the same cell name as the DMGR cell. Do NOT use the manageprofiles option to Federate the profile now. This results in an unusable Portal profile. A WebSphere_Portal server will NOT be created during the profile creation. The WebSphere_Portal server will be created after the node is added to the existing cluster.

    6. After creating the profile, edit...

        /opt/IBM/Portal/WAS1/PortalServer/wps.properties

      ...and verify the following is set...

        ProfileName=wp_profile
        ProfileDirectory=/opt/IBM/Portal/WAS1/wp_profile

  9. Copy and configure DB2 client jars

    1. From primary node...

        cd /opt/IBM/Portal/WAS1/PortalServer
        scp -r db2drivers user1@prdhost2.myco.com:/tmp
        scp -r db2drivers user1@prdhost3.myco.com:/tmp
        scp -r db2drivers user1@prdhost4.myco.com:/tmp

      From secondary node

        cd /opt/IBM/Portal/WAS1/PortalServer
        cp -r /tmp/db2drivers .

    2. Edit...

        /opt/IBM/Portal/WAS1/wp_profile/ConfigEngine/properties/wkplc_dbtype.properties

      ...and set...

        db2.DbLibrary=/opt/IBM/Portal/WAS1/PortalServer/db2drivers/db2jcc4.jar:/opt/IBM/Portal/WAS1/PortalServer/db2drivers/db2jcc_license_cu.jar

  10. On remote dmgr host, ensure the Deployment Manager is started...

      cd /opt/IBM/Portal/WebSphere/AppServer/profiles/Dmgr01/bin
      ./startManager.sh

  11. Ensure that the time on the Deployment Manager server and the time on the additional Portal node server are no more than 5 minutes apart.

  12. Create backup of all nodes and dmgr

  13. Log on to each secondary host in turn, and add the node...

      cd /opt/IBM/Portal/WAS1/wp_profile/bin
      ./addNode.sh prd2dmgr.myco.com 9879 -username wasadmin -password mypassword**

    Example output...

      ADMU0003I: Node P1Node02 has been successfully federated.

  14. Edit...

      /opt/IBM/Portal/WAS1/wp_profile/ConfigEngine/properties/wkplc.properties

    ...and set...

      WasUserid=uid=wasadmin,cn=users,ou=admins,dc=myco,dc=com
      WasPassword=mypassword**
      PortalAdminId=uid=wpsadmin,cn=users,ou=admins,dc=myco,dc=com
      PortalAdminPwd=mypassword**
      PortalAdminGroupId=cn=wpsadmins,cn=groups,ou=admins,dc=myco,dc=com
      WasRemoteHostName=prd2dmgr.myco.com
      WasSOAPPort=9879
      PrimaryNode=false
      ClusterName=P1Cluster

  15. Edit...

      /opt/IBM/Portal/WAS1/wp_profile/ConfigEngine/properties/wkplc_dbdomain.properties

    ...and ensure that the database password values are all set correctly.

    Note that this file should be pre-populated with your database information from running the 'enable-profiles' script on the primary node earlier.

  16. Review settings in...

      /opt/IBM/Portal/WAS1/wp_profile/ConfigEngine/properties/wkplc_dbtype.properties

  17. Confirm the database properties are set up correctly on this node

      cd /opt/IBM/Portal/WAS1/wp_profile/ConfigEngine
      ./ConfigEngine.sh validate-database -DWasPassword=mypassword**

    Example output:

      Wed Feb 26 15:24:28 EST 2014
      BUILD SUCCESSFUL

  18. Edit...

      /opt/IBM/Portal/WAS1/wp_profile/PortalServer/jcr/lib/com/ibm/icm/icm.properties

    ...and set...

      jcr.textsearch.enabled = false

  19. In the same file, set...

      jcr.admin.uniqueName=uid=wpsadmin,cn=users,ou=admins,dc=myco,dc=com

  20. Start the nodeagent

      cd /opt/IBM/Portal/WAS1/wp_profile/bin
      ./startNode.sh

  21. Add node to cluster

      ./ConfigEngine.sh cluster-node-config-cluster-setup-additional -DWasPassword=mypassword**

  22. Execute appserver specific steps for setting up the following...

  23. Restart appserver and verify no errors in logs

  24. Verify we can access the new cluster member in a web browser using the port we identified earlier:


MemberNotFound Issue

Secondary portal site not rendering. Error in log...

We do not want to re-add file registry because that would break short name logon.

Startup errors...

Fix: Edit...

...and set...

...then restart appserver