Sunday, February 28, 2010

Peoplesoft Process scheduler PT8.50

Connect on your front end application with PS user (HCM, VP1 for other applications).

1. Define your local node with password authentication
2. Create a report nodes

=> note, leave the LoginId and password blank, otherwise you could receive the following error message when posting process reports.
From stdout file (prcs/domain/LOGS) :
NULL HTTP response - check Report Repository web server. (63,70)
=================================Error===============================
Message: Unable to post report/log file for Process Instance: 868, Report Id: 714
Process Name: PSXPARCHATTR, Type: Application Engine
Description: XML Publisher Archive
Directory: /home/psadm2/ps/pt/8.50/appserv/prcs/PRCSDOM/log_output/AE_PSXPARCHATTR_868
=====================================================================

From DSTAGNT_xxxx.LOG (prcs/domain/LOGS) :
PSDSTSRV.1982 (7) [02/28/10 11:32:52 PostReport](2) =====================================================================
PSDSTSRV.1982 (8) [02/28/10 11:32:52 PostReport](3) Number of new entries to process: 1
PSDSTSRV.1982 (8) [02/28/10 11:32:52 PostReport](3) 1. Process Instance: 868/Report Id: 714/Descr: XML Publisher Archive
PSDSTSRV.1982 (8) [02/28/10 11:32:52 PostReport](3) from directory: /home/psadm2/ps/pt/8.50/appserv/prcs/PRCSDOM/log_output/AE_PSXPARCHATTR_868
PSDSTSRV.1982 (8) [02/28/10 11:32:52 PostReport](1) PSJNI: Java exception thrown: java.io.IOException: Stream closed.
PSDSTSRV.1982 (8) [02/28/10 11:32:52 PostReport](3) HTTP transfer error.
PSDSTSRV.1982 (8) [02/28/10 11:32:52 PostReport](3) Post Report Elapsed Time: 0.0200
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](3) Number of new entries to process: 1
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](3) 1. Process Instance: 868/Report Id: 714/Descr: XML Publisher Archive
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](3) from directory: /home/psadm2/ps/pt/8.50/appserv/prcs/PRCSDOM/log_output/AE_PSXPARCHATTR_868
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](1) PSJNI: Java exception thrown: java.io.IOException: Stream closed.
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](3) HTTP transfer error.
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](3) Post Report Elapsed Time: 0.0200
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](1) =================================Error===============================
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](1) Unable to post report/log file for Process Instance: 868, Report Id: 714
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](2) Process Name: PSXPARCHATTR, Type: Application Engine
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](2) Description: XML Publisher Archive
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](2) Directory: /home/psadm2/ps/pt/8.50/appserv/prcs/PRCSDOM/log_output/AE_PSXPARCHATTR_868
PSDSTSRV.1982 (9) [02/28/10 11:33:07 PostReport](2) =====================================================================


3. Add the report node to the process server (here PSUNX) :


4. Add the ReportDistAdmin role to the user used to manage the process scheduler (to start it, defined in the process scheduler configuration file) - here PS :
4. You can define the local gateway, based on the webserver url, and load the connector :
Ping to confirm the input
5. Add the local node to your Gateway
Ping the local node to confirm the input
6. Create a new process scheduler, configure and start the process scheduler
------------------------------------------------------------
Quick-configure menu -- Scheduler for Database: hc91dmo
------------------------------------------------------------
Features Settings
========== ==========
1) Master Schdlr : Yes 5) DBNAME :[hc91dmo]
2) App Eng Server : Yes 6) DBTYPE :[ORACLE]
7) PrcsServer :[PSUNX]
8) UserId :[PS]
9) UserPswd :[PS]
10) ConnectID :[people]
11) ConnectPswd:[peop1e]
12) ServerName :[]
Actions 13) Log/Output Dir:[%PS_SERVDIR%/log_output]
========= 14) SQRBIN :[%PS_HOME%/bin/sqr/%PS_DB%/bin]
3) Load config as shown 15) AddToPATH :[%PS_HOME%/cblbin]
4) Custom configuration
h) Help for this menu
q) Return to previous menu

Enter selection (1-15, h, or q): 3
Loading validation table...
setting DBName=hc91dmo
setting DBType=ORACLE
setting UserId=PS
setting UserPswd=PS
setting ConnectId=people
setting ConnectPswd=peop1e
setting ServerName=
setting PrcsServerName=PSUNX
setting Log/Output Directory=%PS_SERVDIR%/log_output
setting Add to PATH=%PS_HOME%/cblbin
setting SQRBIN=%PS_HOME%/bin/sqr/%PS_DB%/bin
New CFG file written with modified Startup parameters

Log Directory entry not found in configuration file.
Setting Log Directory to the default... [PS_SERVDIR/LOGS]
Spawning enabled for server PSDSTSRV.
Configuration file successfully created.
CFG setting changes completed, loading configuration...
Process Scheduler Server configuration complete.


-------------------------------------------
PeopleSoft Process Scheduler Administration
-------------------------------------------

1) Start a Process Scheduler Server
2) Stop a Process Scheduler Server
3) Configure a Process Scheduler Server
4) Create a Process Scheduler Server Configuration
5) Delete a Process Scheduler Server Configuration
6) Edit a Process Scheduler Configuration File
7) Import an existing Process Scheduler Configuration
8) Show Status of a Process Scheduler Server
9) Kill a Process Scheduler Server
10) Clean IPC resources of a Process Scheduler Domain

q) Quit

Command to execute (1-10, q) : 1


Database list:

1) hc91dmo

Select item number to start: 1

No Archive subdirectory, creating it...
No psprcs.cfg in the Archive subdirectory, creating it...

Starting Process Scheduler Server PSUNX for Database hc91dmo ...

Booting all admin and server processes in /apps/psoft/hc91/appserv/prcs/hc91dmo/PSTUXCFG
INFO: Oracle Tuxedo, Version 10.3.0.0, 64-bit, Patch Level (none)

Booting admin processes ...

exec BBL -A :
process id=24737 ... Started.

Booting server processes ...

exec PSMSTPRC -o ./LOGS/stdout -e ./LOGS/stderr -A -- -CD hc91dmo -PS PSUNX -A start -S PSMSTPRC :
process id=24739 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD hc91dmo -S PSAESRV :
process id=24764 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD hc91dmo -S PSAESRV :
process id=24772 ... Started.
exec PSAESRV -o ./LOGS/stdout -e ./LOGS/stderr -- -CD hc91dmo -S PSAESRV :
process id=24781 ... Started.
exec PSDSTSRV -o ./LOGS/stdout -e ./LOGS/stderr -p 1,600:1,1 -sPostReport -- -CD hc91dmo -PS PSUNX -A start -S PSDSTSRV :
process id=24789 ... Started.
exec PSPRCSRV -o ./LOGS/stdout -e ./LOGS/stderr -sInitiateRequest -- -CD hc91dmo -PS PSUNX -A start -S PSPRCSRV :
process id=24799 ... Started.
exec PSMONITORSRV -o ./LOGS/stdout -e ./LOGS/stderr -A -- -ID 135074 -PS PSUNX -S PSMONITORSRV :
process id=24811 ... Started.
8 processes started.


-------------------------------------------
PeopleSoft Process Scheduler Administration
-------------------------------------------

1) Start a Process Scheduler Server
2) Stop a Process Scheduler Server
3) Configure a Process Scheduler Server
4) Create a Process Scheduler Server Configuration
5) Delete a Process Scheduler Server Configuration
6) Edit a Process Scheduler Configuration File
7) Import an existing Process Scheduler Configuration
8) Show Status of a Process Scheduler Server
9) Kill a Process Scheduler Server
10) Clean IPC resources of a Process Scheduler Domain

q) Quit

Command to execute (1-10, q) :

7. Now, you should be able to run process against the process server defined above




Nicolas.

15 comments:

Blue Medora Staff said...

As usual Nicolas, your blog posts on PeopleSoft / Peopletools installation & configuration are the absolute best on the web. You are to be commended for providing this great information to the community.

Thankyou!

Nicolas Gasparotto said...

Thank you Nathan, that's very kind of you. I'm glad if this is useful.

Nicolas.

Anonymous said...

Great Nicloas, you are a saviour. Keep up the good work.

Anonymous said...

Excellent Blog.

Thankyou!

Ayyanar said...

Hi Nicolas,

After Webserver i am getting following message in PIA logon screen,

We've detected that your operating system is not supported by this website. For best results, use one of the following operating systems:
iMAC OS10 Leopard
Windows 2003
Windows XP
Suse 9
iMAC OS10 Tiger
iMAC OS10 Panther
Windows Vista .

I am able to login two tire mode, Peoplesoft9.1/8.5 tools HRMS with Oracle 32 bit server Installed in windows 7.


Please advice

Nicolas Gasparotto said...

Ayyanar, nothing wrong with this message, Windows 7 is not supported yet as a web client.
You can find workaround in the link below to avoid this message :
http://peoplesofttipster.com/2010/01/27/hide-the-windows-7-is-not-supported-message/

Nicolas.

Ayyanar said...

Fixed the above issue, Thanks Nicolas, now i am getting error,

bea.jolt.ApplicationException: TPESVCFAIL - application level service failure

I tried following options

1. unlocked the PTWEBSERVER
and restarted the web and appserver same error

2. In datamover reset the password with bellow script,
update psoprdefn set OPERPSWD = 'PTWEBSERVER', encrypted = 0 where oprid = 'PTWEBSERVER';
encrypt_password PTWEBSERVER;

and restarted the both app and we server again, but still i am getting same error.

Please advice

Thanks
Ayyanar

AarGee said...

Hi Nicolas - I followed all your instructions but am unable to resolve the "NULL HTTP response - check Report Repository web server". This is a PeS 9.1/Tools 8.50 install. Any tip on the root cause would be greatly helpful

Thanks RG

Les Parents de Bayard said...

Check report Repository.
1) in
./applications/peoplesoft/PORTAL.war/WEB-INF/psftdocs//configuration.properties
Line
ReportRepositoryPath=/exec/products/pscrm/v8.4/unit05/cachelog/psreports

2) Check if the report path is set in peopletools > web profile > web profile prod > chose the web prof in you configuration.properties (PROD DEV ... what ever)
Report Repository Path:

Good luck

Honza Michek said...

Thank you Nicolas, I keep coming back to this post to see what I need to set so I thought I should at least offer my thanks.

Toni said...

Hi, great site!, I just have one remark, if after doing all this you still are not able to post a report then go to:

PeopleTools -> Integration Broker -> Integration Setup -> Nodes

and Change Default UserID to PS (has PSADMIN) for ANONYMOUS node, it took me a day to figure this out maybe someone will benefit from this :)

Ramesh said...

Execellent.I was wondering for this process scheduler configuration.Thanks alot its worked fine for me!!!!!!!!!!

bala said...

I searched on so many sites for getting clear peoplesoft.But I feel this is the best one...

Anonymous said...

Thanks a lot.. you have been a great help..

Unknown said...

Hi Nick,
After adding local node to Gateway then tried to ping local node to confirm input that time i get message as "Can't access System Properties: password. Check the configuration of your integration properties fi".
I checked integration properties file its already having encrypted password.

I installed both module FSCM & HRMS and used node PSFT_EP/PSFT_HR respectively. Both are giving same error message. Pls help me out to resolve that.