CMS Document - calstatela.edu€¦ · Web viewAny errors received during the Validation process will appear in the output window. This information can be copied and pasted into

HCM 9.0 Release NotesMaintenance Pack 20_04

Tools Platform 8.54.09

Release Date: 5/06/16

Campus Application Time:

15 minutes

File Reference: document.docx

HCM 9.0 Maintenance Pack Release Notes Maintenance Pack 20_04Tools Platform 8.54.09

Table of ContentsPage

1.0 Definitions [Informational Only]...................................................................................................................... 1

2.0 Prerequisites: [Campus Action Required].....................................................................................................12.1 Prerequisite List................................................................................................................................... 1

3.0 Changes to Campus PeopleSoft Fileshare [Campus Action Required]........................................................13.1 Copy the HCM 9.0 Release Package for Maintenance Pack 20_04....................................................13.2 Shut down Application Server and Process Scheduler........................................................................13.3 Run Repliweb to apply file share objects [Campus Action Required]..................................................2

4.0 Changes to the Application [ Informational Only ].........................................................................................24.1 Summary of Release Changes............................................................................................................2

5.0 Importing the Maintenance Pack Project to Your Staging Database..............................................................25.1 Clear Cache Files................................................................................................................................. 25.2 Unzip the HCM Maintenance Pack 20_04.zip file to C:\temp...............................................................25.3 Set paths for DMS Input, Output and Logs..........................................................................................35.4 Pre Update Activities – N/A.................................................................................................................. 55.5 Import the Project BSL_UPG90_MP_20_04........................................................................................55.6 Validate the Project BSL_UPG90_MP_20_04.....................................................................................85.7 Create Tables – N/A............................................................................................................................. 95.8 Post Create Tables Action – N/A..........................................................................................................95.9 Alter Tables Without Deletes – N/A......................................................................................................95.10 Post Alter Without Delete Action – N/A................................................................................................95.11 Alter with Deletes – N/A....................................................................................................................... 95.12 Post Alter With Delete Action – N/A.....................................................................................................95.13 Create Views – N/A.............................................................................................................................. 9

6.0 Post Build Activities........................................................................................................................................ 96.1 Run Stored Statement Data Mover Scripts – N/A................................................................................96.2 Execute SQL Scripts............................................................................................................................ 96.3 Data Mover Script – Run INC0153111_IMPORT.dms.......................................................................10

7.0 Manual Steps – Special Instructions.............................................................................................................117.1 Clear app server cache and start process schedulers.......................................................................11

8.0 Updating Security - [Campus Action Required]............................................................................................118.1 Update Operator Security – N/A.........................................................................................................118.2 Additional Security Updates – N/A.....................................................................................................12

9.0 Audit Steps................................................................................................................................................... 149.1 Refresh HCM Interface Registry Cache.............................................................................................149.2 Verify Database Stamp...................................................................................................................... 15

10.0 Application of Maintenance Pack to other Campus Databases....................................................................15

Release Date: 5/06/16

HCM 9.0 Maintenance Pack Release Notes Maintenance Pack20_04Tools Platform 8.54.09

1.0 Definitions [Informational Only]

Campus Action Required: Steps containing this label must be performed by the campus.

2.0 Prerequisites: [Campus Action Required]

2.1 Prerequisite List

All Maintenance Packs Through MP 20.03 Oracle 11.2.0.3

3.0 Changes to Campus PeopleSoft Fileshare [Campus Action Required]

3.1 Copy the HCM 9.0 Release Package for Maintenance Pack 20_04

The Maintenance Pack Package consists of the following:

Repliweb Job Project Library

IMPORTANT!!! Note for SA campuses: If you have a customized ECOUTMAP.sqc you must copy that into this new sa85302 fileshare and also attach your customized ECOUTMAP.sqc to your Help Desk Ticket when requesting the migration.

Repliweb Job

Your database/fileshare is located in the data center and you will have to install the fileshare via Repliweb. Instructions and training guides can be downloaded from the CMS Web Site at https://csyou.calstate.edu/Projects-Initiatives/CMS/TechSvcs/Pages/TSObjectMigration.aspx.

Project Library

The project library must be downloaded from the CMS Web Site at https://csyou.calstate.edu/Projects-Initiatives/CMS/CMSReleases/Pages/RelCMS.aspx. Locate the Project link, posted under this maintenance pack release. Follow the instructions contained within the package installation MP20_04_20160506.zip file to install the new project. Any campus specific customized third party objects will need to be moved in to the target instance afterwards.

3.2 Shut down Application Server and Process Scheduler

EXAMPLE

1. Run the ps_admin “stop_all” and “stop_nt” commands.a. sesudo ps_admin –d <dbname> -o stop_allb. sesudo ps_admin –d <dbname> -o stop_nt

NOTE: The servers will be brought back up before starting the Manual Instructions in Section 7.1

Release Date: 5/06/16 Page 1 of 16

https://csyou.calstate.edu/Projects-Initiatives/CMS/CMSReleases/Pages/RelCMS.aspx

https://csyou.calstate.edu/Projects-Initiatives/CMS/CMSReleases/Pages/RelCMS.aspx

https://csyou.calstate.edu/Projects-Initiatives/CMS/TechSvcs/Pages/TSObjectMigration.aspx



3.3 Run Repliweb to apply file share objects [Campus Action Required]

You will need to use Repliweb to apply the file share objects for MP20_04 which will be located under CMS_UPDATES_FIXES in Uniweb. Once the MP20.04 file share objects have been applied, you will need to use Repliweb to reapply any campus modified file share objects.

For detailed instructions on how to use RepliWeb, please refer to the RepliWeb User Guide located at https://csyou.calstate.edu/Projects-Initiatives/CMS/TechSvcs/Pages/TSObjectMigration.aspx.

4.0 Changes to the Application [ Informational Only ]

4.1 Summary of Release Changes

Please refer to the HCM Summary of Release Changes_MP2004_20160506.doc for detailed information regarding specific Help Desk Cases resolved in this maintenance pack.

5.0 Importing the Maintenance Pack Project to Your Staging Database

5.1 Clear Cache Files

Clear the cache files on the local machine where the upgrade will be performed by deleting the contents of the C:\PS\Cache folder.

NOTE: No Oracle/PeopleSoft applications should be active while performing this step.

5.2 Unzip the HCM Maintenance Pack 20_04.zip file to C:\temp

The following table illustrates the steps required to unzip the maintenance release package

Instructions Illustration

• Unzip the MP 20_04 package to the C:\temp directory on your local drive.

• Select/Verify 'Extract' options. Settings should be:

All files Use folder names




5.3 Set paths for DMS Input, Output and Logs

Paths are set to point to C:\Temp, since the data and scripts folders for the Application Release were unzipped to that location.

The following table illustrates how to set the paths for the DMS input, output and logs.


• Navigate to: Start>Programs>PeopleTools 8.54.09>Configuration Manager

• Select the 'Profile' tab

• Once on the 'Profile' tab, click the 'Edit' button to launch the 'Edit Profile' page.




• On the 'Edit Profile' page, select the 'Common' tab

• Select/Verify 'Edit Profile' options. Settings should be:

TCP Packet Size 512 Convert DIB and BMP

images to JPG• Set the following paths for

the Data Mover Directories:

Input Directory: C:\Temp\Data

Output Directory:C:\Temp\Data

Log Directory:C:\Temp

• Click 'OK' to return to Configuration Manager




• Click 'OK' again to save the settings you entered and close out of Configuration Manager.

5.4 Pre Update Activities – N/A

5.5 Import the Project BSL_UPG90_MP_20_04

The following table illustrates how to import the project.


• Logon to the campus database via Application Designer.

• From the 'App Designer' menu select Tools > Copy Project>From File




• Browse to the parent folder C:\Temp

• Select C:\Temp • Click 'OK'• Highlight the project

BSL_UPG90_MP_20_04 in the ‘Select Project from the List Below’ box. Click on the “Select” button.

• Click 'Select All' • Click on 'Options' to

launch the 'Upgrade Options' page.




• On the 'Upgrade Options' page, select the 'Copy Options' tab.

• Click 'Select All' in the Copy Languages list.

• Select the 'General Options' tab

• Enter 500 for the 'Commit Limit'

• Select/Verify 'General Options'. Settings should be:

Set Target Audit Flags from Source

Keep Target DDL Keep Target References Keep Target Display Size Keep Target Field Format

• Click 'OK' to return to the 'Copy' page.

• Click 'Copy'



The following error(s) and warning(s) are expected and can be ignored. • Object Name: xxxxxxxx not copied, entire object already copied

The project, BSL_UPG90_MP_20_04 will be imported into your database.

5.6 Validate the Project BSL_UPG90_MP_20_04

An important part of the PeopleSoft upgrade process involves validating your upgrade project. When you validate a project, Application Designer verifies that all object definitions included in the project actually exist in your database.

Launch the Application Designer to execute the following steps.


• From the App Designer menu select: Tools > Options

• Select the 'Validate' tab• Select/Verify the

'Validate' options. Settings should be:

Validate PeopleSoft Internet Architecture Execution

Validate project integrity • Click ‘OK’

• From the App Designer menu select: Tools > Validate Project


Output Window


• When prompted to delete all invalid objects, click ‘No’

IMPORTANT!!! Any errors received during the Validation process will appear in the output window. This information can be copied and pasted into a text/Word document for future reference. Errors should be resolved before proceeding with the upgrade. If you need assistance with this step, please open a high priority Help Desk Case assigned to SOSS SA Change Control.

The following error(s) and warning(s) are expected and can be ignored. N/A

5.7 Create Tables – N/A

5.8 Post Create Tables Action – N/A

5.9 Alter Tables Without Deletes – N/A

5.10 Post Alter Without Delete Action – N/A

5.11 Alter with Deletes – N/A

5.12 Post Alter With Delete Action – N/A

5.13 Create Views – N/A

6.0 Post Build Activities

6.1 Run Stored Statement Data Mover Scripts – N/A

Launch Data Mover and run the following scripts to modify the steps within stored statements from the <PShome>\src\cbl\base directory.

6.2 Execute SQL Scripts

Stamp the Database

When the migrations are complete, The Stamp_Database_MP2004.sql will stamp the Target database with the new release number:

Log on to the database via SQL+ as SYSADM and run the script ‘Stamp_Database_MP2004.sql’, found in C:\Temp\Scripts. Make sure to spool the output to a log file, and check this log file for errors.



Example:

SQL> spool c:\temp\ Stamp_Database_MP2004.lstSQL> set echo onSQL> @c:\temp\scripts\ Stamp_Database_MP2004.sqlSQL> spool off

6.3 Data Mover Script – Run INC0153111_IMPORT.dms

The Data Mover scripts are in C:\Temp\Scripts; Dat files are in to C:\Temp\Data. Run the following Data Mover Scripts, Start>Programs>PeopleTools 8.53.02>Data Mover

The following error(s) and warning(s) are expected and can be ignored. ‘Unique Constraint’ (duplicate record) Errors

• While running the following data mover scripts (DMS), you may experience ‘Unique Constraint’ (duplicate record) errors. The likely cause of this is that your campus already ran the script in the process of applying an Update/Fix posted to the CMS Web Site. If you need help determining if your campus has already applied an Update/Fix, open a Help Desk Case with SOSS HR Change Control. Make a note of any errors received (include this with your Help Desk Case) and proceed with running the remaining DMS scripts.

The following table illustrates how to run the Post Build data mover script(s)

7.0 Manual Steps – Special Instructions

7.1 Clear app server cache and start process schedulers

Clear app server cache and restart app server and process schedulers using the ps_admin “clr_cache” and “start_nt” commands:

1. Run the ps_admin “clr_cache” and “start_nt” commands.a. sesudo ps_admin –d <dbname> -o clr_cache


Instructions IllustrationFrom the “Data Mover” menu select File > Open

• Open and run the following scripts.

INC0153111_IMPORT.dms

Run Script Check log files in C:\temp


b. sesudo ps_admin –d <dbname> -o start_nt2. For complete instructions on how to use the ps_admin command, please refer to the CMS Oracle

Enterprise Environment Administrators Guide, located at https://csyou.calstate.edu/Projects-Initiatives/CMS/TechSvcs/Pages/TSCampusLocEnvt.aspx.

8.0 Updating Security - [Campus Action Required]

8.1 Update Operator Security – N/A

NOTE: The PeopleSoft Security Administrator at your campus should perform the following steps.

The components listed below have changed as part of this upgrade package. Update operator security to access the following components as deemed appropriate by your campus.

# MENU NAME COMPONENT NAME

The following table illustrates how to update the operator security.


• Navigate to: Home > PeopleTools > Security > Permissions & Roles > Permission Lists

• Enter the name of the permission list that must be updated and click 'Search' to select the permission list.

Note: An example using the PPSUPER permission list is depicted.


https://csyou.calstate.edu/Projects-Initiatives/CMS/TechSvcs/Pages/TSCampusLocEnvt.aspx

https://csyou.calstate.edu/Projects-Initiatives/CMS/TechSvcs/Pages/TSCampusLocEnvt.aspx



• The 'General' tab defaults.

• Select the 'Pages' tab to display the menus available for the permission list.

• Click 'Edit Components' for the required menu name.

• Note : A partial sample representation of the menus that may be displayed on the 'Pages' tab is depicted.

• Click 'Edit Pages' for the required component

• Provide access to new pages according to your campus security setup by clicking on the appropriate check boxes for the desired access.

8.2 Additional Security Updates – N/A

Portal Security Synch

Run Portal Security Synch to synchronize the Portal Registry with your security permissions.

NOTE: The user ID that invokes this process must have the security role Portal Administrator. Otherwise, the process may terminate abnormally.



The following table illustrates the steps required to run the Portal Security Synch

Instructions IllustrationRun the Portal Security Synch process

• Navigation: PeopleTools > Portal > Portal Security Sync

Delete Invalid Security

• Click ‘Run’

• Select PSUNX as the Server Name

• Click ‘OK’

IMPORTANT: Please repeat the process and remove the check box for Delete Invalid Security.



The following table illustrates the steps required to re-run the portal security synch with the ‘Delete Invalid Security’flag unchecked.

Instructions IllustrationRun the Portal Security Synch process

• Navigation: PeopleTools > Portal > Portal Security Sync

Uncheck ‘Delete Invalid Security’

• Click ‘Run’

• Select PSUNX as the Server Name

• Click ‘OK’

NOTE: If users are having trouble accessing the newly designated menu items, you may have to clear your Application Server cache and/or Web server cache.

9.0 Audit Steps

9.1 Refresh HCM Interface Registry Cache

CMS has developed a custom process that only refreshes the cache. This custom AE process does not update any required security. This custom process replaces the ‘push button’ process that is currently used by the Technical services group. This custom AE process will refresh the SOA cache and can be run by the command line interface.



DOS Prompt: <pshome>\bin\client\winx86>

Command: psae -CD dbname -CT type -CO oprid -CP pwd -R run_control -AI CSU_SOAREFR

Where: dbname = the instance where you want to run the program (i.e., HAXXXSTG)

type = ORACLEoprid = a valid operator id for this instance (i.e., SUPEROP)pswd = the password for the operator idrun_control = a run control id for the process

If you are prompted, type ‘g’ to execute the program

9.2 Verify Database Stamp

Verify the Stamp Database sql ran in step 6.2 has been updated correctly:


• In the 'App Designer' menu select Tools > Upgrade > Stamp Database

PeopleSoft ReleaseHRMS & Campus Solutions

• The Service Pack will be updated to 20

• The Customer Release will be updated to '004'

• Click 'Stamp'

10.0 Application of Maintenance Pack to other Campus Databases.

Please repeat the process in these notes for other databases you wish to apply the maintenance pack.



IMPORTANT!!! The process of comparing and migrating the Maintenance Pack(s) from one database to another is being suspended due to the volume of objects in the Maintenance Pack project.


Documents

CMS Document - calstatela.edu€¦ · Web viewAny errors received during the Validation process will appear in the output window. This information can be copied and pasted into