ENTERPRISE SYSTEMS INTEGRATION:

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

AGENDA:
THE PROBLEM
THE SOLUTION

INTRODUCTION

CONCEPT OF SOA

SERVICES

SYSTEM INTEGRATION

INTEGRATION ISSUES

SOA PROVIDERS
CASE STUDY

ORACLE SOA SUITE

THE PROBLEM
An enterprise, consists of many systems, each responsible for

a certain business task, and each communicating to the

other systems.

CRM, ERP, BI, WebPortals etc.

Different vendors means different implementations!

Need people specialized in the each language of each

system.

NO coordination!

THE SOLUTION?

Reduce chaos; i.e. coupling.

Take control over the communication routes

Coordinate the activities.

Unify vendors

INTRODUCTION THE CONCEPT OF SOA

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

misinterpreted:

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 use of services.

All the SOA compliant software, is organized into business services that are accessible over

network, and are based on the public standards for interoperability.

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

INTRODUCTION SERVICES
A service is a logical representation of a repeatable business activity, driven by a well-defined

flow 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

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 SOA

infrastructures choices of the enterprise.

It doesnt really matter how a service is implemented!

Characteristics:

Complies only with the open standards for integration

Loose coupling

Stateless

Transparency

SYSTEM INTEGRATION
System integration is the process of linking together different computing systems and software

applications, 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 capabilities that are

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 faade provides a single consistent interface to multiple applications

INTEGRATION ISSUES
Applications might have different data sources, which most of the time are heterogeneous.

Require adapters.

Connectivity issues all the systems are interacting.

Service centralization and mediation.

Monitoring and control.

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.

SOA VENDORS

CASE STUDY: ORACLE SOA SUITE

CASE STUDY: ORACLE SOA SUITE

Applications might have different data

sources.

Connectivity issues all the systems are

interacting.

Service centralization and mediation.

Monitoring and control.

ORACLE SOA SUITE - ARCHITECTURE

THE END

To be continued