Creating a new cluster from a single server node on LinuxAdded by IBM | Edited by O Perez on May 5, 2011 | Version 5 (Show original)
|Create a new cluster from an installation of IBM® Lotus® Quickr™ for WebSphere Portal on a single server node in the cell. In this scenario, you use an existing Lotus Quickr installation to form the primary node and create a cluster from a single server installation.
Create a new cluster from an installation of IBM® Lotus® Quickr™ for WebSphere Portal on a single server node in the cell. In this scenario, you use an existing Lotus Quickr installation to form the primary node and create a cluster from a single server installation.
If you want to use an existing Lotus Quickr single server installation as the base to create a cluster, follow the steps in this topic to establish the new cluster using this Lotus Quickr installation as the primary node. Before beginning, consider backing up the complete file system and database to enable you to restore this Lotus Quickr installation to a single server (standalone) environment in the future, if required.
- Install and configure the IBM WebSphere® Application Server Network Deployment on the deployment manager system using the instructions found at Installing WebSphere Application Server Deployment Manager on a Linux system.
- Use a text editor to open the wkplc.properties file in the was_profile_root/ConfigEngine/properties directory.
- (Optional): Prepare the shared folder for PlaceCenter Collections. This step is not necessary if the index location is already a shared library. For more information on configuring the shared folder for PlaceCenter Collections, see the topic Configuring places catalog for clusters.
- (Optional): Modify the PlaceCenter Index location. In a cluster it needs to be a shared directory, while this is out-of-band for standalone systems it is a default location under \wp_profile: This step is not necessary if the index location is already a shared library.
Review and if necessary update the wkplc.properties file to guarantee that the values for the following properties are uncommented and correctly defined:
- Update the value of the placecntr.collections.storage.path in wkplc_comp.properties to the shared folder's location; ConfigEngine.bat action-set-collections-path -DWASPassword=WASPassword -DPortalAdminPwd=PortalPassword
WasPassword Verify that all database property values are defined correctly in the wkplc_comp.properties and wkplc_dbtype.properties files. For reference, the required and appropriate property values are described in the transferring databases manually topic. Preparing these values now readies a database transfer either before or following the federation and clustering of the single server node.Update the security configuration on the deployment manager system with the same security settings as the Lotus Quickr node before adding the Lotus Quickr node to the cell. To configure security on the deployment system use the following instructions that correspond to your security configuration.
Optional. If you use the –D option to supply this password on all tasks, then it is not required to store this WebSphere Application Server administrative password value in the properties file.PortalAdminPwd
Optional. If you use the –D option to supply this password when running the configuration tasks, then it is not required to store this password used for portal administration in the local Lotus Quickr node in the properties file.WasSoapPort
Set this property to the port used to connect remotely to the deployment managerWasRemoteHostName
Set property to the fully qualified host name of the server used to remotely connect to the deployment manager
Configure LDAP user registry with realm support in a federated repository configuration
- Configure the default file registry with realm support in a federated repository configuration
- Update the primary administrative user of the deployment manager with the same primary administrative user as the Lotus Quickr node.
- You must create the Portal admin user and group on the deployment manager with the same Portal admin user and group as the Lotus Quickr node. The default Portal admin group name is wpsadmins, and you must add the Portal admin user to the Portal admin group as a member.
- You must configure the LDAP user registry on the deployment manager with the same setting as the Lotus Quickr node.
- You must update the primary administrative user of the deployment manager with the same primary administrative user as the Lotus Quickr node.
ote: If any Portal fixes have been applied to the Quickr Server, download and replace the existing wp_clust_cfg.xml before running the ConfigTask below.
Please review the following technote - https://www-304.ibm.com/support/docview.wss?uid=swg21496740
Ensure that the deployment manager is running and that IBM WebSphere Portal is stopped. To check to see which servers are running, run the following command:
- ./serverStatus.sh -all -user username -password password
Run the following command from a command prompt in the was_profile_root/ConfigEngine directory:Run the following command from a command prompt in the was_profile_root/ConfigEngine directory:
- ./ConfigEngine.sh cluster-node-config-pre-federation -DWasPassword=password
Use a text editor to open the wkplc.properties file on the primary node in the was_profile_root/ConfigEngine/ directory.Review and if necessary update the wkplc.properties file to guarantee that the values for the following properties are uncommented and correctly defined:
- ./ConfigEngine.sh cluster-node-config-post-federation -DWasPassword=password
a. ClusterName Run the following command from a command prompt in the was_profile_root/ConfigEngine directory:
Specify the cluster name you want to use when creating the cluster. Do not use spaces or special characters in the cluster nameb. PrimaryNode
The value for this primary node must be true
Note: You must wait for least an hour for the cluster to synchronise after running the following command.Restart the configuration. To stop the servers:
Note: If you are using the out-of-box security settings, run the following command. The out-of-box security settings are not recommended for a production environment.
- ./ConfigEngine.sh cluster-node-config-cluster-setup -DWasPassword=password
- ./ConfigEngine.sh cluster-node-config-cluster-setup -DOOB=true -DWasPassword=password
Verify that the cluster has been created and that the Lotus Quickr server is running as a cluster member.
- from the dmgr_profile_root\\bin directory - stopManager.bat -username admin_userid -password admin_password
- from the wp_profile\\bin directory - stopNode.bat -user was_admin_userid -password was_admin_password
- stopServer.bat WebSphere_Portal -user admin_userid -password admin_password
- from the dmgr_profile_root\\bin directory - startManager.bat
- from the wp_profile\\bin directory - startNode.bat
- startServer.bat WebSphere_Portal
- Log in to the administrative console for the deployment manager.
- Click Servers -> Clusters, and verify that the cluster you created is displayed.
- Click the cluster name, click Cluster members, and verify that the Lotus Quickr application server is displayed. CC
Note: Remember that WebSphere_Portal is not a cluster member, only the Lotus Quickr server is a cluster member.Verify that Lotus Quickr can launch. Open a browser window and enter in the URL mentioned at the end of the Lotus Quickr installation.
Parent topic: Installing a cluster on Linux systems: qp85Related tasksTransferring all DB2 domains manually: qp85