Absent Member.. Absent Member..
Absent Member..

[OO Tip] Monitoring Remedy with a Flow


Is there an existing Operations Orchestration (OO) flow which checks for (or triggers on) an Apache Tomcat 500 error, creates the ticket, then restarts the service for Remedy?



What is needed is a three step process.

Here is a recommendation:

1.External tool calls appropriate OO flow with appropriate inputs 

2.Act on the call (e.g. restart the affected TomCat)

3.The flow would respond to the Remedy ticket with its activity results.


Note: OO is not a monitoring tool, recommend using an external monitoring tool (e.g. SiteScope) and calling OO. This is documented in the Software Developers Kit (SDK) in the various mechanisms which can be used to launch an OO flow.

Please follow this link to the HP Live Network for Operations Orchestration:




Under the "Patches & Binaries" header select either the 9.07 or 10.00 SDK.



Direct link to the document here:


HP Support
If you find that this or any post resolves your issue, please be sure to mark it as an accepted solution.
Labels (1)
0 Replies
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.