Tuesday 31 March 2015

Executables files and there Path in Peoplesoft



Executables files and there Path :-

  • PSADMIN.EXE- PS_HOME\appserv.
  • UBBGEN.EXE - PS_HOME\bin\server\winx86.
  • TMLOADCF.EXE- TUXDIR\bin
  • TMBOOT.EXE- TUXDIR\bin.
  • TMSHUTDOWN.EXE TUXDIR\bin.

Configuration files are:-
Path:- PS_HOME\appserv\<domain_name>

  • PSAPPSRV.CFG
  • PSAPPSRV.UBX
  • PSAPPSRV.UBB
  • PSAPPSRV.PSX
  • PSAPPSRV.ENV
  • PSAPPSRV.VAL
  • PSTUXCFG

Monday 30 March 2015

Script to Unlock the user

Script to Unlock the user


update psoprdefn set acctlock=0 where oprid = 'abhishek.narayan';

Create spfile from pfile



Create spfile from pfile




 
C:\Users\3130738>set path=D:\app\product\11.2.0\dbhome_2\bin;

C:\Users\3130738>set oracle_sid=abctest

C:\Users\3130738>sqlplus / as sysdba

SQL*Plus: Release 11.2.0.3.0 Production on Fri Feb 13 12:48:41 2015

Copyright (c) 1982, 2011, Oracle.  All rights reserved.

Connected to an idle instance.

SQL> startup nomount pfile='D:\app\product\11.2.0\dbhome_2\database\INITabctest.ora';
ORACLE instance started.

Total System Global Area  926969856 bytes
Fixed Size                  2181224 bytes
Variable Size             587204504 bytes
Database Buffers          331350016 bytes
Redo Buffers                6234112 bytes
SQL> sho parameter spfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string
SQL> sho parameter pfile

NAME                                 TYPE        VALUE
------------------------------------ ----------- ------------------------------
spfile                               string
SQL> create spfile from pfile='D:\app\product\11.2.0\dbhome_2\database\INITabctest.ora';

File created.

Sign on Process in PIA Peoplesoft

Sign on Process in PIA


Various User IDs used For Sign on Process


User ID
Symbolic Id
Access Id
Connect Id
Used For
A PeopleSoft user ID is the ID you enter at the PeopleSoft sign-in dialog box. You assign each PeopleSoft user a user ID
Used to map the User Id to Access Id without exposing the Access Id information.

All the User Id's are associated with a Symbolic Id (on User Profile Page). A Symbolic Id is associated with Access Id in PSACCESSPRFL record (Access Id is encrypted in this record).
The PeopleSoft access ID is the RDBMS ID with which PeopleSoft applications are ultimately connected to your database after the PeopleSoft system connects using the connect ID and validates the User ID and password. An access ID typically has all the RDBMS privileges necessary to access and manipulate data for an entire PeopleSoft application. The access ID should have Select, Update, and Delete access

Users do not know their corresponding access IDs. They just sign in with their user IDs and passwords. Behind the scenes, the system signs them into the database using the access ID.
The connect ID performs the initial connection to the database [RDBMS].Used by 2-tier, App Server, Batch Server to connect the database during Sign-in.

Sunday 29 March 2015

Peoplesoft Database Creation


Peoplesoft Database Creation :-

This first part of the Peoplesoft Database Creation concern the Oracle database creation itself and the Application (including PeopleTools) data.

Peoplesoft provide scripts to create the database, you can find all the required scripts under $PS_HOME/scripts/unix. Because we'll need to modify some of these files, it's better to copy all the files under a working directory, or like me, under $ORACLE_BASE/admin/$ORACLE_SID/create folder.

So, I'll use that ones.
Step 1 to 14 have to be run on the database server.

1. Modify the script createdb10.sql (for the 10g customer), character set and strings :

[oradata/DMOHRMS9/create]$ vi createdb10.sql
set termout on
set echo on
spool createdb.log

startup nomount pfile=$ORACLE_HOME/dbs/initDMOHRMS9.ora
CREATE DATABASE "DMOHRMS9"
MAXINSTANCES 8
MAXLOGHISTORY 1
MAXLOGFILES 16
MAXLOGMEMBERS 3
MAXDATAFILES 100
DATAFILE '/oradata/DMOHRMS9/datafiles/system01.dbf' SIZE 300M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
EXTENT MANAGEMENT LOCAL
SYSAUX DATAFILE '/oradata/DMOHRMS9/datafiles/sysaux01.dbf' SIZE 120M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE '/oradata/DMOHRMS9/datafiles/temp01.dbf' SIZE 20M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
SMALLFILE UNDO TABLESPACE "PSUNDOTS" DATAFILE '/oradata/DMOHRMS9/datafiles/psundots01.dbf' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
CHARACTER SET AL32UTF8
NATIONAL CHARACTER SET UTF8
LOGFILE GROUP 1 ('/oradata/DMOHRMS9/redologs/redo01.log') SIZE 51200K,
GROUP 2 ('/oradata/DMOHRMS9/redologs/redo02.log') SIZE 51200K,
GROUP 3 ('/oradata/DMOHRMS9/redologs/redo03.log') SIZE 51200K;
spool off

2. Create the directories to receive your new database, and your init.ora file.
 
3. Ensure your NLS_LANG env variable is set correctly.


4. Create the password file


5. Add the tns entry for the new database in tnsnames.ora (and listener.ora for fixed addressing)


6. Set the ORACLE_SID, and run the creation database script :
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba

SQL*Plus: Release 10.2.0.3.0 - Production on Sun Jan 6 14:50:12 2008

Copyright (c) 1982, 2006, Oracle. All Rights Reserved.

Connected to an idle instance.

SQL> @createdb10.sql
SQL>
SQL> startup nomount pfile=$ORACLE_HOME/dbs/initDMOHRMS9.ora

ORACLE instance started.

Total System Global Area 767557632 bytes
Fixed Size 1264136 bytes
Variable Size 205522424 bytes
Database Buffers 557842432 bytes
Redo Buffers 2928640 bytes
SQL> CREATE DATABASE "DMOHRMS9"
2 MAXINSTANCES 8
3 MAXLOGHISTORY 1
4 MAXLOGFILES 16
5 MAXLOGMEMBERS 3
6 MAXDATAFILES 100
7 DATAFILE '/oradata/DMOHRMS9/datafiles/system01.dbf' SIZE 300M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
8 EXTENT MANAGEMENT LOCAL
9 SYSAUX DATAFILE '/oradata/DMOHRMS9/datafiles/sysaux01.dbf' SIZE 120M REUSE AUTOEXTEND ON NEXT 10240K MAXSIZE UNLIMITED
10 SMALLFILE DEFAULT TEMPORARY TABLESPACE TEMP TEMPFILE '/oradata/DMOHRMS9/datafiles/temp01.dbf' SIZE 20M REUSE AUTOEXTEND ON NEXT 640K MAXSIZE UNLIMITED
11 SMALLFILE UNDO TABLESPACE "PSUNDOTS" DATAFILE '/oradata/DMOHRMS9/datafiles/psundots01.dbf' SIZE 200M REUSE AUTOEXTEND ON NEXT 5120K MAXSIZE UNLIMITED
12 CHARACTER SET AL32UTF8
13 NATIONAL CHARACTER SET UTF8
14 LOGFILE GROUP 1 ('/oradata/DMOHRMS9/redologs/redo01.log') SIZE 51200K,
15 GROUP 2 ('/oradata/DMOHRMS9/redologs/redo02.log') SIZE 51200K,
16 GROUP 3 ('/oradata/DMOHRMS9/redologs/redo03.log') SIZE 51200K;

Database created.


7. Modify and run the utlspace.sql script (dictionaries views)

[oradata/DMOHRMS9/create]DMOHRMS9$ vi utlspace.sql
-- ******************************************************************

REM * Set terminal output and command echoing on; log output of this script.
REM *
set termout on

REM * The database should already be started up at this point from createdb.sql

set echo off
spool utlspace.log

REM * Creates data dictionary views. Must be run when connected AS SYSDBA
@$ORACLE_HOME/rdbms/admin/catalog.sql;

REM * Creates views of oracle locks
@$ORACLE_HOME/rdbms/admin/catblock.sql;

REM * Scripts for procedural option. Must be run when connected AS SYSDBA
@$ORACLE_HOME/rdbms/admin/catproc.sql;

set echo on

REM * Create a temporary tablespace for database users.
REM *
CREATE TEMPORARY TABLESPACE PSTEMP
TEMPFILE '/oradata/DMOHRMS9/datafiles/pstemp01.dbf' SIZE 300M
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 128K
;

REM * Create a tablespace for database users default tablespace.
REM *
CREATE TABLESPACE PSDEFAULT
DATAFILE '/oradata/DMOHRMS9/datafiles/psdefault.dbf' SIZE 100M
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
SEGMENT SPACE MANAGEMENT AUTO
;

spool off

[oradata/DMOHRMS9/create]DMOHRMS9$
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba
SQL> @utlspace.sql

8. Modify (don't change the PS user name) and run the dbowner.sql script
[oradata/DMOHRMS9/create]DMOHRMS9$ vi dbowner.sql
-- ******************************************************************

set echo on
spool dbowner.log

GRANT CONNECT, RESOURCE, DBA TO PS IDENTIFIED BY PS;
CONNECT PS/PS;
CREATE TABLE PSDBOWNER (DBNAME VARCHAR2(8) NOT NULL, OWNERID VARCHAR2(8) NOT NULL ) TABLESPACE PSDEFAULT;
CREATE UNIQUE INDEX PS_PSDBOWNER ON PSDBOWNER (DBNAME) TABLESPACE PSDEFAULT;
CREATE PUBLIC SYNONYM PSDBOWNER FOR PSDBOWNER;
GRANT SELECT ON PSDBOWNER TO PUBLIC;
CONNECT system/manager;
REVOKE CONNECT, RESOURCE, DBA FROM PS;

spool off
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba
SQL> @dbowner.sql

9. . To create the specific tablespaces (for HRMS hcddl.sql), modify and run hcddl.sql :
[oradata/DMOHRMS9/create]DMOHRMS9$ vi hcddl.sql
-- **************************************************************
REMARK * This script is used to create tablespaces for the PeopleSoft 9 HRMS Products
REMARK * on Oracle UNIX.
REMARK * Date last modified: 01/30/2015

REMARK * NOTE: The sizing of the tablespaces here are only sample sizes that will
REMARK * hold the demo database tables. This is not sized correctly for a
REMARK * production database.

REMARK * Users can choose to use the autoextending tablespace feature.
REMARK * The syntax is at the end of this script.

set echo on
spool hcddl.log

CREATE TABLESPACE AAAPP DATAFILE '/oradata/DMOHRMS9/datafiles/aaapp.dbf' SIZE 21M
EXTENT MANAGEMENT LOCAL AUTOALLOCATE
SEGMENT SPACE MANAGEMENT AUTO
/
[...]
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba
SQL> @hcddl.sql
[...]

You may want to set AUTOEXTEND to ON to avoid space extension problem against the tablespace during the application load.

10. Check and run the database ROLES creation :
 
[oradata/DMOHRMS9/create]DMOHRMS9$ more psroles.sql
-- ******************************************************************

REMARK -- These are the minimum privileges required to run PeopleSoft
REMARK -- applications. If you plan to run SQL<>Secure, you will need to
REMARK -- grant "execute any procedure" to PSUSER and PSADMIN.

set echo on
spool psroles.log

DROP ROLE PSUSER;
DROP ROLE PSADMIN;

CREATE ROLE PSUSER;
GRANT CREATE SESSION TO PSUSER;

CREATE ROLE PSADMIN;
GRANT
ANALYZE ANY,
ALTER SESSION, ALTER TABLESPACE, ALTER ROLLBACK SEGMENT,
CREATE CLUSTER, CREATE DATABASE LINK, CREATE PUBLIC DATABASE LINK,
CREATE PUBLIC SYNONYM, CREATE SEQUENCE, CREATE SNAPSHOT,
CREATE SESSION, CREATE SYNONYM, CREATE TABLE, CREATE VIEW,
CREATE PROCEDURE, CREATE TRIGGER, CREATE TABLESPACE, CREATE USER,
CREATE ROLLBACK SEGMENT,
DROP PUBLIC DATABASE LINK, DROP PUBLIC SYNONYM, DROP ROLLBACK SEGMENT,
DROP TABLESPACE, DROP USER, MANAGE TABLESPACE, RESOURCE,
EXP_FULL_DATABASE, IMP_FULL_DATABASE,
GRANT ANY ROLE, ALTER USER, BECOME USER
TO PSADMIN WITH ADMIN OPTION;

spool off
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba
SQL> @psroles.sql

11. Check and modify if necessary the ceation of the owner of the Peoplesoft objects (psadmin.sql script). Commonly, The admin user is named SYSADM, the default tablespace is PSDEFAULT :
[oradata/DMOHRMS9/create]DMOHRMS9$ more psadmin.sql
-- ******************************************************************

REMARK -- This script sets up the PeopleSoft Owner ID. An Oracle DBA is
REMARK -- required to run this script.

set echo on
spool psadmin.log

ACCEPT ADMIN CHAR PROMPT 'Enter name of PeopleSoft Owner ID: '
ACCEPT PASSWORD CHAR PROMPT 'Enter PeopleSoft Owner ID password:'
PROMPT
PROMPT Enter a desired default tablespace for this user.
PROMPT
PROMPT Please Note: The tablespace must already exist
PROMPT If you are unsure, enter PSDEFAULT or SYSTEM
PROMPT
ACCEPT TSPACE CHAR PROMPT 'Enter desired default tablespace:'


REMARK -- Create the PeopleSoft Administrator schema.

create user &ADMIN identified by &PASSWORD default tablespace &TSPACE
temporary tablespace pstemp;
grant PSADMIN TO &ADMIN;

REMARK -- PeopleSoft Administrator needs unlimited tablespace in order to
REMARK -- create the PeopleSoft application tablespaces and tables in Data
REMARK -- Mover. This system privilege can only be granted to schemas, not
REMARK -- Oracle roles.

grant unlimited tablespace to &ADMIN;

REMARK -- Run the commands below to create database synonyms.
REMARK -- Modify the connect string appropriately for your organization.

connect system/manager

set echo off

@$ORACLE_HOME/rdbms/admin/catdbsyn
@$ORACLE_HOME/sqlplus/admin/pupbld

spool off
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba
SQL> @psadmin.sql

12. Check and modify if necessary the creation script of the security check user people - connector user -, take care the default password is peop1e (1, one, instead of the letter l) :
[oradata/DMOHRMS9/create]DMOHRMS9$ more connect.sql
-- ******************************************************************

REMARK -- This script sets up the PeopleSoft Connect ID.
REMARK -- An Oracle DBA is required to run this script prior
REMARK -- to loading a PSOFT database.
REMARK --
REMARK -- If you wish to use the default CONNECTID and PASSWORD,
REMARK -- then run this script as is.
REMARK -- If you wish to change the default CONNECTID and PASSWORD,
REMARK -- DELETE the default CREATE and GRANT statements below and
REMARK -- uncomment the template version modifying the following
REMARK -- parameters , ,
REMARK --

REMARK -- Create the PeopleSoft Administrator schema.

set echo on
spool connect.log

REMARK -- drop user people cascade;

create user people identified by peop1e default tablespace PSDEFAULT
temporary tablespace PSTEMP;

GRANT CREATE SESSION to people;

REMARK -- drop user cascade;

REMARK -- create user identified by default tablespace
REMARK -- temporary tablespace ;

REMARK -- GRANT CREATE SESSION to ;

spool off
[oradata/DMOHRMS9/create]DMOHRMS9$ sqlplus / as sysdba
SQL> @connect.sql

13. For Unicode database, if you don't want to raise the following error on the application datamover load : ''Character Length Semantics (CLS) is not enabled'' , you may want to add the following line in your parameters file : NLS_LENGTH_SEMANTICS=CHAR, or modify the spfile :
SQL> alter system set NLS_LENGTH_SEMANTICS=CHAR scope=both;


System altered.

14. Lastly, create spfile and bounce your database :

SQL> create spfile from pfile='/apps/oracle/admin/DMOHRMS9/pfile/initDMOHRMS9.ora';

File created.

SQL> shutdown immediate
Database closed.
Database dismounted.
ORACLE instance shut down.
SQL> startup
show parameter ORACLE instance started.

Total System Global Area 767557632 bytes
Fixed Size 1264136 bytes
Variable Size 205522424 bytes
Database Buffers 557842432 bytes
Redo Buffers 2928640 bytes
Database mounted.
Database opened.

Friday 27 March 2015

Change Assistant



Change Assistant:-


Change Assistant Introduction
Change Assistant (CA) was first released in PeopleTools 8.44. Change Assistant (CA) automates many task for applying any bundle, maintenance pack etc. Some benefits of using CA are:
- CA can find out bundles/MPs that have already been applied to a PeopleSoft Database
- CA can figure out Bundles/MPs that need to be applied
- CA can download new bundles/MPs
- CA can determine pre-requisites and post-requisites
- CA can determine the order in which new Bundles/MPs are applied
- CA can migrate bundle/MP project automatically
- CA can generate and execute DDL scripts
- CA can execute Data Mover Scripts
- CA can deploy files such as SQR, COBOL etc to file servers

Environment Management Framework (EMF)
PeopleSoft Environment Management (PSEM) Framework enables CA know about the PeopleSoft installation, configuration, and update information. It is used to obtain the configuration and setup information about PeopleSoft environments (i.e., the files servers, the web servers, the application servers, the process scheduler servers and the individual hosts/machines).
CA uses EMF to apply updates to PeopleSoft installation and configurations by helping in carrying out commands remotely on different machines.
EMF has three core elements:
- Environment Management Agent (PSEM Agent): A Java executable. Only one instance of the agent can run at a given time per physical machine. PSEM Agents are setup on each of the servers. Each PSEM Agent initiates communication to the hub (PSEMHUB) and is assigned a unique peer ID.
- Environment Management Hub (PSEMHUB): A web application that is installed at the time of PIA installation and resides at web server machine. It is started automatically at the time web server is booted up. This hub acts as a broker for all communication between peers. It gathers and reports on the environment information sent to it by PSEM Agents.
- Environment Management Viewer (PSEM Viewer): A command line tool that helps users view data that is retrieved from the PSEMHUB.
Before using Change Assistant (CA) for applying bundles/MPs, EMF should be configured and PSEMAgent should be started up on all the servers.

Change Assistant Validation
Make sure the HUB is up and running before starting EMAgents. Before starting the PSEMAgents – complete tasks below:
Web Server Specific: Delete the following directories:
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\PersistentStorage
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\scratchpad
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\environment
$PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data\proxies
Except data.txt, delete other files from directory $PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB\envmetadata\data

Agent Specific: Delete the following directories on Linux machine:
$PS_HOME\PSEMAgent\envmetadata\data\ids
$PS_HOME\PSEMAgent\envmetadata\PersistentStorage
$PS_HOME\PSEMAgent\envmetadata\scratchpad
$PS_HOME\PSEMAgent\envmetadata\transactions (If it exists)
Except matcher.xml, delete other files from directory $PS_HOME\PSEMAgent\envmetadata\data

Viewer Specific: Delete the following directories on Linux and NT machines:
$PS_HOME\PSEMViewer\envmetadata\data\ids
$PS_HOME\PSEMViewer\envmetadata\PersistentStorage
$PS_HOME\PSEMViewer\envmetadata\scratchpad
$PS_HOME\PSEMViewer\envmetadata\transactions (If it exists)

Change Assistant Specific: Delete the following directories on the machine where Change Assistant being setup:
$PS_HOME\PSEMAgent\envmetadata\data\ids
$PS_HOME\PSEMAgent\envmetadata\PersistentStorage
$PS_HOME\PSEMAgent\envmetadata\scratchpad
$PS_HOME\PSEMAgent\envmetadata\transactions (If it exists)
Except matchers.xml, delete other files from directory $PS_HOME\PSEMAgent\envmetadata\data
Now start the PSEMAgent on each of the Application Server and Process Scheduler machines, which includes Linux as well as Windows machines.
Make sure EMAgents are running before using Change Assistant to validate the Environment Management Hub (PSEMHUB)

Change Assistant Setup
To start with, identify an environment that will act as a PSEMHUB.
Configure PSEHMHUB
To start with, identify an environment that will act as a PSEMHUB. In case of a single server configuration for PIA, the PSEMHUB is started whenever we start PIA… and uses the same http post as the PIA.
Let’s say if the PIA URL is:
http://ws1_ip:9081/site/signon.html, the hubURL will be http://ws1_ip:9081/PSEMHUB/hub (Format of hubURL is: http://[server_name]:[port]/PSEMHub/hub )
To configure PSEMHUB:
- Go to below directory (of web server machine) $PS_HOME/webserv/DOMAIN_NAME/applications/peoplesoft/PSEMHUB/envmetadata/config
- Edit “configuration.properties” for hubURL, agentport (must be unique) and windowsdrivestocrawl or unixdrivestocrawl.
hubURL=http://ws1_1p:9081/PSEMHUB/hub
unixdrivestocrawl=/u02/pt848
or
windowsdrivestocrawl=D:\pt848

Configure PSEM Agent
To configure PSEM Agent:
- Go to $PS_HOME/PSEMAgent/envmetadata/config
- Edit “configuration.properties” for hubURL, agentport (must be unique) and windowsdrivestocrawl or unixdrivestocrawl.

Once PSEM Agent is configured, start the PSEM Agents in App Server machine, Process Scheduler Server machine, File Server machine, NT machine where CA is configured:
$PS_HOME/PSEMAgent/StartAgent.sh (in Unix) $PS_HOME/PSEMAgent/StartAgent.cmd (in Windows)

For the first time, start the PSEMAgent with recrawl command - so that it crawls the drives to identify the environment components (all servers):
$ $PS_HOME/PSEMAgent/StartAgent.sh recrawl (in Unix)
$PS_HOME/PSEMAgent/StartAgent.cmd recrawl (in Windows)

After recrawl is done, start PSEMAgent normally.
$ $PS_HOME/PSEMAgent/StartAgent.sh recrawl (in Unix)
$PS_HOME/PSEMAgent/StartAgent.cmd recrawl (in Windows)

Before doing so, you may want to modify the StartAgent.sh file in unix using nohup command - so that EM Agent keeps running even if we exit from unix box… To modify the StartAgent.sh, open it in vi editor and update the last line as:

nohup ../jre/bin/java com.peoplesoft.pt.environmentmanagement.agent.Agent $1 &

Save and exit.
Execute $./StartAgent.sh

Setup Change Assistance
Now, that we have done with the configuration of PSEMHUB and PSEM Agent – next step would be to setup Change Assistance.

Open the Change Assistance, and go to Tools -> Options:
- Select “Apply Application Update” as Change Assistant Mode
- Download directory is where we have downloaded the bundle or MP zip files
- Staging directory is the one which CA will use as a stage - it will extract zip files from Download directory to Staging Location and will use contents in this directory for processing
- Output directory is the one where CA will keep all the output files generated during implementation of a bundle or MP

Go to Tools -> Options -> Environment Management Tab:
- Server Host: enter the IP address of PSEMHUB machine
- Server Port: enter the Port Number at which PSEMHUB is configured
- Click Ping to check the connection
- Click View to see the Environment Management Hub Summary – it shows all the environments name and availability of their server components.
Go to Tools -> Scan Configuration:
Go to Tools -> validate:

Apply Change Packages (Bundles or MPs)

Go to Tools -> Apply Change Package:
- Next screen will show the installed environment found
- Select the target environment here
- Going ahead CA will ask for entering User ID (PeopleSoft User) and Access ID, Apply Directory (Download directory) etc.
- CA will show the list of all the change packages available at the above mentioned download directory as illustrated below
- Next, CA asks for the method to apply DB Build Scripts – I choose Manually option
- Next, CA shows the confirm selection screen where it summarizes to be applied MP or Bundle details
- Click Validate now
- Click Begin Apply

In Progress…
Next screen appears and I start applying the MP or Bundles now.

The purge process did not run because the Oprid configured to start the Process Scheduler did not have the required permissions to run the purge process.

  Purge process - Required permissions The PeopleSoft Oprid used to start the Process Scheduler, as defined in the Scheduler's psprcs.cf...