ShowTable of Contents
Setting up Multiple Dynamic Clusters in a Single Cell
Abstract :
To improve server availability, failover and disaster recovery, as well as to help span large geographical deployments, it is best to consider deploying multiple portal clusters for the same portal site. With multiple clusters, one cluster can be taken out of production use, upgraded and tested while leaving other clusters in production. This is the best means of achieving 100% availability without requiring maintenance windows. It is also possible to deploy clusters closer to the people they serve, improving the responsiveness of the content they provide.
Software & Operating System
AIX 7.1 64-bit
WAS8.5.5 + SDK1.7 -- WAS855 Contains WVE /ODR built in. No need to install a separate product.
Portal 8.0.0.1 + CF07
DB2 V10.1 FP 2
ITDS6.3 LDAP
Setting up Dynamic Cluster 1 : Primary Node - Node1
1. Install WAS855 with SDK 1.7 using IIM
2. Make SDK 1.7 default using managesdk.sh .Run the following commands from /usr/IBM/WebSphere/AppServer/bin dir
./managesdk.sh -listAvailable
NOTE : lists all available SDK's. sdkName for 1.7 is : 1.7_64
./managesdk.sh -setCommandDefault -sdkName 1.7_64
./managesdh.sh -setNewProfileDefault -sdkName 1.7_64
: this command set's up SDK 1.7 as default for all new profiles created.
3. Now that WAS855 with SDK1.7 setup. Next setup is installing WP8001 GM build on top of this .
4. Launch IIM and Install WP8001 GM build.
While installing we need both 8.0 and 8.0.0.1 repository info as below in the same order :
Following the panels, select Advanced Option to change the Context root:
/wps to support/test
/portal to /wp8
/myportal to /mywp8
PortalAdmin ID = portaladmin
PortalAdmin Pwd = p0rtal81u
so the Portal URL with Alternate Context root should look like (non-auth): http://hostname:10039/support/test/wp8
auth : http://hostname:10039/support/test/mywp8
5. After install is successful. Make sure portal is accessible on new context root and Log in successfully.
Ex: http://hostname:10039/support/test/wp8
6. Make sure no errors in SystemOut.log , ffdc errors
7. Apply latest Portal CF (07) on top of 8001 Portal using IIM. Following is the link to Cumulative Fix :
http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=Cumulative+fix+readme+8.0.0.1#action=openDocument&res_title=IBM_WebSphere_Portal_V8.0.0.1_Combined_Cumulative_Fix_Instructions_standalone_cf8001&content=pdcontent
8. After install is successful. Make sure portal is accessible on new context root.
9. Make sure no errors in SystemOut.log , ffdc errors
Setup DB2 server and configuring Portal Server
NOTE : Setup DB2 on a separate server than Portal Portal
- Setup DB2 Server (on a separate machine : version 10.1.0.x).Follow DB2 Infocenter on how to install/setup DB2 .
- NOTE : Following the Portal Infocenter to execute the following database steps :
- http://dwlhub.swg.usma.ibm.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=IBM+WebSphere+Portal+8+Product+Documentation#action=openDocument&res_title=AIX_standalone_Configuring_Portal_to_use_a_database_wp8&content=pdcontent
- Setup/Create databases manually for all Portal domains on DB2 Server.
- Update wkplc_dbtype.properties, wkplc_dbdomain.properties files with db2 values on Portal Server
- Run the following task to setup databases:
./ConfigEngine.sh setup-database -DWasPassword=p0rtal81u
7. Run the following task to validate all the database domains.
./ConfigEngine.sh validate-database-connection -DWasPassword=p0rtal81u
8. Run the following task to transfer's data from derby to db2.
./ConfigEngine.sh database-transfer -DWasPassword=p0rtal81u
9. Start portal server :
/usr/IBM/WebSphere/wp_profile/bin/startServer.sh WebSphere_Portal
10. Check SystemOut.log , ffdc logs for any errors
11. Access Portal page in browser , login to portal successfully.
Remove Search Collections
NOTE: In Cluster only Remote Search is supported.So we delete default search collections and setup Remote Search Server and Configure Portal after the cluster is setup.
1. Remove Search Collections :
Complete the following steps to prevent search collection creations:
Open the icm.properties file, located in the /usr/IBM/WebSphere/PortalServer/jcr/lib/com/ibm/icm/ directory, and set the jcr.textsearch.enabled property to false.
Restart the WebSphere_Portal server.
Complete the following steps to delete all existing search collections from the primary node, Important: If you plan to use search in a cluster, you must configure a remote search server.
Log on to WebSphere Portal.
Navigate to Administration > Search Administration > Manage Search and then click Search Collections.
Click the Delete Collection icon for each search collection and then click OK until they are all deleted.
Restart the WebSphere_Portal server and then navigate back to the Search Collections page to verify that all search collections have been deleted.
Creating WebSphere Portal Profile Template
1. Run the following task to enable profile templates.This command creates a configuration archive (CAR) file that is used to create additional WebSphere Portal profiles.
The Portal.car file is saved to the /usr/IBM/WebSphere/PortalServer/profileTemplates/default.portal/configArchives directory.
Type 4 database drivers only: If you configured WebSphere Portal for a remote database and placed your database drivers inside of the /usr/IBM/WebSphere/wp_profile/PortalServer directory, they are included in the configuration archive file that is created when running the enable-profiles script.
./ConfigEngine.sh enable-profiles -DWasPassword=p0rtal81u
2. Run the following task to package profiles.This task compress the profileTemplates directory and create a profileTemplates.zip file in the /usr/IBM/WebSphere/PortalServer/profileTemplates directory.
./ConfigEngine.sh package-profiles -DWasPassword=p0rtal81u
Setting up Deployment Manager
NOTE : Install Deployment Manager(Dmgr) on a seperate system.No Portal Server is installed on this machine.
1. Install WAS855 with SDK 1.7 using IIM
2. Make SDK 1.7 default using managesdk.sh .Run the following commands from /usr/IBM/WebSphere/AppServer/bin dir
./managesdk.sh -listAvailable - lists all available SDK's. sdkName for 1.7 is : 1.7_64
./managesdk.sh -setCommandDefault -sdkName 1.7_64
./managesdh.sh -setNewProfileDefault -sdkName 1.7_64
NOTE : this command set's up SDK 1.7 as default for all new profiles created.
3. Now that WAS855 with SDK1.7 setup.Create deployment manager profile below.
4. Create a deployment manager profile using "manageprofiles.sh" command as below :
./manageprofiles.sh -create -templatePath /usr/IBM/WebSphere/AppServer/profileTemplates/management
-hostName <hostname>
-profileName Dmgr01
-profilePath /usr/IBM/WebSphere/AppServer/profiles/Dmgr01
-enableAdminSecurity true
-adminUserName <dmgr_admin>
-adminPassword <dmgr_passwd
NOTE: replace hostname to deployment manager hostname .
dmgradmin / dmgrpass>-- make sure to give the same username / password as Portal admin / Portal admin password on Primary node1 (cluster1).
Ex: ./manageprofiles.sh -create -templatePath /usr/IBM/WebSphere/AppServer/profileTemplates/management
-hostName paix125.rtp.raleigh.ibm.com
-profileName Dmgr01
-profilePath /usr/IBM/WebSphere/AppServer/profiles/Dmgr01
-enableAdminSecurity true
-adminUserName portaladmin
-adminPassword p0rtal81u
5. After the dmgr profile is created successfully in step 4 above. start the dmgr server :
/usr/IBM/WebSphere/AppServer/profiles/Dmgr01/bin/startManager.sh
dmgr server should start successfully.
6. Access the dmgr admin console in browser :
http://hostname:9060/admin
Log in and access the console successfully.
7. An Archive or compressed file
filesForDmgr.zip located in the /usr/IBM/WebSphere/PortalServer/filesForDmgr directory during installation.
Copy the filesForDmgr.zip file to the remote Deployment Manager server.
Stop the deployment manager.
Expand the filesForDmgr.zip file into the installation root directory of the remote Deployment Manager; for example in the /usr/IBM/WebSphere/AppServer directory.
Start the deployment manager.
8.
Augment deployment manager profile using "manageprofiles.sh" command as below:
/usr/IBM/WebSphere/AppServer/profileTemplates/management.portal.augment -profileName Dmgr01
9.
Stop and restart the Deployment Manager server
Preparing to Create the Dynamic Cluster1
Primary Node 1: Run the following steps on Primary Node 1.These steps assume we completed all the
steps 1 and 2 above .
1. Add Node to the dmgr , run the following command :
/usr/IBM/WebSphere/wp_profile/bin/addNode.sh dmgr_hostname dmgr_soap_port -includeapps -username dmgr_admin -password dmgr_passwd
Ex: /usr/IBM/WebSphere/wp_profile/bin/addNode.sh paix125.rtp.raleigh.ibm.com 8879 -includeapps -username portaladmin -password p0rtal81u
Command should run without any errors.
2. Update
wkplc.properties file parameters below on Primary Node1 located in /usr/IBM/WebSphere/wp_profile/ConfigEngine/properties/
- Set WasSoapPort to the port used to connect remotely to the deployment manager.Ex: 8879
- Set WasRemoteHostName to the full host name of the server used to remotely connect to the deployment manager. Ex: paix125.rtp.raleigh.ibm.com
- Verify that WasUserid is set to your Deployment Manager administrator user ID.Ex: portaladmin(same as dmgradmin as mentioned in Step 2)
- Verify that WasPassword is set to your Deployment Manager administrator password.Ex: p0rtal81u (same as dmgrpass as mentioned in Step 2)
- Verify that PortalAdminPwd is set to your WebSphere Portal administrator password. Ex: p0rtal81u (same as PortalAdminPwd as mentioned in Step 1 during Portal Install)
- Verify that ClusterName is set. Ex: PortalCluster8
- Verify that PrimaryNode is set to true.
Creating a Dynamic Cluster1
NOTE: This step assumes all of the steps 1,2,3 above are completed in the same order.
1. Complete the following steps for on the primary node1 of the dynamic cluster:
cd /usr/IBM/WebSphere/wp_profile/ConfigEngine/
./ConfigEngine.sh cluster-node-config-post-federation -DWasPassword=dmgr_passwd
2. Log on to the deployment manager WebSphere Integrated Solutions Console.
Ex: Dmgr Console URL :
http://dmr_hostname:dmgr_port/admin
Complete the following steps to create a node group:
Click
System administration
Node groups.
Click New.
Type the node group Name.Ex: Portal8001
Optional: Type any information about the node group in the Description text box.
Click OK.
Click the Save link to save your changes to the master configuration.
3. Complete the following steps to
add members to the
node group:
Click
System administration
Node groups.
Click the name of the node group that you want to add members to.Ex: Portal8001
Click Node group members under Additional Properties.
Click Add.
Select the primary node1 and then click Add.
Click the Save link to save your changes to the master configuration.
4. Complete the following steps to
create a dynamic cluster in the
node group:
Click
Servers
Clusters >
Dynamic clusters.
Click New.
Select WebSphere Application Server from the Server Type pull-down menu and then
Click Next.
Select the Automatically define cluster members with rules radio button.
Type the cluster name in the Dynamic cluster name text box .
Type the same value that you provided for the ClusterName parameter in the wkplc.properties file of your primary node1. Ex: PortalCluster8
Click Next
Remove all default membership policies and then click Subexpression builder.
Enter the following information in the Subexpression builder window:
Select
and from the
Logical operator pull-down menu.
Select Nodegroup from the Select operand pull-down menu.
Select Equals (=) from the Operator pull-down menu.
Type the nodegroup name you created in the previous step in the Value text box.Ex: Portal8001
Click Generate subexpression.
Click Append.
Click
Preview membership to verify that
all nodes included in the
nodegroup display
Click Next.
Click the
Create the cluster member using an existing server as a template radio button and then
select the
WebSphere_Portal server for the
primary node1 from the pull-down menu.
Click Next.
Specify the required dynamic cluster properties for minimum and maximum number of server instances.
When you are done configuring the dynamic cluster properties, click Next.
Review the summary page to verify your actions and then click Finish.
Click the Save link to save your changes to the master configuration.
Verify the Dynamic Cluster : PortalCluster8 is listed in Dynamic Clusters tab
5. Define or verify the following parameters in the
wkplc.properties file, located in the /usr/IBM/WebSphere/wp_profile/ConfigEngine/properties directory:
Verify that
CellName is set to the
deployment manager cell.
Ex:paix125Cell01
Verify that NodeName is set to the local WebSphere Portal Primary node1.Ex:paix119Node
Set ServerName to the server that is used for the dynamic cluster member on this node.
Note: Log on to the deployment manager WebSphere Integrated Solutions Console
Click Servers > Clusters > Dynamic Clusters > PortalCluster > Dynamic cluster members to find the name of the server used for the dynamic cluster. Ex: PortalCluster8_paix119Node
Verify that PrimaryNode is set to true.
6. From the
/usr/IBM/WebSphere/wp_profile/ConfigEngine directory
Run the
./ConfigEngine.sh cluster-node-config-dynamic-cluster-setup -DWasPassword=dmgrpass
task to
create the dynamic cluster.
Ex:
./ConfigEngine.sh cluster-node-config-dynamic-cluster-setup -DWasPassword=p0rtal81u
Note: This task may display a warning message since the cluster already exists. The task proceeds to create the new dynamic cluster. Therefore, the warning can be ignored.
7. Run the following tasks to pick up the configuration changes:
Note: WebSphere_Portal_servername is the name of the node's WebSphere Portal server; but if you customized the server name, the default name changes. If you are uncertain of the server name,
run the following task to get a list of the server names and their status.
/usr/IBM/WebSphere/wp_profile/bin/serverstatus -all -username portaladmin -password p0rtal81u
./stopServer.sh WebSphere_Portal_servername -username portaladmin -password p0rtal81u Ex:PortalCluster8_paix119Node
./startServer.sh WebSphere_Portal_servername Ex:PortalCluster8_paix119Node
8. Launch Portal Server in browser and make sure you login successfully.
Configuring Standalone LDAP Security-Dynamic Cluster1-Primary Node1
1. On Cluster1 Primary Node1 update
wkplc.properties Standalone.ldap.* section with ITDS LDAP values.(replace with your ldap values)
2. From /usr/IBM/WebSphere/wp_profile/bin run the following commands to see the PortalServer name , run the following command:
./serverStatus.sh -all -username portaladmin -password p0rtal81u
./stopServer.sh WebSphere_Portal_servername (dynamic cluster member from Step 4 above)
3. From /usr/IBM/WebSphere/wp_profile/ConfigEngine , run the following task to validate ldap values:
./ConfigEngine.sh validate-standalone-ldap -DWasPassword=p0rtal81u
4. From /usr/IBM/WebSphere/wp_profile/ConfigEngine , run the following task to validate ldap values:
./ConfigEngine.sh wp-modify-ldap-security -DWasPassword=p0rtal81u
5. After the task ran successfully, restart all servers in the Dynamic Cluster including : Dmgr , nodeagent,PortalServer
6. Launch Dmgr admin Console in browser , make sure login with ldap admin id/pwd successfully.
7. Launch Portal Page in browser, make sure login with ldap admin id/pwd successfully.
Setting up Dynamic Cluster 1 - Node2
1. Install WAS855 with SDK 1.7 using IIM
2. Make SDK 1.7 default using managesdk.sh .Run the following commands from /usr/IBM/WebSphere/AppServer/bin dir
./managesdk.sh -listAvailable
lists all available SDK's. sdkName for 1.7 is : 1.7_64
./managesdk.sh -setCommandDefault -sdkName 1.7_64
./managesdh.sh -setNewProfileDefault -sdkName 1.7_64
: this command set's up SDK 1.7 as default for all new profiles created.
3. Now that WAS855 with SDK1.7 setup.Next setup is installing WP8001 GM build
(Secondary Nodes in a Cluster doesn't need Full Portal Install. So we need only Portal Binary Install).
4. Launch IIM and Install WP8001 GM build.
While installing we need both 8.0 and 8.0.0.1 repository info as below in the same order :
5. Select
BINARY Only Install option and Complete the Install.
6. Apply latest Portal CF (07)(BINARY ONLY ) on top of 8001 Portal using IIM.Following is the link to Cumulative Fix :
http://www-10.lotus.com/ldd/portalwiki.nsf/xpDocViewer.xsp?lookupName=Cumulative+fix+readme+8.0.0.1#action=openDocument&res_title=IBM_WebSphere_Portal_V8.0.0.1_Combined_Cumulative_Fix_Instructions_standalone_cf8001&content=pdcontent
7. Copy the
profileTemplates.zip from Step 1 above
to ,
/usr/IBM/WebSphere/PortalServer/profileTemplates dir.
8. Extract the profileTemplates.zip , if any templates already exist in profileTemplates dir ,overwrite them.
9. Run chmod -R 755 /usr/IBM/WebSphere/PortalServer/profileTemplates to change the permissions on profileTemplates
10. Run ./installPortalTemplates.sh /usr/IBM/WebSphere/AppServer to install the copied profile template
11. Create a Portal profile :
./manageprofiles.sh -create -templatePath
/usr/IBM/WebSphere/PortalServer/profileTemplates/managed.portal
-profileName wp_profile
-profilePath /usr/IBM/WebSphere/wp_profile
-cellName testCell
-nodeName testNode
-hostName myportal.myco.com
12.After the profile is created successfully in above step.
verify
wkplc_dbtype.properties - db2 library value, update if necessary
verify wkplc_dbdomain.properties values should match with the Primary Node1 database properties
Run the following task to validate database connection for all domains.Task should run successfully.
./ConfigEngine.sh validate-database-connection -DWasPassword=p0rtal4u
Adding 2nd Node to Dynamic Cluster 1
1. From /usr/IBM/WebSphere/wp_profile/bin run addNode :
./addNode dmgr_host_Name dmgrport -username dmgr_admin -password dmgr_admin_pw
2. update wkplc.properties :
Verify that
WasUserid is set to your deployment manager administrator ID.
Verify that WasPassword is set to your deployment manager administrator password.
Verify that WasRemoteHostName is set to the fully qualified host name of the dmgr.
Verify that WasSoapPort is set to the SOAP port that the dmgr is using; the default value is 8879.
Verify that ServerName is set to the correct server name. The default is WebSphere_Portal .
Verify that PrimaryNode is set to false.
Verify that ClusterName is set to the primary node's ClusterName .
3. Run the following task for post federation:
./ConfigEngine.sh cluster-node-config-post-federation -DWasPassword=dmgr_password
4. Complete the following steps to add members to the node group:
Click System administration > Node groups.
Click the name of the node group that you want to add members to.
Click Node group members under Additional Properties.
Click Add.
Select the additional node you want to add into the node group and then click Add.
Click the Save link to save your changes to the master configuration.
5. Update wkplc.properties file with the following :
Verify that
ClusterName is set to the name of the existing dynamic cluster.
Verify that CellName is set to the deployment manager cell.
Verify that NodeName is set to the local WebSphere Portal node.
Set ServerName to the server that is used for the dynamic cluster member on this node.
Note: Log on to the deployment manager WebSphere Integrated Solutions Console
click Servers > Clusters > Dynamic Clusters > PortalCluster > Dynamic cluster members to find the name of the server used for the dynamic cluster.
Verify that PrimaryNode is set to false because this is an additional node.
6. Run the following task to add the 2 node to the cluster.
./ConfigEngine.sh dynamic-cluster-setup-additional -DWasPassword=dmgr_password
7. Start the server :
./startServer.sh WebSphere_Portal_servername - dynamic cluster member
8. Update the properties files and Run the following tasks.
update
wkplc.properties Standalone.ldap section with the same ldap values as Primary Node1. All the values has to match with Primary Node1.
./ConfigEngine.sh validate-standalone-ldap -DWasPassword=p0rtal4u
./ConfigEngine.sh update-jcr-admin -DWasPassword=p0rtal4u
9. Restart the
Nodeagent and
Portal server (Dynamic Cluster Member)
10. Launch the Portal in browser, Login successfully. Make sure no errors in the logs.
Setting up Dynamic Cluster 2 - Primary Node1
1. Install WAS855+JDK 7.0.4 manually.
2. Set the JDK as default :
Run the following commands from /usr/IBM/WebSphere/AppServer/bin
./managesdk.sh -listAvailable
./managesdk.sh -setCommandDefault -sdkName 1.7_64
./managesdk.sh -setNewProfileDefault -sdkName 1.7_64
3. Install WP8001 GM driver with alternate context root :
4. Make sure Portal is up , launch Portal page in browser and Log in successfully
5. Apply latest Portal CF (07) on top of 8001 Portal using IIM
NOTE : Link to CF readme listed above in Step 1.
6. After install is successful. Make sure portal is accessible on new context root.
7. Make sure no errors in SystemOut.log , ffdc errors
Configuring Portal Server with DB2
NOTE: Dynamic Cluster 2 Nodes DONOT share "JCR and Release" domains and share all other domains with Dynamic Cluster 1. So create 2 new databases for JCR & Release domains on the same DB2 server as Dynamic Cluster 1. Ex: Give different database name for JCR& Release like : jcrdb121,reldb121
8. Update properties files for domains "JCR & Release"
update wkplc_dbtype.properties-- to update dbLibrary to same db2jcc* jar file from DB2 server.Copy the db2jcc* jar files to the Portal machine and point to this location in properties file.
update wkplc_dbdomain.properties - JCR and Release Domains ONLY. Match DataSource names,db2admin/pwd for JCR & Release domains from Cluster1 - PrimaryNode1
9. Run the following tasks to validate and transfer database for JCR & Release domains.
./ConfigEngine.sh validate-database-connection -DTransferDomainList=release,jcr -DWasPassword=p0rtal81u
./ConfigEngine.sh database-transfer -DTransferDomainList=release,jcr -DWasPassword=p0rtal81u
10.Update wkplc_dbdomain.properties for Feedback,Likeminds,customization,community domains - Match All the values Ex: DataSource,db2admin/pwd etc from Cluster1 - PrimaryNode1
11. Run the following tasks to validate and transfer database for feedback,likeminds,community,customization domains.
./ConfigEngine.sh validate-database-connection -DTransferDomainList=feedback,likeminds,community,customization -DWasPassword=p0rtal81u
./ConfigEngine.sh connect-database -DTransferDomainList=feedback,likeminds,community,customization -DWasPassword=p0rtal81u
12. Run the following tasks to create / package Portal Profile Templates for secondary nodes in the Cluster 2:
./ConfigEngine.sh enable-profiles -DWasPassword=p0rtal81u
./ConfigEngine.sh package-profiles -DWasPassword=p0rtal81u
NOTE : Remove Default Search Collections . Follow steps mentioned in Step 1 section
13. Run the following task from the wp_profile_root/ConfigEngine directory to build an inventory list of PrimaryNode1-Cluster2 Enterprise Applications and Portlets.
./ConfigEngine.sh mapped-app-list-create -DWasPassword=p0rtal81u
14. Update wkplc.properties - standalone.ldap section.Match the values with Cluster1-Primary Node1 - standalone.ldap section
NOTE: Ensure that you set WasUserid and WasPassword to the Deployment Manager user ID and password.
15. Add the Node to deployment manager .Run addNode from /usr/IBM/WebSphere/wp_profile/bin dir :
addNode.sh dmgr_hostname dmgr_port -includeapps -username dmgr_admin -password dmgr_pwd
16. Update wkplc.properties as below :
Set
WasSoapPort to the port used to connect remotely to the deployment manager.Ex:8879
Set WasRemoteHostName to the full host name of the server used to remotely connect to the deployment manager.Ex: paix125.rtp.raleigh.ibm.com
Verify that WasUserid is set to your Deployment Manager administrator user ID.Ex:uid=wpsadmin,cn=users,dc=ibm,dc=com(since Dmgr is ldap configured)
Verify that WasPassword is set to your Deployment Manager administrator password.Ex:p0rtal4u
Verify that PortalAdminPwd is set to your WebSphere Portal administrator password.Ex:p0rtal4u
Verify that ClusterName is set.Ex:PortalCluster2
Verify that PrimaryNode is set to true.
17. Run the following task to determine which applications from the inventory list are no longer mapped to Portal 1(Cluster 2). The task uses the application profiles already in the cell to restore the mappings.
Wait for 30 minutes after running this task to allow all EAR files to expand before proceeding to the next step.
./ConfigEngine.sh map-apps-to-server -DWasPassword=dmgr_pwd
18. Ensure that all database parameters are correctly set, including passwords, in the wkplc_comp.properties and wkplc_dbtype.properties files.
Run the following task to run port federation:
./ConfigEngine.sh cluster-node-config-post-federation -DWasPassword=dmgr_pwd
19. Verify Cluster1 - Nodes are still up and login to portal successfully
20.Complete the following steps to define a dynamic cluster using Portal 1(Cluster 2) as the basis:
Log on to the deployment manager WebSphere Integrated Solutions Console.
Complete the following steps to create a node group:
Click New.
Type the node group Name.
Type any information about the node group in the Description text box.
Click OK.
Click the Save link to save your changes to the master configuration.
Complete the following steps to
add members to the node group:
Click System administration > Node groups.
Click the name of the node group that you want to add members to.
Click Node group members under Additional Properties.
Click Add.
Select the primary node and then click Add.
Click the Save link to save your changes to the master configuration.
Complete the following steps to
create a dynamic cluster in the node group:
Click Servers > Clusters > Dynamic clusters.
Click New.
Select WebSphere Application Server from the Server Type pull-down menu and then click Next.
Type the cluster name in the
Dynamic cluster name text box and then click Next. Type the same value that you provided for the
ClusterName parameter in the wkplc.properties file of your primary node.
Remove all default membership policies and then click Subexpression builder.
Enter the following information in the Subexpression builder window:
Select and from the Logical operator pull-down menu.
Select Nodegroup from the Select operand pull-down menu.
Select Equals (=) from the Operator pull-down menu.
Type the nodegroup name you created in the previous step in the Value text box.
Click Generate subexpression.
Click Append.
Click Preview membership to verify that all nodes included in the nodegroup display and then click Next.
Click the Create the cluster member using an existing server as a template radio button and then select the WebSphere_Portal server for the primary node from the pull-down menu.
Click Next.
Specify the required dynamic cluster properties for minimum and maximum number of server instances.
Review the summary page to verify your actions and then click Finish.
20. Define or verify the following parameters in the wkplc.properties file
Verify that
CellName is set to the deployment manager cell.
Verify that NodeName is set to the local WebSphere Portal node.
Set ServerName to the server that is used for the dynamic cluster member on this node.
Verify that PrimaryNode is set to true.
21. Run the following task to create the dynamic cluster.
./ConfigEngine.sh cluster-node-config-dynamic-cluster-setup -DWasPassword=dmgr_password
NOTE : Set up Secondary Node2 in Dynamic Cluster2. Follow same steps as Dynamic Cluster1 - Secondary Node
1.Install WAS855+JDK7.0.4 on a standalone machine
2. Set JDK as default
Make SDK 1.7 default using managesdk.sh .Run the following commands from /usr/IBM/WebSphere/AppServer/bin dir
./managesdk.sh -listAvailable - lists all available SDK's. sdkName for 1.7 is : 1.7_64
./managesdk.sh -setCommandDefault -sdkName 1.7_64
./managesdh.sh -setNewProfileDefault -sdkName 1.7_64
3. Create a custom profile as below :
./manageprofiles.sh -create -templatePath /usr/IBM/WebSphere/AppServer/profileTemplates/managed -profileName ODRProfile1 -profilePath /usr/IBM/WebSphere/AppServer/profiles/ODRProfile1
4. Add this node to dmgr from : /usr/IBM/WebSphere/AppServer/profiles/ODRProfile1/bin
./addNode.sh <dmgrhostname> <dmgrport> -username dmgr_user -password dmgr_passwd
Ex: ./addNode.sh paix125.rtp.raleigh.ibm.com 8879 -username wpsadmin -password p0rtal4u
5. Create an ODR using this node.Follow the link below to create and configure the ODR.
NOTE: http://pic.dhe.ibm.com/infocenter/wasinfo/v8r5/topic/com.ibm.websphere.wve.doc/ae/twve_odr.html
6. Start the ODR Server
7. Access Portal using this ODR node. Ex: http://odrhostname:port/support/test/wp8
8. Test failover of each node to make sure ODR routes requests to all nodes in the cell.