Cost-Based Optimization of Integration Flows - Datenbanken ...
Cost-Based Optimization of Integration Flows - Datenbanken ...
Cost-Based Optimization of Integration Flows - Datenbanken ...
- No tags were found...
Create successful ePaper yourself
Turn your PDF publications into a flip-book with our unique Google optimized e-Paper software.
2.4 Use Cases<br />
Receive (o1)<br />
[service: s3, out: msg1]<br />
Selection (o2)<br />
[in: msg1, out: msg2]<br />
Fork (o1)<br />
Selection (o3)<br />
[in: msg2, out: msg3]<br />
Assign (o2)<br />
[out: msg1]<br />
Assign (o4)<br />
[out: msg3]<br />
Assign (o6)<br />
[out: msg5]<br />
Selection (o4)<br />
[in: msg3, out: msg4]<br />
Invoke (o3)<br />
[service s3, in: msg1, out: msg2]<br />
Invoke (o5)<br />
[service s4, in: msg3, out: msg4]<br />
Invoke (o7)<br />
[service s5, in: msg5, out: msg6]<br />
@type='SCM'<br />
Switch (o5)<br />
[in: msg4]<br />
@type='MAT'<br />
Setoperation (o8)<br />
[in: msg2,msg4, out: msg7]<br />
UNION DISTINCT<br />
Translation (o6)<br />
[in: msg4, out: msg5]<br />
Translation (o7)<br />
[in: msg4, out: msg5]<br />
Setoperation (o9)<br />
[in: msg7,msg6, out: msg8]<br />
UNION DISTINCT<br />
Assign (o8)<br />
[in: msg5, out: msg6]<br />
Assign (o10)<br />
[in: msg8, out: msg9]<br />
Invoke (o9)<br />
[service s6, in: msg6]<br />
Invoke (o11)<br />
[service s6, in: msg9]<br />
(a) Plan P 5<br />
(b) Plan P 6<br />
Receive (o1)<br />
[service: s3, out: msg1]<br />
Fork (o2)<br />
Assign (o1)<br />
[out: msg1]<br />
Assign (o3)<br />
[in: msg1, out: msg2]<br />
Assign (o6)<br />
[in: msg1, out: msg5]<br />
Assign (o9)<br />
[in: msg1, out: msg8]<br />
Assign (o11)<br />
[in: msg1, out: msg10]<br />
Invoke (o2)<br />
[service s6, in: msg1]<br />
Invoke (o4)<br />
[service s1, in: msg2, out: msg3]<br />
Invoke (o7)<br />
[service s2, in: msg5, out: msg6]<br />
Invoke (o10)<br />
[service s4, in: msg8, out: msg9]<br />
Invoke (o12)<br />
[service s5, in: msg10, out: msg11]<br />
Assign (o3)<br />
[out: msg2]<br />
Translation (o5)<br />
[in: msg3, out: msg4]<br />
Translation (o8)<br />
[in: msg6, out: msg7]<br />
Translation (o13)<br />
[in: msg11, out: msg12]<br />
Assign (o4)<br />
[out: msg3]<br />
Join (o14)<br />
[in: msg1,msg9, out: msg13]<br />
Join (o15)<br />
[in: msg13,msg12, out: msg14]<br />
Join (o16)<br />
[in: msg14,msg4, out: msg15]<br />
Join (o17)<br />
[in: msg15,msg7, out: msg16]<br />
Assign (o18)<br />
[in: msg16, out: msg17]<br />
Invoke (o19)<br />
[service s6, in: msg17]<br />
INNER<br />
INNER<br />
INNER<br />
INNER<br />
Invoke (o5)<br />
[service s6, in: msg2, out: msg4]<br />
Invoke (o6)<br />
[service s6, in: msg3, out: msg5]<br />
Assign (o7)<br />
[in: msg4, out: msg6]<br />
Assign (o8)<br />
[in: msg5, out: msg7]<br />
Invoke (o9)<br />
[service s7, in: msg6]<br />
Invoke (o10)<br />
[service s7, in: msg7]<br />
(c) Plan P 7<br />
(d) Plan P 8<br />
Figure 2.11: Example Vertical <strong>Integration</strong> <strong>Flows</strong><br />
the collected orders information. Furthermore, two queries are prepared in order to read<br />
orders and orderline information from the data warehouse. After those data sets have been<br />
extracted from the data warehouse, two Invoke operators are used in order to load the data<br />
into the DSS.<br />
To summarize, the plans P 5 and P 7 are data-driven integration flows, while the plans<br />
P 6 and P 8 are scheduled and thus, time-based initiated integration flows. Only plan P 5 is<br />
initiated synchronously, while the plans P 6 , P 7 , and P 8 are all initiated asynchronously.<br />
We will use these eight integration flows from the use cases <strong>of</strong> horizontal and vertical<br />
integration as running examples throughout the whole thesis. All <strong>of</strong> these flows exhibit<br />
different characteristics that can be exploited for optimization purposes.<br />
31