Working with policies

Policies define the business requirements that have to be met when a consumer requests a service.

A policy is a set of assertions that represent requirements, constraints or capabilities for a business service. For example, "A Business Service must use HTTP or HTTPS as a medium of communication" is the example of a policy.

A policy consists of three sections:
Note: These requirements are modeled as assertions.

At run time, the Business Services Dynamic Assembler determines the set of policies that are relevant for the request and then locates the best endpoints that meet these requirements.

Policies are executed at run time by the Business Services Dynamic Assembler, which dynamically selects the most appropriate endpoint based on the policies. The Business Services Dynamic Assembler is a semantic mediation engine that is highly scalable and uses policy-based composition and semantic mediation for dynamic service assembly and service behavior adaptation based on content, context, and contract.

Note: For more detailed information on the Business Services Dynamic Assembler, refer to the Business Services Dynamic Assembler documentation.

Policies can target application suites, applications, business services, interfaces and other types of resources. Each business service can be composed of multiple interfaces. Each interface can be associated with multiple endpoints. If a policy is applied on a business service, then that policy applies to all associated interfaces and also to the endpoints associated with the interfaces.

Related topics

Related concepts
Working with business services
Working with business variables
Working with correlation queries
Working with namespaces
Working with composite services
Working with interfaces
Working with endpoints
Working with the WSRR
Working with assertions
Working with context extraction
Working with the repository
Working with the SCA framework