Configuring Process Control
Process Control executes external procedures specified in automations and manages local and remote processes such as ObjectServers, probes and gateways. The scripts can be installed on UNIX based platforms to allow the process agent to start automatically when the system boots.
To configure Process control for your system; navigate to the directory
This directory contains the install scripts; each depending on your current operating system:
The scripts should be run as the root user. This example shows the script setup for a Linux based system.
- The permissions of the scripts need to be modified to make them executable:
chmod 755 linux2x86install
- Run the install script:
- Set a different name for the process agent if required (Alternative shown in italics):
Name of the Process Agent Daemon [NCO_PA] ORB_PA
- If you require the Process Agent to run in secure mode accept the default response: (Secure mode controls authentication of connection requests.)
Should <pa_name> run in secure mode (y/n)? [y]
- Enter the value for the NETCOOL_LICENSE_FILE environment variable: (The value points to the local Flex License Server.)
Enter value for environment variable NETCOOL_LICENSE_FILE [ 27000@localhost>]:
- The following needs to be added to the file
/etc/rc.d/init.d/ncobefore the line
# Source function library:
- The tool
chkconfigprovides a method for activating and deactivating services.
chkconfigneeds to be configured and is done with the following command:
- Specify the ObjectServer name when prompted.
- The script updates the PAM configuration file /etc/pam.d. The updates made are:
- The service name used when the PAM interface is initialized is Netcool and a config file containing the PAM modules needs to be created for this. The same modules that PAM uses for system users is required. In the directory
/etc/pam.dissue the following command:
- Now that the PAM setup is complete, you need to specify PAM authentication for the ObjectServer. This is done by adding the following setting to the <
ObjectServername>.propsfile found in