It's all about the answers!

Ask a question
QuestionsTagsUsersBadges
Guidelines | FAQ
Follow this question
Question details

×42,877
×10,962
×7,470
×4,318
×3,954
×2,351
×1,381

question asked: Jan 23 '13, 9:05 a.m.
question was seen: 8,273 times
last updated: Feb 04 '13, 3:24 a.m.

Related questions

Going from a single CLM host to multiple

0
Adrian Daniels (63●1●21●20) | asked Jan 23 '13, 9:05 a.m.
retagged Jan 23 '13, 12:07 p.m. by Michael Afshar (701●4)
Hi,
I am just about to convert a single server deployment to an enterprise one as described here:

This was always the plan and the DNS and URI have been configured appropriately for this.

I have been looking through the installation guide and cannot find anything that actually takes you through the steps to move from one configuration to the enterprise one.

It is currently running on Tomcat and the proposal is to go to WAS - do you think that we should do the migration first and then got to WAS as a second step. The user database is on tomcat at the moment, the proposal is to move the LDAP (all the user names are consistent to the LDAP domain, it was just that the LDAP setup was not ready)

I think that the steps are:
(1) Install WAS on each of the new servers.
(2) Install the relevant component on each server, ie JTS on one, then RRC, then RTC, then RQM on one of each of the others.
(3) Shutdown the JTS on the old server.
(4) Install the relevant WAR files on each of the app servers.
(5) Start the app servers for each app, JTS,RRC,RTC and RQM.
(6) Run the /setup on each of the other servers to configure them to access the original database - or can I just do something with the teamserver.properties file from the original setup ?
(7) Test access for each app.

Am I on the right track ?

Cheers,
Adrian

3 answers

Most liked answers ↑|Newest answers|Oldest answers

1
permanent link
Ralph Schoon (63.5k●3●36●46) | answered Jan 23 '13, 10:48 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER
edited Jan 23 '13, 10:48 a.m.
Adrian,

the help is not able to cover all the gory details especially since there are so many topologies. We have created https://jazz.net/library/article/831 to give you an idea how that process could look like.
Comments
Ralph Schoon commented Jan 23 '13, 10:49 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

One detail to add, since all your applications have the same public URI (which is great), you would need a proxy to split. IBM HTTP Server and IBM WebSphere Application Server support this out of the box.

0
permanent link
Michael Afshar (701●4) | answered Jan 23 '13, 12:05 p.m.
JAZZ DEVELOPER
Adrian,

Migrating databases and application servers are covered here: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/nav/6_3

And configuring a reverse proxy is covered here: http://pic.dhe.ibm.com/infocenter/clmhelp/v4r0m1/topic/com.ibm.jazz.install.doc/topics/t_config_reverse_proxy_ihs.html
0
permanent link
Adrian Daniels (63●1●21●20) | answered Jan 24 '13, 11:51 a.m.
Thanks both for the information.

I am comfortable with migrating from Tomcat to WAS and also setting up a reverse proxy.

However a reverse proxy will not help in this case because each application was configured with a different Public URI that is resolved to the same box using DNS entries. The customer does not want to use a separate IHS server.

Ralph, I went through the section that explains moving the JTS to a new server, this is only explained for WAS - do I take it from that, that it would be best to convert the existing single box to WAS first and then migrate to the separate boxes ? I guess that moving RRC, RTC and RQM is just the same procedure.

So I think the procedure is starting to emerge as:

(1) Upgrade the current Linux box from CLM 4 to CLM 4.0.1
(2) Move the Oracle database to a separate box as per the infocenter instructions.
(3) Install WAS and migrate the applications over to WAS (This is clearly documented in the infocenter).
(4) Configure LDAP and ensure success on the single box.
(5) Install WAS on each of the new application server boxes.
(6) Install the relevant application on each of the new app server boxes, JTS,RRC,RTC and RQM
(7) Stop the original JTS.
(8) Migrate the applications as per Ralphs lab instructions.
(9) Reconfigure the DNS to point to the new separate servers.
(10) Install the SSL certificates on the new WAS application servers.
(11) Start up the new application servers.
(12) Test access.

Please can you run your eye over this and see if I am on the right track.

Cheers
Adrian
Comments
Ralph Schoon commented Jan 24 '13, 12:18 p.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Hi Adrian, if the customer has provided different public URI'S with different host names in the public URI say https://jts.server.com/jts, https://ccm.server.com/ccm and so forth, a scenario I did not expect, you can simply move the applications to their own boxes. then redirect the DNS to the separate boxes and you are done.

You don't need WAS, Tomcat would do. The only caveat would be that there is no single sign on solution I am aware of with Tomcat. So splitting would require people to log into each server once, if they use them.

IHS and WAS would help with SSO if you had a cmmon public URI with just /jts and /ccm being different. I am not sure you can use SSO with WAS in the described scenario. Please look into https://jazz.net/library/article/413 and some other enlightening articles to get more information.

PS: I won't be available to answer next week.

Adrian Daniels commented Jan 25 '13, 3:29 a.m.

 Hi Ralph,

Are you saying that I just zip up the existing Jazz server directory and copy it to each of the new machines. Do I then just adjust the Teamserver.properties file to tell the app server which app to start up on that particular box ? I guess do the JTS first so the other apps have something to talk to ?
The scenario was chosen from the install guide, it is one option that is put forward complete with a architectural diagram.
I looked into SSO and yes we will need to move to WAS to allow this scenario to function with a single login.
I think that the documentation needs updating to warn people that with this configuration you will need a SSL cert wildcard (using the SAN in the https header) and if going to WAS a separate SSO configuration.

I hope you are going somewhere nice and warm or out on the ski slopes !!

Cheers
Adrian

Ralph Schoon commented Feb 04 '13, 3:21 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

Adrian, almost.

You would install only the apps you need on each box, then restore the backup data for each app on the box that should run that app. You can see what data needs to be moved in https://jazz.net/library/article/795.

You should not install apps that you don't need on a server. At least for registration the conf/app folders are passed and it will find folders that are not needed.

I went somewhere with a bit more pleasant, warmer weather.

Ralph Schoon commented Feb 04 '13, 3:24 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

This assumes that you can do the moves with keeping the URI's of the applications stable. Also be aware that e.g. the Lifecycle Process Administration (LPA) app conf/admin needs to stay with the JTS. You would see which data needs to be backed up once you install the apps desired on a box. look into the server/conf/ folder and restore the data for the apps you find there.

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.