Cisco Cisco Workload Automation 6.3 User Guide

Installing and Configuring the HP OMU Integration

Configuring the HP OMU Integration for CWA

On a separate line in the file, add the 

<opcmsgPath> parameter providing the directory path to the opcmsg 

executable file. 

UNIX example:

Windows example:

opcmsgPath=C:\\Program Files\\HP\\HP BTO Software\\bin\\win64\\OpC\\opcmsg.exe

This step is required for Windows.

Add a new line that specifies the <masterID> parameter. For example:

This step is required for Windows.

Save the changes and close the master.props file.

Stop and restart the Master to recognize the new configuration.

Configuring Unix Agents for HP OMU 

To monitor the CWA agent on Unix, an additional configuration step is necessary prior to distributing the HP OMU 
templates to the machine. The HP OMU templates that monitor the Unix CWA agents rely on this configuration step.

No additional steps are required for CWA Agents on Windows.

You must create the file /etc/TIDAL/aglist on each managed node. You may have to create the /etc/TIDAL directory if it 
does not already exist. Permissions must be set to allow all users to read the file. This means at least read and execute 
permissions on the /etc/TIDAL directory, and read permissions on the aglist file itself (i.e. chmod -R a+rx /etc/TIDAL).

The aglist file should contain a line for each Unix agent that you want to monitor. Since each line includes the host name, 
you can create a single aglist file containing all agents on every node, and place a copy of that file on each CWA Unix 
agent node. Or, you can create a separate file on each managed node that lists only the agentsnode.

The format of each line of the aglist file is as follows:

where:

<descriptive-name> is a defined string explaining what the product is used for or where it is deployed (such as 
“development”, “accounting”, etc.) or just the agent name (for example, TIDAL_AGENT_2).

<user> is the user name (login name) of the user who owns the CWA agent files

<host> is the name of the host machine where the product is installed

<tidalagent-directory-path> is the directory where the product is installed (the $tidalagent variable)

Fields in the aglist file cannot contains spaces. Fields may be separated by spaces or tabs. Per normal Unix 

convention, include a new line at the end of the last line of data.

The following is an example of the aglist file in the java-based version of the CWA Agent for Unix: