Managing PeopleSoft Process Scheduler

This chapter provides an overview of managing PeopleSoft Process Scheduler and discusses how to:

• Use Oracle Tuxedo software.

• Use the PSADMIN utility to configure PeopleSoft Process Scheduler Tuxedo servers.

• Configure the Analytic Calculation Engine (ACE) and Analytic Engine in the Process Scheduler domain.

• Grant PeopleSoft Process Scheduler administrative rights.

• Use PSADMIN with PeopleSoft Process Scheduler.

Understanding the Management of PeopleSoft Process Scheduler

PeopleSoft Process Scheduler with Microsoft Windows or UNIX operating system is always started by means of Oracle Tuxedo software.

The following table lists Oracle Tuxedo servers that are available with PeopleSoft Process Scheduler. Some servers are optional. Ones that are required are started using the PSADMIN utility’s Quick-configure menu.

Note. OS390 is the only platform on which PeopleSoft Process Scheduler servers are initiated outside of Oracle Tuxedo.

See Using the PSADMIN Utility.

Servers in OS390

The servers that are listed as optional in the preceding table are not available in the OS390 UNIX System Services (USS). These servers require specific functionality in the Oracle Tuxedo software, which is not ported in USS. For this operating system, the PeopleSoft Process Scheduler Server (PSPRCSRV) and Distribution Agent (PSDSTSRV) are the only servers that are booted when you start PeopleSoft Process Scheduler.

When the PeopleSoft Process Scheduler Server initiates an Application Engine program in OS390, it initiates the program using the executable $PS_HOME/bin/psae.

Note. PSAE is the same executable that is used in PeopleSoft releases before 8.4.

Server Logging System

Each of the Process Scheduler Tuxedo servers generates a separate log file.

See Using the PSADMIN Utility.

Using Oracle Tuxedo Software

This section discusses how to:

• Change a local system account to a network account.

• Create a Tuxedo configuration file (PSTUXCFG).

Changing a Local System Account to a Network Account

When Oracle Tuxedo software is installed, the BEA ProcMGR Windows service is set up by default to be started by a local system account—a user account that does not have access to the Windows network. The service must be started by a network account if PeopleSoft Process Scheduler (or processes initiated through Process Scheduler):

• Uses a network printer.

• Accesses files from a network drive.

• Uses Microsoft Windows utilities, such as XCopy, that may access universal naming convention (UNC) paths.

To change an account to a network account:

1. Select Start, Settings, Control Panel.

2. Double-click Services.

   The Services dialog box appears.

3. Select BEA ProcMGR service.

4. Select Stop to stop the current BEA ProcMGR process.

5. Select Yes to change of status message.

6. Select Startup to modify settings.

   The BEA ProcMGR Service dialog box appears.

7. Select the Log On As This Account option.

8. Enter the domain and machine name in the This Account field.

   Note. When configuring the TUXEDO server, the user ID that is designated to be the Application Server Administrator must have read and write permissions to the PeopleSoft file directory and read permission to the %TUXDIR% directory, such as c:\tuxedo.

9. Enter the machine password in the Password and Confirm Password fields.

10. Click OK.

11. Click Start.

    A message in the Services dialog box indicates the Started status.

12. Click Close to return to the Control Panel.

See Also

PeopleTools 8.51 Installation Guide for your database platform.

Creating the Tuxedo Configuration File (PSTUXCFG)

The Tuxedo configuration file (PSTUXCFG) is created in the PS_CFG_HOME\appserv\prcs\<Database Name> directory when you use the PSADMIN utility to:

• Perform a quick-configure and load the configuration by selecting option 4 in the Quick-Configure menu.

• Select the Configure Process Scheduler Server option from the Process Scheduler Administration menu of the PSADMIN utility.

See Understanding PS_HOME and PS_CFG_HOME.

You can detect a new PSTUXCFG file when you see the message: Configuration file successfully created. Loading new configuration.

If changes were made to any of the following parameters in the PeopleSoft Process Scheduler configuration file, Oracle Tuxedo does not recognize the changes until a new Tuxedo configuration file is rebuilt. You can rebuild the PSTUXCFG file by selecting the Configure Process Scheduler Server option. The last task of this option is to rebuild the PSTUXCFG file.

• StartUp

• Process Scheduler

• Tuxedo Settings

• PSTools

• PSAESRV

• PSDSTSRV

• CacheSettings

To go directly to the last task after selecting the Configure Process Scheduler server option, enter n at the Do you want to change any config values (y/n) prompt. The following prompts appear to rebuild the PSTUXCFG file:

• Do you want to change any config values (y/n)? [n]:

• Do you want the Application Engines configured (y/n)? [y]:

• Do you want the Master Scheduler configured (y/n)? [n]:

• Configuration file successfully created.

Add To Path

The Add To Path parameter in the Tuxedo Settings section of the PeopleSoft Process Scheduler configuration file is set with all of the libraries that are needed to run the executables that are delivered with PeopleSoft. If you plan to run processes using software that is not supplied by PeopleSoft, include all of the directory paths that are needed to run the process through PeopleSoft Process Scheduler successfully. Recreate the Tuxedo configuration as noted previously.

You can verify the current library path that is included in the appropriate environment variable by browsing the contents of the PSPRCSRV.ENV file.

Note. If you experience any printing problem in the UNIX environment, be sure to enter a full path in the Add To Path parameter in the Process Scheduler configuration file. For example, you may enter /bin:/usr/bin

Using the PSADMIN Utility to Configure Process Scheduler Tuxedo Servers

All of the PeopleSoft Process Scheduler server configuration information for a specific database is contained in the PSPRCS.CFG configuration file, and the PSADMIN utility provides an interface for editing the PSPRCS.CFG file.

This section discusses how to set parameters for the:

• Distribution Agent (PSDSTSRV).

• Application Engine Server (PSAESRV).

• Master Scheduler Server (PSMSTPRCS).

The PeopleSoft system automatically archives the Process Scheduler configuration file whenever it is changed. The older version is archived as PSPRCS_<Time Stamp>.CFG and the current version becomes psprcs.cfg. The archive directory path is <PS_CFG_HOME>\Appserv\<database>\Archive\, for example, C:\Documents and Settings\admin\psft\pt\8.50\Appserv\fin50\Archive\

Setting Parameters for the Distribution Agent

The Distribution Agent posts reports and system log files to the Report Repository. When the PSPRCSRV server detects that a process has finished, it sends the PostReport Oracle Tuxedo service request to the Distribution Agent to initiate the transfer of the report.

Setting Parameters for the Application Engine Server

This server is responsible for running requests with a process type of Application Engine.

PSAESRV Max Instance and Application Engine Max Concurrent

By default, three instances of the PSAESRV are booted in PeopleSoft Process Scheduler to allow the maximum concurrent processes, as specified in the server definition. If this server is intended to increase or decrease the maximum concurrent for PeopleSoft Application Engine, you must change Max Instances in the PSAESRV section of the process configuration file to match the Max Concurrent value for PeopleSoft Application Engine. PeopleSoft Process Scheduler schedules the maximum concurrent processes for PeopleSoft Application Engine based only on the minimum number from both values.

Note. Because PSAESRV runs both of the Application Engine and Optimization Engine processes, you must include the Max Concurrent for the Application Engine and Analytic Engine process type when you configure the number of PSAESRV tuxedo processes in the domain.

Select PeopleTools, Process Scheduler, Servers to access the Server Definition page.

PSAE Versus PSAESRV

You should use PSAESRV because it delivers improved system performance.

If PeopleSoft Process Scheduler was set to not start any instance of PSAESRV in Microsoft Windows or UNIX, but the server definition corresponding to this server allows you to run PeopleSoft Application Engine, then Process Scheduler initiates an Application Engine program using the $PS_HOME\bin\psae executable.

Note. This functionality is similar to how PeopleSoft Process Scheduler initiates PeopleSoft Application Engine in OS390.

Setting Parameters for the Master Scheduler Server

Master Scheduler is an optional server that enables you to distribute workload across multiple Process Schedulers. However, in certain conditions, a Master Scheduler is required.

Note. You should always use a Master Scheduler.

See Also

Managing PeopleSoft Master Scheduler Servers

Configuring the Analytic Calculation Engine and Analytic Engine in the Process Scheduler Domain

Unlike the Application Server domain that requires you to configure the Analytic Server, you do not need to configure the Analytic Server in the Process Scheduler domain. Because the Analytic Calculation Engine (ACE) and the Analytic Engine are built in the Analytic Server, all Application Engine jobs that are launched by Process Scheduler are run in PSAESRV or on the command line: psae. Consequently, PSAESRV and psae load the analytic instances directly into their own process rather than sending the analytic instances to the Analytic Engine.

See Managing Analytic Servers.

Granting PeopleSoft Process Scheduler Administrative Rights

Personnel who are responsible for administering a PeopleSoft Process Scheduler Server require administrative rights that are granted through PeopleSoft Security.

Using PSADMIN with PeopleSoft Process Scheduler

This section discusses how to use PSADMIN from the command line.

Note. This section does not discuss how to configure, start, and stop PeopleSoft Process Scheduler.

See PeopleTools 8.51 Installation Guide for your database platform.

In addition to the instructions in the Installation and Administration manual about how to administer PeopleSoft Process Scheduler through PSADMIN in interactive mode, this table lists the options PSADMIN provides for the following tasks:

<ps_set> specifies startup settings having the following format:

DBNAME/DBTYPE/PRCSSERVER/OPR_ID/OPR_PSWD/CNCT_ID/CNCT_PSWD/SERV_NAME/LOGOUTDIR/SQRBIN/ADD_TO_PATH/CRYSTALBIN/DBBIN/(NO)ENCRYPT

For example:

psadmin -p create -d PSHRDB1 -t windows -ps PSHRDB1/MICROSFT/PSNT/ PS/PS/people/peop1e/_____/"c:\psft app\log_output"/c:\psfthr\bin\sqr\MSS\binw/c:\WINNT\SYSTEM32/“C:\Program Files\BusinessObjects\BusinessObjects Enterprise 12.0\win32_x86”/c:\apps\db\mssql\binn/ENCRYPT

Show Status of a Process Scheduler Server

The Show Status of a Process Scheduler Server option includes the following Distribution Agent queue information:

See Also

Using the PSADMIN Utility