The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 10:30am (PST)
The community will be in read-only from Tuesday 11:59pm (PST) to Wednesday 10:30am (PST)
Project and Portfolio Management Practitioners Forum
cancel
Showing results for 
Search instead for 
Did you mean: 

PPM Replication - Suggestions

Highlighted
fahadymohammed
Acclaimed Contributor

PPM Replication - Suggestions

 

We are replicating our HP PPM application from one server to another. We are not aware of the exact procedure. Anyone has some sample documents or procedure to do the same?

 

Thanks and Regards

2 REPLIES
Celil
Esteemed Contributor

Re: PPM Replication - Suggestions

Hi,

 

Here is a PPM data migration process (Creating a clone system):

 

1) Take a snapshot of source system db: First of all close PPM system and be ensure that oracle is running. We use export command:

       example:

                  exp system/password@sid owner=ppmuser,ppmrmluser log=logfilename

 

2) Prepare destinition system for data migration. First of all close PPM system and be ensure that oracle is running. We use some SQLs and some scripts:

      example:

                  run in sqlplus: DROP USER ppmuser CASCADE;
                  run in sqlplus: DROP USER ppmrmluser CASCADE;

                  <PPMHOME>\utilities\db\system> sqlplus system@sid  CreateRMLUser.sql
                  <PPMHOME>\utilities\db\system> sqlplus system@sid  CreateKintanaUser.sql
                  <PPMHOME>\utilities\db\sys> sqlplus sys@sid as sysdba GrantSysPrivs.sql

 

3) Import source data to the destination system. We use import command:

      example:

                  imp system/password@sid log=logfilename file=ppmuser.dmp full=y

 

4) Change passwords: Beacuse the encryption method different between these two systems. With the migration you transported passwords in data with encryption method of source system. But now it is in destination system and it has a different encryption method. At this point, we rehash all users default PPM passwords in db. Then rehash oracle user, rml user passwords in server.conf. We use some SQL commands:

      example:

                  run in <PPMHOME>\bin\ folder: kEncrpyt.sh default_ppm_password

                  copy result to notepad and remove #@# characters at two sides of hash string.

                  run in sqlplus: update KNTA_USERS set password='default_ppm_password_hash'

                  don't forget to commit it.

                  run in <PPMHOME>\bin\ folder: kEncrpyt.sh oracle_ppm_user

                  copy result to related posisiton in server.conf file  ( you don't need to remove #@# characters)

                  run in <PPMHOME>\bin\ folder: kEncrpyt.sh oracle_ppm_rml_user

                  copy result to related posisiton in server.conf file  ( you don't need to remove #@# characters)

                  don't forget to save changes in server.conf file.

 

5) Rebuild system to apply all changes:

      example:

                  run in <PPMHOME>\bin\ folder: kJSPCompiler.sh
                  run in <PPMHOME>\bin\ folder: kUpdateHTML.sh

 

6) Destination system is ready for running as clone.

 

Celil

 

Celil

IT Governance Professional
& PPM Solution Architect
Jim Esler
Honored Contributor

Re: PPM Replication - Suggestions

The processes you should use are described in the Installation and Administration Guide in the chapter titled "Migrating Instances". These processes can be used to move an ITG instance or database to another server, create another node for a cluster or create a new instance. Note that if you clone an existing instance and modify the configuration to run as a new instance, the original and new instances will share encryption keys and no adjustments will be required when refreshing databases from one to the other.

//Add this to "OnDomLoad" event