1 Reply Latest reply on Jun 9, 2009 6:13 PM by 697670

    PS 9.0 Security - maintaining security in 2 releases.

    705751
      I am working on an upgrade approach for security 9.0, Our current PS environment is 8.3, with PeopleTools 8.2. We are upgrading to PS 9.0/ PT 8.49. We create Oprid's during a nightly batch cycle. We have taken a copy of our PS 8.3 database, with the PeopleTools tables for the initial upgrade, using Oracle Labs. My question, is there a way to migrate the new production Oprid's that have been created since the initial copy of production. We will not be going live with 9.0 for 16 months, and need to maintain PS Oprid's in the upgrade environment.

      Any help is appreciated,
      KT Hargett
        • 1. Re: PS 9.0 Security - maintaining security in 2 releases.
          697670
          I do not know why PeopleSoft does not provide a good solution for such situation. i've seen numerous situations where the client need to address this problems through thier own solutions.

          In order to preserve security upto date as with production, your golden copy (the target database that was upgraded during initial pass) must be constantly updated with all security tables. There is no one clear cut solutions. What many of them have done is if the length of upgrade project is spanning more than 6 months, they would write a custom process to update the OPRID everytime they do test move to prod and migrate the security tables data to golden copy.

          here's what one of the PeopleSoft Customer Connection Solution says:

          E-UPG How can you preserve security through upgrade passes? (Doc ID 642944.1)

          SOLUTION:

          In order to preserve security through your upgrade passes, you will have 3 options.

          1) Low Risk - Re-enter your security changes into one of the target databases. Once this is complete, those security tables can be exported out and imported into any other upgraded databases at the same tools release using security migration reDocument:610138.1, included below.

          2) Low Risk - Re-do the Initial Upgrade again. This will get the security as it is when you take the copy of production. Many customers chose this option because they are most comfortable with it. Once the initial upgrade is completed, follow the steps outlined in reDocument:610138.1 (Included below) to migrate security to your other upgraded databases.

          3) High Risk -
          Attention! This workaround has not gone through our formal quality regression test cycle. We strongly recommend that you thoroughly test this workaround in a development environment before applying it to your production environment.

          Be sure to document this change as this workaround may be detected during your next upgrade. Because this workaround has not yet gone through our formal quality regression test cycle, this workaround will have risk.


          You should only follow this option if you only want the latest operator security in production migrated to your upgraded database. Do the Initial Upgrade again, up through the end of Chapter 2 (Updating PeopleTools). You will need to definitely run the Relnnn.sql scripts, copy the projects and do the alters - but to make sure you get everything correct, it would be best to run all steps in Chapter 2. Once completed your tools release will be at the same level as your fully upgraded database that you want operator security imported into. DO NOT FOLLOW Document:610138.1 as you will LOSE ALL security delivered by the new application release you just upgraded to. To migrate your operator security, select the appropriate Data Mover script for your PeopleTools release to export and import operator security:


          For PT 8.4x -

          ******Export******
          USEREXPORT.dms

          This script looks as follows:

          -- USERS
          EXPORT PSOPRDEFN;
          EXPORT PSOPRALIAS;
          EXPORT PSROLEUSER;
          EXPORT PSUSERATTR;
          EXPORT PSUSEREMAIL;
          EXPORT PSUSERPRSNLOPTN;
          EXPORT PS_ROLEXLATOPR;
          EXPORT PS_RTE_CNTL_RUSER;

          ******Import******
          USERIMPORT.dms

          This script looks as follows:

          UPDATE PSLOCK SET VERSION = VERSION + 1 WHERE OBJECTTYPENAME = 'UPM';

          REPLACE_DATA *;

          UPDATE PSVERSION SET VERSION = VERSION + 1 WHERE OBJECTTYPENAME = 'SYS';
          UPDATE PSVERSION SET VERSION = VERSION + 1 WHERE OBJECTTYPENAME = 'UPM';

          UPDATE PSOPRDEFN SET VERSION = (SELECT VERSION FROM PSVERSION WHERE OBJECTTYPENAME = 'UPM');


          ----------------------------------------------------------------------------------------------------------------------------------------------------------------------------

          hope this helps

          [Learn PeopleSoft HRMS and Upgrade|http://www.learnpeoplesoft.info]