It's all about the answers!

Ask a question

Preparing staging environment instructions are outdated


Mahari Hill (47261175) | asked Dec 17 '14, 8:32 a.m.
edited Aug 07 '15, 3:10 a.m. by Krzysztof Kaźmierczyk (7.2k34389)
CLM 4.0.5
SQL Server
Active Directory

We would like to create a quick test environment to prepare for 5.0.2. We created a copy of our production CLM VM, and SQL DBs but are told we need to do a server rename before we start testing. (they created "test dbs", but I don't think they replicated the AD server). I looked at the following:

http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.2/com.ibm.jazz.install.doc/topics/t_prepare_staging_env.html

But I don't think this has been updated, because now we have to consider the new RM database. The steps in the procedure, I am not sure if that is for Option 1, 2 or 3...from the beginning of the article.

Any advice?

Comments
Alan Sampson commented Dec 21 '14, 11:29 a.m.
JAZZ DEVELOPER

Mahari,

Please consult the following Flash (Alert) before undertaking a migration to 5.0.2 that include server rename:
CLM LPA templates may not be retrieved after a migration from older release to 5.0.2
[http://www-01.ibm.com/support/docview.wss?uid=swg21693288]

Accepted answer


permanent link
Paul Ellis (1.3k613) | answered Dec 17 '14, 8:47 a.m.
JAZZ DEVELOPER
Hi Mahari,

I see that there are a few outdated images in those pages, so I will create defects against the docs team.
I think the RM procedure is more clearly specified here: http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.2/com.ibm.jazz.install.doc/topics/c_upgrade_flow_clm.html

Assuming you can isolate your test environment, then a server rename isn't necessary.  If you do have to server rename, then the RM split from the JTS shouldn't impact the URI, just the backend storage location.

Please let me know if I missed something,
Paul
Mahari Hill selected this answer as the correct answer

Comments
Mahari Hill commented Dec 17 '14, 9:32 a.m.

Thanks for answering. Just to be clear.

If we can also copy LDAP, then we should move it to an isolated network.
If we can't also copy LDAP, we should do a server rename.

The procedure for this task does not indicate what option 1/2/3 that was chosen. Can we get by without a server rename and just follow the procedure if we don't have a copy of LDAP?

thanks for any assistance..

SFII


Ralph Schoon commented Dec 17 '14, 9:45 a.m.
FORUM ADMINISTRATOR / FORUM MODERATOR / JAZZ DEVELOPER

You can not run a copy of the same server in the same environment. You can isolate some servers in the same environment if you use the hosts files on several machines to make sure the environments don't see each other. This is an option that is a scenario for 3. Complex and error prone. You have to isolate all machines, client, servers and DB servers. This would not require a duplicate LDAP server, as that could be shared.

Another would be a physically isolated network. This would require to duplicate LDAP.

If you do 1 or 2 in your network you have to make sure to rename the servers.

To do a server rename, you need a special key. You need to contact support to obtain the key.


1
Paul Ellis commented Dec 17 '14, 2:37 p.m. | edited Dec 17 '14, 2:41 p.m.
JAZZ DEVELOPER

Just to be sure.  Options 1 and 2 in this document http://www-01.ibm.com/support/knowledgecenter/SSYMRC_5.0.2/com.ibm.jazz.install.doc/topics/t_prepare_staging_env.html
refer to editing the hosts file, so these are the complex and error prone example Ralph alludes to. However, these do not need server rename. There is a clear advantage if you do as being on the same network, there are chances users may not use the local hosts file and access the wrong server. You can implement Themes https://jazz.net/wiki/bin/view/Main/WebUITheming#Image_References to help differentiate them.

However you should have access to the LDAP unless as Ralph states you totally isolate the machine from the original network.
The two issues though are not related in my mind. 

I hope that helps

Your answer


Register or to post your answer.