- Added in Builder 6.0
A Scheduler service (in this example SchedulerService) has no external interface; the class resident on the <<SchedulerService>> contains no operation. This class (Scheduler) must have the stereotype <<E2EScheduler>>; that is, the class must be a Scheduler.
Figure: Scheduler Component Diagram
The SchedulerExample composite contains a Scheduler service (SchedulerService). The Scheduler service artifact contains a Scheduler class (Scheduler).
The Scheduler has the following tagged values that define, when a Scheduler event handler is executed.
| Tagged Value | Possible Entries | Default |
|---|---|---|
allowParallelExecutions | If true (default), each time a scheduler pattern matches, the scheduler activity diagram is executed - even if another execution is already running. If false, the next execution cycle is suppressed, if an activity diagram is already being run. | true |
| years(s) | positive and negative integers or a pattern | * |
| month(s) | 1 to 12 or a pattern | * |
| weekday(s) | Mon(day), Tue(sday), Wed(nesday), Thur(sday), Fri(day), Sat(urday), Sun(day), or a pattern | * |
| day(s) | 1 to 28, 29, 30, or 31 depending on the month or a pattern | * |
| hour(s) | 0 to 23 or a pattern | * |
| minute(s) | 0 to 59 or a pattern | 0 |
| seconds | 0 to 59 or a pattern |
For explanations on date time patterns refer to Date Time Patterns.
Following the explanation of the tagged values above, the Scheduler defined in the component diagram above executes the activity each hour between 8 am and 8 pm (hour(s) = "8-20"), but only from Monday until Friday (weekdays = "Mon - Fri"). Tagged values that are specified with "*" are not displayed on the class.
Scheduler Components and Deployment of E2E Builder Version 5.1
- Deprecated since Builder 6.0
Figure: Scheduler Component Diagram of E2E Bridge Version 5.1
The Scheduler composite deployment contains a Scheduler service artifact (SchedulerServiceArtifact). The Scheduler service artifact contains a Scheduler class artifact (SchedulerArtifact).
The Scheduler has the following tagged values that define, when a Scheduler event handler is executed.
| Tagged Value | Possible Entries | Default |
|---|---|---|
| minute(s) | 0 to 59 or a pattern | 0 |
hour(s) | 0 to 23 or a pattern | * |
day(s) | 1 to 28, 29, 30, or 31 depending on the month or a pattern | * |
weekday(s) | Mon(day), Tue(sday), Wed(nesday), Thur(sday), Fri(day), Sat(urday), Sun(day), or a pattern | * |
month(s) | 1 to 12 or a pattern | * |
years(s) | positive and negative integers or a pattern | * |
Following the explanation of the tagged values above, the Scheduler defined in the component diagram above executes the activity each hour (hour(s) = *), on the 50th minute (minute(s) = 50), each year (year(s) = *), and each month (month(s) = *), but only from Monday until Friday (weekdays = Mon - Fri).
The deployment diagram Scheduler Deployment Diagram shows only one node: the E2E Server node. Because the file system backend service (FileSystemService) runs on the Server, there is no additional backend node. Therefore, the Server has two assigned stereotypes: <<E2EBridgeServerInstance>> and <<BackendServerInstance>> , because this node acts as E2E Server and backend server at the same time.
In the deployment diagram, you specify components to be deployed; the component diagram defines the components. Deployment means instantiating components, and annotating all configuration information to run these components, on their target systems.
Figure: Scheduler Deployment Diagram
Overview
Content Tools