Create a static cluster on AIX

 

+

Search Tips   |   Advanced Search

 

After...

  1. installing IBM WebSphere Portal on the primary node
  2. configuring a remote database
  3. preparing the primary node to communicate with the Deployment Manager

...you can create a static cluster to handle failover requests.

  1. If the Deployment Manager is configured to use a stand-alone LDAP user registry, on the primary node, update...

    WP_PROFILE/ConfigEngine/properties/wkplc.properties

    ...with the stand-alone LDAP user registry property values from the Deployment Manager.

    You can find these settings under the VMM Stand-alone LDAP configuration heading.

  2. Stop the server1 and WebSphere_Portal servers on the primary node

  3. Edit...

    WP_PROFILE/ConfigEngine/properties/wkplc.properties

    ...and set...

    WasSoapPort Port used to connect remotely to the WAS.
    WasRemoteHostName Full hostname of the server used to remotely connect to the WAS.

  4. On the primary node, Run...

    cd WP_PROFILE/ConfigEngine
    ./ConfigEngine.sh cluster-node-config-pre-federation

    Add the parameters...

    -DDMgrUserid=dmgrid -DDMgrPassword=dmgrpassword

    ...if the credentials the Deployment Manager cell uses are different from the local node you are adding to the Deployment Manager cell.

    If you specify the parameter...

      -DDMgrUserid

    when running...

    ...it resets the WasUserid parameter in wkplc.properties to the -DDMgrUserid value.

  5. Run the following task for EACH WebSphere Portal node that participates in the cluster to set up access to the database drivers. If multiple nodes share the same database library path you can submit a comma separated list of node names:

    1. Set the property value for federated.db.DbType if using a database user registry or if the cell is migrated from a previous version

      Set the property value for la.DbType if using a property extension database in wkplc.properties file.

    2. To create the variable used to access the VMM database jars. 

       cd WP_PROFILE/ConfigEngine
./ConfigEngine.sh wp-node-prep-vmm-db-secured-environment
                  -DWasPassword=wpsadmin 
                  -DDbDomain=la|federated.db 
                  -DVmmNodeName=node 
                  -Ddb_type.NodeDbLibrary/path/to/DB/jars

      Where DbDomain is either...

      • la
      • federated.db

      depending on whether you are using...

      VmmNodeName is a list of one or more WebSphere Portal nodes names in the cell which share the same database driver paths.

      The db_type in db_type.NodeDbLibrary should be set to the type of database you are using, for example db2.

      The local full path of the database jars should be one of the following options:

      DB2 Type 2 driver: db2java.zip
      DB2 Type 4 driver: db2jcc.jar;db2jcc_license_cu.jar
      DB2 for z/OS Type 2 driver: db2java.zip
      DB2 for z/OS Type 4 driver: db2jcc.jar;db2jcc_license_cisuz.jar;db2jcc_javax.jar
      Oracle: ojdbc14.jar

    3. Run...

      ./ConfigEngine.sh cluster-node-config-post-federation task

    4. Since the WebSphere Portal node is now using security settings from the Deployment Manager cell, you may need to update the WebSphere Portal administrative user ID and password to match an administrative user defined in the cell's user registry.

      Run...

      ./ConfigEngine.sh wp-change-portal-admin-user -DnewAdminId=newadminid –DnewAdminPw=newpassword -DnewAdminGroupId=newadmingroup

      ...from the...

      WP_PROFILE/ConfigEngine

      ...directory, to update the WebSphere Portal administrative user ID if the Deployment Manager cell is using a different user registry.

      This task verifies the user against a running LDAP server instance when LDAP security is enabled.

      If the LDAP server is stopped, add...

        -Dskip.ldap.validation=true

      ...to the task to skip the validation.

      If stand-alone LDAP security is already enabled on the Deployment Manager cell, delay running...

      wp-change-portal-admin-user

      ...until after...

        cluster-node-config-cluster-setup
      ...completes. After running...

        wp-change-portal-admin-user

      ...start or restart the WebSphere_Portal server to use the updated administrator user ID.

      The WebSphere Portal administrative user ID and administrative group must exist in the Deployment Manager before running the task...

      wp-change-portal-admin-user

      -DnewAdminPw is an optional parameter to update the Administrative password in wkplc.properties if required.

    5. Run...

      ./ConfigEngine.sh cluster-node-config-cluster-setup

    6. Configure the cluster to use an external Web server to take advantage of features such as workload management. Choose one of the following options:

      Start with the step about launching the Plug-ins installation wizard.

    7. To access the WCM content through an external Web server:

      1. Log on to the deployment manager administrative console.

      2. Select Environment > WebSphere Variables.

      3. From the Scope drop-down menu, select the Node=node, Server=WebSphere_Portal option to narrow the scope of the listed variables, where Node=node is the node that contains the application server.

      4. Update the WCM _HOST variable with the fully qualified host.name used to access the WebSphere Portal server through the Web server or On Demand Router.

      5. Update the WCM _PORT variable with the port number used to access the WebSphere Portal server through the Web server or On Demand Router.

      6. Save changes and then restart the deployment manager, the node agent(s), server1, and the WebSphere_Portal servers.

    8. Change the task list settings to point to the cluster instead of a single server.

     

    Parent topic

    Choosing the type of cluster to create on AIX