Assertions are characteristics that describe the capabilities of
an endpoint.
You can define these capabilities along five dimensions: performance, reliability,
interoperability, security, and manageability.
You have the ability to extend the industry ontology to add assertions
that are custom to their enterprise IT environment.
At run time, the Business Services Dynamic Assembler uses these characteristics
to find the best suited endpoint or service realization for a consumer based
on their business requirements. In our meta-model, these business requirements
are called policies.
- Assertions can be attached to endpoints to specify a particular characteristic
of an endpoint (for example, maximum transaction time available).
- Assertions are also used in policy contract. During run time, if a policy
is applicable then the contract is applied. When the policy is fired, the
contract is applied. When the policy target, context, and content conditions
are satisfied, the contract is enforced.
- Assertions on a policy can either be used for endpoint selection during
run time or for other non-endpoint selection purposes, like transformation
assertion or data format assertion.
Note: - Assertions that are not endpoint selections should be used only in policy
contracts and not in endpoints.
- The "hours of operation" assertion should be used only in endpoints and
not in policy contracts.
- Duplicate Allowed: Some assertions are marked as "duplicate allowed,"
which indicates that the user can add more than one assertion of that type
to a single policy or a single endpoint (for example, WSI-Profile
assertion).