How to Disable Browser Caching in PeopleSoft

A browser will cache various pages and states in memory to increase performance. It may be necessary to disable these performance features on the browser for security reasons. Note that once caching is disabled, the Back button on the browser stops working in PIA.
To disable caching:
1. In PIA, navigate to PeopleTools, Web Profile, Web Profile Configuration.
2. Select the web profile that you want to configure; for example, PROD.
3. Select the Caching page.
4. Make sure that the "Cache Generated HTML" and "Cache Homepage" check boxes are both cleared.
5. Save your changes

Using Putty with XManager

 

1.Installing and Starting Xmanager
Download the Xmanager and install the software on windows machine where graphical display is required. After installation is complete, go to Start > Programs > Xmanager3 > Xmanager – PassiveThis will start the Xmanager is passive mode and xmanager will run in background.

2.Configuring PuttyGo to Session and enter the hostname of the server. Make sure SSH is chosen as Connection Type.

Go to SSH – X11 and Enable X11 forwarding. In X display location,enter localhost:0. Hit Open.

3. Using putty for graphical display
Login into the server and start xclock. Output will be a graphical clock displayed on the local windows machine.

PIA login page shows intermittent behaviour

After entering the login details on the PeopleSoft PIA page, browser shows blank page and URL keeps on blinking intermittently in the address bar at the bottom
------------------------------------------------------------------------------------------

Below steps are suggested to resolve this issue.
1. Please make sure the system time of the local client machines is correct and synchornized with PeopleSoft Server. In case the time difference is more than session time out set at webserver ,user IE will keep on looping after the login screen.
2. In your browser, check the Internet Options > Connections > Lan Settings and see whether there is any proxy server specified there.
3. Try setting Security Medium-low for local intranet, Low for trusted sites.
4. Add the Authentication Domain into the Exceptions for use of the Proxy. In IE, > Connections> LAN Settings > set the *.AuthDomain to Proxy Exceptions.
5. Disable all browser popup blockers.
6. Go to Tools > Internet Options > Advanced and Hit Restore Defaults.

What is a Peoplesoft Connect ID ?

What is a PeopleSoft connect id?PeopleSoft connect id is a very important peoplesoft database id which is required for initial connection to database in PeopleSoft. It replaces the old concept of having database userid for every peoplesoft user id. A connect Id is a valid user ID that, when used during sign in takes the place of Peoplesoft User Id.
Where is connect ID used?
As mentioned above, peoplesoft connect Id is used for initial authentication with peoplesoft database. We require connect Id whenever we need to configure application server, process scheduler and configure 2 tier client like peoplesoft application designer and data mover. If connect id is not mentioned correctly you will face error while starting application server,process scheduler server & will be unable to login in app designer or data mover.

Application Server: Connect Id is entered when choosing "Configure this domain" option for any application server domain using psadmin utility.
Connect Id can also be entered directly in application server configuration file psappsrv.cfg for the domain being configured. After making changes to psappsrv.cfg file , appserver needs to be configured again using psadmin so that psadmin picks up new settings as mentioned in "psappsrv.cfg" file.
Process Scheduler Server: Similar to application server configuration, connect id is used in process scheduler configuration as well. Connect Id can be entered in process scheduler configuration file "psprcs.cfg" as well.
2 tier client eg. PeopleSoft Application Designer, Data mover: As these 2 tier clients also connects with database so connect id is also required to be configured for these. To configure this we need to go to the configuration manager which can be accessed via installed peopletools workstation. Enter values of connect id and password on the startup tab of peoplesoft configuration manager.
If you don't specify connect id , system will assume that you are trying to access peoplesoft using 3 tier access. Learn how to setup 3 tier connection in peoplesoft.

How to create a connect Id?
While creating a new database, connect id is created using connect.sql script which is present in PS_HOME\scripts\nt\ folder. By default 'people' is connect id, although a new connect id can be created any time later.

What are the permissions required for connect id?
For initial connection with peoplesoft database, connect id needs to have read only access to three major peoplesoft tables i.e PSSTATUS, PSOPRDEFN and PSACCESSPRFL. Usually this access is also granted as part of database installation using grant.sql which is also present in PS_HOME. You can also grant access by running the below commands.
GRANT SELECT ON PSACCESSPRFL to people;
GRANT SELECT ON PSSTATUS to people;
GRANT SELECT ON PSOPRDEFN to people;

Refresh and CleanUp the Environment Hub (PSEMHUB)

1. Symptoms
Java errors may occur when running jobs in Change Assistant, such as:

"Exception Java.lang.NullPointerException Caught in
Com.peoplesoft.pt.environmentmanagement.peer.PeerSupport.send()"

2. Cause
This is caused by corruption of Change Assistant's internal cache files.

3. Solution
To Clean up the PSEMHUB cache data you also need to ensure that you delete data from all the Agents and the Peers, you cannot just delete data from the PSEMHUB server.

You need to perform this cleanup on all Agents, Change Assistant (CA), Viewer and HUB, that will reinitialize everything for you.

a.) Make sure you stop the Agents, CA, Viewer, HUB before you delete these files or directories. After that you can restart them.

b.) For Agents, Viewer and Change Assistant:

Delete the following directories, under PS_HOME\PSEMAgent for Agents, under PS_HOME\PSEMViewer for the Viewer and under the Change Assistant directory for Change Assistant.

envmetadata/PersistentStorage
envmetadata/scratchpad
envmetadata/data/ids
envmetadata/transactions (if it exists)

For Agents and Change Assistant delete the following file:

envmetadata/data/search-results.xml

c.) For HUB

Delete the following directories under PS_HOME\webserv\peoplesoft\applications\peoplesoft\PSEMHUB
if your domain name is not 'peoplesoft' then change the above directory accordingly.

PSEMHUB\envmetadata\Scratchpad
PSEMHUB\envmetadata\PersistentStorage
PSEMHUB\envmetadata\transactions (if it exists)

Also delete all files and directories within:
PSEMHUB\envmetadata\data\*.* (files and directories.don't delete the data directory itself)

How to delete a process scheduler server definition

There is no delivered method to delete a process scheduler server definition from the PeopleSoft system tables. It will need to be done manually.

To remove it in process monitor, the following command should be issued:

delete from PSSERVERSTAT where SERVERNAME = ;

If the server definition has not been used and needs to be removed entirely, then use the following SQL.

delete from PS_SERVERCLASS where servername = ;
delete from PS_SERVEROPRTN where servername = ;
delete from PS_SERVERDEFN where servername= ;

Server definition that has been used, needs to be removed from the following tables as well
PS_SERVERACTVTY
PS_SERVERMESSAGE
PS_SERVERNOTIFY
PS_SERVERPURGLIST
PSPRCSQUE
PS_CDM_TRANSFER
PSPRCSRQST
This resolution for PeopleTools 8.4 and above.

Cloning a PeopleSoft Database

One of the most common tasks of a PeopleSoft administrator or DBA is to clone a development or test database from a production database. Here are some of the steps you'll want to consider when refreshing PeopleSoft databases that are running PeopleTools 8.4x.
Note:  I'm sure this list isn't complete for every installation and it can certainly be improved, but that's the purpose of this Wiki -- Please incorporate your corrections, comments or suggestions so everyone can benefit. For purposes of discussion, the source database will be production, and the target database will be the dev/test database that you're overlaying.

1. Export any security that you need to preserve from the target database to a flat file. Data Mover is a nice tool to use for this since you can qualify each table with a list of operator ID's to export. The tables you should consider exporting for specific users are PSOPRDEFN, PSOPRALIAS, PSROLEUSER, PSUSERATTR, PSUSEREMAIL, PSUSERPRSNLOPTN, PS_ROLEXLATOPR and PS_RTE_CNTL_RUSER.

2. Stop the target application environment, including application servers and process schedulers. Stopping the web server is optional since it doesn't connect directly to the database. Be sure to clear cache.
3. Overlay the target database with a recent backup of the Production database. The exact process will differ for your database platform, but your DBA should be able to do this with minimal direction.
4. After the database comes back on-line, set DBNAME in PSDBOWNER back to the target database name.
5. Set GUID to ' ' in the PSOPTIONS table. This will cause PeopleSoft to generate a new GUID so that change assistant can track it separately from the source database.
6. Delete the data from the reporting tables, process scheduler tables and application messaging tables since this data isn't relevant in the target database. Run prcsclr.dms, rptclr.dms and appmsgpurgeall.dms. In addition, I also delete from the report manager tables PSRF_RATTR_TBL; PSRF_RSCRTY_TBL; PSRF_RINFO_TBL; and delete from PSRF_FINFO_TBL where PSRF_PRNT_FLDR_ID <> 0;
7. If you have a script to reset everyone's e-mail address to a pre-defined value so that workflow messages from the Test environment don't get sent to real users, run it now. It should update the PSUSEREMAIL and PS_ROLEXLATOPR tables.
8. Log on to the target database with data mover and run the following command to set the SYSADM password and any other back to it's pre-refreshed value:
Purpose: Reset application passwords and purge PeopleTools tables after a database refresh so that
-- the application can be started with minimal reconfiguration.
-- Compatibility: This works with PeopleTools 8.4x releases
-- Notice: This script modifies data in your PeopleSoft database. It changes account passwords, and
-- it deletes data from process scheduler, report repository and integration broker tables.
-- It as provided for reference purposes only. Use it at your own risk.
set log c:\temp\dbrefresh.log;
-- Change Access Password (SYSADM)
CHANGE_ACCESS_PASSWORD SYSADM1 CHANGEME1;
-- Change Application Password (PSAPPS)
update psoprdefn set OPERPSWD = 'changeme1', encrypted = 0 where oprid = 'PSAPPS';
encrypt_password PSAPPS;
-- Set GUID to blank so PSEMAgent and Change Assistant doesn't get confused
update psoptions set guid = ' ';
-- Purge Process Scheduler
RUN h:\fdmo881\scripts\PRCSCLR.DMS;
-- Purge Report Repository Tables
RUN h:\fdmo881\scripts\RPTCLR.DMS;
-- Purge Application Messaging RUN h:\fdmo881\scripts\APPMSGPURGEALL.DMS;
9. Import the security that you exported in step 1.
10. While you're in data mover, change the user passwords that are configured in your application server, process scheduler, and integration broker configurations back to the pre-refresh values:
update psoprdefn set OPERPSWD = 'devpswd', encrypted = 0 where oprid = ('PSAPPS');
encrypt_password PSAPPS;
update psoprdefn set OPERPSWD = 'devpswd', encrypted = 0 where oprid = ('PTWEBSERVER');
encrypt_password PTWEBSERVER;
11. Clear application server, web server and process scheduler cache if you haven't already done it. Start the target application environment.
12. Log on through the web front end.
13. Update the Report Node configuration and verify your Process Scheduler Servers are using the correct configuration. Make any Web Profile changes if needed.
14. Navigate to PeopleTools > Utilities > Options and update the database name and description.
15. Change password rules as appropriate for a development environment.
16. Change your default local node if it should be named differently than the default local node from the source database. If it's not named differently, you may be at risk for a single sign-on vulnerability.
17. Reconfigure attachment servers (if used)
18. Reconfigure REN servers and clusters if the application server didn't configure it correctly at startup.
19. Make sure you copy all of the batch objects (SQR's, Crystal Reports, COBOL programs, etc.) from your source to your target environment to keep the environment in synch. Don't forget to do this on both UNIX and Windows servers.
20. Perform some sanity checks to make sure the environment is behaving itself before you let users back into it. At a minimum you should verify you can log on and run a report. Verify the report runs to completion, posts, and allows you to view the report without having to sign in a second time.