NOTE:
To improve performance, assign the source object to a variable instead of using the Source method every time it is needed.

• NTPERFMON\\Object\\Counter\\Instance
  Access a perflib metric (not supported on UNIX nodes). Object, Counter, and Instance are strings as specified in the current monitor configuration for NT performance monitors. Example: NTPERFMON\\Process\\Elapsed Time\\*
• SNMP\\object id[\\hostname]
  Perform an SNMP get on the specified object id (OID). By default, the collection will be done on the managed node but can be elsewhere if the optional hostname is given. For SNMP, the method will have to wait until the value is returned which might take some time. Example: SNMP\\.1.3.6.1.2.1.1.7.0\\onion.veg.com
• PROGRAM\\command[\\monname]
  Run the specified command or script for gathering the monitored value. The command or script must at some point run the opcmon command to return the value associated with the monitor. If no monitor name is specified, then the default DynPROGRAM must be used. For example, to specify the monitor mymonname: opcmon mymonname=value; to specify the default, opcmon DynPROGRAM=value. Examples:
  PROGRAM\\opcmon DynPROGRAM=12
PROGRAM\\opcmon testmon=25\\testmon
• EXTERNAL[\\monname]
  Wait for a value returned by the execution of the opcmon command. This is similar to the PROGRAM expression but a command is not directly carried out. An external command previously triggered by the ExecuteCommand object must provide the monitor value. The default value is DynEXTERNAL (opcmon DynExternal=10) Examples:
  EXTERNAL
EXTERNAL\\testmon
• WBEM\\namespace\\class name\\property name
  WMI interface (not supported on UNIX nodes). Get access to WBEM values. Namespace, class name and property name are strings as specified in the current monitor configuration for WBEM. Example: WBEM\\ROOT\CIMV2\\Win32_PerfRawData_PerfDisk_LogicalDisk\\DiskReadBytesPersec
• CODA\\data source\\collection\\metric name
  Query a metric from the embedded performance component. Data source, collection and metric name are strings as specified in the monitor configuration for the embedded performance component. Currently if the data source is empty, the string Coda will be used. Example: CODA\\\\CPU\\BYCPU_CPU_TOTAL_UTIL

  You can view a of list of available metrics in the HP Performance Agent Dictionary of Operating System Performance Metrics which is available at http://ovweb.external.hp.com/lpe/doc_serv/. (Select the product Performance Agent, the required version, OS, and language.)

  NOTE:
  In Perl, the backslash character '\' is an escape code. A backslash is only introduced in a string when preceded by another backslash. Because of this, tokens in expressions need to be separated by quadruple backslashes '\\\\'. Example for Perl: my $TestSource = $Policy->SourceEx("PROGRAM\\\\/tmp/script.sh\\\\testmon");

Note that you must either use complete paths or ensure that any needed path is included in the PATH variable.

Example: dir_con = Policy.ExecuteEx ("cmd /c dir c:\")

• expression: (An embedded performance component metric in the format:
  CODA\\data source\\collection\\metric name[\\category])
  
• sourceobj: (Any valid source object)

• expression: An embedded performance component metric in the format:
  CODA\\data source\\collection\\metric name.
  
• rangeofseconds: The number of seconds for which metrics should be returned.
  
• endtime: End time for rangeofseconds. The format of time is of type DATE for VB Script or a string (format DD/MM/YYYY HH:MM:SS) for Perl. The date is optional.

VB Script example:
set Sourceobj = Policy.CreateObject("Ito.OvEpScriptMetric")
Sourceobj.Add "a:",10
Sourceobj.Add "b:",25
Policy.StoreCollection "CODA\\floppy\\disk\\space\\\\gauge",Sourceobj

Perl example:
my $Sourceobj = new Source;
$Sourceobj->Add("a:",10);
$Sourceobj->Add("b:",25);
$Policy->StoreCollection("CODA\\\\floppy\\\\disk\\\\space\\\\gauge",$Sourceobj);

1. Open a command prompt.
2. Change directory to the agent install directory. By default, this directory is:
   \Program Files\HP\HP BTO Software\Installed Packages\{790C06B4-844E-11D2-972B-080009EF8C2A}\bin\OpC\install
3. Encrypt your password with the command: opcpwcrpt yourpassword
4. Use the output string as the password in your script.

If the command is unsuccessful (return value non-zero) the string "ERROR:\n" followed by STDERR is returned. Commands can be run synchronously or asynchronously, as needed. Multiple uses of the Start method are supported. This way, the same script can trigger multiple external commands.