Page History
Div | ||||||
---|---|---|---|---|---|---|
| ||||||
|
Version | ||
---|---|---|
| ||
|
...
...
...
...
...
...
...
Scheduler Components and Deployment of E2E Builder Version 5.1
Version | ||
---|---|---|
| ||
|
...
title | Click here to read the documentation of the component diagram used in E2E Builder releases before 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 | * |
...
Note | ||
---|---|---|
| ||
Depending on the location of the E2E Runtime, the value of hour(s) may differ from your local time. Even if the Server is located in the same time zone as your workstation, the time used by the scheduler to match the patterns depends on whether the Server uses UTC or local time. Which time zone is to be used, can be configured in the E2E Runtime. |
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
...