#2 By triggers, I meant WM broker or JMS triggers, where we can specify something like “Apama” instead of a subscribing service.
Looks like this is not the case. Still, please suggest.
You can publish JMS messages from WM using whatever mechanism you usually use to publish messages from WM.
From Apama, the supported ways of receiving messages are as a JMS client, using the UM connectivity plug-in, or using the Digital Event Services connectivity plug-in (which is the simplest way to get messages from wM Integration Server).
The WM concept of a JMS trigger doesn’t really make sense within the Apama correlator, where we have a simple, transport-agnostic and unified way to handle incoming events that is fully asynchronous (in line with concept of CEP). Just configure the JMS/UM/DES transport to receive the requried messages, then subscribe to the associated channel(s) from any monitors that want to see the data (that is if using UM/DES; if using JMS make sure your monitor isn’t running in a private context and you’ll get the messages without even subscribing to a channel).
4 Do we need the monitor.subscribe() statement in our monitor if we are using JMS correlator to receive messages; or only while using the UM connectivity plug-in?
No, JMS (for the time being) is an exception. Incoming JMS messages go to all public contexts automatically without subscribing, so provided you’re not using a monitor instance running in a private context that you’ve created you’ll be able to listen for incoming JMS events from any monitor. There’s nothing to subscribe to for JMS, just need to configure the the transport with the queues/topics to pull events from.
#5 By query, I meant EPL query that does the same work as the EPL monitor. So my question is if we can have an EPL query receive messages from UM/other bus, just as the monitor does. If yes, what should we write in the EPL query to subscribe; just like we have monitor.subscribe() in case of monitors.
For getting JMS messages from queries see http://www.apamacommunity.com/documents/10.3.0.1/apama_10.3.0.1_webhelp/apama-webhelp/index.html#page/apama-webhelp%2Fco-DepAndManApaApp_query_connecting_to_jms.html
For getting messages from UM/DES or any other connectivity plugin, you need to configure your transport to send messages into the correlator on the special channel name com.apama.queries, or alternatviely write a simple piece of forwarding EPL that subscribes to whatever channel the events are coming in on and forwards them to com.apama.queries. See http://www.apamacommunity.com/documents/10.3.0.1/apama_10.3.0.1_webhelp/apama-webhelp/index.html#page/apama-webhelp%2Fco-EplQueRun_comparison_of_queries_and_monitors.html
#6 Here also, I meant EPL query. I think we can use “send to” here also to send events to UM. Please confirm.
Yes you can use send … to … from a queries action just as you can from EPL, to send to JMS, UM/DES or other connectivity plugins.