uCosminexus Service Platform, Overview
![[Contents]](FIGURE/CONTENT.GIF)
![[Glossary]](FIGURE/GLOSS.GIF)
![[Index]](FIGURE/INDEX.GIF)
![[Back]](FIGURE/FRONT.GIF)
![[Next]](FIGURE/AFTER.GIF)
(1) When two synchronous invoke service activities are arranged
- When the processing continues successfully
- In such a case, the transaction is committed immediately before the message send processing of each invoke service activity, and a new transaction is started.
- The following figure shows the transaction scope when the processing continues successfully during the synchronous service invocation:
Figure 3-16 Transaction scope when the processing continues successfully (Synchronous service invocation)
![[Figure]](FIGURE/ZC041500.GIF)
- When an exception occurs
- When the processing of Service invocation 2 results in an error because of an exception, a rollback occurs up to the point where the transaction was committed (Receive: Completed, Service invocation 1: Completed, Service invocation 2: Executing).
- The following figure shows the transaction scope when an exception occurs during the synchronous service invocation:
Figure 3-17 Transaction scope when an exception occurs (Synchronous service invocation)
![[Figure]](FIGURE/ZC042100.GIF)
(2) When an asynchronous and a synchronous invoke service activity are arranged
- When the processing continues successfully
- In such a case, the transaction is not committed in the message send processing of the asynchronous invoke service activity, but is committed in the message send processing of the synchronous invoke service activity, and a new transaction is started.
- The following figure shows the transaction scope when the processing continues successfully during the asynchronous and synchronous service invocation:
Figure 3-18 Transaction scope when the processing continues successfully (Asynchronous and synchronous service invocation)
![[Figure]](FIGURE/ZC041600.GIF)
- When an exception occurs (Asynchronous and synchronous service invocation)
- When the processing of service invocation 2 results in an error because of an exception in a configuration where service invocation 1 is asynchronous and service invocation 2 is synchronous, a rollback occurs up to the point where the transaction was committed (Receive: Completed, Service invocation 1: Completed, Service invocation 2: Executing).
- The following figure shows the transaction scope when an exception occurs during the asynchronous and synchronous service invocation:
Figure 3-19 Transaction scope when an exception occurs (Asynchronous and synchronous service invocation)
![[Figure]](FIGURE/ZC042200.GIF)
- When an exception occurs (Synchronous and asynchronous service invocation)
- When the processing of service invocation 2 results in an error because of an exception in a configuration where service invocation 1 is synchronous and service invocation 2 is asynchronous, a rollback occurs up to the point where the transaction was committed (Receive: Completed, Service invocation 1: Completed, Service invocation 2: Executing).
- The following figure shows the transaction scope when an exception occurs during the synchronous and asynchronous service invocation:
Figure 3-20 Transaction scope when an exception occurs (Synchronous and asynchronous service invocation)
![[Figure]](FIGURE/ZC042300.GIF)
(3) When two asynchronous invoke service activities are arranged
- When the processing continues successfully
- In such a case, the transaction is not committed in the message send processing of the asynchronous invoke service activity. Therefore, the transaction is committed when the business process sends a response.
- The following figure shows the transaction scope, when the processing continues successfully during the asynchronous service invocation:
Figure 3-21 Transaction scope when the processing continues successfully (Asynchronous service invocation)
![[Figure]](FIGURE/ZC041700.GIF)
- When an exception occurs
- When the processing of service invocation 2 results in an error because of an exception, a rollback occurs up to the point where the transaction was committed (Receive: Unexecuted, Service invocation 1: Unexecuted, Service invocation 2: Unexecuted).
- The following figure shows the transaction scope when an exception occurs during the asynchronous service invocation:
Figure 3-22 Transaction scope when an exception occurs (Asynchronous service invocation)
![[Figure]](FIGURE/ZC042400.GIF)
(4) When a data transformation activity exists after a synchronous invoke service activity
- When the processing continues successfully
- In such a case, the transaction is committed immediately before the message send processing of each invoke service activity, but the transaction is not committed in the data transformation activity. This holds true even for the activity other than the activity shown in Table 3-7.
- The following figure shows the transaction scope when the processing continues successfully in the presence of the activities such as data transformation:
Figure 3-23 Transaction scope when the processing continues successfully (When activities such as data transformation exist)
![[Figure]](FIGURE/ZC041800.GIF)
- When an exception occurs (When activities such as data transformation exist after synchronous service invocation)
- When an error occurs in the data transformation processing after service invocation 1 in a configuration where service invocation 1 is synchronous, a rollback occurs up to the point where the transaction was committed (Receive: Completed, Service invocation 1: Executing).
- The following figure shows the transaction scope when an exception occurs in the presence of activities, such as the data transformation after the synchronous service invocation:
Figure 3-24 Transaction scope when an exception occurs (When activities such as the data transformation exist after synchronous service invocation)
![[Figure]](FIGURE/ZC042500.GIF)
- When an exception occurs (When activities such as data transformation exist after asynchronous service invocation)
- When an error occurs in the data transformation processing after service invocation 1 in a configuration where service invocation 1 is asynchronous, a rollback occurs up to the point where the transaction was committed (Receive: Unexecuted, Service invocation 1: Unexecuted).
- The following figure shows the transaction scope when an exception occurs in the presence of activities such as data transformation after asynchronous service invocation:
Figure 3-25 Transaction scope when an exception occurs (When activities such as data transformation exist after asynchronous service invocation)
![[Figure]](FIGURE/ZC042600.GIF)
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.