Page History
...
Added in Builder 6.0In front of E2E xUML services we have the service client followed by the E2E service itself. Thus, components serving these clients are called frontend components or frontend services. These E2E frontend services can be further grouped into a logical deployment unit called E2E composite. This is done in the component diagram.
...
Each composite manifests itself as repository file after compilation. This means, after compilation the <projectPath>/repository folder contains the repository file HelloWorldExample.rep. Additionally, each of the logical components can be configured by the use of tagged values. This repository belongs to the category E2E Examples and uses the control port 22020. For further composite attributes see the table below.
...
Multiexcerpt | ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| ||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||||
|
The component diagrams, the E2E composites, and services artifacts are always found in the same place in all E2E UML models:
Figure: Component View in the Containment Tree
Frontend Components of
...
Builder Version 5.1
...
Deprecated since Builder 6.0
Expand | |||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| |||||||||||||||||||||||||||||||||||||||
Component DiagramThe most simple component diagram is depicted below. It contains a <<E2EComposite>> component. This component is the deployment unit of a set of service components. Each <<E2EComposite>> component may contain several services. The different service types are described in the Add-ons chapter. Examples are: SOAP, HTTP, JMS, Java, Timer, Scheduler, SAPRFC, etc. Finally, each service contains at least one class realizing the service. For example, SOAP services contain SOAP port types. Each of these logical components - composite, service, class - can then be configured by an UML artifact. For instance, each composite manifests itself as repository file after compilation. The filename and some additional parameters can then be configured on the UML artifact manifesting the UML composite component. In the component diagram above, the HelloWorldExample artifact configures the HelloWorld composite. This means, after compilation the <projectPath>/repository folder contains the repository file HelloWorldExample.rep. Additionally, this repository belongs to the category E2EExamples and uses the control port 22020. For further configuration attributes see the table below. It is important to understand that a composite can be manifested by more than one artifact. This allows to create various deployment instances for each composite. Each composite artifact can then be separately compiled and deployed using the model compiler. For example, the HelloWorldExample composite deployment depicted in the above component diagram is also found in the model compiler view: Figure: Deployment of Service in Model Compiler
<<E2EComposite>> AttributesThe composite holds the following tagged values:
<<E2ECompositeDeployment>> AttributesThe composite deployment artifact allows to define the following general tagged values:
Additionally, some tagged values configuring the Persistent State machine can be set as well. These tagged values - externalStateDBAlias, storageMedium, and workers - are described in the Persistent State Components and Deployment chapter. The component diagrams, the E2E composites, services and all manifesting artifacts are always found in the same place in all E2E UML models: Deployment DiagramAfter having created a component diagram, it is now possible to define a deployment diagram, telling the model compiler where to deploy the compiled repository file. The following deployment diagram shows how to deploy the HelloWorldExample repository to localhost. However, instead of localhost one could use every qualified host name being in the Bridge domain . All deployment diagrams and deployment instances are found in the same place in all E2E UML models: the so called File View. The name derives from the fact that it describes the deployment of the repository files to machine instances. The File View folder looks like: |