Prepare to create the cluster on Solaris

If you installed a IBM WebSphere Application Server Network Deployment, create a static cluster to handle failover requests. If you installed a IBM WebSphere Virtual Enterprise, create a dynamic cluster to balance member workloads.


Prerequisites


Prepare the Solaris OS
Prepare the primary node on Solaris
Tune the servers

PK97393; 6.1.1: Utility to generate edition metadata

Plan the product installation

Use the graphical user interface to augment profiles

Use the manageprofiles command to augment and unaugment profiles

To prepare for creating cluster and then choose the type of cluster you want to create:

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

      WP_PROFILE/ConfigEngine/properties/wkplc.properties
    on the primary node 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.

    Ensure that you set WasUserid and WasPassword to the Deployment Manager user ID and password.

  2. Perform the following steps on the Deployment Manager server 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.

      See the Planning the product installation link below for information about installing WebSphere Virtual Enterprise. 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. Optional. Run the following command from the WP_PROFILE/bin directory to federate the primary node:

    If you chose the option to automatically federate this new profile to a Deployment Manager 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.

    addNode.sh dmgr_hostname dmgr_port -includeapps -includebuses
    	-username was_admin_user
    	-password was_foo

    The above variables are defined as:

    • dmgr_hostname is the TCP/IP host name of the Deployment Manager server

    • dmgr_port is the SOAP port number of the Deployment Manager server

    • was_admin_user and was_foo are the user ID and password for the Deployment Manager administrator

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

    • -localusername local_was_admin_user

    • -localpassword local_was_foo

    See the addNode command file for more information about the addNode command and other optional parameters.
    Warning: 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.

      1. Set WasSoapPort to the port used to connect remotely to the dmgr.

      2. Set WasRemoteHostName to the full host name of the server used to remotely connect to the dmgr.

      3. Verify that WasUserid is set to Deployment Manager administrator user ID.

      4. Verify that WasPassword is set to Deployment Manager administrator password.

      5. Verify that PortalAdminPwd is set to WebSphere Portal administrator password.

      6. Verify that ClusterName is set.

      7. Verify that PrimaryNode is set to true.

  5. Optional. If you configured a database user registry or a property extension (lookaside) database on the Deployment Manager, run the following task 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.

  6. Add the library paths to the VMM_JDBC_CLASSPATH variable:

    1. Log on to the WAS console.

    2. Click Environment -> WebSphere Variables.

    3. Select scope: cell.

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

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

    6. Copy the files that you entered in for the VMM_JDBC_CLASSPATH variable into the appserver/lib directory.

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

  7. Run the ./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 task from the WP_PROFILE/ConfigEngine to create the local Deployment Manager WebSphere variable used to access the database jars.

      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 Deployment Manager 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

  8. Run the ./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 task from the WP_PROFILE/ConfigEngine to create the variable used to access the VMM database jars.

      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.

  • Choose one of the following options to create cluster:

    • Create a static cluster: Choose this option to handle failover requests.

    • Create a dynamic cluster: Choose this option to dynamically balance member workloads.


    Parent

    Set up a cluster on Solaris


    Related tasks


    Prepare the WAS Deployment Manager on Solaris
    Prepare a remote Web server when portal is installed on Solaris in a clustered environment
    Configure WebSphere Portal to use a user registry on Solaris in a clustered environment
    Prepare additional nodes on Solaris
    Configure search in a cluster on Solaris
    Set up multiple clusters on Solaris
    Share database domains between clusters on Solaris

     


    +

    Search Tips   |   Advanced Search