Prepare to create the cluster on AIX


Prerequisites

  1. Prepare the AIX OS
  2. Prepare the primary node on AIX
  3. Prepare the WAS Dmgr on AIX
  4. PK97393; 6.1.1: Utility to generate edition metadata
  5. Plan the product installation
  6. Use the graphical user interface to augment profiles
  7. Use the manageprofiles command to augment and unaugment profiles


Prepare

  1. If the Dmgr is configured to use a stand-alone LDAP user registry, edit...

      WP_PROFILE/ConfigEngine/properties/wkplc.properties

    .and under...

      VMM Stand-alone LDAP configuration

    .set WasUserid and WasPassword to the Dmgr user ID and password.

  2. If you are creating a dynamic cluster...

    1. Install WebSphere Virtual Enterprise and augment the dmgr profile to make it compatible with WebSphere Extended Deployment Operations Optimization.

    2. On the WebSphere Portal primary node, install WebSphere Virtual Enterprise and augment the wp_profile profile to make it compatible with WebSphere Extended Deployment Operations Optimization.

    Profile augmentation is performed using the Profile Management Tool (PMT) graphical interface on systems that support it or through the manageprofiles command that is available on all systems. When using the graphical interface as discussed in the link below, make sure you select...

      Operations Optimization

    .when choosing the type of augmentation to perform. When using the manageprofiles command as discussed in the link below, be sure to follow the instructions to augment a stand-alone application server profile.

  3. Federate the primary node.

    If you chose the option to automatically federate this new profile to a Dmgr as part of the profile creation, then this step is not necessary. If you are not sure, go ahead and run the addNode command as documented below. The task will fail if the node is already federated. 

    cd WP_PROFILE/bin 
./stopServer.sh server1 -user wpadmin -password foo
./stopServer.sh WebSphere_Portal -user wpadmin -password foo
addNode.sh dmgr_hostname  \
           dmgr_port \
           -includeapps -includebuses
           -username was_admin_user
           -password was_foo

    If the WAS administrator user ID and password for the local node are different than the Dmgr administrator user ID and password, add the following parameters to the addNode task:

    • -localusername local_was_admin_user
    • -localpassword local_was_foo


    If the addNode task fails for any reason, perform the following steps before rerunning the task:

    1. Remove the node if the AddNode task succeeded in creating the node.

    2. Log on to the dmgr and perform the following steps if the items exist:

      1. Remove all enterprise applications.

      2. Remove the WebSphere_Portal server definition.

      3. Remove the WebSphere Portal JDBC Provider.

  4. Stop the WebSphere_Portal server on the primary node and ensure that the following parameters are set correctly in ...

      WP_PROFILE/ConfigEngine/properties/wkplc.properties

    Although you can add these parameters directly to any task that you run while creating cluster, you may want to add them to the properties file while creating cluster and then remove them when you are finished to keep environment secure.

    WasSoapPort Port used to connect remotely to the dmgr
    WasRemoteHostName Full host name of the server used to remotely connect to the dmgr
    WasUserid Dmgr administrator user ID
    WasPassword Dmgr administrator password.
    PortalAdminPwd WebSphere Portal administrator password.
    ClusterName  
    PrimaryNode true

  5. Optional. If you configured a database user registry or a property extension (lookaside) database on the Dmgr, to set up access to the database drivers.

    You will also need to run this task if you migrated the primary node from a release prior to V6.1.0, even if you did not configure a database user registry or a property extension (lookaside) database.

    1. Set the property value for federated.db.DbType if using a database user registry or set the property value for la.DbType if using a property extension database in wkplc.properties.

      If you migrated the primary node from a version prior to V6.1.0 and you are not using a database user registry or a property extension database, set the property value for...

        federated.db.DbType

      .to the same value that is in wkplc.properties on the primary node.

    2. Add the library paths to the VMM_JDBC_CLASSPATH variable:

      1. Log on to the WAS console and go to...

          Environment | WebSphere Variables

      2. Select scope: cell.

      3. Select the VMM_JDBC_CLASSPATH variable. If this variable does not exist, click New to create the variable.

      4. Enter the complete paths to the library files in Value. Separate multiple files with a colon (:); for example, enter...

          SQLLIB/java/db2jcc.jar:SQLLIB/java/db2jcc_license_cu.jar

      5. Copy the files entered for the VMM_JDBC_CLASSPATH variable into...

          WAS_HOME/appserver/lib

      6. Stop and restart the appropriate servers to propagate the changes.

    3. Create the local Dmgr WebSphere variable used to access the database jars... 

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

        The db_type in db_type.DmgrDbLibrary should be set to the type of database you are using, for example db2. The local path of the database jars on the Dmgr should be one of the following options:

        DB2Type 2 driver db2java.zip
        DB2 Type 4 driver db2jcc.jar;db2jcc_license_cu.jar
        DB2 for z/OSType 2 driver db2java.zip
        DB2 for z/OS Type 4 driver db2jcc.jar;db2jcc_license_cisuz.jar;db2jcc_javax.jar
        Oracle ojdbc14.jar
        SQL Server JDBC driver provided by Microsoft sqljdbc.jar
        SQL Server JDBC driver provided by DataDirect sqlserver.jar;base.jar;util.jar

    4. Create the variable used to access the VMM database jars. 

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

      VmmNodeName is a list of one or more WebSphere Portal nodes names in the cell which share the same database driver paths. Set db_type.NodeDbLibrary to the type of database you are using, for example db2.

  6. Create the cluster:


Parent

Set up a cluster on AIX


Previous

Prepare the WAS Dmgr on AIX


Next topic

Prepare a remote Web server when portal is installed on AIX in a clustered environment


+

Search Tips   |   Advanced Search