It's all about the answers!

Ask a question

Move RM 6.0.1 to its own server


Cameron McKay (571021) | asked Feb 27 '17, 12:39 p.m.

Hello,


Presently, I have CLM 6.0.1 installed in my environment with one server.  The one server contains JTS, RM, QM, CCM, LDX and GC.  The usage of RM has increase over the past year and performance of RM has decreased.  I would like to put RM on its own server to facilitate this increased usage and improve performance.

In the new topology, there will be three servers.
  • Server 1: Apache re-direct server that will re-direct requests to the correct server based on the URL.
  • Server 2: RM server that will have WebSphere 8.5.5.9 and RM installed.
  • Server 3: JTS, QM, CCM, LDX and GC server that will have WebSphere 8.5.5.9 and each of those web apps installed.
I'm seeking some guidance in moving RM to its own server using the topology mentioned above.  Some questions I have are as follows:
  • Do you see any challenges with moving RM to its own server?
  • Is there an alternative topology that would be easier to implement?
  • Do you have any advice or materials that I could read for implementing this change?
Any help with this would be greatly appreciated.

Cheers, Cam.

Accepted answer


permanent link
Cameron McKay (571021) | answered Mar 07 '17, 2:56 p.m.

For anyone who encounters a similar situation, I've found an article that details the full process and several different situations for you to consider.


Ralph Schoon selected this answer as the correct answer

One other answer



permanent link
Ralph Schoon (63.5k33646) | answered Feb 28 '17, 2:36 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

 Please make yourself familiar with the Deployment Wiki: This section


https://jazz.net/wiki/bin/view/Deployment/DeploymentMigratingAndEvolving has a link Migrating CLM to a new Environment that is relevant to your question. Other scenarios like DB or App Server changes are also available.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.