Blue Medora Blog

Sharing Experience and Knowledge About IT Infrastructure Monitoring and Management

Loading the ITCAM for Apps 6.2.1: PeopleSoft database components into PeopleSoft

This is the 1st in Blue Medora’s series of technical posts on IBM’s new ITCAM for Apps PeopleSoft management Agent(s). In this post we’ll focus on the installation steps for loading the prerequisite Agent components into the PeopleSoft database. This step is mandatory and should be completed before the actual installation of the Agent(s).

--Jeremy Rowe (jeremy.rowe@bluemedora.com)

 

Background

 

A subset of the data collected by the ITCAM for Apps: PeopleSoft Agent(s) is collected from a PeopleSoft system via a custom PeopleSoft Application Engine (PSAE) based program – called a “Project” in PeopleSoft-speak. The Project is loaded into the PeopleSoft database that a particular PeopleSoft application domain or process scheduler is configured to use. The Peoplesoft Application Designer client is used to load the Project, either in GUI or CLI modes.

This post will discuss the steps require to load the required PeopleSoft Project. I’ll also talk about the steps required to load the optional default profile (ITM_PS) that, when loaded into the database, provides a PeopleSoft UserID and Permissions list for the Agent(s). The loading of the default profile involves the loading of a PeopleSoft Project AND a Datamover script.

 

Unzipping the PeopleSoft Project Files

 

The Installation Media for either of the ITCAM for Apps PeopleSoft Agents looks essentially the same. As mentioned above the PeopleSoft Database related files can be loaded from the media of either of the Agents and it only has to be performed once per database, regardless of how many PeopleSoft Domain Agents and Process Schedulers are installed as long as all of the Domains and Schedulers being monitored are connected to the same database instance.

Everything you need for this stage is in two of the top level folders: ITM Application Engine and ITM PeopleSoft User.

The two PeopleSoft Project files within those two folders are zipped up and if you are installing from CDs, as we do in this example, you’ll need to move them to a writeable file system before you can unzip them.

Copy both of those directories to a temporary folder (in our example: C:\PS_TEMP and depending on the PeopleTools version you are installing onto (in our case PeopleTools 8.49), unzip the following two files:

C:\PS_TEMP\ITM Application Engine.49\ITM_QUERY_8.49.zip

and

C:\PS_TEMP\ITM PeopleSoft User.49\ITM_PS_8.49.zip

 

Importing the ITM_QUERY_PROJ PeopleSoft Project into the Database

 

In this step we’ll load the ITM_QUERY_PROJ into the Database that the PeopleSoft Project Schedulers and PeopleSoft Application Domains we want to monitor are connected to.

On your Application Designer system, log in using the appropriate credentials for your PeopleSoft system. Remember, Peopletools 8.48 and 8.49 running against MS-SQL, DB2, and Oracle are supported. Previous iterations of PeopleTools and the other databases (Informix, Sybase, and DB2 on Zseries Linux is not supported).

Our demo PeopleSoft environment is running against SQL Server 2005 running on Windows 2003 Server 64-bit.

Login into the Application Designer.

Once you’ve successfully authenticated and logged into the Application Designer, select Tools –> Copy Project –> From File…

Your will be prompted with a Copy From File: Select Project Dialog Box. Navigate to the file location where you unzipped the IT Application Engine Project. In our example, the unzipped folder is located at:

C:\PS_TEMP\ITM Application Engine.49\ITM_QUERY_8.49\ITM_QUERY

The ITM_QUERY_PROJ should show up in the Select Project from the List Below box. Highlight ITM_QUERY_PROJ and click Select.

Next you will be prompted with a Copy from File dialog box. Ensure all the Definition Type(s) are selected (they should be by default) and click Copy.

If all went well, the Project is loaded and the output log shown on screen shows no errors. Next up, we’ll load the ITM_PS PeopleSoft Project.

Note, the process of loading the ITM_QUERY_PROJ could have been accomplished from the command line with the following command:

C:\apps\hrms9\bin\client\winx86> pside -PJFF ITM_QUERY_PROJ -FP "C:\TEMP_PS" -CT MICROSFT -CD DH9WIN6 -CP PS -CO PS -QUIET -LF out.txt

 

Importing the ITM_PS PeopleSoft Project into the Database

 

Since we are already authenticated to the PeopleSoft Application Designer from the previous step, just select Tools –> Copy Project –> From File… and navigate to the following folder where we unzipped the “ITM PeopleSoft User” zip:

C:\PS_TEMP\ITM PeopleSoft User.49\ITM_PS_8.49

The ITM_PS should show up in the Select Project from the List Below box. Highlight ITM_PS and click Select.

Next you will be prompted with a Copy from File dialog box. Ensure all the Definition Type(s) are selected (they should be by default) and click Copy.

Once again, if all went well the Project has been loaded and the output log shown on screen shows no errors. Next up we’ll load the ITM_PS Datamover script using the Datamover GUI utility.

As with the ITM_QUERY_PROJ example above, the ITM_PS Project could have been loaded from the command line using the following “pside” command.

C:\apps\hrms9\bin\client\winx86> pside -PJFF ITM_PS -FP "C:\TEMP_PS" -CT MICROSFT -CD DH9WIN6 -CP PS -CO PS -LF out.txt

 

Loading the ITM_PS User via DataMover

 

Log into the Data Mover GUI using the credentials for your PeopleSoft environment.

Once you’ve successfully authenticated and the DataMover utility comes up select File –> Open and navigate to the import_itm_ps.dms script. In our example, the script is located in:

C:\PS_TEMP\ITM PeopleSoft User.49\ITM_PS_8.49\DMS\import_itm_ps.dms

The import_itm_ps.dms script appears in the DataMover window. Looks good to us – we click the Run Icon (4th Icon from the left – Looks like a Stoplight).

In the output Window we get a “Error: Unable to open INPUT: itm_ps.dat” unsuccessful completion error.

A quick glance at the User’s Guide (Chapter 2) indicates we might need to edit the file location of itm_ps.date in the script. On the screen we change the following line of the script:

set input itm_ps.dat;

to the location where your C:\itm_ps.dat file has been unzipped to. In our case we placed that file in the root of the C: drive, so we modified the line to:

set input C:\itm_ps.dat

With that change in the script, we click the Run Icon once again and successfully complete the process.

 

Linking the ITM_PS User ID to a Security Profile

 

The final step is to link the ITM_PS UserID loaded above to the appropriate Symbolic ID in Peopletools.

Log into your PeopleSoft PIA using superuser credentials.

In the Left Hand “Menu” navigator, navigate down the PeopleTools –> Security –> User Profiles –> User Profiles:

From PeopleTools –> Security –> User Profiles –> User –Profiles panel, enter “ITM_PS” in the begins with box and click Search.

The General TAB of the ITM_PS User Profile will appear. Select Symbolic ID and change it the appropriate Symbolic ID for your environment. The choice varies depending on database type (Oracle, DB2, MS SQL) and installed PeopleSoft applications. This is also your chance to set the password for the ITM_PS account (It’s “password” by default). After you’ve selected the appropriate Symbolic ID and changed the password, Click Save.

That completes the steps required to load the the custom queries project needed for the PeopleSoft Agent(s) to function, along with loading the default ITM_PS userID that the agents will use to connect into the PeopleSoft environment and monitor data. Make a note of the UserID (ITM_PS if you’ve loaded the default that ships with the media) and password you set in the previous step as you will need that info when you deploy and configure the agents themselves to PeopleSoft systems.

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 at: jeremy.rowe@bluemedora.com

Posted By Blue Medora
March 10, 2009 Tuesday, March 10, 2009