Page History
...
Sometimes it is reasonable for one Event Observer to trigger more than one time event because the observed events are associated logically . This can be done by drawing another hour glass symbolizing another time event (see Modeling the Behavior of an Event Observer).
| Noteinfo | ||
|---|---|---|
| ||
The E2E Bridge supports no synchronization mechanism between parallel running event handlers. By definition, the event handlers are independent. Therefore, if event handlers have common dependencies, such as shared resources, the modeler must consider this issue. |
| Noteinfo | ||
|---|---|---|
| ||
Running the xUML service, the service may write the following warning to the xUML service standard log:
The Bridge provides a mechanism for viewing the xUML service standard log. Troubleshooting Timer and Event Observer Services describes the reason for, and solution to, this problem. |
Event Observer Components
...
...
- Added in Builder 6.0
A service component stereotyped <<E2EEventObserverService>> models an Event Observer service (EventObserverService) . The class EventObserver (<<E2EEventObserver>>) represents the actual Event Observer. An activity assigned to the class contains the calls to the event handlers. The class can have operations that model the behavior of this class. They may contain the event handler.
...
The backend service alias FileSystemServiceAlias, shown in the component diagram above, is required because the activities access the file system. For more details, refer to the example file.
Event Observer Components and Deployment of E2E Builder Version 5.1
| Version | ||
|---|---|---|
| ||
|
...
| title | Click here to read the documentation of the component and deployment diagram used in E2E Builder releases before 6.0 ... |
|---|
...
to
...
the
...
example
...
file
...
.
...
Figure: Event Observer Component Diagram
The EventObserverExample composite deployment contains an Event Observer service artifact(<<E2EEventObserverServiceDeployment>> ). The Event Observer service artifact contains a class artifact (EventObserverArtifact).
The backend service artifact FileSystemServiceArtifact, shown in the component diagram above, is required because the activities access the file system. For more details, refer to the example file.
The deployment diagram Event Observer Deployment Diagram shows only one node: the E2E Bridge node. As the File System backend service (FileSystemService) runs on the Bridge, there is no additional backend node. Therefore, the Bridge has assigned two stereotypes: <<E2EBridgeServerInstance>> and <<BackendServeInstancer>> , because this node acts as E2E Bridge 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: Event Observer Deployment Diagram
...
Overview
Content Tools