uCosminexus Service Platform, Basic Development Guide
A standby activity defines a process that puts the processing flow of a business process in standby mode at regular intervals or until a certain time limit. You can use this activity to put a business process in standby mode for a specified period or until a specified time.
Define the details of the standby activity in the Wait Activity dialog box. Specify the standby time interval or time limit in an XPath expression.
An XPath expression is used to specify standby time. An XPath expression is evaluated in the processing of a business process, and the character string obtained as a result of the evaluation is used as standby time. The BPEL standard imposes some limitations on the character strings that can be obtained by evaluating XPath expressions.
The following subsections describe the character strings that can be obtained by evaluating XPath expressions. For details about specifying XPath, see 5.6.18 Specifying an XPath.
If For is specified in Standby time, the character strings that can be obtained by evaluating XPath expressions must conform to the XML Schema type duration (xsd:duration). The XML Schema type duration is the variable type indicating character strings that express elapsed time in PnYnMnDTnHnMnS format.
The following example shows the character strings that can be obtained by evaluating XPath expressions when For is specified for Standby time:
Instead of specifying an XPath expression in Expression in the Wait Activity dialog box, you can also specify a standby time interval directly by enclosing it in single quotation marks (') or double quotation marks ("). The following examples show direct specifications of standby time intervals by using single quotation marks (').
If Until is specified for Standby time, the character strings that can be obtained by evaluating XPath expressions must conform to the XML Schema type dateTime (xsd:dateTime). The XML Schema type dateTime is the variable type indicating character strings that express a date and time in CCYY-MM-DDThh:mm:ss.sssTZ format (where .sss and TZ can be omitted).
The following example shows the character strings that can be obtained by evaluating XPath expressions when Until is specified for Standby time.
Instead of specifying an XPath expression in Expression in the Wait Activity dialog box, you can also specify a standby time limit directly by enclosing it in single quotation marks (') or double quotation marks ("). The following examples show direct specifications of standby time limits by using single quotation marks (').
In an environment set up using the HCSC easy setup functionality, processes following a standby activity for multiple process instances are not executed concurrently because the multiplicity of processes following a standby activity is set as 1 by default. If processes following a standby activity start simultaneously from multiple process instances, the processing of a process instance that starts later is not executed until the previous processing finishes.
To simultaneously execute processes following a standby activity for multiple process instances, adjust the process multiplicity by changing the ejbserver.ejb.timerservice.maxCallbackThreads property in usrconf.properties.
The figure below shows an example of processing where multiple process instances are executed when the multiplicity of processes following a standby activity is 1 and the multiplicity is increased. This example assumes that the standby activity (Standby 1) causes multiple process instances to wait for processing until 13:00 and then it takes two minutes for post-standby processes (Empty 2 and Empty 3) to finish.
Figure 5-10 Examples of processing where the multiplicity of processes following a standby activity is 1 and where the multiplicity is increased
For details about how to set the ejbserver.ejb.timerservice.maxCallbackThreads property in usrconf.properties, see 2.4 usrconf.properties(User property file for J2EE servers) in the Application Server Definition Reference Guide.
All Rights Reserved. Copyright (C) 2015, Hitachi, Ltd.