This is the 2nd 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 required to load application support of the PeopleSoft Agent(s) into your ITM Server infrastructure – ie, TEMS, TEPS, TEPD, etc.
--Jeremy Rowe (firstname.lastname@example.org)
Note: The following post describes the installation of ITM application support for the PeopleSoft Domain agent. The instructions are identical for the PeopleSoft Scheduler agent.
From the installation media, select the installer that is appropriate for the operating system that your ITM Server components (TEMS, TEPS, TEPD, etc) exist on.
In our demo environment, we are installing the PeopleSoft Domain agent on a MS Windows 2003 Server that is an “all-in-one” ITM Server containing DB2, TEMS, TEPS, TEPD, and TDW so we click setupwin32.exe.
The first screen will appear indicating you are about to install “IBM Tivoli Composite Application Manager for Applications Agent for PeopleSoft Enterprise Application Domain” – ITCAMAAPEAD for short… Click Next.
Next you will be prompted to accept the License Agreement. Press Next after you have accepted the license agreement.
The next panel will ask you for the location of the Tivoli Monitoring installation directory. In our case, TEMS, TEPS, and TEPD are all installed under C:\IBM\ITM. The Solution Installer should auto-detect this location for you and automatically fill in the top panel along with the location of the installation media in the 2nd panel.
The next screen asks you to select the ITM Server components that you want to add ITM application support to. You’ll need to add application support to each HTEMS, RTEMS, TEPS, and TEPD instance in your network that the ITM PeopleSoft Agent data will potentially be flowing through or viewed through. In our case, TEMS, TEPS, and TEPD are all installed on our single server so we will leave the default selections which the Solution Installer auto-detected for us. We also select “Perform a TEMS depot install of the solution on this machine” because we’ll want to add the PeopleSoft Agents to the TEMS agent depot so we can remote deploy it later on. After you’ve made your selections click Next.
The next panel asks you to enter the ITM Administrative credentials and the hostname of the Hub TEMS. In our case, we enter the credentials for sysadmin and the hostname of HUB TEMS host you want to install on and then click Next.
Note: The only reason why you would select “Perform a local install on the the solution on this machine is if PeopleSoft was located on the system and you wanted to install the actual agents on the system. We’ll cover the installation of the actual agents onto PeopleSoft systems in a later blog post.
The next screen asks you to select which application you’d like to add support for. Not much to do here other than ensure PeopleSoft Enterprise (Domain) is checked and click Next.
The next panel tells you what the Installer is going to install. Verify that everything is as you expect and click Next.
Assuming everything went well the installation should complete and you see “Installation completed successfully” in the next panel. Click “Finish” to exit the installer.
There are a couple of things to remember when you are installing:
- You’ll need to add application support to each Hub TEMS, Remote TEMS, TEPS, and TEPD the PeopleSoft monitoring data might potentially flow through (in the case of HTEMS and RTEMS) or viewed through (TEPS and TEPD).
- The installation is more or less same for ITM running on other OS platforms. The only notable difference is the name of the installer (ie: setupwin32 for Windows) is different.
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: email@example.com.