Installing the ITCAM for Apps 6.2.1: PeopleSoft Scheduler Agent on a Windows server

by bluemedora_editor on March 11, 2009

This is the fourth in Blue Medora’s series of technical posts covering IBM’s new ITCAM for Applications PeopleSoft management Agent(s). In this post we’ll focus on the installation and configuration of the PeopleSoft Scheduler agent which is intended to be installed on PeopleSoft servers that are running PeopleSoft Application Domains.

There is a lot of territory to cover here and I will do my best to lay it out in a straightforward, step by step, screenshot by screenshot approach.

–Jeremy Rowe (

Step 1

Ensure installation pre-requisites are met as indicated by Chapter 2 of the PeopleSoft Scheduler Agent User’s Guide:

  • Verify that you are installing the v6.2.1 versions of the PeopleSoft Agent(s). The installation instructions for the v6.2.2 rev of the agents are different and will be covered in a future blog post.
  • Verify Application Support has been loaded into all the TEMs, TEPS, and TEPD components in your environment that the PeopleSoft monitoring data will flow through.
  • ITM Windows Operating System agent v6.2 FP1+ is pre-installed. In our example it has been installed into C:\IBM\ITM.
  • Ensure an IBM JRE 1.5 is installed on the system, a JAVA_HOME is set for that JRE, and that the JRE’s bin directory has been added to the PATH.
  • The ITM PeopleSoft Project has been loaded into the Database that the PeopleSoft Scheduler is configured to use.
  • (Optionally) load the PeopleSoft Project and Datamover script used to create a default ITM_PS User ID that the Agent will use to connect to PeopleSoft (See separate blog entry on this topic).
  • It is highly recommended that you request that your PeopleSoft administrator provide you the information required in Step 14 below prior to the installation.

In our example, we’ve unzipped and untar’ed the ITCAM for Apps 6.2.1: PeopleSoft Scheduler Agent installation media onto the network share Y:\CB0Z6en.tar.

Click setup32.exe to begin the installation:[vc_single_image image=”2814″ img_size=”full” alignment=”center”]

Step 2

The first panel of the Solution Installer screen appears. Click “Next”:[vc_single_image image=”2815″ img_size=”full” alignment=”center”]

Step 3

Accept the License Agreement and click “Next”:[vc_single_image image=”2816″ img_size=”full” alignment=”center”]

Step 4

Enter the location of your existing Windows OS Agent installation (CANDLEHOME) and click “Next”:[vc_single_image image=”2817″ img_size=”full” alignment=”center”]

Step 5

Select “Perform a local install of the solution on this machine” and click “Next”.

Note: This screen is a bit confusing in that it indicates that it is going to add application support. When installing on a non TEMS/TEPS/TEPD server, the “Perform a local install of the solution on this machine” equates to “Install just the monitoring agent on the PeopleSoft server”.[vc_single_image image=”2818″ img_size=”full” alignment=”center”]

Step 6

Select “PeopleSoft Enterprise (Scheduler)” and click “Next”:[vc_single_image image=”2819″ img_size=”full” alignment=”center”]

Step 7

This panel talks about Installing and importing into the local UA – this is another oddity of the Solution Installer. The PeopleSoft agents are not Universal Agents — they are the more fully functional / integrated ITM IRA agents. Don’t worry about the UA messages and click “Next”:[vc_single_image image=”2820″ img_size=”full” alignment=”center”]

Step 8

If all went well, you will get a successful installation message. Again, disregard the mention of UA. Click “Finish”:[vc_single_image image=”2821″ img_size=”full” alignment=”center”]

Step 9

Installation is complete. To confirm that the base PeopleSoft Scheduler Agent has been installed on the system click the Manage Tivoli Monitoring Services icon. It may be on your desktop or you may need to navigate to Start –> All Programs –> IBM Tivoli Monitoring folder to find it.[vc_single_image image=”2822″ img_size=”full” alignment=”center”]

Step 10

If installation was successful, you will see a Monitoring Agent for PeopleSoft SchedulerTemplate as one of the items listed under Service/Application.

Note: In our example the PeopleSoft Domain Agent Template has also been installed.[vc_single_image image=”2823″ img_size=”full” alignment=”center”]

Step 11 (Optional)

When installing onto a ITM 6.2.1 Windows OS Operating System environment (as opposed to ITM 6.2.0), it is possible that the “Monitoring Agent for PeopleSoft Scheduler” Template will not show up in the Manage Tivoli Enterprise Monitoring Service window. If this happens to you, execute the following steps to resolve the issue:

  1. Open a CMD prompt and navigate to the kp9\UA_APP\BUNDLE directory of the install media.
  2. Type: installIraAgent.bat <The CANDLEHOME of your pre-installed Windows OS Agent>. In our example, the command line is: installIraAgent.bat c:\ibm\itm

[vc_single_image image=”2824″ img_size=”full” alignment=”center”]You should be able to go back to the Manage Tivoli Enterprise Monitoring Service window and see a Monitoring Agent for PeopleSoft Scheduler Template as one of the items listed under Service/Application.

At this point you are ready to configure an agent instance to monitor one or more of the PeopleSoft Schedulers on the server you’ve installed onto.

Step 12

Next we are going to create an agent instance to monitor a PeopleSoft Scheduler that is on our server. Right click the Monitoring Agent for PeopleSoft Scheduler entry and select “Configure Using Defaults”:[vc_single_image image=”2825″ img_size=”full” alignment=”center”]

Step 13

Next, you will be prompted to enter a unique instance name. This should be a descriptive name that helps you identify the agent instance when you view it in the TEP and elsewhere. In our case, we’ve named it SW3G3, which is the scheduler name of the PeopleSoft Scheduler we are going to monitor:[vc_single_image image=”2826″ img_size=”full” alignment=”center”]

Step 14

The following panel is where all the PeopleSoft Scheduler specific configuration information needed by the Agent is entered. Any mistake here will likely result in a partially or non-functioning agent when started. Enter the information and click “Ok.”

A brief description of each field and the data we entered for our example follows:


Config Option Example Value Description
Database Type Oracle The database type that the Scheduler is configured to use. You can use the PeopleSoft psadmin CLI utility to determine this value. It can also be determined by searching for “DBType=” in the Scheduler’s psappsrv.cfg file. In our example, that search returns “DBType=ORACLE.”
Database Server Hostname bmpsdb-ora Hostname of the server where the database instance that the Scheduler is configured to use resides. Ask your DBA for this name.
Scheduler Server Name SW3G3 Scheduler Server name the Scheduler is configured to use. You can use the PeopleSoft psadmin CLI utility to determine this value. It can also be determined by searching for “PrcsServerName=” in the Scheduler’s psprcs.cfg file. In our example, that search returns “PrcsServerName=SW3G3”.
Database Name DH9849OR Database Instance the Scheduler is configured to use. You can use the PeopleSoft psadmin CLI utility to determine this value. It can also be determined by searching for “DBName=” in the Scheduler’s psprcs.cfg file. In our example, that search returns “DBName=DH9849OR”.
PSAE user name ITM_PS The PeopleSoft User ID the agent will use to monitor the Scheduler. ITM_PS is the default user ID shipped with the media that optionally could have been installed in the Loading the ITCAM for Apps: PeopleSoft Agent(s) PeopleSoft Project and User_ID in the PeopleSoft Database part of the installation steps (see User’s Guide). Optionally a superuser account such as PS (HRMS) or VP1 (FSCM) can be used.
PSAE password <password> Password assigned to the PeopleSoft user that the Agent will use to monitor the Scheduler.
Confirm PSAE password <password> Again — Password assigned to the PeopleSoft user that the Agent uses to monitor the Scheduler.
Peopletools base install directory c:\apps\psoft\hrms9 The PS_HOME of the Peopletools installation where the Scheduler resides.
Fully qualified path to the Scheduler’s server config file C:\apps\psoft\hrms\appserv\prcs\DH9849OR\psprcs.cfg The fully qualified path to the Scheduler’s psprcs.cfg file.
Working directory to place PSAE database query files c:\TEMP A readable/writeable folder that the agent has permissions to write temp files to.
Data Collection Interval 10 A majority of attribute groups/attributes have their data cached at this interval within the Agent to prevent the agent from adding undue stress to the PeopleSoft Scheduler. Refer to the User Guide for more information on the specific attribute groups affected by this value. We’ve elected to use the default value.
Maximum numbers of records to return 0 This setting acts as a governor for when the PeopleSoft Scheduler might return extremely large datasets back to the Agent and possibly end up timing out PeopleSoft, the Agent, or both. In our lab environment we’ve set it to 0 which means “give us all of the data”.
Logging Level Warn Logging Level of the Agent. WARN is the default which we’ve selected. Use DEBUG if you are having issues.


Below is a screenshot of the configuration panel from our example Agent Instance:[vc_single_image image=”2827″ img_size=”full” alignment=”center”]

Step 15

You will be returned to the Manage Tivoli Enterprise Monitoring Services screen. You should now see an Agent instance for the Scheduler you just configured the Agent to monitor in the Task/Subsystem column.

By default, the Windows User Account that ITM defaults to for starting and running the agent instance is LocalSystem. The User Account must be changed to the same UserID that PeopleSoft is running under. On Windows this is determined by opening the Windows Task Manager on the system where a PeopleSoft Scheduler is already booted and determining which UserID the PeopleSoft processes (psdstsrv is a good one to look for) are running under. On our example PeopleSoft system, PeopleSoft is running as Administrator.

In our example, the Instance name was SW3G3. Right click that row and select “Change Startup”:[vc_single_image image=”2828″ img_size=”full” alignment=”center”]

Step 16

The “Service Startup for Monitoring Agent for PeopleSoft Scheduler” panel will be displayed. By default it will look like this:[vc_single_image image=”2829″ img_size=”full” alignment=”center”]Because the PeopleSoft Scheduler we want to monitor is running as Administrator, we select Log on As: -> This Account and enter the Administrator credentials. In our example, we entered the Administrator credentials and click “OK”:[vc_single_image image=”2830″ img_size=”full” alignment=”center”]If you’ve entered the credentials correctly, the following panel will appear. Click “OK” to proceed:[vc_single_image image=”2831″ img_size=”full” alignment=”center”]

Step 17

You will be returned to the Manage Tivoli Enterprise Monitoring Services screen. To start the Agent instance, Right click the agent instance and select “Start”:[vc_single_image image=”2833″ img_size=”full” alignment=”center”]

Step 18

To confirm the agent instance has been configured correctly and that everything is working correctly, log into the TEP, and navigate down to the server that your monitored agent was started on. Open up the PeopleSoft Scheduler node, right click on the Availability node and choose Workspace –> Agent Messages:[vc_single_image image=”2834″ img_size=”full” alignment=”center”]From the Agent Messages workspace, examine the Performance Object Status view (Top Right view in the Workspace). If all the Attribute Groups indicate ACTIVE and don’t indicate any Errors in the ERROR CODE column, your agent is likely configured correctly and functioning as expected as seen below.

Note: Two of the attribute groups in our example are returning “NO INSTANCES RETURNED”. In our case that simply means that no jobs are or have been recently scheduled on this Process Scheduler and therefore no data is being returned by PeopleSoft for those two attribute groups.[vc_single_image image=”2835″ img_size=”full” alignment=”center”]

Alternate Installation Method A: tacmd based Remote Deploy

If you’ve previously added the PeopleSoft Scheduler TEMS Depot, you can remote deploy the agent using the tacmd CLI instead of performing a GUI based local installation. To perform a tacmd based remote deploy using the exact same configuration values we used in step 14 above, for our example, we enter the following commands (our server hostname was PW3G3):

REM Login into the Tivoli Enterprise Management Server (TEMS)
tacmd login -s localhost -u sysadmin -p password
REM Add P9 Agent for Windows Process Scheduler instance SW3G3 on PeopleSoft server pw3g3


Repeat Step 18 from above to confirm that the remote deploy was successful.

Alternate Installation Method B: TEP based Remote Deploy

If you’ve previously added the PeopleSoft Scheduler agent to a TEMS Depot, you can remote the agent instead of performing a local installation. To perform a remote installation using the exact same configuration values we used in step 14 above, for our example, navigate to the server node you want to deploy the Agent to (in our case server pw3g3 ), right-click the node and select “Add Managed System”:[vc_single_image image=”2836″ img_size=”full” alignment=”center”]Select the Agent you want to remote deploy. We want to deploy the PeopleSoft Scheduler agent so select “”Monitoring Agent for PeopleSoft Scheduler” and click “OK”:[vc_single_image image=”2837″ img_size=”full” alignment=”center”]The next panel will ask for nearly all the same information that you would have entered in Step 14 above, plus it asks you for a monitoring instance name. Remember that the Instance name is a descriptive name that can be named anything. In our case since our Scheduler is SW3G3 we’ve named our Instance Name SW3G3. When you’ve completed entering all the information on this panel click the “”Agent” tab at the top:[vc_single_image image=”2838″ img_size=”full” alignment=”center”]In this panel, enter the same information as you would have entered in Steps 15-16 above. When you are done click “Finish”:[vc_single_image image=”2839″ img_size=”full” alignment=”center”]Repeat Step 18 from above to confirm that the remote deploy was successful.


In the post we covered three different ways (Local Install, tacmd remote deploy, and TEP based remote deploy) of installing and configuring the ITCAM for Apps: PeopleSoft Scheduler Agent on a Windows based PeopleSoft server.

PeopleSoft is a complex ERP and correspondingly the ITCAM for Apps: PeopleSoft Agent(s) have a more involved installation process than some of the other more basic ITM agents (ie, OS Agents, etc). As I stated at the beginning of this post, we highly recommend that the individual installing ITM works hand-in-hand with the PeopleSoft environment’s PeopleSoft admin – that should make the installation fairly straightforward.

If you have any questions regarding the information posted here, feel free to submit a comment, contact us via the form on the Blue Medora contact page or simply send me an email[vc_column width=”1/3″ el_class=”sidebar”][ultimatesocial_false align=”left” share_text=”Share: ” networks=”facebook, twitter, linkedin, reddit”]

Get started

Try BindPlane for free. No credit card required.

Sign up
True Visibility
BindPlane for VMware vRealize Operations

True Visibility allows cloud management teams to use VMware vRealize’s powerful machine learning and capacity planning engine across their entire hybrid cloud environment.

Azure Monitor...everything
BindPlane for Microsoft Azure Monitor

Make Azure Monitor your first-pane-of-glass across your entire multi-cloud, multi-database or hybrid platform environment.

Thank you for contacting us. Your information was received. We'll be in touch shortly.