Hello,

I Have questions on Creating CLM Staging environment (along with reverse proxy) using Production Data.

(We use Websphere, Active Directory and Kerberos Integration.)

The Production Environment has a Distributed environment CLM (502) with Reverse Proxy in a windows server (along with converter deployed in WAS in the same server as Reverse proxy) and CLM installed in Websphere ND on IBM i.

We are planning on moving this into Production Distributed Environment using WAS Base (all using Windows servers) and upgrade to 603.

Before we do that we would like to test the whole migration in a staging environment by creating one.

New Staging Environment

Step 1:

export db data for production clm
create new db, create new schema & import data into the new schema (db2i) / or clone the DB (db2i)
Install CLM in distributed environment using Websphere base with Reverse Proxy in the windows servers.
Use the host file to imitate production environment (reverse proxy is clm.company.com & clmstage.company.com etc.)
Do a server rename to create the staging environment (Reverse proxy is clmstage.company.com)
Test

Will this work? Can we use server rename for the reverse proxy form URI clm.company.com to clmstage.company.com in the staging server?

Step 2:

Upgrade from CLM 502 to 603
test


 +++++++++++++++

Now repeat the same in New Windows Production Servers and use the host files during the migration. If everything works in CLM 502, then we can remove the DNS Alias from IBMi and set it to the windows reverse proxy server (clm.company.com) and test it. Follow it with a CLM 603 Upgrade.

I have done server rename without reverse proxy in a distributed environment in staging (using production data). I am thinking will the same work with reverse proxy in place? It sound a little complicated with reverse proxy URI being clm.company.com and we want to set the staging URI to clmstage.company.com and use the production data (which will need a server rename).

Thanks
RK