These are the high level steps
- Install Deployment manager. Check Enable administrative security check box
- Configure Deployment Manager: Change the request timeout for SOAP, Web Container Chain,.. Also create a WebSphere Portal Admin user in the local file system based repository using WAS Admin Console.
- Install Standalone portal server. This portal install will act as primary portal node.
- Configure the websphere portal server to use external database.
- Federate and cluster the primary portal node
- Collect files from portal node using ConfigEngine.bat collect-files-for-dmgr task
- Copy the filesforDmgr.zip from primary node to DMGR
- Expand the filesForDmgr.zip on DMGR and copy content to appropriate directories
- Add node to the deployment manager by executing following command on the primary portal node ConfigEngine.bat cluster-node-config-pre-federation
- Update the deployment manager configuration for new WPS by executing the following command ConfigEngine.bat cluster-node-config-post-federation
- Create the cluster definition and add the WebSphere_Portal server as a cluster member by executing following command ConfigEngine.bat cluster-node-config-cluster-setup
- Install Standalone portal server on secondary portal server
- Copy database configuration from primary node to secondary node
- Add node to the deployment manager by executing ConfigEngine.bat cluster-node-config-pre-federation command
- Update the deployment manager configuration for the new WebSphere Portal server by executing the following ConfigEngine script: ConfigEngine.bat cluster-node-config-post-federation
- Add this newly federated WebSphere_Portal server as a cluster member to the existing cluster by executing the following ConfigEngine script: ConfigEngine.bat cluster-node-config-cluster-setup
1 comment:
Thanks for info....
ERP Solutions
Post a Comment