Resolution:
When using the
process: getProcess method (Unix) or performance: ProcessCount method (Windows NT), you may find that process names longer than a certain length cannot be matched exactly. This limit on process names comes from the operating system functions used to collect this information. For example, in the Windows NT performance monitor a maximum of 14 characters is shown per process. In Unix the ps command often has a similar limit. You can work around this problem by using regular expressions to match portions of process names. For example, to find process abcdefghijklmn you might search for the regular expression "abcdef.*". To find out how many characters are supported in any operating system, we suggest invoking the process method from the microagent's window with no arguments. This will return the process names given by the operating system, and you can see how many characters will be recognized when you specify a process name.
Taken from TIBCO/Hawk release notes (for unix platforms):
          *******************
For Solaris:
Use a script that utilizes the UCB ps utility
(e.g. /usr/ucb/ps -auxww | grep
-c mycommand) in conjunction with
custom::executeForNumber()
          *******************
For HP-UX,  a version of ps has the option of displaying extended format:
ps -exf.    Do a "man ps" on your system for more info.
          *******************

Why can't I match long process names?

Product: TIBCO Hawk Version: OS: --------------------