When I was working on a project I observed BPEL 11g is putting some useful JMS message properties when message is being produced from BPEL to JMS queue/topic.
Following are JMS message properties that BPEL engine copies automatically
tracking_ecid
tracking_compositeInstanceId
tracking_parentComponentInstanceId
tracking_conversationId
We can use above proprieties in many ways and to solve certain correlation problem between BPEL instance that generated it and applications that are consuming.
For example, we build a reporting application which reads messages from JMS destination and report messages onto dashboards. If we wanted to display composite instance id that generated the message then we can simply resort to this property .
Following are JMS message properties that BPEL engine copies automatically
tracking_ecid
tracking_compositeInstanceId
tracking_parentComponentInstanceId
tracking_conversationId
We can use above proprieties in many ways and to solve certain correlation problem between BPEL instance that generated it and applications that are consuming.
For example, we build a reporting application which reads messages from JMS destination and report messages onto dashboards. If we wanted to display composite instance id that generated the message then we can simply resort to this property .
No comments:
Post a Comment