TruClient scripts with BPM - Not Initialized status or errors not reported

The TruClient script uses very long pathnames.

If the BPM workspace path is also very long (ex: "C:\Documents and Settings\All Users\Application Data\HP\BPM\workspace"), some of the files in the workspace directory may become inaccessible.

This may cause scripts uploaded to Business Process Monitor to get stuck in a "Not initialized" state.

Another problem that can occur: script errors not being reported correctly to BSM (ex: transactions showing "No Data" instead of "Critical").

Have more questions? Submit a request


Please sign in to leave a comment.