If integrating your PeopleSoft environment with BMC Control-M for PeopleSoft automation system sounds intimidating to you, then the following high-level setup steps can get you started. It should not be a big challenge because it is a straightforward process that involves putting “everything in its place”. This method has worked with PeopleTools 8.48 and 8.52, Windows Server 2003 and 2008 R2, and HRMS 8.8/9.0/9.1. If you already have Control-M Server installed on your network and it is up and running, you can proceed with these steps to integrate the Control-M PeopleSoft module with your PeopleSoft environment:
1. Install Control-M Enterprise Manager on a server or workstation of your choice. You don’t have to install it on all machines. Control-M Enterprise Manager provides the necessary tools to monitor and maintain the whole integrated Control-M interface. The tools include: Control-M Configuration Manager, Control-M Desktop, Control-M Reporting Facility, and Control-M Enterprise Manager.
2. Install Control-M Agent on all Windows servers or workstations where the automated batch jobs will be kicked off. The Control-M Agent can be stopped and restarted as needed from Windows Services.
3. Once the Agent is installed, launch Control-M Configuration Manager and add the Control-M Agent host name. The host name should be the name of the server or workstation where the Agent is installed. Once added, verify that the Agent is communicating properly with the Control-M server.
4. Verify that the server/workstations, where the Control-M for PeopleSoft module will reside, have Java Runtime Environment installed. If not, make sure the proper version of JRE is loaded before continuing.
5. Run the Control-M Module for PeopleSoft setup from the installation media. The module should be installed on the same servers where the PeopleSoft application/process scheduler servers are running.
6. Log into the PeopleSoft database and import CONTROLM Component Interface. This CI should be located in the Control-M Module for PeopleSoft installation media.
7. There are two PeopleSoft JAR files that must be copied to the proper folders/directories: PSJOA.JAR and PSAPI.JAR. These two files are necessary to establish the connection between PeopleSoft and Control-M. While PSJOA.JAR can be copied from ‘PS_HOME/class’ directory, PSAPI.JAR must first be generated from the CONTROLM Component Interface imported in the previous step. Both PSJOA.JAR and PSAPI.JAR should be copied to the Control-M Agent directory (in our case, we copied both to: “C:Program FilesBMC SoftwareCONTROL-MAgentDefaultCMPS8java8.52”).
8. Create a Connection Profile using the Control-M Module for PeopleSoft. This profile should contain the profile name, PeopleSoft user, PeopleSoft password, application server name, and Jolt Port of the PeopleSoft environment.
9. Once the Connection Profile is created, validate it using the Control-M for PeopleSoft Configuration Utility by making sure you can ping the PeopleSoft server, verify the component interface, and connect to PeopleSoft CM. If the validation is successful, you should be ready to go. If not, a troubleshooting session should be initiated to trace the issue.
The Control-M Module for PeopleSoft has enabled us to automate a great deal of our manual PeopleSoft administration work, reduce delays in processing PeopleSoft jobs, decrease errors, take immediate action when failures occur, and monitor the whole PeopleSoft environment from one central interface. We currently run hundreds of PeopleSoft jobs, secure file transfers, and file move jobs through Control-M on a daily basis.