Mauricio Salatino [http://community.jboss.org/people/salaboy21] created the discussion "Re: A question on the external event using event Correlation" To view the discussion, visit: http://community.jboss.org/message/592495#592495 -------------------------------------------------------------- Hi, basically you have two different things to solve, one is about how to locate the correspondant session and the other is how to choose the right process to notify the event right? For locating the right process to signal and to restore the right session we usualy implement a business layer that store a business key and information about your workitem or processid. Take a look at the following example, using that layer you can also map a JMS message to a specific event or workitem to complete. I think that you can use the same approach provided in the example. Example: https://github.com/Salaboy/Drools_jBPM5-Training-Examples/tree/master/jbp... https://github.com/Salaboy/Drools_jBPM5-Training-Examples/tree/master/jbp... Hope it helps! -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/592495#592495] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Jim Hill [http://community.jboss.org/people/jdh] created the discussion "Re: A question on the external event using event Correlation" To view the discussion, visit: http://community.jboss.org/message/593075#593075 -------------------------------------------------------------- I am implementing a similar solution and agree with Mauricio that you need to implement a business layer.  I am not as familiar with Drools and took a different approach which I will describe briefly.  I implemented the Selective Consumer pattern as described in Hohpe and Woolf's Enterprise Integration Patterns book.  In my case processes were started before the business key was assigned, so my messages do not always pass around the same business key.  This makes it harder to link them back to a running instance of a process.  I ended up writing a manager component in mule that receives JMS messages that may need to go to JBPM processes.  This component manages the start and end of process instances.  When it receives a messages it extracts the business key from the message and looks to a self contained map to determine if this key is related to an active process. If we find a match I pass the message to the active state in the process.  These are defined as custom nodes in the process.  The class implements ExternalActivityBehavior.  It is responsible for making sure it received the right message.  The value it returns is used by a decision node to determine if we need to keep waiting or can move on to the next wait state. This is just one approach.  I welcome feedback from those who have been at this longer than I have.  It is working for me, but I am struggling with group timers which I am trying to implement in order to kill the process if the right message does not show up in a specified period of time.  Hope this adds an option for you to pursue. Jim -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/593075#593075] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

byungwoojun [http://community.jboss.org/people/byungwoojun] created the discussion "Re: A question on the external event using event Correlation" To view the discussion, visit: http://community.jboss.org/message/604069#604069 -------------------------------------------------------------- As I addressed above, to support an async message event (external), I store a unique correlation id, with a session id and a process instance id. When an intermediate message arrives, I restore a session and a procss instance is based on the incoming message correlation id field. Using the following code: ksession.signalEvent(eventType, eventData, restoredProcessInstanceId); It worked nicely, but there is a problem. If the async message event is in a reusable sub-process (not in the top-level process), the above method won't work because the sub-process has its own process id. I looked at the jBPM ProcessInstanceInfo database table, there is no link between the parent and the sub-process. So, how do I get the sub-process process id when the top-level hit the async message event and returns back to the process caller? Any suggestion will be appreciated. bwj -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/604069#604069] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

Francesco Pietrobelli [http://community.jboss.org/people/francesco.pietrobelli] created the discussion "Re: A question on the external event using event Correlation" To view the discussion, visit: http://community.jboss.org/message/609252#609252 -------------------------------------------------------------- Sorry for the direct question (and my poor english), actually i'm to end of working day. But reading http://www.omg.org/cgi-bin/doc?dtc/10-06-02 BPMN 2.0 by example and http://www.omg.org/spec/BPMN/2.0/ BPMN 2.0 spec i'm became curious about correlation, does exists a jBPM5 example like Salaboy Training Examples (thanks to Mauricio S.) about correlation? Even just a request correlated to a response by an id defined in the payload of the messages. Maybe tomorrow i add more details about what i want to do... Greetings -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/609252#609252] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]

byungwoojun [http://community.jboss.org/people/byungwoojun] created the discussion "Re: A question on the external event using event Correlation" To view the discussion, visit: http://community.jboss.org/message/609667#609667 -------------------------------------------------------------- After my previous post, using ksession.signalEvent(eventType, eventData) without the process instance id, I realized that the method does NOT work well. The jBPM engine is supposed to find the proper process instance id in the session, but many times it did NOT point the correct process instance id when there are some left-over data in the EventType database table (due to multiple process instances for the same process definition are running (of course they have the same eventType name) or previous sessions failed and did not clean up the database table entries). When I used the intermediate message event in a nested subprocess, the engine confused more. Once the engine returned a wrong process instance id, a wrong process instance ened up being processed. Then, subsequent process instances got null pointer exceptions, etc. It was NOT pretty. I reported this problem, see http://community.jboss.org/thread/166536 http://community.jboss.org/thread/166536, that the name query ProcessInstanceWaitingForEvent used by the ksession.signalEvent didn't return with the correct process/subprocess instance which has the intermediate event type. So, my team solved the issues as follows: 1. When we start the process, we store a unique correlation id, a session id and a process instance id (it will be the top-level process instance id) in a database table (e.g., correlation id, session id, process instance id). 2. When an intermediate message arrives, we restore the session using the incomig correlation id from the database table. Using this table, we also find the top-level process instance id. 3. Using this process id, we query the EventType database table to find the process or sub-process which has the proper event type. The EventTypes database table has two columns: instance id and element. e.g., InstanceID              Element ----------------------------------------------------------------------------------- 1356                       processInstanceCompleted:1357 1357                       eventType1 As you can see, the 1356 row points the 1357 row. In my opinion, the proper way to find a correct pid is drilling down the chain from the top-level pid which is getten from the startProcess. Instead of embedding the next pid part of the text data in the Element field, if we have the third column to point the next pid, we could use SQL chain query. Using the current schema, I need to get the 356 instance id, parse the element text (after the colon), then, get the row 1357 instanceid, so on.... Since we don't want to add additional column at this time, we created a function with two parameters: eventType, topLevelProcessInstanceId: - the function queries the EventType database table using the topLevelProcessInstanceId. - it parses the element column.      - If the element contains the same eventType, it returns the processInstanceId.      - Otherwise, it gets a sub-string after ":" (e.g., 1357). Use this sub-string (need to convert it to long) as a parameter along with the eventType (unchanged), and call the same function recursively until the element is equal to the event type.  4. After the function, we call ksession.signalEvent(eventType, eventData, foundProcessInstanceId); As you noticed, this method may end up querying multiple times depending on the depth of sub-processes. There could be some performance penalties. But, it works reliably regardless the EventTypes database table entries. If jBPM engine itself supports the correlation out-of-the-box, it would be great. But for now, we need to code for the correlation support. Any suggestions would be appreciated. bwj  -------------------------------------------------------------- Reply to this message by going to Community [http://community.jboss.org/message/609667#609667] Start a new discussion in jBPM at Community [http://community.jboss.org/choose-container!input.jspa?contentType=1&...]