SOA

[Former Member]

what exactly is SOA,eSOA,and how is it related to XI.Can you give me an example where it is used and how to use it.

Thanks

[rajasekhar_reddy14]

Hi,

SOA is more generic. Any system that provides web services (which are self-contained and self-describing) can be termes as SOA enabled. The provider of the service registers the service over UDDI in the form of WSDL. The consumer searches the UDDI for the desired service and invokes it. There can be multiple web services (from multiple providers) for the same application (eg. purchase order creation).

ESOA 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 ESOA 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 ESOA

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

Regards,

Raj

[JoelTrinidade]

Hi,

The simplest possible definition of what is SOA is given as below which even the links mentioned about dont convey.

What is service-oriented architecture?

Service-oriented architecture (SOA) is an evolution of distributed computing based on the request/reply design paradigm for synchronous and asynchronous applications. An application's business logic or individual functions are modularized and presented as services for consumer/client applications. What's key to these services is their loosely coupled nature; i.e., the service interface is independent of the implementation. Application developers or system integrators can build applications by composing one or more services without knowing the services' underlying implementations. For example, a service can be implemented either in .Net or J2EE, and the application consuming the service can be on a different platform or language.

Service-oriented architectures have the following key characteristics:

• SOA services have self-describing interfaces in platform-independent XML documents. Web Services Description Language (WSDL) is the standard used to describe the services.

• SOA services communicate with messages formally defined via XML Schema (also called XSD). Communication among consumers and providers or services typically happens in heterogeneous environments, with little or no knowledge about the provider. Messages between services can be viewed as key business documents processed in an enterprise.

• SOA services are maintained in the enterprise by a registry that acts as a directory listing. Applications can look up the services in the registry and invoke the service. Universal Description, Definition, and Integration (UDDI) is the standard used for service registry.

• Each SOA service has a quality of service (QoS) associated with it. Some of the key QoS elements are security requirements, such as authentication and authorization, reliable messaging, and policies regarding who can invoke services.

For further reading refer: http://www.javaworld.com/javaworld/jw-06-2005/jw-0613-soa.html

Regards

joel

[former_member200962]

Hi,

Relation between XI/PI and SOA......XI/PI come under SOA (or rather ESOA)....for more information SDN has a dedicated homepage for SOA:

https://www.sdn.sap.com/irj/sdn/nw-soa

Also SDN is hosting a separate forum for SOA:

All the scenario objects that are developed in PI are termed as services which can be modified, executed and reused.....hence it is termed as ESOA...

Regards,

ABhishek.

[Shabarish_Nair]

https://www.sdn.sap.com/irj/sdn/soa

refer this SDN link and you will find all possible documentation around that subject