On The Peoplesoft Road

On The Peopleso Road: Peopleso database connec vity part 3/3 ...
1 of 5
More
Next Blog
Create Blog
h p://gasparo o.blogspot.in/2010/03/peopleso databaseconnect...
Sign In
On The Peoplesoft Road

Oracle & PeopleSoft administration tasks
Nicolas Gasparotto
Amsterdam, Netherlands
Sunday, March 28, 2010
Peoplesoft database connectivity part 3/3 : Apps/Batch/Pia
Contact me
After DataMover and AppDesigner, last part of the Peoplesoft database connectivity, this one devided in 4 parts : the application server, the process
scheduler, the PIA and finally the front end user connections.
Once again, all these tests will require a level trace settings, but only on server side. The files generated will be only on server, under
$PS_CFG_HOME/appserv/domain_name/LOGS and $PS_CFG_HOME/appserv/prcs/domain_name/LOGS.
View my complete profile
Note : all the tests below have been done from a W2k8 64bit workstation, on Peopletools 8.50.02 , Peoplesoft OVM database server (Peopletools
8.50.02/HCM9.1), Peoplesoft App/Batch server (Peopletools 8.50.02) and Peoplesoft PIA server (Peopletools 8.50.02).
Pages
1. The Application server connection

To determine how the connection is working, we'll set the trace file in the configuration file psappsrv.cfg as following :
Home
Peoplesoft Installs
Peoplesoft OVM
Peoplesoft and Active DataGuard
Peoplesoft plugin for OEM
About
;=========================================================================
; Server Trace settings
;=========================================================================
;------------------------------------------------------------------------; SQL Tracing Bitfield
...
;TraceSql=0
TraceSql=63
TraceSqlMask=12319
...
;TracePC=0
TracePC=2124
TracePCMask=4095
OEL installation
Oracle Linux 6.0
Oracle Entreprise Linux 5.3
Oracle Entreprise Linux 4.6
Oracle DB Install
Then simply start the AppServer :
---------------------------------------------Quick-configure menu -- domain: APPDOM
---------------------------------------------Features
Settings
==========
==========
1) Pub/Sub Servers
: Yes
15) DBNAME
:[H91TMPLT]
2) Quick Server
: No
16) DBTYPE
:[ORACLE]
3) Query Servers
: Yes
17) UserId
:[PS]
4) Jolt
: Yes
18) UserPswd
:[PS]
5) Jolt Relay
: No
19) DomainID
:[APPDOM]
6) WSL
: Yes
20) AddToPATH :[.]
7) PC Debugger
: No
21) ConnectID :[people]
8) Event Notification: No
22) ConnectPswd:[peop1e]
9) MCF Servers
: No
23) ServerName :[____]
10) Perf Collator
: No
24) WSL Port
:[7000]
11) Analytic Servers : No
25) JSL Port
:[9000]
12) Domains Gateway
: No
26) JRAD Port :[9100]
Oracle 11.2.0.2 on OL6.0

Oracle 11.2.0.2 (out-of-place) on OEL5.3
Oracle 11.2.0.1 install on OEL5.3
VMWare - XClient
VMWare 2.0.2
Cygwin (XClient and NFS)
Blogroll
Grey Heller
Stony Brook University Goes Live with PeopleMobileTM
1 day ago
...
Oracle Security Alerts
exec PSWATCHSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 128959 -D APPDOM -S PSWATCHSRV :
Updated Release of the Oracle Java SE Critical Patch
process id=2386 ... Started.
Update - February 2013
exec PSAPPSRV -o ./LOGS/stdout -e ./LOGS/stderr -s@psappsrv.lst -- -D APPDOM -S PSAPPSRV :
1 day ago
exec PSAPPSRV -o ./LOGS/stdout -e ./LOGS/stderr -s@psappsrv.lst -- -D APPDOM -S PSAPPSRV :
Oracle's Virtualization Blog
Oracle Solaris Remote Lab Uses Oracle Secure Global
exec PSQRYSRV -o ./LOGS/stdout -e ./LOGS/stderr -s@psqrysrv.lst -- -D APPDOM -S PSQRYSRV :
Desktop!
1 day ago
exec PSSAMSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -D APPDOM -S PSSAMSRV :
PeopleSoft Technology Blog
Statement of Direction for PeopleSoft Interaction Hub
exec PSBRKHND -o ./LOGS/stdout -e ./LOGS/stderr -s PSBRKHND_dflt:BrkProcess -- -D APPDOM -S PSBRKHND_dflt :
2 days ago
exec PSBRKDSP -o ./LOGS/stdout -e ./LOGS/stderr -s PSBRKDSP_dflt:Dispatch -- -D APPDOM -S PSBRKDSP_dflt :
Oracle Technology Network's Blog
What's
Driving
the
Cloud
for
Developers
exec PSPUBHND -o ./LOGS/stdout -e ./LOGS/stderr -s PSPUBHND_dflt:PubConProcess -- -D APPDOM -S PSPUBHND_dflt :
3 days ago
exec PSPUBDSP -o ./LOGS/stdout -e ./LOGS/stderr -s PSPUBDSP_dflt:Dispatch -- -D APPDOM -S PSPUBDSP_dflt :
Show All
exec PSSUBHND -o ./LOGS/stdout -e ./LOGS/stderr -s PSSUBHND_dflt:SubConProcess -- -D APPDOM -S PSSUBHND_dflt :
exec PSSUBDSP -o ./LOGS/stdout -e ./LOGS/stderr -s PSSUBDSP_dflt:Dispatch -- -D APPDOM -S PSSUBDSP_dflt :
Links
OTN Hosted PeopleBooks
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 128959 -D APPDOM -S PSMONITORSRV :
OTN Tags
exec WSL -o ./LOGS/stdout -e ./LOGS/stderr -A -- -n //psovmab.phoenix.nga:7000 -z 0 -Z 0 -I 5 -T 60 -m 1 -M 3 -x 40 -c 5000 Oracle Forums
Oracle Docs
exec JSL -o ./LOGS/stdout -e ./LOGS/stderr -A -- -n //psovmab.phoenix.nga:9000 -m 5 -M 7 -I 5 -j ANY -x 40 -S 10 -c 1000000 Oracle Download
OTN Community
exec JREPSVR -o ./LOGS/stdout -e ./LOGS/stderr -A -- -W -P /home/psadm2/ps/pt/8.50/appserv/APPDOM/jrepository :
15 processes started.
Popular Posts
As a result, under $PS_CFG_HOME/appserv/APPDOM/LOGS, several files have been created, including one per process started :
[psadm2@psovmab LOGS]$ ls -lrt
total 3644
-rw-r--r-- 1 psadm2 oracle
926
193
0
0
137
-rw-r--r-- 1 psadm2 oracle 74066
7090
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
28
28
28
28
28
28
28
28
28
28
28
28
28
28
28
28
28
28
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
06:59
07:00
07:00
07:00
07:00
ULOG.032810
bblcheck.out
stdout
stderr
WATCHSRV_0328.LOG
PS_PSAPPSRV.tracesql
PS_PSQRYSRV.tracesql
PS_PSSAMSRV.tracesql
PS_PSBRKHND_dflt.tracesql
PS_PSPUBHND_dflt.tracesql
PS_PSSUBHND_dflt.tracesql
TUXLOG.032810
MONITORSRV_0328.LOG
APPSRV_0328.LOG
PS_PSBRKDSP_dflt.tracesql
PS_PSPUBDSP_dflt.tracesql
PS_PSSUBDSP_dflt.tracesql
PS_PSMONITORSRV.tracesql
We will focus on only one here, PS_PSAPPSRV.tracesql, and here below the firsts lines :
--- router libpsora load succeeded
INI
Connect=Primary/H91TMPLT/people/
GET type=1003 dbtype=4
GET type=1004 release=11
COM Stmt=SELECT OWNERID FROM PS.PSDBOWNER WHERE DBNAME=:1
SSB column=1 type=2 length=9 scale=0
Bind-1 type=2 length=8 value=H91TMPLT
EXE
Fetch
SET type=3018 des=early
Troubleshooting : process scheduler and distribution

Peoplesoft Database creation - Part I
On The Peoplesoft Road : Peoplesoft Database creation Part I
Peoplesoft Process scheduler PT8.50
On The Peoplesoft Road : Web Server - Weblogic
Blog Archive
2013 (1)
2012 (15)
2011 (43)
2010 (52)
December (2)
November (1)
October (4)
September (10)
August (3)
July (1)
June (2)
May (1)
April (4)
March (6)
Peoplesoft database connectivity part 3/3 : Apps/B...
Peoplesoft database connectivity part 2/3 : AppDes...
Peoplesoft database connectivity part 1/3 : DataMo...
PSOVM : sysadm's password policy
2/21/2013 9:23 PM
2 of 5
COM Stmt=SELECT OWNERID, TOOLSREL, TO_CHAR(LASTREFRESHDTTM,'YYYY-MM-DD HH24:MI:SS'), TO_CHAR(LASTCHANGEDTTM,'YYYY-MM-DD HH24:

Peopletools 8.50 and IE8
SET type=3018 des=never
Peopletools 8.50 and UK English
February (16)
January (2)
2009 (52)
EXE
2008 (34)
Fetch
COM Stmt=SELECT DBID FROM SYSADM.PSSTATUS
2007 (6)
2006 (8)
EXE
Fetch
COM Stmt=SELECT VERSION, OPERPSWD, ENCRYPTED, SYMBOLICID, ACCTLOCK FROM SYSADM.PSOPRDEFN WHERE OPRID = :1
Bind-1 type=2 length=2 value=PS
EXE
Fetch
COM Stmt=SELECT ACCESSID, ACCESSPSWD, ENCRYPTED FROM SYSADM.PSACCESSPRFL WHERE SYMBOLICID = :1
Bind-1 type=2 length=7 value=SYSADM1
EXE
Fetch
Disconnect
Connect=Primary/H91TMPLT/SYSADM/
SET type=2012 program=PSAPPSRV
SET type=2 OprId=PS
GET type=1101
GET type=1102
GET type=1103
SET type=50 resource=PSAPPSRV
CEX Stmt=select pt_tde_encrypt_alg from psoptions
Fetch
TDE Encryption Algorithm: ''
Others
4,573,424 Points
(Rank: #21,147)
Join World
Community Grid
today!
1. connect to the database with connectid (people)

2. check database name in PSDBOWNER
3. check if the user choose to manage the appserver (PS) is an application user in PSOPRDEFN and get the SYMBOLICID
4. from SYMBOLICID, it takes the ACCESSID and password
5. reconnect to the db with ACCESSID user (SYSADM)
=> Starting the application server does nothing but a 2tier connection
Again, there are hundreds of queries fired when starting the application server, we'll keep only the following :
1-268
06.59.43
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
PSAPPSRV.2400 (0)
0.000307 Cur#1.2400.H91TMPLT RC=0 Dur=0.000087 COM Stmt=UPDATE PSOPRDEFN SET LASTSIGNONDTTM = TO_TIMESTA
1-269
06.59.43
0.000019 Cur#1.2400.H91TMPLT RC=0 Dur=0.000005 Bind-1 type=25 length=26 value=201
1-270
06.59.43
0.000017 Cur#1.2400.H91TMPLT RC=0 Dur=0.000004 Bind-2 type=2 length=2 value=PS
1-271
06.59.43
0.003641 Cur#1.2400.H91TMPLT RC=0 Dur=0.003628 EXE
1-272
06.59.43
0.000021 Cur#1.2400.H91TMPLT RC=0 Dur=0.000005 SET type=3018 des=early
1-273
06.59.43
0.001678 Cur#1.2400.H91TMPLT RC=0 Dur=0.001664 COM Stmt=SELECT 'PS_DOES_TABLE_EXI
1-274
06.59.43
0.000040 Cur#1.2400.H91TMPLT RC=0 Dur=0.000004 SET type=3018 des=never
1-275
06.59.43
0.000120 Cur#1.2400.H91TMPLT RC=0 Dur=0.000055 COM Stmt=INSERT INTO PSACCESSLOG (
1-276
06.59.43
1-277
06.59.43
0.000017 Cur#1.2400.H91TMPLT RC=0 Dur=0.000004 Bind-2 type=2 length=7 value=UNKNO
1-278
06.59.43
1-279
06.59.43
1-280
06.59.43
1-281
06.59.43
0.002948 Cur#1.2400.H91TMPLT RC=0 Dur=0.002924 Commit
1-282
06.59.43
0.006653 Cur#1.2400.H91TMPLT RC=0 Dur=0.000190 COM Stmt=SELECT DBID FROM PSSTATUS
1-283
06.59.43
0.000018 Cur#1.2400.H91TMPLT RC=0 Dur=0.000005 SSB column=1 type=2 length=33 scal
1-284
06.59.43
1-285
06.59.43
0.000018 Cur#1.2400.H91TMPLT RC=0 Dur=0.000005 Fetch
1-286
06.59.43
0.000088 Cur#1.2400.H91TMPLT RC=0 Dur=0.000062 COM Stmt=SELECT 'X' FROM PSCLASSDE
1-287
06.59.43
1-288
06.59.43
1-289
06.59.43
0.000067 Cur#1.2400.H91TMPLT RC=0 Dur=0.000054 Fetch
1-290
06.59.43
1-291
06.59.43
0.000233 Cur#1.2400.H91TMPLT RC=0 Dur=0.000005 GET type=3003 cursor=persistent
1-292
06.59.43
=> Once again, update and insert for auditing purposes, and then an interesting query, the last one to check if the user PS configured to managed the
AppServer is authorized to do so. Unfortunately, nowhere in the log file we can see which role is required.
2. The Process Scheduler connection
To determine how the connection is working, we'll set the trace file in the configuration file psprcs.cfg as following :
[Trace]
;=========================================================================
; Trace settings
;=========================================================================
; SQL Tracing Bitfield
...
;TraceSQL=0
TraceSQL=63
;------------------------------------------------------------------------; PeopleCode Tracing Bitfield
...
;TracePC=0
TracePC=2124
Then startup the process scheduler :
Booting server processes ...
exec PSMSTPRC -o ./LOGS/stdout -e ./LOGS/stderr -A -- -CD H91TMPLT -PS H91TMPLT -A start -S PSMSTPRC :
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD H91TMPLT -S PSAESRV :
exec PSDSTSRV -o ./LOGS/stdout -e ./LOGS/stderr -p 1,600:1,1 -sPostReport -- -CD H91TMPLT -PS H91TMPLT -A start -S PSDSTSRV :
exec PSPRCSRV -o ./LOGS/stdout -e ./LOGS/stderr -sInitiateRequest -- -CD H91TMPLT -PS H91TMPLT -A start -S PSPRCSRV :
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 62391 -PS H91TMPLT -S PSMONITORSRV :
8 processes started.
It will create the log file under $PS_CFG_HOME/appserv/prcs/PRCSDOM/LOGS, several files have been created, including one per process started :
[psadm2@psovmab LOGS]$ ls -lrt
total 1176
0
1824
399
54
2205
3051
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
Mar
28
28
28
28
28
28
28
28
28
07:29
07:29
07:29
07:29
07:29
07:29
07:29
07:29
07:29
stderr
PS_PSAESRV.tracesql
AESRV_0328.LOG
PS_PSDSTSRV.tracesql
DSTAGNT_0328.LOG
stdout
TUXLOG.032810
SCHDLR_0328.LOG
PS_PSPRCSRV.tracesql
2/21/2013 9:23 PM
3 of 5
-rw-r--r-- 1 psadm2 oracle 17210 Mar 28

[psadm2@psovmab LOGS]$
07:29
07:29
07:29
07:29
MONITORSRV_0328.LOG
PS_PSMSTPRC.tracesql
MSTRSCHDLR_0328.LOG
PS_PSMONITORSRV.tracesql
We will focus on one of them here, PS_PSPRCSRV.tracesql :

PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
1-1
1-2
1-3
1-4
1-5
1-6
1-7
1-8
1-9
1-10
1-11
1-12
1-13
1-18
1-19
1-20
1-21
1-22
1-23
1-24
1-30
1-31
1-32
1-33
1-37
1-38
1-39
1-40
1-41
1-42
1-43
1-48
1-49
1-51
1-52
07.29.07
07.29.07
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
0.009027
0.148481
0.000106
0.000537
0.000969
0.000024
0.000045
0.002408
0.000053
0.000085
0.001003
0.000030
0.001441
0.000018
0.000093
0.000018
0.000945
0.000017
0.000083
0.000017
0.001218
0.000027
0.000084
0.000017
0.001084
0.000017
0.004006
0.158337
0.063165
0.002877
0.013951
0.001756
0.001427
0.000022
Cur#0.2746.H91TMPLT RC=0 Dur=0.040736

Cur#0.2746.H91TMPLT RC=0 Dur=0.008987
Cur#1.2746.H91TMPLT RC=0 Dur=0.148323
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.000520
Cur#1.2746.H91TMPLT RC=0 Dur=0.000116
Cur#1.2746.H91TMPLT RC=0 Dur=0.000004
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.002358
Cur#1.2746.H91TMPLT RC=0 Dur=0.000013
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.000989
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.001422
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.000041
Cur#1.2746.H91TMPLT RC=0 Dur=0.000004
Cur#1.2746.H91TMPLT RC=0 Dur=0.000932
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.000050
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.001205
Cur#1.2746.H91TMPLT RC=0 Dur=0.000015
Cur#1.2746.H91TMPLT RC=0 Dur=0.000066
Cur#1.2746.H91TMPLT RC=0 Dur=0.000004
Cur#1.2746.H91TMPLT RC=0 Dur=0.001072
Cur#1.2746.H91TMPLT RC=0 Dur=0.000005
Cur#1.2746.H91TMPLT RC=0 Dur=0.003828
Cur#1.2746.H91TMPLT RC=0 Dur=0.158158
Cur#1.2746.H91TMPLT RC=0 Dur=0.012732
Cur#1.2746.H91TMPLT RC=0 Dur=0.002859
Cur#1.2746.H91TMPLT RC=0 Dur=0.013938
Cur#1.2746.H91TMPLT RC=0 Dur=0.001673
Cur#1.2746.H91TMPLT RC=0 Dur=0.001399
TDE Encryption Algorithm: ''
--- router libpsora load succeeded

INI
Connect=Primary/H91TMPLT/people/
GET type=1003 dbtype=4
COM Stmt=SELECT OWNERID FROM PS.PS
SSB column=1 type=2 length=9 scale
Bind-1 type=2 length=8 value=H91TM
EXE
Fetch
SET type=3018 des=early
COM Stmt=SELECT OWNERID, TOOLSREL,
SET type=3018 des=never
EXE
Fetch
COM Stmt=SELECT DBID FROM SYSADM.P
SSB column=1 type=2 length=33 scal
EXE
Fetch
COM Stmt=SELECT VERSION, OPERPSWD,
EXE
Fetch
COM Stmt=SELECT ACCESSID, ACCESSPS
Bind-1 type=2 length=7 value=SYSAD
EXE
Fetch
Disconnect
SET type=2012 program=PSPRCSRV
SET type=2 OprId=PS
SET type=50 resource=PSPRCSRV
CEX Stmt=select pt_tde_encrypt_alg
Fetch
Here again, exactly same output as for the AppServer.

=> Starting the process scheduler does nothing but a 2tier connection.
But then, there are many queries checking the servername (defined in database), disttribution node and so on :
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
...
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
...
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
...
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
PSPRCSRV.2746
...
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
1-378
1-379
1-380
1-381
1-382
1-383
1-384
1-385
1-386
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
0.000084
0.000017
0.000027
0.016067
0.000022
0.000085
0.000017
0.000017
0.017499
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000063
Dur=0.000004
Dur=0.000014
Dur=0.016054
Dur=0.000005
Dur=0.000062
Dur=0.000004
Dur=0.000004
Dur=0.017477
COM Stmt=SELECT COUNT (DISTINCT CL

EXE
Fetch
COM Stmt=SELECT DISTINCT CLASSID F
EXE
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
1-792
1-793
1-794
1-795
1-796
1-797
1-798
1-799
1-800
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
0.000071
0.000018
0.000017
0.001236
0.000017
0.000112
0.000017
0.000017
0.001951
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
Cur#2.2746.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=1
RC=0
RC=0
RC=0
RC=0
Dur=0.000047
Dur=0.000004
Dur=0.000005
Dur=0.001223
Dur=0.000004
Dur=0.000052
Dur=0.000004
Dur=0.000004
Dur=0.001937
COM Stmt=SELECT 'X' FROM PSROLEUSE

EXE
Fetch
COM Stmt=SELECT 'X' FROM PSROLEUSE
EXE
(0)
(0)
(0)
1-1584
1-1585
1-1586
07.29.08
07.29.08
07.29.08
0.000292 Cur#1.2746.H91TMPLT RC=0 Dur=0.000226 COM Stmt=SELECT 'X' FROM PSCLASSDE

(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
(0)
1-1634
1-1635
1-1636
1-1637
1-1638
1-1639
1-1640
1-1641
1-1642
1-1643
1-1644
1-1645
1-1646
1-1647
1-1648
1-1649
1-1650
1-1651
1-1652
1-1653
1-1654
1-1655
1-1656
1-1657
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
07.29.08
0.000079
0.000021
0.000021
0.001374
0.000017
0.000099
0.000017
0.000017
0.001575
0.000016
0.000064
0.000017
0.000017
0.001461
0.000017
0.000064
0.000018
0.000017
0.001308
0.000017
0.000065
0.000017
0.000017
0.003472
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
Cur#1.2746.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000048
Dur=0.000006
Dur=0.000006
Dur=0.001360
Dur=0.000004
Dur=0.000078
Dur=0.000004
Dur=0.000005
Dur=0.001562
Dur=0.000005
Dur=0.000045
Dur=0.000004
Dur=0.000004
Dur=0.001449
Dur=0.000005
Dur=0.000044
Dur=0.000005
Dur=0.000004
Dur=0.001295
Dur=0.000005
Dur=0.000044
Dur=0.000004
Dur=0.000005
Dur=0.003429
COM Stmt=SELECT COUNT(*) FROM PS_S

EXE
Fetch
EXE
Fetch
EXE
Fetch
EXE
Fetch
EXE
No big differences between Apps and Batch server, except (of course) in the statements executed.
3. The PIA connection
To determine how the connection is working, we'll set the trace file in the configuration file psappsrv.cfg as defined in part 1 above. The PIA connects to
the Application server through the JSL port defined in configuration.properties (for the PIA) and psappsrv.cg for the Application server. This is the only
one link between them.
Just starting up the PIA (startPIA.sh for Weblogic) create a file under the log directory of application server : PTWEBSERVER_psovmpia.tracesql
Note : PTWEBSERVER is configured in configuration.properties to manage the webserver, psovmpia is the name of the server hosting the webserver.
And here a first remark : the name appears in clear. Ok, then what's wrong ?
The thing is the user who manage the webserver has been encrypted in the configuration.properties file :
...
## sd="Web User Id", ld="The User Id that the Portal uses to access the web profile"
WebUserId={V1.1}JP9ukEkTssmYrzsK1yvXFg==
## sd="Web Password", dt="e", ld="The User Password that the Portal uses to access the web profile", tip="The password is aut
WebPassword={V1.1}JP9ukEkTssmYrzsK1yvXFg==
...
And seeing this file and the log file name, we could easily determine what is the password (in that peculiar case they are same).
Going through the log file itself, it is showing the Tuxedo session connection :
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
(1)
(1)
(1)
(1)
(1)
(1)
1-335
1-339
1-340
1-341
1-342
1-343
07.46.00
07.46.00
07.46.00
07.46.00
07.46.00
07.46.00
0.010892
0.000025
0.023656
0.000035
0.000212
0.002733
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#2.2855.H91TMPLT
Cur#2.2855.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000254
Dur=0.000005
Dur=0.023625
Dur=0.000008
Dur=0.000029
Dur=0.002706
COM Stmt=SELECT LANGUAGE_CD, OPERP

Bind-1 type=2 length=11 value=PTWE
EXE
Fetch
Mon OprID=PTWEBSERVER OSUserName=p
Then like for Appserver and process scheduler, it is checking the roles assigned to PTWEBSERVER :
PSAPPSRV.2855 (1)
PSAPPSRV.2855 (1)
PSAPPSRV.2855 (1)
1-376
1-377
1-378
07.46.01
07.46.01
07.46.01
0.000071 Cur#1.2855.H91TMPLT RC=0 Dur=0.000049 COM Stmt=SELECT COUNT (*) FROM PSR
0.000007 Cur#1.2855.H91TMPLT RC=0 Dur=0.000003 SSB column=1 type=6 length=4 scale
0.000003 Cur#1.2855.H91TMPLT RC=0 Dur=0.000001 Bind-1 type=2 length=11 value=PTWE
2/21/2013 9:23 PM
4 of 5
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
1-379
1-380
1-381
1-382
1-383
1-384
1-385
1-390
1-391
1-392
1-393
1-394
1-395
1-396
1-397
1-398
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
0.001208
0.000017
0.000067
0.000017
0.000016
0.000017
0.001364
0.000082
0.000018
0.000017
0.005495
0.000024
0.000129
0.000024
0.000019
0.013212
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.001200
Dur=0.000005
Dur=0.000048
Dur=0.000004
Dur=0.000005
Dur=0.000005
Dur=0.001350
Dur=0.000062
Dur=0.000005
Dur=0.000004
Dur=0.005473
Dur=0.000007
Dur=0.000094
Dur=0.000005
Dur=0.000004
Dur=0.013197
EXE
Fetch
COM Stmt=SELECT ROLENAME, DYNAMIC_
EXE
EXE
Fetch
EXE
Then from the webprofile taken from the configuration.properties file, check the webprofile definition in the db :
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
1-433
1-434
1-435
1-436
1-437
1-438
1-458
1-459
1-464
1-465
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
0.000432
0.000002
0.000000
0.000000
0.000000
0.006487
0.000027
0.000810
0.000018
0.008446
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000059
Dur=0.000000
Dur=0.000000
Dur=0.000000
Dur=0.000000
Dur=0.006476
Dur=0.000004
Dur=0.000086
Dur=0.000004
Dur=0.008424
COM Stmt=SELECT WEBPROFILENAME, PR

SSB column=3 type=2 length=255 sca
Bind-1 type=2 length=3 value=DEV
EXE
Commit
COM Stmt=SELECT WEBPROFILENAME, PR
EXE
0.000724
0.000018
0.000017
0.000017
0.017739
0.000320
0.000024
0.000017
0.000017
0.000016
0.000017
0.000034
0.000017
0.000017
0.000016
0.000017
0.000017
0.004406
0.007314
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000052
Dur=0.000005
Dur=0.000005
Dur=0.000004
Dur=0.017718
Dur=0.000111
Dur=0.000005
Dur=0.000004
Dur=0.000005
Dur=0.000004
Dur=0.000004
Dur=0.000004
Dur=0.000005
Dur=0.000005
Dur=0.000004
Dur=0.000005
Dur=0.000005
Dur=0.004388
Dur=0.007271
COM Stmt=DELETE FROM PSWEBPROFHIST

Bind-1 type=2 length=8 value=psovm
Bind-2 type=19 length=4 value=8000
Bind-3 type=2 length=2 value=ps
EXE
COM Stmt=INSERT INTO PSWEBPROFHIST
Bind-1 type=2 length=8 value=psovm
Bind-3 type=2 length=2 value=ps
Bind-6 type=2 length=13 value=192.
Bind-8 type=2 length=16 value=http
Bind-9 type=2 length=45 value=psov
Bind-10 type=2 length=1 value=
Bind-11 type=22 length=1137 LONG T
EXE
Commit
And finally, the last two statements save the records :

PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
(1)
1-1020
1-1021
1-1022
1-1023
1-1024
1-1025
1-1026
1-1027
1-1028
1-1029
1-1030
1-1031
1-1032
1-1033
1-1034
1-1035
1-1036
1-1037
1-1038
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
07.46.01
So, the PIA is connecting in 3tier mode to the application server, and again, the log file does not help to determine which roles are needed for
PTWEBSERVER, but helps a lot to see all the tables read and modified during the PIA startup.
4. The front end connection
The front end user has no idea about the the PIA, application server and even less about database user to be used. From the given url, he needs only an
application user. But behind this "simple" action of login, hundreds of queries are executed against the database.
Here below the first lines of the file generated when a user enter to the login page and press enter (format mask of the file is _.tracesql).
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
...
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
PSAPPSRV.2855
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
1-1152
1-1156
1-1157
1-1158
1-1159
1-1160
1-1161
1-1162
1-1163
1-1164
1-1165
1-1166
1-1167
1-1190
1-1191
1-1192
1-1193
1-1194
1-1195
1-1196
1-1197
1-1198
1-1199
1-1200
1-1201
1-1202
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
0.001503
0.000018
0.001843
0.000018
0.000134
0.002373
0.000040
0.000023
0.000275
0.000018
0.001221
0.000017
0.000173
0.000017
0.002087
0.000021
0.000125
0.000017
0.000017
0.001468
0.000017
0.000074
0.000018
0.000017
0.000017
0.003793
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#2.2855.H91TMPLT
Cur#2.2855.H91TMPLT
Cur#2.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000088
Dur=0.000004
Dur=0.001829
Dur=0.000006
Dur=0.000070
Dur=0.002355
Dur=0.000021
Dur=0.000004
Dur=0.000055
Dur=0.000004
Dur=0.001208
Dur=0.000005
Dur=0.000072
Dur=0.000005
Dur=0.002075
Dur=0.000009
Dur=0.000087
Dur=0.000004
Dur=0.000005
Dur=0.001456
Dur=0.000005
Dur=0.000048
Dur=0.000005
Dur=0.000004
Dur=0.000005
Dur=0.003780
COM Stmt=SELECT LANGUAGE_CD, OPERP

EXE
Fetch
Mon OprID=PS OSUserName=nicolas Ma
Disconnect
Commit
COM Stmt=SELECT VERSION FROM PSVER
EXE
Fetch
COM Stmt=SELECT VERSION, EMPLID, E
EXE
Fetch
COM Stmt=SELECT COUNT (*) FROM PSR
EXE
Fetch
COM Stmt=SELECT ROLENAME, DYNAMIC_
EXE
(3)
(3)
(3)
(3)
(3)
(3)
(3)
(3)
1-1966
1-1967
1-1968
1-1969
1-1970
1-1971
1-1972
1-1973
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
07.49.20
0.000086
0.000018
0.000017
0.005135
0.000019
0.000099
0.000018
0.000017
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
Cur#1.2855.H91TMPLT
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
RC=0
Dur=0.000065
Dur=0.000004
Dur=0.000005
Dur=0.005120
Dur=0.000005
Dur=0.000069
Dur=0.000004
Dur=0.000005

EXE
Fetch
RC=0
RC=0
RC=0
RC=0
Dur=0.000066
Dur=0.000005
Dur=0.000005
Dur=0.000005
COM Stmt=SELECT PORTAL_OBJNAME, PO

Bind-1 type=2 length=8 value=EMPLO
Bind-2 type=1 length=1 value=C
So, it is starting exactly like the PIA connection, but immediately check the user's roles.
It is also checking of the Webbrowser language (here ENG) has been installed onto the database :
COM Stmt=SELECT INSTALLED FROM PSLANGUAGES WHERE LANGUAGE_CD = :1
Bind-1 type=2 length=3 value=ENG
EXE
Finally, it takes from the database the portal name for further page construction :
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
(6)
(6)
(6)
(6)
1-1826
1-1830
1-1831
1-1832
07.49.21
07.49.21
07.49.21
07.49.21
0.006145
0.000019
0.000021
0.000017
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
Cur#1.2868.H91TMPLT
1-1885
1-1886
1-1887
1-1888
1-1889
1-1890
1-1891
1-1892
1-1893
07.49.22
07.49.22
07.49.22
07.49.22
07.49.22
07.49.22
07.49.22
07.49.22
07.49.22

0.041947
>>> start-ext Nest=00 IScript_HPDefaultHdr WEBLIB_PORTAL.PORTAL_HOMEPA
0.000239 >>>>> Begin WEBLIB_PORTAL.PORTAL_HOMEPAGE.FieldFormula level 0 row 0
0.000579
21: Function IScript_HPDefaultHdr()
0.000021
22:
&BrandingObj = CreateBrandingObject();
0.000652
>>> start-ext Nest=01 CreateBrandingObject WEBLIB_PORTAL.PORTAL_HEADER
0.000018
>>>>> Begin WEBLIB_PORTAL.PORTAL_HEADER.FieldFormula level 0 row 0
0.000100
82: Function CreateBrandingObject() Returns object;
0.000006
83:
SQLExec("SELECT PACKAGEROOT, APPCLASSID FROM PSOPTIONS", &A
And calls Peoplecode function :

PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
PSAPPSRV.2868
...
(9)
(9)
(9)
(9)
(9)
(9)
(9)
(9)
(9)
Here we can see a big difference, so far, no Peoplecode have been seen in the trace file, the real business is starting right now, with menus and pages
building.
The main conclusion of this part 3 is App and Batch are connecting in 2tier mode against the database, the PIA in 3tier mode and an other layer has been
added for front end user in 4tier mode, the presentation layer.
2/21/2013 9:23 PM
5 of 5
Of course, this "series" was not to intend to answer to every single question (I did not show the entire trace file, and a lot of part are still hidden and not
showing in trace file), but hopefully it helped to understand the key point of the Peolesoft security and the main differences between all the possible
connection to a Peoplesoft database.
Enjoy,
Nicolas.
Publi par Nicolas Gasparotto l'adresse 5:48 PM
2 comments:
Erik said...
Hi,
Stumbled upon your blog about the peoplesoft connects. Interesting stuff.
But there is one thing youi never mention an which I (DB tuning expert) find very interesting and strange as
well.
When logging on there is a query:
SELECT COUNT (DISTINCT CLASSID)
FROM PSROLEUSER A, PSROLECLASS B, PSROLEDEFN C
WHERE A.ROLEUSER = :1
AND A.ROLENAME = B.ROLENAME
AND B.ROLENAME = C.ROLENAME
AND A.ROLENAME = C.ROLENAME
AND C.ROLESTATUS = 'A'
Strange enough after this the same query is used again and now without the count. This is really weird since
it is relatively expensive query in the system I am working on. In my system the query does 96 logical IO's.
times 2 makes 192 logical reads. This does not seem very high, but the system I am tuning has a hugh
amount of logon's.
My question, for which I have not found an answer, is WHY is it doing it twice. I do not see any valid reason
for this.
September 28, 2011 10:24 AM
Gasparotto Nicolas said...

Erik,
That's indeed weird, I have no explanation neither, one pass would be enough, unfortunately this is how it is
coded. Probably it is a a legacy of older version...
I remember older Peopletools I worked on with a lot of login time issues (<=8.48), that has greatly been
improved since then, but we have still that kind of stuff.
Just few thoughts : try to keep the lowest as possible the number of roles... You could also investigate a
code change on the login to query a MView (containing all required columns - CLASSID and ROLEUSER - and
refreshing on change of the underlying tables), but of course, it moves you out of support.
Good luck,
Nicolas.
September 28, 2011 11:00 AM
Post a Comment
Newer Post
Home
Older Post
Subscribe to: Post Comments (Atom)
2/21/2013 9:23 PM

On The Peoplesoft Road - Peoplesoft Database Connectivity Part 3 - 3 - Apps - Batch - Pia

Uploaded by

Document Information

Original Title

Copyright

Available Formats

Share this document

Share or Embed Document

Sharing Options

Did you find this document useful?

Is this content inappropriate?

Copyright:

Available Formats

On The Peoplesoft Road - Peoplesoft Database Connectivity Part 3 - 3 - Apps - Batch - Pia

Uploaded by

Copyright:

Available Formats

On The Peopleso Road: Peopleso database connec vity part 3/3 ...

h p://gasparo o.blogspot.in/2010/03/peopleso databaseconnect...

Sunday, March 28, 2010

Peoplesoft database connectivity part 3/3 : Apps/Batch/Pia

View my complete profile

1. The Application server connection

Oracle 11.2.0.2 on OL6.0

Troubleshooting : process scheduler and distribution

h p://gasparo o.blogspot.in/2010/03/peopleso databaseconnect...

COM Stmt=SELECT OWNERID, TOOLSREL, TO_CHAR(LASTREFRESHDTTM,'YYYY-MM-DD HH24:MI:SS'), TO_CHAR(LASTCHANGEDTTM,'YYYY-MM-DD HH24:

1. connect to the database with connectid (people)

-rw-r--r-- 1 psadm2 oracle 17210 Mar 28

h p://gasparo o.blogspot.in/2010/03/peopleso databaseconnect...

We will focus on one of them here, PS_PSPRCSRV.tracesql :

Cur#0.2746.H91TMPLT RC=0 Dur=0.040736

--- router libpsora load succeeded

Here again, exactly same output as for the AppServer.

COM Stmt=SELECT COUNT (DISTINCT CL

COM Stmt=SELECT 'X' FROM PSROLEUSE

0.000292 Cur#1.2746.H91TMPLT RC=0 Dur=0.000226 COM Stmt=SELECT 'X' FROM PSCLASSDE

COM Stmt=SELECT COUNT(*) FROM PS_S

COM Stmt=SELECT LANGUAGE_CD, OPERP

h p://gasparo o.blogspot.in/2010/03/peopleso databaseconnect...

COM Stmt=SELECT WEBPROFILENAME, PR

COM Stmt=DELETE FROM PSWEBPROFHIST

And finally, the last two statements save the records :

COM Stmt=SELECT LANGUAGE_CD, OPERP

COM Stmt=SELECT COUNT (DISTINCT CL

COM Stmt=SELECT PORTAL_OBJNAME, PO

0.000022 Cur#1.2868.H91TMPLT RC=0 Dur=0.000005 Commit

And calls Peoplecode function :

h p://gasparo o.blogspot.in/2010/03/peopleso databaseconnect...

Gasparotto Nicolas said...

Subscribe to: Post Comments (Atom)

You might also like