uCosminexus Service Platform, Basic Development Guide
This activity defines a process flow consisting of one or more activities as a single coherent processing unit.
The following figure shows processing units that use scope activities.
Figure 5-11 Setting up processing units using scope activities
When you define a scope activity, you can handle the processing flow inside the scope as a single coherent unit. You can also define a scope inside the processing flow of another scope, as exemplified by Scope 3 in the figure above.
Note that variables defined inside a scope are valid only within that scope. For details about the scopes and the valid range for variables, see 5.5.1(5)(a) Use of variables when scope activities are used.
- Organization of this subsection
- (1) Definition procedure
- (2) High level settings
- (3) Notes on definition
(1) Definition procedure
To define a receive activity:
- Deploy a scope activity on the canvas.
For details about how to deploy activities, see 5.4.1 Deploying Activities.
- Use one of the following methods to open the Scope Activity dialog box:
- Double-click a scope activity on the canvas.
- Choose and right-click a scope activity on the canvas, and choose Setting.
The Scope Activity dialog box opens.
- Enter an activity name.
- Click OK.
- Choose and right-click a scope activity on the canvas, and choose Open.
A tab with the scope activity name is displayed in the bottom portion of the canvas.
- Click the tab with the scope activity name.
The canvas for specifying the processing inside the scope is displayed.
- Deploy, link, and define the desired activities to specify the processing inside the scope.
(2) High level settings
You can set the scope activity such that transaction is not committed in the internally defined activity.
When you select Commit at the time of start and end of this scope radio button in High level settings of Scope activity dialog, transaction is committed at the time of start and end of the scope activity. The activity defined in the scope activity is not committed.
When you select Commit in the activity unit radio button, activity is not committed at the time of start and end of the end activity. Activity to execute commit defined in the scope activity is committed.
By default, Commit in activity unit radio button is in selected status.
For details on Scope activity dialog, see "1.4.18 Scope activity dialog" in the "Service Platform Reference Guide".
For details on the transaction when you select Commit only at the time of start and end of this scope radio button, see "3.4.5 Transaction when selecting the settings of committing at the time of start and end of scope" in the "Service Platform Function Guide".
(3) Notes on definition
- An activity name must not exceed 64 bytes.
- Do not specify the control character in the input field of the dialog box.
You must note the following points to be noted when defining the scope activity for which Commit only at the time of start and end of this cope radio button:
- You cannot define following activity in the scope activity:
- Scope activity for which Commit only at the time of start and end of this scope radio button is selected
- If you define following activities in the scope activity, validation error occurs.
- Receive activity
- Reply activity
- Standby activity
- You can specify only the DB adapter in the invoke service activity defined in the scope activity for which Commit only at the time of start and end of this scope radio button is selected. If you specify the service adapter other than DB adapter, and the business process, operation is not guaranteed.
- If transactions of the business process and service invoke destination are different, transaction control target is the transaction of the business process. Transaction of the service invoking destination operates without getting impacted by the transaction control (such as in case of defining invoke service activity that invokes a business process and invoke service activity that invokes the function of RequiresNew)
- When you define invoke service activity that invokes the DB adapter, in the scope activity, operating with value of " dba-separate-transaction" property of HCSC server runtime definition file as "false" or value of " dba_separate_transaction" attribute of SQL operation definition file as "N" is pre-requisite.
- When system exception occurs and rolled back business process is re-executed, you must assume that activity defined in the scope activity and service of service invoking destination are re-executed.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.