cancel
Showing results for 
Search instead for 
Did you mean: 

SOA Policy and governance

Former Member
0 Kudos

Hi Experts,

Could you please provide the details of SOA Policy and governance?

What all things/points we have to check for SOA Policy and governance?

Documents please..

Regards

Sara

Message was edited by:

Sara D

Accepted Solutions (0)

Answers (3)

Answers (3)

Former Member
0 Kudos

Dear Sara,

In a nutshell, enterprise services are simply Web services that provide enterprise-level business functionality.They may range from very simple lookup services (like finding a company’s location or product offerings) to more complex and composite services — but

what they have in common is that they’re highly integrated into your process or application.Typically enterprise services are high-level components that take more granular Web services and aggregate them into reusable elements with business value. For example, take the service Cancel Purchase Order. An elementary Web

service like Delete Purchase Order would simply lead to the deletion of a purchase order in the corresponding

database. However, if the stated goal is “cancel purchase order,” the service has to become a more far-reaching enterprise service that handles this process end-to-end, and therefore has to trigger a number of follow-up actions, including:

=> Check against production orders

=> Check against a corresponding billing process

=> Update of inventory/warehouse information Or consider the Credit Limit Check

service, which at first glance seems to be quite simple. Normally, this service is one ingredient of the Order Creation service. But typically, credit checking is

really a more elaborate composite service.

5 Key Principles of ESA

1. Abstraction — hiding confusing details

2. Modularity — breaking down complexity, resulting in reusable pieces

3. Standardized connectivity — enabling flexible composition of services to

create bigger processes and scenarios

4. Loose coupling — allowing for separate evolution of the various components

without breaking any points of integration

5. Incremental design — enabling changes to composition and configuration

without affecting the interior of components, and vice versa

<b>Service Oriented Architecture (SOA)</b>

A service-oriented architecture (SOA) is a collection of services that communicate with each other. Communication can involve either simple data passing or it can involve two or more services coordinating some activity. Some means of connecting services to each other is needed.

A service is a function that is well-defined, self-contained, and does not depend on the context or state of other services.

The communication is initiated by the a service consumer that sends a service request message to a service provider. The service provider returns a response message to the service consumer. The request and subsequent response connections are defined in a way that is understandable to both the service consumer and service provider. The connections are defined by Web services. A service provider can also be a service consumer.

<b>Enterprise Service Architecture (ESA)</b>

Enterprise Services Architecture (ESA) is SAPs open architecture for adaptive business solutions. ESA creates a gradual path to flexible, service-centric system landscapes and allows a non-disruptive transition of existing applications and architecture for more flexibility and value.

The fundamental premise of ESA is the abstraction of business activities or events, modelled as enterprise services, from the actual functionality of enterprise applications. Aggregating Web services into business-level enterprise services provides more meaningful building blocks for the task of automating enterprise-scale business scenarios. Enterprise services allow IT organizations to efficiently develop composite applications.

Hope it was usefull..

Prem

Former Member
0 Kudos

Hi Sara,

SOA is an architecture principles on which we work towards better agility between BUSINESS and IT in an organization. SOA bring the concept of composing business needs and use cases in terms of service not in terms of components. Interface is the backbone of a service which concentrates of implementation independent way of composing a business use case objectives.

Doing business use case realization in terms of services and underlining interfaces bring agility and loose coupling, so that business can execute the changes without much worry about the underlining component implementation.

However, this kind of architecture principle bring more responsibilities to all phase of software life cycle, cuz we are decoupling the close bridge between business use cases and IT implementation component by introducing a high level abstraction in terns of interfaces.

Also interface realization is accomplished by using early matured technologies such as web services, xml, XSD, soap, BPEL, and a bunch of young specification from W3.

All these steps telling us SOA is not just web services, it is an architecture principle to address IT realization of business needs using an AGILE approach so that we can make use of features such as loose coupling, reusability, asynchronous mode of execution, enterprise wide transparency,

It is same as a water glass broken into peaces on the floor but magical power still allows us to pour water through the glass parts through some strong and agile principles.

This approach is a journey than a sleep over so it comes with ROLES, RESPONSIBILITIES.

SOA governance and management address how you maintain the loose coupled pieces of SOA based application together so that it will not deviate from the expected GOALS.

Governance is applied to SOA life cycles using POLICIES. Policies can be defined and enforced through a policy management tool such as Registry. Policies are similar to RULE engine rules, which as applied to different phase of a SOA project.

SOA project have different phase such as PLAN, DEFINE, DESIGN, DEVELOP, TEST, DEPLOY, Release and Maintain.

Since SOA is an aligned work between business and IT of an organization there will be roles and associated responsibilities assigned people from business and IT of the organization during each phase of the SOA service life cycle. Registry play as a single place holder for the governance policy during all phase of an SOA service life cycle.

A governance body can define SOA governance policy for SOA services in an organization with the help of tools like Systinet, WSSR and even with XI registry or any UDDI standard based registry.

Service management tools are interceptors of service invocation and service status management in different phase of a service life cycle.

Service management tool can work service registry, repository and ESB run time to enforce the service governances policies

So Service governance and service management ARE the core features need to be in place to get the agility explained in SOA architecture principle.

Note: if you r happy with the answer make sure u have rewarded the points.

Former Member
0 Kudos

Hi Shaji,

Thanks a lot. Ya, I am really happy with the information. Only thing is you have not provided the links/sites.

Regards

Sara

sbhutani1
Contributor
0 Kudos

Hi Sara,

Here are few good presentations, which you can refer for the SOA governance and policies.

http://www.sap.com/community/pub/showdetail.epx?itemID=8978

http://www.sap.com/community/pub/showdetail.epx?itemID=7890

Regards

Sumit Bhutani