The basic steps for creating dynamic cluster can be divided into three basic parts
Preparing DM and portal nodes
- Install and configure Deployment Manager
- Install WAS XD and augment the deployment manager profile
- On all the WebSphere portal servers install WAS XD and augment wp_profile
Adding Primary Node to dynamic cluster
- Prepare the node for dynamic cluster
- cluster-node-config-pre-federation
- Optional tasks if your using look aside repository or database backed user registry
- cluster-node-config-post-federation
- wp-change-portal-admin-user
- Login into WAS Admin consol and Create a node group
- Add primary portal server as node to the node group
- Create Dynamic cluster, in the WAS Admin Console
- Create the primary portal node as cluster member using the existing server as a template
- Create dynamic cluster by executing cluster-node-config-dynamic-cluster-setup config task
- Access the web content management content:Set the WCM_HOST and WCM_POST websphere variables at the primary portal server level to point to the web server host name and port name through which the WCM content would be accessed.
- Propogate the changes
- Stop DM
- Stop Node Agent
- Stop Server 1
- Stop portal server
- start DM
- Start Node
- Start Server1
- Start WebSPhere POrtal
Adding additional nodes to the cluster
- Setup the wkplc_dbtype.properties and wkplc_comp.properties files to point to correct database
- Validate database settings by executing
- validate-database-driver
- validate-database-connections
- Prepare the node for dynamic cluster
- cluster-node-config-pre-federation
- Optional tasks if your using look aside repository or database backed user registry
- cluster-node-config-post-federation
- wp-change-portal-admin-user
- Login into the WAS Admin Console and add the new node as new member to the node group
- Run the ConfigEngine.bat/sh cluster-node-config-dynamic-cluster-setup task to add the new member to the existing dynamic cluster
- Apply changes by restarting the server
- Access the Web Content Management Content by changing value of WCM_HOST and WCM_PORT websphere variables at the nodename scope to indicate the name of the fully qualified host and port
No comments:
Post a Comment