...
Steps | Domain Services | SPIs | Tools | Note | |
---|---|---|---|---|---|
Add Assets, Store, and StoreClient contributions to the domain | Install/Uninstall contributions | Workspace | Static:
| We can build different ways to make contributions available to the SCA domain. | |
Parse the contributions | Contribution Processing | ContributionScanner |
|
| |
Resolve dependencies across contributions | Import/Export resolution | ContributionDependencyBuilder |
| We need to find out a collection of contributions to support a composite application based on the import/export statements | |
Find/Load/Resolve the composites from the contributions | The assembly builders |
| ArtifactProcessor | The endpoints using SCA addresses or relative URIs should be resolved against the physical base URIs for the bindings based on the node configuration. | Deployable composites can be designated by the contributions. It's also possible that the assembler to define a deployment composite on the fly. |
Configure the nodes to the SCA domain | implementation.node | NodeImplementation |
| The node represents the computing capabilities in the SCA domain. | |
Assign a deployment composite to a node | Run the composite application by a node |
|
| The deployable image of an SCA composite application to a node is the composite and a list of contributions to support the composite application. | |
Monitor and control the services running on a node | See what's going on, start/stop the services |
|
|
|