The Business Application Explorer provides a hierarchical
representation of a resource.
The following figure shows Business Application Explorer
hierarchical service tree.
The Business Application Explorer shows a tree form of the
hierarchy. All objects will have a number beside them that denotes
the number of instances of each object.
Note: Applications and
Application Suites are also created within this explorer.
- Application Suites - An application suite is a logical grouping
of related applications.
- Applications - An application or composite business application
is a logical collection of related business services.
- Business Services - A business service is a business function
whose execution can be adapted at runtime based on business policies
and user context, and is classified by three types: Composite Services,
Process Services and Optimization Services.
- Process Services - A process service is a specific process flow
within the context of a business service.
- Optimization Services - An optimization service works together
with a visibility service in order for administrators to understand
where in their business service, they can improve performance.
- Composite Services - A Composite Service in Composition Studio
refers to an SCA module. A Composite Service may be as simple as an
SCA module that implements and exposes a web service; or it may include
complex BPELs and have bindings to other services and exposed by other
modules.
- Dynamic Assembly Components - A Dynamic Assembly component knows
its own identity at runtime, the system also automatically supplies
the composite service and dynamic assembly component dimensions within
the context.
- Interfaces - An Interface supports authentication and authorization
systems.
- Endpoints - An Endpoint is the realization of one or more Interfaces.
- Context Specifications - A Context Specification defines what
context is needed at runtime for a Dynamic Assembly to make the endpoint
selection decision.
- Policies - A Policy customizes behavior based on organizations,
roles, specific users, or service level agreements.
- Service Levels - A Service Level represents established levels
of service. Services are software components with well-defined interfaces
that are implementation-independent.
- Simulations - A Simulation enables a Fabric developer to enter
a simulated context and content and, in return, determine which policies
would have been used to create a composite policy.