SOA Governance

Governance Defined• Governance is about decision making

• Governance defines the chains of responsibility, authority, and communication, as well as the measurement and control mechanisms to enable people to carry out their roles and responsibilities.

• There are a number of governance categories, for example:– Information Technology (IT) Governance– Enterprise Architecture (EA) Governance– SOA Governance

Governance Types Defined• IT Governance

– The processes that ensure the effective and efficient use of IT in enabling an organization to achieve its goals[1]

• EA Governance– A mechanism to ensure projects apply prescriptive

guidance provided by the EA process– The process of making decisions regarding the adoption

of EA content• SOA Governance Extends IT Governance

– Specifically focused on an organization’s SOA:• Service Lifecycle• Metadata• Composite applications

A scenario on the importance of SOA governance - Step 1

Currency conversion service

Accounting department

App. 1 App. 2

1. Provide acurrency service that fills a specific line of business (LOB)

* Scenario from Introduction to SOA Governance, Bobby Woolf. * Scenario from Introduction to SOA Governance, Bobby Woolf.

A scenario on the importance of SOA governance - Step 2

Currency conversion service

Accounting department

App. 1 App. 2

Orderfulfillment

Sales

Purchasing

Legal

2. Other LOBs start using

the service

1. Provide acurrency service that fills a specific line of business (LOB)

A scenario on the importance of SOA governance - Step 3

Currency conversion service

Accounting department

App. 1 App. 2

3. LOBs increase use of services / quality suffers

2. Other LOBs start using

the service

1. Provide acurrency service that fills a specific line of business (LOB)

Orderfulfillment

Sales

Purchasing

Legal

A scenario on the importance of SOA governance - Step 3

8

Currency conversion service

Accounting department

App. 1 App. 2

3. LOBs increase use of services / quality suffers

2. Other LOBs start using

the service

1. Provide acurrency service that fills a specific line of business (LOB)

Orderfulfillment

Sales

Purchasing

Legal

x

x

x

x

x x

A scenario on the importance of SOA governance - Step 4

4. Service is fixed at provider’s expense

Currency conversion service

Accounting department

App. 1 App. 2

3. LOBs increase use of services / quality suffers

2. Other LOBs start using

the service

1. Provide acurrency service that fills a specific line of business (LOB)

Orderfulfillment

Sales

Purchasing

Legal

A scenario on the importance of SOA governance - Step 5

4. Service is fixed at provider’s expense

Currency conversion service

Accounting department

App. 1 App. 2

3. LOBs increase use of services / quality suffers

2. Other LOBs start using

the service

1. Provide acurrency service that fills a specific line of business (LOB)

Orderfulfillment

Sales

Purchasing

Legal

x

x

x

x

x x

5. Fix works temporarily but problem

reappears

A scenario on the importance of SOA governance - Step 6

11

4. Service is fixed at provider’s expense

Currency conversion service

Accounting department

App. 1 App. 2

3. LOBs increase use of services / quality suffers

2. Other LOBs start using

the service

1. Provide acurrency service that fills a specific line of business (LOB)

Orderfulfillment

Sales

Purchasing

Legal

5. Fix works temporarily but problem

reappears

x

x

x

xx x

6. Maintenance costs soar / provider ends service

The key aspects that need to be governed in the context of SOA

Architecture

As part of SOA journey, consider policies built around:

• Standards compliance—for example, WS-I Basic Profile compliance for service interfaces.

• Use of architectural assessments, including reviews and change processes.

• Adherence to reference architectures

Technology Infrastructure

Policies need to be enacted to ensure that • Consensus is built regarding the migration of legacy

systems and platforms to SOA technologies.• SOA platform enhancements coincide with the

project portfolio plan and business service portfolio plan.

• The design and implementation of shared foundation / utility services are a part of SOA infrastructure.

Information

• Make data readily discoverable, accessible, and interoperable

• Realize policy-driven security for data services.• Enforce data standards in the data services

layer.

Financial

• The sharing of hardware and software infrastructure that is the backbone of an enterprise-wide SOA.

• The funding of business and technical services that will be shared across multiple departments.

Portfolios

• Ensure that application lifecycles are consistent with your SOA strategy and enterprise architecture—especially with the SOA standards on which interoperability is built.

• Ensure that hardware and software agendas and plans are consistent with your SOA and enterprise strategy.

People

• Developing the skills necessary for architecting, building, testing, and deploying services and service-oriented applications.

• Creating incentives to encourage the building of sharable services and the reuse of existing services.

Six Steps to Successful Governance with SOA

Step 1: Define Goals, Strategy and Constraints

• Every policy, process, architecture, and decision should be traceable back to the business goals.

• It is also important to take into account applicable constraints, including resources, organizational readiness, budgeting, legacy and cultural issues.

Step 2: Define Policies and Procedures

• Define standards, policies, and procedures that address the alignment of finance, portfolios, projects, and operations.

• Clearly state who has the decision and input rights in formulating specific governance policies

Step 3: Define Metrics for Success

• Define the success factors and key performance indicators that will let you know you have achieved your goals and objectives.

• As you mature on your SOA and EA journey and receive feedback from the business customers, your metrics should also mature.

Step 4: Put Governance Mechanisms in Place

• The enactment of governance mechanisms , including how to obtain and evaluate metrics.

• Methods to enforce policies and procedures.• To reward the architects and developers that create

sharable services and the individuals or organizations that use them

Step 5: Analyze and Improve Processes

• Measure the progress made on the SOA Roadmap, relaxing overly restrictive policies.

• As you continue to eliminate the highest-priority bottlenecks and hindrances, you can focus your attention on the next-highest-priority items.

Step 6: Refine Your SOA

• Periodically, as your SOA matures, re-evaluate and refine your SOA strategy, along with your SOA goals and objectives.

WSO2 Service RegistryWSO2 Governance Registry, is an open source tool from WSO2 (Web Services Oxygen) available at www.wso2.com

It has the following components:

• Service Registry/Repository• Service directory with descriptive metadata• Service Manager• Service lifecycle management• Service version management• Policy Server• Policy management and enforcement

Starting Up Governance Registry

Management Console

Open a web browser and navigate to the Management Console URL:

https://<IP_ADDRESS>:9443/carbon/

Register a Service

A WSDL List will be displayed showing the uploaded WSDL file.

Examine and Update the Service Resource

This Service was added automatically, since the WSDL file contained a service element. It was also automatically versioned (i.e., 1. 0. 0-SNAPSHOT).

Set Security Parameters

Add a Lifecycle to a Service

1. “SOA Governance: Framework and Best Practices”- Oracle White Paper , May 2012 www.oracle.com/us/.../oracle-soa-governance-best-practice-066427.pdf

2. “SOA Maturity Model -Guiding and Accelerating SOA Success” Oracle White Paper, September 2013 http://www.oracle.com/technetwork/topics/entarch/oracle-wp-soa maturity-model-176717.pdf

3. Introduction to SOA Governance, Bobby Woolf, IBM Library, July 2007.

4. http://blog.webagesolutions.com/archives/814

*SOA Maturity Model[2]

Enterprise Level• The capability is implemented consistently across the

enterprise i.e. all divisions or business units are applying the SOA approach.

Cross Division• The capability is implemented by multiple divisions using a

common approach i.e. the approach is being shared or is spreading to multiple divisions.

Division Wide• The capability is implemented consistently across a division or

business unit. • A division or business unit is led by an executive at the VP

level or higher.

Program Level• A relatively small group of projects (program) share an

implementation of the capability. The program is under a single management structure below the VP level and encompasses less than an entire division or business unit.

Project Level• Individual projects implement the capability as appropriate

for that specific project. There may be informal and unregulated sharing across projects.

No Implementation• There is no current implementation anywhere in the

organization of the capability being measured