We are going to run through the installation and configuration of ITCAM for Apps 6.2.1: PeopleSoft Domain Agent on Linux and Unix systems. There are a lot of things to take into account when installing and configuring these agents. I have included a brief requirement list and some common things that are overlooked. That being said, lets get started!
If you need to refer back to the official installation document you can find it here.
[vc_single_image image=”2854″ img_size=”full” alignment=”center”]Starting the installation
Navigate to your media on the destination system. The name of the installer that you run depends on the Host Operating System version that you are installing. For example if you are installing on a linux based system you will be running the ./setupLinux.bin command, and for Unix based systems ./setupUnix.sh. I have noticed that starting the executable has worked better for me when launching the installer from the command line. A window should pop up and now we are ready to begin our installation process.
[vc_single_image image=”2855″ img_size=”full” alignment=”center”]Click next to continue.[vc_single_image image=”2856″ img_size=”full” alignment=”center”]Accept the agreement, and click next.
[vc_single_image image=”2857″ img_size=”full” alignment=”center”]In the input box that says: “Enter your Tivoli Monitoring installation directory” enter the path of your ITM installation directory (e.g. /opt/IBM/ITM). This would normally be the location where you installed the Operating System agent. Click next.[vc_single_image image=”2859″ img_size=”full” alignment=”center”]This occurs if the destination path doesn’t exist, it should if you have installed ITM.
** Remember ** You must install ITM prior to installing this agent, it is required.
[vc_single_image image=”2860″ img_size=”full” alignment=”center”]Check the box that says PeopleSoft Enterprise (Domain). Click next.
[vc_single_image image=”2861″ img_size=”full” alignment=”center”]Click the box “Perform a local install of the solution on this machine”, then click next.
[vc_single_image image=”2862″ img_size=”full” alignment=”center”]Great! If you have made it this far, then you have successfully installed the Domain agent. Now that this is done, we need to configure the agent.
The following steps will describe the configuration of a PeopleSoft Domain Agent for a Peoplesoft system within our Blue Medora test lab. This example will by no means be an identical configuration to yours.
Note: this example assumes that a PeopleSoft Domain server has been successfully setup prior to installing and configuring the agent.
|CONFIG OPTION||EXAMPLE VALUE||DESCRIPTION|
|Database Type||Oracle||The database type that the Domain 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 Domain’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 Domain is configured to use resides. Ask your DBA for this name.|
|Scheduler Server Name||DH9849OR||Database Instance the Domain 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 Domain’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 Domain. 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||PS||Password assigned to the PeopleSoft user that the Agent uses to monitor the Domain.|
|Confirm PSAE password||PS||Again — Password assigned to the PeopleSoft user that the Agent uses to monitor the Domain.|
|Peopletools base install directory||/apps/psoft/hrms9||The PS_HOME of the Peopletools installation where the Domain resides.|
|Fully qualified path for Application Server config file||/apps/psoft/hrms9/appserv/D100/psappsrv.cfg||The fully qualified path to the Domain’s psappsrv.cfg file.|
|Working directory to place PSAE database query files||/tmp||A readable/writable 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 Domain. 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 Domain 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.|
To start the configuration navigate to the agent install path (e.g. /opt/IBM/ITM ). From there we want to go into the bin directory (EG. /opt/IBM/ITM/bin) and run the command “./itmcmd config -A p8”.
After the configuration starts we will be asked the instance name for this configuration. This, of course, can be anything you want it to be. You will want to come up with a naming convention that you can easily remember. We use dmon01, dmon02, etc. for our Domain agent instances. Type in your instance name and press enter to continue.
You can find this in your ps_home directory if you can’t remember how your domain was configured. There will be a directory within PS_HOME/appserv with the name of your Domain name.
Type in your domain name and hit enter to continue.
In order to find this, navigate to your domain name folder as described above. There will be a file within this directory called “psappsrv.cfg”. Search for the string “Domain ID=” and you should be able to find the Domain ID. This is important to check because the Domain ID and Domain Name don’t always match in all cases.
Type in your Domain ID and hit enter to continue.
Select the database type that you will be using for your configuration. In our example we are using an Oracle database. Type in your database type based on the provided options and press enter to continue.
Note: This should be setup prior to the installation and configuration of the agent. If you are unsure of the hostname for your database please contact your network administrator to verify your configuration.
Enter your database hostname and press enter to continue (e.g. bmpsdb-oracle is ours).
The next step requires that you know the database instance name. Again, if this is an unknown to you, please contact your network administrator.
Enter your database instance name and press enter to continue (eg: DH9848OR)
If you don’t know the database instance name it can be easily determined by looking at the top of the Domain’s psappsrv.cfg file. Search for DBName in that file.
The next three steps will ask you to enter your PSAE credentials. By default the username / password provided are PS/PS. This, however, probably won’t be the case in your environment. Refer to the Loading the ITCAM for Apps 6.2.1: PeopleSoft database components into PeopleSoft blog post for the various options available for the PSAE username
Enter your PSAE credentials and hit enter to continue.
The next two steps will ask you for the location of your PeopleTools environment. Enter the proper paths to your PeopleTools environment.
PeopleTools base install directory (typically called PS_HOME)
(default is: ): /apps/psoft/hrms9
Fully qualified path for the Domain agent psappsrv.cfg file
(default is: ): /apps/psoft/hrms9/appserv/D100/psappsrv.cfg
The next step you will be connecting to the TEMS system. By default the host name of the agent machine will be present. Typically this is not what you want. In our example below, we are connecting to a TEMS with the hostname of tw3g7.
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): 1
TEMS Host Name (Default is: pr4g7): tw3g7
Setting the working directory for the PSAE database query files
You must have read/write/execute permissions to this folder, and it can be any place that makes sense to you. This is where the PSAE temporary query calls are stored.
Working directory for the PSAE database query files (default is: ): /tmp
To start your image, navigate to your ITM directory ( e.g. /opt/IBM/ITM ). Go into the bin directory and execute the following command:
./itmcmd agent -o \<instname\> start p8
Where \<instname\> is the instance name that you configured for the agent. We set this in Step 2.
[hrms9@pr4g7 CB0Z6EN.tar]$ itmcmd config -A p8That should complete the configuration of a PeopleSoft Domain agent monitoring instance. To find out for sure, start the agent using the following command (in our example dmon1 is the instance name):
Agent configuration started...
Enter instance name (default is: ): dmon01
Edit "Monitoring Agent for PeopleSoft Domains" settings? [ 1=Yes,
2=No ] (default is: 1): 1
Edit 'Basic' settings? [ 1=Yes, 2=No ] (default is: 1): 1
Application Server Domain Name (default is: ): D100
Application Server Domain ID (default is: ): D100
Database Type [ 1=Microsoft SQL Server, 2=Oracle, 3=DB2 ] (default
is: ): 2 Database Server hostname (default is: ): bmpsdb-oracle
Database Name (default is: ): DH9848OR
PeopleSoft Application Engine (PSAE) user name (default is: ): PS
Enter Peoplesoft Application Engine (PSAE) password (default is: ):
Re-type : Peoplesoft Application Engine (PSAE) password (default is: ):
Peopletools base install directory (typically called PS_HOME) (default is: ): /apps/psoft/hrms9
Fully qualified path for Application Server config file
(psappsrv.cfg) (default is: ): /apps/psoft/hrms9/appserv
Working directory to place PSAE database query files (default is: ): /tmp
Data collection interval (in minutes) (default is: 10): 10
Maximum number of records to return (0 for unlimited) (default is: 0): 0
Logging Level of the agent [ 1=Debug, 2=Info, 3=Warn, 4=Error,
5=Fatal ] (default is: 3): 3
Will this agent connect to a TEMS? [1=YES, 2=NO] (Default is: 1): 1
TEMS Host Name (Default is: pr4g7): tw3g7
Network Protocol [ip, sna, ip.pipe or ip.spipe] (Default is: ip.pipe):
Now choose the next protocol number from one of these:
- sna -
- 0 for none
Network Protocol 2 (Default is: 0): 0
IP.PIPE Port Number (Default is: 1918): 1918
Enter name of KDC_PARTITION (Default is: null): null
Configure connection for a secondary TEMS? [1=YES, 2=NO] (Default is: 2): 2
Enter Optional Primary Network Name or 0 for "none" (Default is: 0): 0
KCIIN2569E ERROR: You are not running as root, and rexec is not
enabled on this machine,
so your machine boot scripts cannot be updated automatically for
you. Please re-run this configuration session as root, or please manually run
/opt/IBM/ITM/bin/UpdateAutoRun.sh as rootAgent configuration
// The prior error can be fixed by running the following command
[hrms9@pr4g7 CB0Z6EN.tar]$ su -c '/opt/IBM/ITM/bin
./itmcmd agent -o dmon1 start p8[vc_column width=”1/3″ el_class=”sidebar”][ultimatesocial_false align=”left” share_text=”Share: ” networks=”facebook, twitter, linkedin, reddit”]