0 votes
524 views
in Integrations by

1 Answer

0 votes
by (2.1k points)
 
Best answer

1) Start message event : 

- If you are using UCA as start message event where on occurance of an event  you are starting a process, Irrespective of how many numbers of tracks and snapshot you have, only UCA attached to active and default snapshot will get invoked. As there can only be one active and default snapshot on a given process application , No additional steps will required to be performed.

2) Intermediate Message Event:

- If you are using UCA as an intermediate message event, where we are binding the invocation of UCA based on co-relation Id where process gets suspended until  the event with specific co-relation id occurs.All the active snapshots of an application will listen to the event where we can ending up creating a race condition.

- To avoid these, you need to ensure , there will always be unique co-relation id per instance (i.e instance id , case id etc)

  

Related questions

0 votes
1 answer 820 views
0 votes
1 answer 883 views
0 votes
0 answers 172 views
0 votes
0 answers 272 views
asked May 15, 2016 in Integrations by anonymous
0 votes
1 answer 466 views
0 votes
1 answer 424 views
0 votes
0 answers 189 views
0 votes
1 answer 1.1k views
+1 vote
1 answer 879 views

613 questions

493 answers

91 comments

2.0k users

Welcome to BPM Tips Q&A, Community wiki/forum where you can ask questions and receive answers from other IBM BPM experts and members of the community. Users with 2000 points will automatically be promoted to expert level.
Created by Dosvak LLC
Our Youtube Channel
...