Moving to Enterprise Toplogy (CLM 6)
Hi
Would you be able to provide us with some documentation with regards to the steps involved in moving from a single WAS instance, to a distributed WAS instance for CLM. I am struggling to find enough documentation on this in order for us to get ready to do this on our staging environment first. I found a few wikis, but we are looking for something similar to the IBM Interactive Installation/Upgrade Guide, which has all your pre-requisites,upgrade scripts and necessary guidelines in order to move from a single server instance to a multiple server instance.
Thanks
Leesen
2 answers
Hi Leesen,
Please find the below wiki it will help you but accordingly you have to use the topology from the installation interactive guide.
https://jazz.net/wiki/bin/view/Deployment/MigratingCLMToANewEnvironment
Regards,
Arun.
Please find the below wiki it will help you but accordingly you have to use the topology from the installation interactive guide.
https://jazz.net/wiki/bin/view/Deployment/MigratingCLMToANewEnvironment
Regards,
Arun.
I am not aware of any detailed steps on moving from a departmental to enterprise topology, but here is a high level overview:
Existing topology:
One WAS server with JTS, ccm, rm and QM installed.
host name: server 1
putlic uri: https://server1:9443/jts
New Topology:
There will be for servers hosting each application running on Websphere.
Steps
1. Follow the interactive upgrade guide and install Websphere and the CLM application on each Server
2. While the servers are stopped, move the configuration files for CLM. The steps are outlined in the link in the first answer
3. Stop the original server.
4. Test the new install
a. Update the host file of each server to map server 1 to the loopback
b. start up the new WAS instances
c.From a browser running on each server, access the application to make sure all is working as expected
d. Once all is working as expected a server rename may be needed. IF so look into setting up a proxy server before running through the server rename
NOTE: IF a proxy server was in place for the departmental topology then step 4 would need to be replaced with merge the plugin-cfg.xml from all the WAS instances and then propogate to the reverse proxy.
If more help is needed please open a PMR.
Existing topology:
One WAS server with JTS, ccm, rm and QM installed.
host name: server 1
putlic uri: https://server1:9443/jts
New Topology:
There will be for servers hosting each application running on Websphere.
Steps
1. Follow the interactive upgrade guide and install Websphere and the CLM application on each Server
2. While the servers are stopped, move the configuration files for CLM. The steps are outlined in the link in the first answer
3. Stop the original server.
4. Test the new install
a. Update the host file of each server to map server 1 to the loopback
b. start up the new WAS instances
c.From a browser running on each server, access the application to make sure all is working as expected
d. Once all is working as expected a server rename may be needed. IF so look into setting up a proxy server before running through the server rename
NOTE: IF a proxy server was in place for the departmental topology then step 4 would need to be replaced with merge the plugin-cfg.xml from all the WAS instances and then propogate to the reverse proxy.
If more help is needed please open a PMR.