SOA - part1.pdf

8/18/2019 SOA - part1.pdf

1/15

ENTERPRISE SYSTEMS INTEGRATION:

A SOA APPROACHDANIEL DOBOSERU | FEB 2015PROIECTAREA SI INTEGRAREA SISTEMELOR INFORMATICE| TIE


2/15

AGENDA:

THE PROBLEM

THE SOLUTION

INTRODUCTION

CONCEPT OF SOA

SERVICES

SYSTEM INTEGRATION

INTEGRATION ISSUES

SOA PROVIDERS

CASE STUDY

ORACLE SOA SUITE


3/15

THE PROBLEM

An enterprise, consists of many systems, eaca certain business task, and each communicother systems.

CRM, ERP, BI, WebPortals etc.

Different vendors means different implemen

Need people specialized in the each languasystem.

NO coordination!


4/15

THE SOLUTION?

Reduce chaos; i.e. coupling.

Take control over the communication rou

Coordinate the activities.

Unify vendors


5/15

INTRODUCTION – THE CONCEPT OF SOA

The term Service-Oriented Architecture (SOA) is a widely known term, but often mmisinterpreted:

SOA is NOT a technology.

SOA is NOT a technical standard.

SOA is an architectural blue print, used to build enterprise applications based upon the

All the SOA compliant software, is organized into business services that are accesnetwork, and are based on the public standards for interoperability.

Service-orientation is a way of thinking in terms of services, and service-based de


6/15

INTRODUCTION – SERVICES

A service –

is a logical representation of a repeatable business activity, driven byflow that has a predictable outcome.

Ex. computing the risk level for a client requesting a credit, getting currency exchange rates etc.

May be self-contained

Seen as a black-box for the consumers

May be composed of other services

A service contains:

Contract – definition, description, functional and QoS constrains etc

Interface – the set of available operations

Implementation – the backend logic and data


7/15

INTRODUCTION – SERVICES

A service provides a discrete business function that operates on data.

How the service is implemented and how it is accessed, is governed only by the Sinfrastructures choices of the enterprise.

It doesn’t really matter how a service is implemented!

Characteristics:

Complies only with the open standards for integration

Loose coupling

Stateless

Transparency


8/15

SYSTEM INTEGRATION

System integration is the process of linking together different computing systems aapplications, physically or functionally, to act as a coordinated whole.

An enterprise system is usually made of an aggregation of cooperating systems

Represents a very important component of any enterprise system, as it adds cap

possible only because of the interactions between subsystems.

An enterprise application integration (EAI) can be used for different purposes:

Data integration – keeps consistency between data shared by multiple systems

Vendor independence – makes the business rules become vendor independent

Common façade – provides a single consistent interface to multiple applications


9/15

INTEGRATION ISSUES

Applications might have different data sources, which most of the time are heter

Require adapters.

Connectivity issues – all the systems are interacting.

Service centralization and mediation.

Monitoring and control.


10/15

SERVICE-ORIENTED ARCHITECTURE - CHARACTERISTICS

Quality of service, security and performance are specified.

Software infrastructure is responsible with the management of resources.

Services are cataloged and discoverable.

Protocols use only industry standards.


11/15

SOA VENDORS


12/15

CASE STUDY: ORACLE SOA SUITE


13/15

CASE STUDY: ORACLE SOA SUITE

Applications might have different datasources.

Connectivity issues – all the systems areinteracting.

Service centralization and mediation.

Monitoring and control.


14/15

ORACLE SOA SUITE - ARCHITECTURE


15/15

THE END

To be c

SOA - part1.pdf

Documents

Transcript of SOA - part1.pdf