header

PeopleSoft Load Balancer Implementation (F5)


STEPS:
--------
1)Configured two Weblogic domains servers with SSL(Refer to Weblogic HTTPS implementation in my old blog)

2)Make two weblogic domains as https:\\servername:80 to get the PS login page
This can be done by creating a soft link to redirect Weblogic admin console page from weblogic to signin.html page.So, when the servername with port is called it gives the PS login page instead of console page

3)Now the F5 device has to be configured with pool with load balanced server name and listening port Eg.,https:\\servername1:80 and https:\\servername2:80.

4)We have to NFS mount a common share such as /reports between Web Domain hosting servername1 and servername2.Configure two web servers with same report repository path as /reports - This is needed because when User hits F5 he will be redirected to any one of the servername 1 or servername2.Lets say he connected to servername1 from F5 and runs report it gets posted to the /reports NFS mount and it available and readable from both servername1 and servername2.Now after some time he login and if he landed on server2 he will still see the report from report repository as /report is a NFS from available from both load balanced servers through F5.

5)Set the Report Node as ABC.xinc.com with port 80 and mode as HTTPS>make sure the F5 load balancer time out value more than the PS timeout otherwise you will see session bounce between different web server.

6)If you are using REN and need SLL configure refer the old blog with REN SSL implementation.Baically We need to Import SSL in to Database to make the REN SSL work.

7)Now yo have two option of choosing session stickiness on the F5 for the connection established session.
    a)Server Ip - Session will lose connection when one of the weblogic is down and we have to relogin and reconnect to connect to second active webserver throuch F5.But the instance will be up and running for new session, it is only issue with connected session.
     b)Cookies enable  - PS Authenticated cookie will be caught on the browser and it will reconnect to active web domain without re - connection .To do this follow below


*********************************************************************************
HOW TO SET PEOPLESOFT COOKIES ENABLED FOR F5 LOAD BALANCE WITH COOKIES ENABLED  STICKY SESSION

---> For customers that use a load balancer, Oracle recommends using a cookie (session) based load balancer and sticky bits enabled.  Please consider using cookie insertion and ensure that load balancer's cookie is configured to be in the same domain as PeopleSoft's authentication domain. Contact your load balancer vendor on how to use the load balancer's cookie insertion.  IP based load balancing is not recommended and IP based load balancing is known to cause session stickiness problems.  Here is one example where IP based load balancing will cause problems: Note 949387.1

DNS Round Robin is not recommended and customer should use cookie based load balancing.

For more information on cookie based load balancing and sticky bits, please follow up with your load balancer vendor.

Vendor URL's for Setting up their Load Balancers with the PeopleSoft Application:

Deploying F5 With PeopleSoft Enterprise Applications

Note: The F5 document referenced recommends "content compression" enabled on the F5, however this can prevent output docs from being opened from the Process Monitor or Report Manager. Disabling F5's "content compression" can resolve the issue of not being able to view reports.
 Cisco Application Networking for PeopleSoft Enterprise Deployment Guide

Questions on the above documents need to be directed to the third party vendor that created these instructions.

---> Ensure all your webservers have the same cookie name in each weblogic.xml file.  This file can be found in the following directory:

/webserv//applications/peoplesoft/PORTAL/WEB-INF/weblogic.xml

In this example, there's two webservers behind the load balancer. Therefore, verify that your cookie names are the same:

weblogic.xml (webserver 1):

CookieName
pststweb-7011-PORTAL-PSJSESSIONID  <--- this name have to be same on both web server

weblogic.xml (webserver 2):

CookieName
pststweb-7011-PORTAL-PSJSESSIONID   <--- this name have to be same on both web server

Save both weblogic.xml files.

Note:  If you're running Enterprise Portal and have content providers, please ensure that all Enterprise Portal webserver cookie name are all exactly the same. The content provider's webserver cookie names should have their own set of cookie names. Therefore, both Portal and content should not have the exact same cookie name. Suppose Enterprise Portal had 4 webservers and HR had 4 webservers. All 4 Enterprise Portal cookie names could be eportal-7011-PORTAL-PSJSESSIONID, but all 4 HR cookie names could be hrms-7011-PORTAL-PSJSESSIONID.  In addition, node URI should point to the load balancer URL, not individual webservers directly.


---> In weblogic.xml, ensure CookieDomain is set in all weblogic.xml. This value is automatically set when entering the authentication domain during the PIA install. If the authentication domain isn't set during PIA install, please reinstall PIA and set authentication domain.  Please see Note 885452.1 for more information on setting/changing cookiedomain.

---> In PIA, navigate to "PeopleTools -> Web Profile -> Web Profile Configurations". Search for your Web Profile. Click on

Virtual Address and populate your default addressing. For example, suppose your end users access your load balancer with the following URL:@ http://mycompany.com/ps/signon.html You would need to set the following:

Default addressing Protocol: HTTP
Default addressing Name: mycompany.com
Default addressing Port: 80

* The above is an example. You'll need to populate with your load balancer info.

It is required that the load balancer and PeopleSoft WebLogic web servers are in the same domain.

---> Please ensure PIA "Inactivity Logout" in seconds matches HTTP timeout in minutes.

a) In PIA, navigate to "PeopleTools -> Web Profile -> Web Profile Configurations". Search for webprofile. Click on "Security" tab. PIA timeout is "Inactivity Logout" in seconds. Suppose "Inactivity Logout" = 1200 seconds.

b) In WebLogic, open web.xml file.  This file can be found in the following directory:

/webserv//applications/peoplesoft/PORTAL/WEB-INF/web.xml

WebLogic HTTP timeout appears in minutes:

20

In this example, ensure WebLogic HTTP timeout is 20 minutes to match "Inactivity Logout" (1200 seconds).

The Load Balancer's timeout should be higher than the PIA "Inactivity Logout" timeout and webserver HTTP timeout. Please consult with load balancer vendor to find out where to set load balancer timeout.

---> After updating weblogic.xml, web.xml and webprofile, you must bounce your webservers. 

For Radware load balancers the setting "Sessions Mode" has several options. Set to "Regular" which tells the load balancer to keep users sessions on the web server that they logged on to initially to maintain session persistence.
 If you have completed all these steps and still experience intermittent problems, it's likely that your load balancer is not maintaining session stickiness.  Please review the document below  for additional troubleshooting.

E-PIA: How To Identify Session Stickiness Problem On Load Balancer? (Doc ID 1307344.1)
*********************************************************************************


PeopleSoft New Menu Navigation

PS Applications prior to 9.1 release, that the horizontal menu is disabled by design and the left hand menu is preferred. Please see the below KM document
E-PORTAL: PeopleTools 8.50 - Left Hand And Horizontal Floating Menu Supportability In Pre & Post 9.1 Applications. (Doc ID 1110623.1)


To enable Drop down menu, navigate to:

1. Main Menu PeopleTools > Portal > General Settings
2. Reconfigure the following: Update the Navigation Type from "Left" to "Drop-down"
3. Save the General Settings page.
4. Click Home link or Sign out 
5. Sign in and check the navigation type

How to restart Application Server process(PSREN,PSAPPSERV etc.,) with out restarting the Application server


The below steps will help to restart the specific process of application server if we made change to process and user logged in to the production system.The below option will reboot only the specific PeopleSoft application server process eg., PSRENSERV,PSAPPSERV etc while the application server is up and running....

PeopleSoft Domain Administration
Domain Name: PSXX89

1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit

Command to execute (1-10, q) : 3
PeopleSoft Domain Status Menu
Domain Name: PSXX89

1) Server status
2) Client status
3) Queue status
q) Quit

Command to execute (1-3, q) [q]: 1
Loading command line administration utility ...
tmadmin - Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.

Prog Name Queue Name Grp Name ID RqDone Load Done Current Service
--
---------
PSSUBDSP SUBDQ_dflt PUBSUB 300 0 0 ( IDLE )
BBL 63085 chqpvuu+ 0 7649 382450 ( IDLE )
PSAPPSRV APPQ APPSRV 1 84 4200 ( IDLE )
PSANALYTICSRV 00080.00001 ANALYTI+ 1 0 0 ( IDLE )
PSSUBHND SUBHQ_dflt PUBSUB 301 0 0 ( IDLE )
PSMONITORSRV MONITOR MONITOR 1 0 0 ( IDLE )
PSWATCHSRV WATCH WATCH 1 0 0 ( IDLE )
PSAPPSRV APPQ APPSRV 2 81 4050 ( IDLE )
PSANALYTICSRV 00080.00002 ANALYTI+ 2 0 0 ( IDLE )
PSANALYTICSRV 00080.00003 ANALYTI+ 3 0 0 ( IDLE )
JREPSVR 00094.00250 JREPGRP 250 11 550 ( IDLE )
PSQRYSRV QRYQ APPSRV 70 0 0 ( IDLE )
PSQRYSRV QRYQ APPSRV 71 0 0 ( IDLE )
JSL 00095.00200 JSLGRP 200 0 0 ( IDLE )
PSPUBDSP PUBDQ_dflt PUBSUB 200 0 0 ( IDLE )
PSPUBHND PUBHQ_dflt PUBSUB 201 0 0 ( IDLE )
PSBRKDSP BRKDQ_dflt PUBSUB 100 0 0 ( IDLE )
PSSAMSRV SAMQ APPSRV 100 0 0 ( IDLE )
PSRENSRV RENQ1 RENGRP 101 0 0 ( IDLE )
PSBRKHND BRKHQ_dflt PUBSUB 101 0 0 ( IDLE )

Go into server status and you will see the PSRENSRV line. he third column and the value of the Group process.For example if we need to bounce PSREN server only then the group is "RENGRP". Take that value and do the following:

PeopleSoft Domain Administration
Domain Name: PSXX89

1) Boot this domain
2) Domain shutdown menu
3) Domain status menu
4) Configure this domain
5) TUXEDO command line (tmadmin)
6) Edit configuration/log files menu
7) Messaging Server Administration menu
8) Purge Cache
9) Preload File Cache
10) Clean IPC resources of this domain
q) Quit

Command to execute (1-10, q) : 5
Loading command line administration utility ...
tmadmin - Copyright (c) 1996-1999 BEA Systems, Inc.
Portions * Copyright 1986-1997 RSA Data Security, Inc.
All Rights Reserved.
Distributed under license by BEA Systems, Inc.
Tuxedo is a registered trademark.

shutdown -g RENGRP

Shutting down server processes ...

Server Id = 101 Group Id = RENGRP Machine = xxxxxx: shutdown succeeded
1 process stopped.

boot -g RENGRP
INFO: BEA Tuxedo, Version 9.1, 64-bit, Patch Level 036
INFO: Serial #: 650522264137-2065448083901, Expiration NONE, Maxusers 1000000
INFO: Licensed to: Oracle-Peoplesoft-ISV

Booting server processes ...

exec PSRENSRV -A -- -C psappsrv.cfg -D PSXX89 -S PSRENSRV :
process id=778302 ... Started.
1 process started.

PSUNX process scheduler redirect to look for cobols in a non-default location and RCCBL remote call

You can have cobols being looked at different directory on Unix by modifying the following parameters in the following files, then clear caches and restart the process scheduler and the application server.


A) For the process scheduler
------------------------------------

1 ) psprcs.cfg
CBLBIN=%PS_HOME%/CBLBIN%PS_COBOLTYPE%
if the CBLBIN does not exist in the psprcs.cfg , simply you can add this parameter

2) psprcsrv.ubx
{UNIX}
COBPATH={$PS_HOME}/cblbin


3) Clear cache and restart the process scheduler



B) For the Application server to run the remote cobol

-------------------------------------------------------------------
1) psappsrv.cfg
; UNIX:
RCCBL PRDBIN=%PS_HOME%/cblbin

2) psappsrv.ubx
{UNIX}
COBPATH={$PS_HOME}/cblbin

3) Restart application server.

PeopleSoft Installaton script order for new environment creation

CHANGE AND ON SCRIPTS createdb10.sql, rollback.sql,epddl.sql,ptddlupg.sql,ptddl.sql,utlspace.sql ,ts841.sql TO THE APPROPRIATE VALUES FOR  DATABASE STANDARD



All the scripts will be available on PS_HOME\scripts\NT after the Peoplesoft application installation
1)createdb10.sql-- creates database (Change the database name and file locatoin)
2)rollback.sql -- created rollback segnemt .
3)epddl.sql -- Creates PeopleSoft metadata tools tablespace and PS application data tablespace (Change the datafiles location in the script for server standard)
4)ptddlupg.sql -- Creates additional metadata tools tablespace.Ignore error tablespace already exists (Change the datafiles location in the script)
5)ptddl.sql -- Creates additional metadata tools tablespace.Ignore error tablespace already exists (Change the datafiles location in the script)
6)utlspace.sql -- Creates temp tables and Runs catalog,cataproc,catablock for loading oracle metadata ( Change datafiles location and script path)
7)ts841.sql -- Creates additional metadata tools tablespace.Ignore error tablespace already exists (Change the datafiles location in the script)
8)dbowner.sql -- creates user PS and PSDBOWNER table/synonym (change oracle system password in script to connect)
9)connect.sql -- creates user people

10)psrole.sql -- creates two roles PSUSER and PSADMIN

11)psadmin.sql -- Enter user name as “sysadm” and password “sysadm” when prompts. This script also runs catdbsyn/pupbld (change oracle system password in script to connect)

12)upstats.sql -- runs the DB statistics after data load from data mover


Then load the data from datamover



COBOL custom path compilation different from PS HOME

Create a custom directory called "TEST".Copy all the cobol source code to to this directory and also copy the setup folder to this TEST directory.Follow the below steps to generate the .gnt executables in the custom target path from custom souce path




C:\Documents and Settings\svc_psoft>set PS_HOME=d:\psoft\TEST

C:\Documents and Settings\svc_psoft>set path=D:\psoft\TEST\src\cbl\win32;%path%

C:\Documents and Settings\svc_psoft>set COBROOT="D:\Program Files\Micro Focus\Net Express 5.0\Base"

C:\Documents and Settings\svc_psoft>d:

D:\>cd %PS_HOME%\setup

D:\pt849gbl\FINGRPT\setup>cblbld c: \temp

Commands to test COBOL server express

$PS_HOME/bin> ./ptpdbtst
$PS_HOME/bin> cobrun
$PS_HOME/bin> cob -v
$PS_HOME/bin> cob -V
$PS_HOME/bin> ls -l PSRUN*

Oracle cold backup database refresh

1.  Prepare controlfile creation script.  This can be done by
alter database backup controlfile to trace as '/export/home/oracle/ctlfile.sql';
2.  View the edit ctlfile.sql, so that it should contain the following
CREATE CONTROLFILE SET DATABASE "UATDB" RESETLOGS NOARCHIVELOG
  MAXLOGFILES 16
  MAXLOGMEMBERS 3
  MAXDATAFILES 100
  MAXINSTANCES 1
  MAXLOGHISTORY 453
LOGFILE
  GROUP 1 '/u01/oradata/UATDB/redo01.log' SIZE 200M,
  GROUP 2 '/u02/oradata/UATDB/redo02.log' SIZE 200M,
  GROUP 3 '/u03/oradata/UATDB/redo03.log' SIZE 200M
-- STANDBY LOGFILE
DATAFILE
  '/u01/oradata/UATDB/system01.dbf',
  '/u01/oradata/UATDB/undotbs01.dbf',
  '/u01/oradata/UATDB/users01.dbf',
  '/u01/oradata/UATDB/data01.dbf',
  '/u01/oradata/UATDB/tools01.dbf',
  '/u01/oradata/UATDB/perfstat01.dbf',
  '/u01/oradata/UATDB/sysaux01.dbf'
CHARACTER SET WE8ISO8859P1
;
3. Gernerate script to create TEMP tablespace
set long 2000
select DBMS_METADATA.GET_DDL('TABLESPACE','TEMP') from dual;
4. Shutdown UATDB cleanly
shutdown immediate
5. Copy the cold backup files from production to UAT box.
6. Start the database in nomount state

startup nomount
7. Run the create control file script
@/export/home/oracle/ctlfile.sql
8. Open the database with resetlogs
alter database open resetlogs;
9. Create temp tablespace from the script generated from step 3:
CREATE TEMPORARY TABLESPACE "TEMP1" TEMPFILE
'/u01/oradata/UATDB/TEMP01.dbf' SIZE 5242880000
EXTENT MANAGEMENT LOCAL UNIFORM SIZE 1048576

PeopleSoft database refresh steps

Below are steps can we followed for pre and post refresh of PeopleSoft application environment.Please also  copy the SQR,COBOL,Crystal for file object refresh.


  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:
    -- Author: Brent Martin, ERP Associates Inc.
    -- Date: February 10, 2006
    -- 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.

Windows COBOL compilation(Net Express)

Below are the commands to compile cobol on windows.The .gnt files - executable version of cobol will be generated after compilation and copied to CBLBINU for unicode version and CBLBIN for non unicode . Adjust the paths as necessary.


set PS_HOME=c:\pshome\hcm90

set PATH=%ps_home%\src\cbl\win32;%path%

set COBROOT="c:\program files\micro focus\net express\base"

cd %PS_HOME%\setup

cblbld c: \temp\compile

(make sure you have a space between the c: and the \temp\compile)

Here is the output:

ASCII Cobol Compilations Proceeding

Creating Directory c:\temp\compile

Logging progress to file c:\temp\compile\CBLBLD.LOG

COBOL compiler found in “c:\program files\micro focus\net express\base”  -- note the " and space

The system cannot find the path specified.

Target directory (c:\pshome\hcm90\CBLBINA) exists and is writable



Copying source files …

useful EXCEL formula to generate SQL DDL/grant scripts

TO generate update script:

---------------------------
Enter the formula as below to generate the multiple statement and drag colums to generate DDL statements
=CONCATENATE($E$3,A2,"';")
Where
$E$3 Excel cell -->update psoprdefn set operpswd = ' ' where oprid='  (or similar insert statement)
A2 Excel  cell --> list table names or user name
“’;” --> is a string


To Generate role and permision and grants
----------------------------------------------
="grant select, update, delete, insert on " & A1 & " to user_role;"
="create public synonym " & A1 & " for sysadm." & A1 & ";"


Where
& A1 & Excel column  contains the table list