Skip to main content

Centralized Policy Administration, Enforcement, and Monitoring for Runtime Policies

Web Doc

Note: This is publication is now archived. For reference only.

thumbnail 

Published on 15 January 2013, updated 22 January 2013

  1. View in HTML
  2. .PDF (1.8 MB)

Share this page:   

IBM Form #: TIPS0952


Authors: Robert Laird and Margaret Ticknor

menu icon

Abstract

The SOA Policy Solution provides centralized policy administration, enforcement, and monitoring for runtime policies that enable traffic management for service level agreement (SLA) enforcement, service mediation, and other customized policies.

Business users can employ the SOA Policy Solution to help create the SLAs for their business services to deliver on promises for business performance. IT architects can use the SOA Policy Solution to create policy solution patterns that will standardize the runtime policy usage at their organization. Developers select specific policy patterns to implement the nonfunctional requirements that are associated with their projects. Operations provide information about operation needs and create a standardized monitoring policy for operational action at run time.

You can define policies once and reuse them among multiple services, enabling a standardized, consistent approach to runtime policy. With this approach, you save time and money for implementation and maintenance of nonfunctional requirements for the enterprise and achieve faster time to market.

Contents

The SOA Policy Solution provides centralized policy administration, enforcement, and monitoring for runtime policies that enable traffic management for service level agreement (SLA) enforcement, service mediation, and other customized policies.

Business users can employ the SOA Policy Solution to help create the SLAs for their business services to deliver on promises for business performance. IT architects can use the SOA Policy Solution to create policy solution patterns that will standardize the runtime policy usage at their organization. Developers select specific policy patterns to implement the nonfunctional requirements that are associated with their projects. Operations provide information about operation needs and create a standardized monitoring policy for operational action at run time as shown in the example in Figure 1.

Example pattern for the SOA Policy Solution
Figure 1. Example pattern for the SOA Policy Solution

You can define policies once and reuse them among multiple services, enabling a standardized, consistent approach to runtime policy. With this approach, you save time and money for implementation and maintenance of nonfunctional requirements for the enterprise and achieve faster time to market.


Did you know?

Many organizations find that they can group their services into about a half dozen sets, where each set requires the same policies. A set of policies might include, for example, a couple of security policies, several traffic management policies, and a message transformation policy that all of the services in that set need applied to their transactions during runtime execution. By using the SOA Policy Solution, the process of managing multiple individual policies in the various middleware devices is condensed to a half dozen or so policy patterns in a centralized policy repository.


Business value

All organizations implement policy in some form to make decisions that are important to the business and IT. For example, human decisions are a common method of implementing a policy. Your business people or finance group might ask you to prove that automating your policy decisions will provide a positive return on investment (ROI) for your organization. Proving to these decision makers that your project to automate a policy is a worthwhile endeavor always comes down to two factors:

 

Others who read this also read

Special Notices

The material included in this document is in DRAFT form and is provided 'as is' without warranty of any kind. IBM is not responsible for the accuracy or completeness of the material, and may update the document at any time. The final, published document may not include any, or all, of the material included herein. Client assumes all risks associated with Client's use of this document.