How to convert RAM in standalone node to cluster in DMGR
I have a RAM installed and configured in a websphere standalone node.
Infrastructure requirement changed and I need to convert the RAM in standalone node into a RAM in managed cluster node From the RAM information center, in order to have RAM in a managed cluster node. RAM must be installed on a managed node and the node must be a member of a cluster. However, I could not find any documentation that show me how to do the conversion from RAM in standalone node to RAM in Cluster managed node. My logical thinking tells me that I only have two option 1) Federated the RAM standalone node 2) Create the cluster and add this managed RAM node (server) as cluster member or 1) Federated a plan standalone was node 2) Create a cluster and add this standalone was node as cluster member 3) then federated the RAM standalone node 4) Add Managed RAM node (server) as second cluster member This two scenarios are pretty much the same. The limitation here is that there is no way to federate a standalone was node directly into a cluster. Performing addnode and add cluster member all in one step. Please help... running out of idea.. |
5 answers
Hi,
I think the safest thing is to: 1) Backup your database 2) Backup your persist area 3) If your new cluster will be spanning more than one WAS node (i.e. more than one physical machine) you will need to move your persist area onto a shared network drive so that it is available to all of the nodes. 4) Get rid of your current WAS, create a complete WAS ND cluster as you wish it to be. Read the cluster requirements documentation of RAM. 5) Then use the RAM Server Setup program to install RAM into this cluster, but point it to your existing database and the shared drive of your persist area, as described in the RAM cluster install docs. This way it will be properly configured for a cluster. You can point to an existing database and persist area and Server setup will manage configuring it for the new cluster. -- Rich Kulp Rational Asset Manager developer |
|
Forgot one thing:
a) Backup your RTC b) If you are RAM 7501 you can then point to this same RTC instead of creating a new one. You must maintain the same RTC database for the new RTC if you create a new one because of existing data in that RTC. This one scares me the most. RTC in WAS is hard to configure. Server setup does a good job installing a brand new one. But I'm not sure if it can install a new RTC software, but point back to the old RTC database. I think it can, but I'm not sure. Maybe another developer knows that answer. -- Rich Kulp Rational Asset Manager developer |
|
Forgot one thing:
a) Backup your RTC b) If you are RAM 7501 you can then point to this same RTC instead of creating a new one. You must maintain the same RTC database for the new RTC if you create a new one because of existing data in that RTC. -- Rich Kulp Rational Asset Manager developer |
|
Thank you for your answer.
The RAM cluster set up mention that the RTC node need to be federated to the same cell but not part of the cluster. Do you think is better to just let the installer installed the embedded RTC instead of adding the standalone RTC node to the cell? |
I would suggest keeping the database & assets backed up and uninstall WAS and reinstall a new ND, create a cluster for RAM & an app server for RTC.
and use server setup to point to the database & assets. This is the simplest option, There are a lot of settings that we configure that differ between standalone & cluster. Its always easy to federate a node when you have nothing running on it and you do not care for the settings, but when you have application settings that you do not know about, I don't think its a good idea. >Do you think is better to just let the installer installed the embedded RTC >instead of adding the standalone RTC node to the cell? yes, but point to the RAM & RTC databases that you have used earlier, do not create a new one. |
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.