Trigger metadata moved to NM properties to facilitate BC to BC in Fuji

Previously, metadata (such as the trigger Name, Group and Date) and the actual triggering message were both encapsulated in the XML message sent to the provider endpoint.  However, this necessitates extra intermediary processing in Fuji IFL if the metadata were not desired when connecting the Scheduler binding directly to another such as File.  Thus, SchedulerBC now transmits metadata via Normalized Message Properties (NM Properties) and the triggering message solely represents the message part sent to the provider.  If however trigger metadata is still required in say a BPEL business logic, then they can be accessed via the BPEL Mapper Properties node under the respective BPEL variable as illustrated below:


Comments:

Post a Comment:
  • HTML Syntax: NOT allowed
About

Edward Wong

Search

Archives
« April 2014
SunMonTueWedThuFriSat
  
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
   
       
Today