TH e-GIF on SOA Using Open Enterprise Architecture

TH e-GIF on SOA Using Open EnterpriseArchitecture

Dr.Thanachart NumnondaBusiness Development DirectorSoftware LOBSun Microsystems (Thailand)

Agenda• Why SOA for TH e-GIF?• What is SOA?• SOA Definition (Re-caps)• SOA Implementation Framework

– Services (web services/ non web services)– ESB– Business Process

• SOA using GlassFish ESB• Case Study

Why SOA for TH e-GIF?

Technology Interoperability

TH e-GIF

TH e-GIF & Services

HeterogeneousTechnology

Enterprise Service Bus (ESB)

Business Process Management

Access Layer

What is SOA?

Principles and practices for designing shared, reusable, distributed services

SOA Attributes: Separation of service interface from underlying

implementation (loose coupling) Promotes service reuse through discoverable and self-

describing services Services are course-grained, composable, and rely on

a standards based infrastructure

The “Move” to Service Orientation

AccidentalRigid

Silo-Oriented

LayeredExtensible

Service-Oriented

Layering Principle

• Shared Network-based Layered Services

Process Layer

Access Layer

Service Layer

Resource Layer

SOA Architecture Layers

• Resources– Operational Resources; e.g. CRM, ERP, HR,

Databases– Enterprise components; technologies e.g.

Java, .NET, CORBA, PHP• Services

– Selected components which have been developed as services

– Can implement various way; e.g. Web Services

– Normally has well defined interface; e.g. WSDL

SOA Architecture Layers

• Business Process– Represent powerful orchestration of one or

more services that solve a business problem– Business Process itself is a service of services

• Access – Front or User Interface that calls business

process– Web Programming, Desktop, Dashboard– Can be implemented to run on various

devices

Enterprise SOA Implementation

Reusable Services

Credit Card Mortgage

Partner Credit Data Customer Data

Internet

Bill PayAutoLoans Stocks

MutualFunds

Customer

Data Service

Access

Service

Credit Check

Fraud Detection

Payment

Management

Service

TradeExecution

Service

AccessManager

(Liberty)

ServicesRegistry

(RegrepUDDI)

Interest Calc

Balance Check

Back-End System Back-End System

Composite

Applications

Increased

Agility

Monolithic Systems

Reuse Services via Re-composition

The most important SOA concepts

• Services• Composition of services into business processes• Exchange of messages• Support for synchronous and asynchronous

communication• Loose coupling• Service registries• Quality of service• Self-describing interfaces with coarse granulation

SOA Value Proposition

• Reducing integration expense– Both development and maintenance cost by

isolating components and systems through well-defined interfaces and proper architecture layering.

• Increasing asset reuse• Increasing business agility

– Simplified Business Integration• Reducing business risk

– Both operational and compliance risk

SOA Value Proposition

• Faster time to market• Align IT and Business Units• Visible Business Process

SOA Definition (Re-caps)

AccountManagement

OrderProcessing

ServiceScheduling

The Root of the Problem

DataRepositories

Check Order Status

Check Credit

Check Customer Status

Check Inventory

Check Order Status

Check Inventory

Check Credit

Monolithic,IndependentApplications

Multiple CustomerViewsDispersed, unintegrated data

Check Inventory

Check Customer Status

FinanceSalesMarketing ExternalPartner

DataWarehouseCRM

IT Silo

CheckCustomer Status

Determine ProductAvailability

VerifyCustomer Credit

Order Status

CalculateShipping Charges

Order Status

VerifyCustomer Credit

DataRepository

ExternalTradingPartner

AnotherBusiness

Red PrairieWarehouse

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

CustomMarketingSystem

MonolithicApplications

AccountsManagement

OrderProcessing

FieldService

Scheduling

IT Silo

Order Status

CalculateShipping Charges

Verify Customer Credit

DataRepository

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

MonolithicApplications

AccountsManagement

OrderProcessing

FieldService

Scheduling

Determine ProductAvailability Order Status

Verify Customer Credit

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

CustomMarketing

System

Reuse Services Via Re-composition

ElementalBusinessServices

AccountsManagement

OrderProcessing

FieldService

Scheduling

DataRepository

CheckCredit

CheckInventory

CheckOrder Status

CreateInvoice

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

Reuse Services Via Re-composition (cont.)

AccountsManagement

OrderProcessing

FieldService

Scheduling

DataRepository

ComposedBusinessProcesses

Installation Scheduling Process Customer Order Bill Presentment/Payment

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

CheckCredit

CheckOrder Status

CreateInvoice

CheckInventory

Installation Scheduling

CheckInventory

AccountsManagement

OrderProcessing

FieldService

Scheduling

DataRepository

CreateInvoice

CheckCreditCheck

Order StatusCheck

InventoryCheck

Customer Status

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

Process Customer Order

CheckCredit

CheckInventory

CheckOrder Status

AccountsManagement

OrderProcessing

FieldService

Scheduling

DataRepository

CheckCredit

CheckInventory

CheckOrder Status

CreateInvoice

Bill Presentment/Payment

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

CheckOrder Status

CreateInvoice

DataRepository

AnotherBusiness

Mgmt. System

SAPFinanceSystem

OracleCRM

System

AS400Sales

System

Business Processes Are Composed Hierarchicallyto Create Composite Applications

AccountsManagement

OrderProcessing

FieldService

Scheduling CompositeApps

CheckCredit

CheckInventory

CheckOrder Status

CreateInvoice

CheckCredit

CheckInventory

CheckOrder Status

CreateInvoice

DataRepository

AnotherBusiness

Mgmt. System

OracleFinanceSystem

SiebelCRM

System

AS400Sales

System

Shared Services – Composite Apps – Increased Functionality

AccountsManagement

OrderProcessing

FieldService

SchedulingAnother

OneManage

ExceptionOrders

SubmitChangeOrder

SOA Implementation Framework

SOA Framework

Resources

Services

Business Process

Access Layer

SOA Framework

External/Internal Systems

Build Re-usable Services (ESB)

Business Process Management (BPEL)

User Interface + Single Window (Portal)

User Interface Dashboard (KPI)

SOA Implementation• Services Implementation

– Various Programming

– Web Services

– Non Web Services; Legacy via adaptors

– Data Services => JDBC

• Message Exchange => XML Schema (TH -eGIF)

• Self-describing interface => WSDL• Communication of Services/Management => ESB• Service Orchestration => BPEL• Presentation => Portal, Web Programing

SOA Hardware Architecture

Resources Layer

Customer

BankManufacturer System1

Shipping

LineBank Custom System2 System3 SAP Databases

Resource Layers (cont.)

Customer

Shipping

Build Re-usable Services

Services Layer

Customer

Shipping

Services Layer (cont.)

CheckProduct Accounting Booking

Distribute

Custom

ClearingBilling Payment Order Purchasing

Enterprise Service Bus (ESB)

Components of Business Service Layer

Customer

Shipping

Distribute

Custom

Why ESB?• In most enterprise, Web Services are not the only

middleware solution.– Only SOAP is not adequate for services

connection

• Other middlewares products, messaging servers, Java EE, ORBs, Databases etc..

– Other binding communication protocols may be need; such as JDBC, JMS, Files, SMTP,MSMQ

• ESB acts as an intermediary layer of middleware to communicates between services using various protocols.

Enterprise Service Bus (ESB) is the software middleware

ESB acts as a mediator between different, often incompatible protocols and middleware products

ESB is the backbone of SOA

You can't buy SOA, but you can buy an ESB

The role of ESB in SOA

Features of an ESB• Web Services Support

– ESB offers an ability to invoke SOAP and WSDL based Web Services

• Adapters– Many ESB vendors will provide adapters to integrate

with different thrd-part applications, such as PeopleSoft, SAP

– Used for applications which do not directly have SOAP or XML interface

• Invocation– ESB supports synchronous and asynchronous calls

to services and sometimes callbacks

Features of an ESB (Cont.)• Mediation and protocol independence

– Variety of protocols can be reconciled for complex route across a variety of platform

– Allows to connect with different protocols such as HTTP, FTP, SMTP, JDBC

• Routing– Allows us to route the messages to different services

based on their content, origin or other attributes• Transformation

– Data represented as XML can be transformed using XSLT or XQuery before they are delivered to services.

– Some ESB supports various XML, e.g. HL7, SWIFT

Business Service Layer–Protocols /Adapters

Customer

Manufacturer

(Mail)System1

Shipping

LineBank

Custom

(Web Services)

System2

(Legacy)

System3

(Legacy)SAP Databases

Distribute

Custom

Adapter

Oracle

JDBCAdapter

AdapterFTP SMTP TCP/IP FTP FTP HTTP / SOAP

Business Service Layer – Data Format

Customer

Shipping

LineBank

Custom

(WebServices)System2 System3 SAP Databases

Distribute

Custom

Adapter

Oracle

JDBCAdapter

AdapterFTP SMTP TCP/IP FTP FTP HTTP/SOAP

EDIProprietary

FormatSWIFT FIX XML Table CSV

Transformation

Translation

Enrichment

Validation

Business Service Layer – Data Delivery

Customer

Shipping

Distribute

Custom

Adapter

Oracle

JDBCAdapter

EDIProprietary

Transformation

Translation

Enrichment

Validation

Queue Queue Topics Topics Topics Guaranteed Data Delivery

Business Service Layer – B2B Requirements

Customer

Shipping

Distribute

Custom

Adapter

Oracle

JDBCAdapter

EDIProprietary

Transformation

Translation

Enrichment

Validation

AuthenticationPartner

Management

Message

TrackingAuthorizationEncryption

Certificate

Management

Components of Business Service Layer

P/RP/O

Product

Inland

Booking

Vessel

Booking

Distribute

Custom

Clearing

Billing

Service

ServicePurchasing

Adapter

Oracle

Adapter

EDIProprietary

Format SWIFT FIX XML Table CSVData

Transformation

Translation

Enrichment

Validation

AuthenticationPartner

Management

Message

TrackingAuthorizationEncryption

Certificate

Management

Customer

Manufacturer

(Mail)System1

Shipping

LineBank

Custom

(WebServices)

System2

(Legacy)

System3

(Legacy)SAP Databases

Addition of Future Systems

Customer

Shipping

LineBank

Management

Future

System

Future

System

Future

System

Future

System

Retrieval

Future

ServiceBilling

Future

Service

Future

Service

Future

Service

Business Processes Management

The concept of Business Process Management [BPM] has its roots in Operation Transformation and enables flexible design deployment, monitoring and tracking, process focus and efficiency.

Customer

Shipping

LineBank

Courier

CompanySystem2 System3 SAP Databases

Distribute

Custom

Business Process Management (BPEL2.0)

BPM Standards : WS4BPEL 2.0

• Business Process Execution Language• Based on XML• IBM, BEA and Microsoft developed the first

version in 2002• BPEL 2.0 is latest version

BPEL Components

BPEL Editor

Example : BPEL

Customer

Shipping

LineBank

Courier

Distribute

Custom

Business Process Management (cont.)

Customer

Shipping

LineBank

Courier

Distribute

Custom

Business Process Monitoring

Customer

Shipping

LineBank

Courier

Distribute

Custom

Access Layer

User Interface + Single Window View

Customer

Shipping

LineBank

Courier

Distribute

Custom

User Interface and Single Window View (cont.)

AccountsManagement

OrderProcessing

FieldService

Scheduling

PersonalizedService

ManageException

Orders

SubmitChangeOrder

Customer

Shipping

LineBank

Courier

Distribute

Custom

Key Performance Indicators (KPI)

AccountsManagement

OrderProcessing

FieldService

Scheduling

PersonalizedService

ManageException

Orders

SubmitChangeOrder

Performance Measurement (KPI)

Customer

Shipping

LineBank

Courier

Distribute

Custom

Key Performance Indicators (KPI) (cont.)

AccountsManagement

OrderProcessing

FieldService

Scheduling

PersonalizedService

ManageException

Orders

SubmitChangeOrder

SOA Using GlassFish ESB

Open SOA Framework

Build Re-usable Services (ESB)

Business Process Management (BPEL)

User Interface

Challenges with Legacy ESBs

Most are proprietary and closed source>No transparency into vendor development

process– Complex and risky upgrade process

>Complete control by vendor– Vendor lock-in– Customers/partners unable to influence platform

direction>Can't easily incorporate external innovation

– Difficult for partner/customer to include value-added differentiation

Sun GlassFish PortfolioThe Open Platform for Building Dynamic Web Applications

Enterprise Server Web Space Server

Web Stack

Portal for web sitedevelopment andcollaborativework spaces

ApplicationServer withEnterprise-scalemanagement and monitoring,including support for SNMP

A full SOA web platform

A complete LAMP stack

Web Stack GlassFish ESB

A Need for Two Approaches• Complex ESB

– Purpose:• Highly complex requirements,

feature overload

– Target Usage:• Enterprise-wide infrastructure

• Lightweight ESB– Purpose

• For rapid deployment

– Target Usage• Specific project, narrow initial focus

A sledgehammer

solution can be overkill

for a small project

The right tool for the right

Enterprise Service Bus

Business Process Mgmt. Adapte

3rd Party & Custom

ComponentsData Mash

XSLTProcess

“We Already Have an ESB”

Existing Proprietary

Federation

“Spaghetti” connectivity architecture

• ...so why a new ESB?– Need to react faster, lower risk– High costs, risk, complexity, and lack of agility

• Strategy: For all new projects– Federate with existing ESB– Lower costs and risks and increase agility with lightweight ESB

National ESB

ESB in each organization

GlassFish ESB – A Lightweight ESB

Open source, standards based, pluggable ESB with commercial support from Sun

• Platform Capability– Rich tooling and dynamic language support with NetBeans IDE– GlassFish Enterprise Server– Java Business Integration (JBI) Runtime and Containers– Centralized management and monitoring

• Integration Capability– Message Server, Business Process Management– Core Adapters & Service Engines: FTP, LDAP, database, HTTP, XSLT...– Ensured Web Service interoperability (WSIT WS* Support)– Data Mashup

• Low Cost Pricing Model– Simple per server per year subscription model– No upfront license cost, start low and pay as usage grows

Product Architecture

Java Business Integration Container

Normalized Message Router

Installation Deployment Control Monitoring

BPELEngine

XSLTEngine

DataMashup

FTPBinding

Java EEEngine

HTTPBinding

DBBinding

• Lightweight• Open source• Pluggable

– ...leverages the JBI infrastructure• The Java “plug-in”

standard for engine/adapters

Web Services

• The NetBeans IDE– Single, unified, modern, comprehensive design time tooling– Open-source, Java-based, modular, fast & extensible– Promotes productivity and rapid development lifecycle– GUI editors for all purposes

• BPEL process modeling, XSLT, XSD, WSDL, CASA...• Sophisticated Java editor

– Integrated Service Administration Plugins (JBI, Databases..)– Design, compose, build and deploy

• Composite applications, web services, Java EE components

– Integrated debugger, help, samples, blueprints and patterns– Plugins available for other Sun SWI software (e.g. Identity

Manager, Access Manager and Portal Server)

Design-time: Develop, Debug & Deploy

Open SOA Framework

Build Re-usable Services (ESB) – openESB (GlassFish)

Business Process Management (BPEL) NetBeans / BPEL SE (GlassFish)

User Interface NetBeans (Visual JSF), GlassFish

Health Bank orPersonal Health Record (PHR)

Support Organization

Community #1

IntegratedDelivery System

Community Health Centers

Community #2

CDC VA

The InternetStandards, Specifications and Agreementsfor Secure Connections

Common “Dial Tone” & “Chain of Trust”

Sun Open Source SOA Case StudyNationwide Health Information Network - Connect (NHIN-Connect)

• Challenge– Lacking ability to easily share

electronic health information between multiple healthcare entities

• Social Security, Military Health,Veterans Admin...

• Solution– Using Sun open source Open

ESB, GlassFish...– Secure exchange of

interoperable health information

– ESB/SOA frameworkSource: Office of the National Coordinator for ITU.S. Dept. of Health & Human ServicesApril 2008

http://events.fcw.com/events/2008/ea/downloads/EA08_2-4_Sankaran.pdf

The Gateway utilizes an Enterprise Service Bus (JBI/JSR208)

Developed as open source using open standards

SOA Case Study

2003: The state of UK Healthcare IT

Pharmacy Community

GP Community Hospital Community A

Private CareHospital Community B

Social Care

Stand-Alone Boxed applications and systems

Patient-centred services Patient SafetyConfidentiality/SecurityService Reliability Management Information Clinical Data SharingNHS Reform

Regional and National

IT Services for the NHS= £6billion

NHSNational Programme

for IT

Existing Systems

Replacement & Integration

Patient PortalNHS Choices

myhealthspace

Prescribing processChoose and Book

Process

PatientAppointments

Prescriptions Picture Archiving &Communications

Managementinformation

Today's evolving landscape

National and Regional ServicesCare

Record Service

Payment byResults

Pharmacy Community

GP Community

Hospital A Private careHospital B

Social Care

New Care Pathways

and ServiceOrchestratio

New Composite

Applications

PharmacistPortal

Telecare Portals

Maternity

Portal

Clinical Spine Portal

Maternity Care

Diabetes Care Transfer of CareTheatres

Why EAI in Healthcare is here to stay

• SOA generates demand for EAI service and data discovery

• NPfIT programme requires EAI for existing systems to fulfil national and regional SOA services

• EAI firmly established as healthcare core IT skill since 1996

• Existing customers need to upgrade as older SeeBeyond products are EOLed

> Healthcare integration standards (HL7 v2/v3, etc) still messaging based, see example HL7 v3 schema :

Healthcare CIO awareness of SOA is rising• Nearly all UK hospitals have EAI platforms for:

– HL7 version 2 - ubiquitous– HL7 version 3 – mainly around NHS Spine

• Desire for Healthcare SOA capability is strong:– UK National Programme is forcing uptake of

national and regional services– Cost pressures forcing NHS to develop shared

services– Government agenda for NHS reform demand

greater agility from IT – Increasing involvement of private sector care

• More press coverage of healthcare SOA

SOA for the worlds largest integration project $2.3B project 50+ million patients with life-long healthcare records Linking with 250 hospitals 600,000 providers (doctors, nurses, scientists) 10,000 systems, 40,000 sites For the National Service Provider (NASP) “Spine”• 2005 – 2 billion transactions per year

2010 - 6 billion transactions per yearDue to peak usage approximately 420 messages per second (4–6x hourly average)Response SLA – 0.2 secondsAvailable 99.9% (44 minutes per month downtime)Failover in 30 minutes

For the Local Service Providers (LSP’s)• Each has a lot of local messages (10bn to 12bn per year) and shares

some with the NASP There are 5 LSP and therefore the total volumes of messages per

year is: 56 billion to 66 billion messages per year

+NewcastleNewcastle

BristolBristol

NameNHS No.Address

Broken Leg

Chest infection

Back Pain

Broken Leg

Chest Infection

NameNHS No.Address

Back Pain

Broken Leg

Chest Infection

NameNHS No.

Back Pain

Broken Leg

Chest Infection

NameNHS No.Address

Emergency

Largest Healthcare Project in the World

• One of largest databases in world (entire NHS population of 55+ million)

• Potentially 500,000 users

• 600+ million prescriptions will be processed per annum

• High levels of availability (99.9%)

• Very fast response times (less than 0.35 secs)

UK - NHS

+● A Bristol resident visits Newcastle

● Taken ill - admitted to local hospital

● A&E Consultant needs patient’s medical history

● Searches Spine by name, address, or NHS Number

● An entry found in PDS (Personal Demographic Service)

Newcastle

Bristol

How the Spine works … In an emergency

… more

NameNHS No.Address

● Clinical records then retrieved from PSIS (Personal Spine Information Service)

● Immediately made available to A&E Consultant in Newcastle

● Patient receives treatment – Details recorded locally

● AND transmitted back to Spine for future reference

+Newcastle

Bristol

… more

NameNHS No.Address

Broken Leg

Chest infection

Back Pain

Broken Leg

Chest Infection

NameNHS No.Address

Emergency

● Patient goes back home to Bristol

● Discharge message transmitted from hospital to Spine

● Discharge summary (details of diagnosis & treatment) is sent automatically to G.P. in Bristol for follow-up care

● All communications in real-time and virtually immediate

+Newcastle

Bristol

Broken Leg

Chest infection

Back Pain

Emergency

NameNHS No.

Discharge Summary

Discharge

What does the NHS want?

• Access to patient records transformed

• Fast and secure access nationally

• Link to full demographic information

• Portal access for clinicians

• Highly resilient transmission of eBookings and ePrescribing

• eEnablement of the NHS in a secure and high integrity environment

Benefits

Thank you

thanachart.numnonda@sun.comwww.facebook.com/thanacharttwitter.com/thanachartwww.thaijavadev.com

TH e-GIF on SOA Using Open Enterprise Architecture

Documents

Transcript of TH e-GIF on SOA Using Open Enterprise Architecture

JBoss Enterprise SOA Platform - library.corporate-ir.netlibrary.corporate-ir.net/library/67/671/67156/items/279799/FINAL... · JBoss Enterprise SOA Platform Announcement JBoss Enterprise

Enterprise SOA & Cloud Computing planing

SOA- DOA? The enterprise perspective

JBoss Enterprise SOA Platform 4.2 SOA ESB JBPM Integration Guide

Enterprise SOA. Service-Oriented Architecture Best

1 SOA and Enterprise Computing Enterprise Java Beans.

SOA World Magazine-Enterprise SOA

Unified SOA Governance for the JBoss Enterprise SOA Platform

Complete SOA Solution for your Enterprise

Enterprise IT Architectures SOA Part 1 - UZH · Enterprise IT Architectures SOA Part 1 ... SOA Reference Architecture ... tools, methods and technologies such as web services.

e-Framework, SOA and Enterprise Architecture

Architecture Patterns for Enterprise-Wide SOA

SOA as Business Strategy for Enterprise

JBoss Enterprise SOA Platform 4.2 SOA ESB Registry Guide

Enterprise Mashups With Soa

JBoss Enterprise SOA Platform 4.2 SOA ESB Message Action Guide

Enterprise Java and SOA

APIs Inside Enterprise - SOA Displacement?

Enterprise Architecture and SOA - Digital Transform · Enterprise Architecture and SOAEnterprise Architecture and SOA ... Enterprise ArchitectureEnterprise Architecture Service ManagementService

ARQUITETURA - Understanding Enterprise SOA