Monitor adapters are triggered by the app that it is monitoring and not by a workflow.
When an monitor adapter is triggered it generates an context item inputevent which can be used to trigger a workflow.
Hi A Kachwala,
Thanks for quick reply.
OK ..fine but could you please explain a little bit more about what should we do after configuration of a monitor adapter.?
And if we have more than one monitor adapter on a single peer then how can we track the context item "inputevent " from which monitor adapter it is coming..??
I have successfully configured monitor adapter but facing issues while using context item inputevent.
Could anyone please explain me how to use this and how toc check the valuse stored in this inputevent.
1 of 1 people found this helpful
In the inputevent application details will be there like,server name,text,adapter name, etc.in xml format.
what we need to do id create rules and apply x path expression ,based on that configure a particular process.
For monitor adapter you have to follow 4 steps
step-1) First configure any monitor adapter, eg. SQLMonitor,SNMPMonitor etc. that you want.
step-2)Enable the adapter in peer.
step-3)Create a workflow that will help if the monitor adapter found any event.
In your workflow , in START activity , create a context item named inputevent (in small letter all ,with no other text) .This inputevent is used to capture the event occurred by monitor adapter. Then what will be your workflow, you can do.
step-4)Create a Rule : You can find Rule in the bottom if your module. in that give your Rule name and conditions that you want . This Rule is useful as if the condition(s) is/are true then the corresponding workflow will work.
This is my opinion. If you want any help , please feel free to ask.
Thanks & Regards