summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-09-30 08:51:15 (EDT)
committer Stephan Born2013-10-23 06:48:35 (EDT)
commita7019db3f4272b1fe3239235155f871dfe793cf4 (patch)
tree1549faed6b41aa00ad363c8cc3ec2c2ee85e793d
parente995cbd3d9cc9ebb3266fe00ce080bfb844df410 (diff)
downloadorg.eclipse.stardust.documentation-a7019db3f4272b1fe3239235155f871dfe793cf4.zip
org.eclipse.stardust.documentation-a7019db3f4272b1fe3239235155f871dfe793cf4.tar.gz
org.eclipse.stardust.documentation-a7019db3f4272b1fe3239235155f871dfe793cf4.tar.bz2
CRNT-30740 - Added details for corelation
git-svn-id: https://svn.csa.sungard.com/repos/ipp2/product/branches/b_dev_7_2_x/stardust/documentation@67661 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b Signed-off-by: Vrishali Doke <vrishali.doke@sungard.com>
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/applications/pep-application-generic-end.htm12
1 files changed, 11 insertions, 1 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/applications/pep-application-generic-end.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/applications/pep-application-generic-end.htm
index 6e735df..f5143fd 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/applications/pep-application-generic-end.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/applications/pep-application-generic-end.htm
@@ -459,7 +459,17 @@ derived from configuration variables.
</p>
<p>There are multiple ways to address the correct activity instance to be
-completed by adding certain header fields to the Camel message.
+completed by adding certain header fields to the Camel message.</p>
+<p>
+For the following cases, when we use corelation it should always use activity ID, process ID and data
+of the same consumer application.
+In this case only consumer activity will get completed.
+For example, when we corelate an activity using process ID, activity ID and data,
+the activity found should be same
+as Consumer activity for which consumer route is activated. If we give any
+other activity say DummyAct then in consumer route it will find the DummyAct activity,
+which won't be useful and no action will be taken on that found activity. In this case,
+the consumer activity will remain in hibernated state.
</p>
<h3>Correlate by activity instance OID</h3>