|
System name
|
WaitService
|
|
Graphical Process Modeler (GPM) categories
|
All Services, Process Controls
|
|
Description
|
The Wait service allows a business process to wait for a period of time before moving on to the next step in the process. The Wait service does not hold its active thread during this wait time, which can reduce resource consumption.
|
|
Business usage
|
The Wait service allows synchronization of polling events without consuming resources. Use this service to specify a certain wait time after a step in a business process. During the wait time, this service does not use an active thread.
|
|
Usage example
|
A business process with a B2B transmit requires a block of time after a failure before a retry is attempted.
|
|
Preconfigured?
|
Yes
|
|
Requires third party files?
|
No
|
|
Platform availability
|
All supported Gentran Integration Suite platforms
|
|
Related services
|
No
|
|
Application requirements
|
No
|
|
Initiates business processes?
|
This service does not initiate a business process. It cannot be used without a business process.
|
|
Invocation
|
Runs as part of a business process.
|
|
Business process context considerations
|
While in its waiting state, this service does not hold an active thread, which frees up system resources.
|
|
Returned status values
|
- Success - Wait time has completed successfully.
- Error - If wait time value is not found or the value cannot be parsed.
|
|
Restrictions
|
For short wait intervals (less than 30 minutes), Gentran Integration Suite places the business process in a special "0" queue. From the "0" queue, it regains an active thread when it reaches its expiration, within a range of plus or minus 30 seconds (because the "0" queue checks every 30 seconds for wait times that have completed).
For longer wait times, the business process is returned to active by the scheduled system process BPExpirator. The frequency the BPExpirator process is scheduled to run (defaults to every 15 minutes) must be inline with intended wait times. The WaitService could potentially wait up to a full BPExpirator cycle, not being restarted until the next scheduled BPExpirator execution. For example, if a 45 minute wait expired just after an execution of the BPExpirator on a 15-minute cycle, that wait will continue until the next BPExpirator executes, making it a 60 minute, rather than 45 minute wait. By coordinating the wait time and the BPExpirator schedule, you can configure a window of time that is appropriate for your needs.
|
|
Persistence level
|
Full
|
