3rd Party Batch Scheduler for PeopleSoft

Organizations that manage critical applications such as HR or their Supply Chain with Peoplesoft run many jobs both within the Process Scheduler as well as outside of the Peoplesoft environment. The scheduling facilities included in Peoplesoft are rudimentary and are not capable of managing workload outside of Peoplesoft making it challenging to get an end-to-end business view or to avoid manual processes that can cause outages.


ERP systems are the mainstream systems in most of the organization. Different ERP system and other system in the organization has to co-exist in the organization to support the business processes.


Business Need

  • Integrate the PeopleSoft production environment with other systems
  • Eliminate errors and processing delays
  • Enhance the PeopleSoft built-in scheduler capabilities 
  • broad range of platform and application support integrate different system in the organization.
In an organization multiple batch process across different applications needs to scheduled in particular order. manage, monitor  and analyze the impact of different batch process on business process is very essential.
Some of the companies use Crontab - in the unix to schedule the jobs in the PeopleSoft and other applications. It will be common place to analyze and manage scheduling. This is  platform dependent and doesn't support all the process types.


There are few Scheduling softwares - Which can manage the different batch processes across different platform and  applications and server as a common point to manage and monitor the different business processes. Workflow of different business process can be created with these softwares/applications.
job dependencies, workload balancing, and event-based job execution can be managed easily.


3 - Third party Schedulers that are popularly used with Peoplesoft ERP systems.
1) Unicenter Autosys
2) Control - M
3) Tivoil Work schedular


There are Peoplesoft adapters so that these schedulers can connect to Peoplesoft system.


The Adapter connects to the PeopleSoft Enterprise database and collects the data it needs to define the task. The Adapter submits the task, waits for Oracle’s PeopleSoft Enterprise Process Scheduler to finish running the task, and retrieves the status changes in the PeopleSoft Enterprise database. The status can be viewed from the Schedular Operator Console and the PeopleSoft Enterprise Process Monitor.


The integration is accomplished by inserting PeopleSoft Enterprise job or process information into various database tables that emulate a submission through the PeopleTools GUI. Once the PeopleSoft Enterprise work has been scheduled, it is monitored to completion, reflecting status changes back to the Scheduler.

1 comments  

PeopleSoft Tracing & Logging

Tracing online People Code and SQL


1. Select Trace at the login screen or add “&trace=Y” to the login URL OR - To set trace flags, click here (use this link.

2. Choose the options in the tracing screen and login.
3. Perform the actions you wish to record.
4. Once complete logout and retrieve the file from the /appserv//LOGS directory. 
The trace file name will include your login name.


Tracing online PeopleCode and SQL (Alternative)

1. Login to PeopleSoft and navigate to PeopleTools > Debug.
2. Choose the options and save.
3. Perform the actions you wish to record.
4. Once complete logout and retrieve the file from the
/appserv//LOGS directory. The trace
file name will include your login name.


Application Engine Tracing
1. Open the process definition
2. Select the overrides tab.
3. Select Append on the parameters field.
4. Enter -TRACE 131 -TOOLSTRACEPC 3596 -TOOLSTRACESQL
143
5. Save the record.


SQR Tracing
1. Open the process definition
2. Select the overrides tab.
3. Select Append on the parameters field.
4. Enter –DEBUG[ABC]… (replace ABC with the debug letters
provided in the sqr, sqc source).
5. Save the record.


Cobol Tracing
1. Open the Cobol SQL process type for the platform you are running on.
2. Enter 255 in the command line field between two forward slashes “//”.
3. Save the record.
%%PRCSNAME%% %%DBTYPE%%/%%DBNAME%%/%%OPRID%%/%%OPRPSWD%%/%%RUNCNTLID%%/%%INSTANCE%%/255/%%DBFLAG%%
4. Run the process and retrieve the COBOL sqltrace from the process monitor.


Tracing Settings
1. Both the process scheduler (psprcs.cfg) and application server (psappsrv.cfg) config files allow for permanent tracing settings as well as setting up trace Masks. psprcs.cfg - /appserv/prcs// psappsrv.cfg - /appserv//

2. Trace Masks are setup to limit the amount of tracing allowed when a user wants to trace through the front end package (see all methods
above).

3. LogFence allows for lower and higher detail tracing with regards to application server standard logging. This is ideal for identifying problems on the application server.

4. To enable the trace link in the Sign on page.
    People-tools > Web-profile.
  
   Web profile > Debugging Tab -> Check the Option - Show Trace Link at Signon
  

1 comments