Service-Oriented Architecture and Web Services Essentials by Iway - Jake Freivald

You might also like

Download as ppt or pdf
Download as ppt or pdf
You are on page 1of 67

Service-Oriented Architecture

and Web Services


Essentials

Jake Freivald
February 9, 2008

Copyright © 2001 iWay Software 1


A Lesson From Calvin and Hobbes

service-oriented
architecture
First, A Question

 What does the “S” stand for in SOA?


“Service”

 Who or what is being serviced in SOA?


The business process owner

Copyright © 2001 iWay Software


The Concept Behind SOA

 A Lieutenant has:
 A flagpole
 A rope
 A flag
 Two shovels
 Three bags of cement
 A Corporal, a Lance Corporal, and a Private
 He has been ordered to erect the flagpole
 How should he erect it?
“Corporal, erect the flagpole.”
Copyright © 2001 iWay Software
Business Questions for IT Managers

 How do we improve check processing?


 What will it cost to merge order processing apps?
 How long to implement the CRM application?
 How do I know that this IT investment will pay off?

Answering these questions requires a solid


understanding of enterprise architecture

Copyright © 2001 iWay Software


The Problem With Current Architecture

 What’s this change going to cost?


 What will it affect?
 Will it be worth it?
Copyright © 2001 iWay Software
Service-Oriented Architecture:
An Attempt to Gain Control
 Align IT with business requirements
 “Process check”
 “Accept order”
 “Change address”
 Not “Connect SAP to JDE, getting additional
information through CICS transaction WNIT, then sending a message
through WMQI to the EDI processor for sending to…”
 How do we do it?
 Define services
 Have IT create an architecture that
supports services
Copyright © 2001 iWay Software
Implication

 Web services aren’t the same thing as SOA


 Can be application-oriented
 Can be “tightly coupled”
 Can be unarchitected

 What are Web services?


 How do we use them properly?

Copyright © 2001 iWay Software


What Are Web Services,
and Why Use Them?

Copyright © 2001 iWay Software Copyright © 2001 iWay Software 2


Interface Flexibility vs. Interoperability
Flexibility

Interoperability
Copyright © 2001 iWay Software 1
Interface Flexibility vs. Interoperability

text
Flexibility

HTML

Flash

Interoperability
Copyright © 2001 iWay Software 1
Interface Flexibility vs. Interoperability

Flat file + FTP


Flexibility

Web services

CORBA

Interoperability
Copyright © 2001 iWay Software 1
Our Five Web Services Terms

XML

Schema
Flexibility

SOAP + WSDL

UDDI

Interoperability
Copyright © 2001 iWay Software 1
Topic: XML

XML

Schema
Flexibility

SOAP + WSDL

UDDI

Interoperability
Copyright © 2001 iWay Software 1
XML

 “Self-describing”
 Easy to understand and use (in theory)
 Cross-platform
<book>
<author>Joliet Jake Blues</author>
<title>Shades of Blue</title>
<publisher>Free Forest Publishing</publisher>
</book>

Copyright © 2001 iWay Software 1


XML – Issues

 Too flexible. Can describe anything, but we need


to know specifically what we’re going to see
<book>
<author>Joliet Jake Blues</author>
<title>Shades of Blue</title>
<publisher>Free Forest Publishing</publisher>
</book>
<book>
<authors>
<author>
<title>Joliet</title>
<first>Jake</first>
<last>Blues</last>
</author>
</authors>
<title>Shades of Blue</title>
<publisher>Free Forest Publishing</publisher>
</book>

Copyright © 2001 iWay Software 1


Topic: XML Schema

XML

Schema
Flexibility

SOAP + WSDL

UDDI

Interoperability
Copyright © 2001 iWay Software 1
Schema

 Sets limits for what a given XML document holds


 The absolute minimum for automatic interactions
<book>
<author>Joliet Jake Blues</author>
<title>Shades of Blue</title>
<publisher>Free Forest Publishing</publisher>
</book>
<book>
<authors>
<author>
<title>Joliet</title>
<first>Jake</first>
<last>Blues</last>
</author>
</authors>
<title>Shades of Blue</title>
<publisher>Free Forest Publishing</publisher>
</book>

Copyright © 2001 iWay Software 1


Topics: SOAP and WSDL

XML

Schema
Flexibility

SOAP + WSDL

UDDI

Interoperability
Copyright © 2001 iWay Software 1
Example: Using SOAP and WSDL
User Administrator

SOAP
WSDL
Request

“Can you help me “Sure. Here’s the


gain access to SAP?” WSDL file.”

SOAP
Response SAP

Copyright © 2001 iWay Software 2


Topic: UDDI

XML

Schema
Flexibility

SOAP + WSDL

UDDI

Interoperability
Copyright © 2001 iWay Software 2
Example: Using UDDI with
SOAP and WSDL
User UDDI Directory

SOAP
UDDI
WSDL
Request

SOAP
Response SAP

Copyright © 2001 iWay Software 2


SOA and Web Services

Copyright © 2001 iWay Software Copyright © 2001 iWay Software 2 2


The Vision of Web Services in
Service-Oriented Architecture

Java and Business B2B


Portals
.NET Apps Intelligence Interaction

Web Services: XML and HTTP

WS WS WS WS WS WS WS WS
The Reality

Java and Business B2B


Portals
.NET Apps Intelligence Interaction

Web Services: XML and HTTP


Custom Web Service Implementation

API API API API API API API API


Eliminating Code from Web Services

Java and Business B2B


Portals
.NET Apps Intelligence Interaction

Web Services: XML and HTTP


iWay SOA Middleware: ESB, etc.

API API API API API API API API


SOA Means Not Being
Limited To Web Services

Java and Business B2B


Portals
.NET Apps Intelligence Interaction

Web Services, XML, HTTP, JCA, ODBC, Plug-ins,…


iWay SOA Middleware: ESB, etc.

API API API API API API API API


One of Our Customer’s Requirements

1. Get approved work 2. Load design detail into 3. Get Services Request
design work request Detail

4. Obtain Accomplish 5. Update Crew Schedule 6. Get Labor Equipment Info


Records

7. Update estimate tables 8. Extract Employee Skills

Copyright © 2001 iWay Software 2


Customer Solution

Customer/1 PragmaCAD Passport Primavera (P3E)


Customer Rates & Mobile Crew Material Projects Activity
Equipment
Billing metering Management Profiles Catalogue Planning Estimates

CIS Customer Job Order AM Work Actual Labor


Schedules Equipment
Tools Info Tools Tools Orders Hours, costs

Service Exposure, Composition, Provision: ESB

App Server:
Orchestration

Service Exposure, Composition, Provision: ESB


ArcFM Timberline eTimeMachine Peoplesoft
Enterprise
Mapping & Work Accounting Material Resources & Employee HR
Project
Models Design & Estimating Catalogue Employees Skills Records
Management

Graphical Gas & Estimating Enterprise Time and HR Organization


Evaluations
Tools Electric tools PM tools Expense Tools detail
Copyright © 2001 iWay Software 2
Web Services
Aren’t Enough

Copyright © 2001 iWay Software Copyright © 2001 iWay Software 2 3


Web Services Alone Don’t Mean
You Have a Good Architecture
Service Credit Risk
consumers Engine

Application owners create


different services for each
ERP

Credit Credit
in PSFT in SAP

Information
Assets
The Usual Solution

Service Credit Risk


consumers Engine

Common (but bad) idea:


application developers call
each service independently

Credit Credit
in PSFT in SAP

Information
Assets
Terrible Development

Service Credit Risk


consumers Engine

Requires knowledge of
business problem,
which functions to call,
application security, metadata,
transaction management

Credit Credit
in PSFT in SAP

Information
Assets
Worse Maintenance

Service Credit Risk


consumers Engine

Tightly couples new application


to underlying ERPs, so upgrades
must propagate to new
application.

Credit Credit
in PSFT in SAP

Information
Assets
Problems Multiply With Reuse

Service EAI or BPM Credit Risk Portals and


consumers Tools Engine B2B systems

Every new application has to


recode multiple service calls the
same way, reducing the benefit
of service reuse.

Credit Credit
in PSFT in SAP

Information
Assets
No Isolation From Change

Service EAI or BPM Credit Risk Portals and


consumers Tools Engine B2B systems

Adding or removing applications


causes a ripple effect throughout
the environment.

Credit Credit Credit


in PSFT in Siebel in SAP

Information
Assets
Better: Use “Service Composition”

Service EAI or BPM Credit Risk Portals and


consumers Tools Engine B2B systems

Complete isolation from change.


Service implementation has little
to no effect on consumers.

Enterprise
Service
Bus

Credit Credit
in PSFT in SAP

Information
Assets
Better: Use “Service Composition”

Service EAI or BPM Credit Risk Portals and


consumers Tools Engine B2B systems

Complete isolation from change.


Service implementation has little
to no effect on consumers.

Enterprise
Service
Bus

Credit Credit Credit


in PSFT in Siebel in SAP

Information
Assets
Better: Use “Service Composition”

Service EAI or BPM Credit Risk Portals and


consumers Tools Engine B2B systems

Complete isolation from change.


Service implementation has little
to no effect on consumers.

Enterprise
Service
Bus

Credit Credit
in Siebel in SAP

Information
Assets
What Was That Again?

Copyright © 2006 iWay Software Copyright © 2001 iWay Software 2 4


Web Services and Legacy Systems

Turn this… …into this


Application Application Application Application
App App App App
Service Service Service Service
Interface Interface Interface Interface

Service Service Service Service


Application Application Application Application
Interface Interface Interface Interface
App App App App

Web services decouple


service interfaces and applications
…but service invocations and interfaces
are usually still tightly coupled

Copyright © 2006 iWay Software 4


ESB and Legacy Systems

Turn this… …into this


Service Service Service Service
App App App App
Interface Interface Interface Interface
Service Service Service Service
Interface Interface Interface Interface

Service Service Service Service


Interface Interface Interface Interface
Service Service Service Service
App App App App
Interface Interface Interface Interface

ESBs can decouple service invocations


from service interfaces
…through transformation,
routing, and service composition

Copyright © 2006 iWay Software 4


SOA, Legacy, and the ESB
Focus on your core business rather then IT …

New Check
Traveler
Service

Add new services


Travel
Reservation
Book Flight Check Credit faster
Service Service
Process

Enterprise Service Bus

Hotel Flight Book Book


Availability Availability Hotel Car Change services with
Service Service Service Service
minimal impact to
existing services
New Flight Old Flight
Availability Availability
Service Service

Copyright © 2006 iWay Software 4


SOA, Legacy, and the ESB

1 When all applications 2 When not all applications


conform to Web Services conform to Web Services
standards… standards…
Travel Check Travel Check
Check Credit Book Flight Check Credit Book Flight
Reservation Traveler Reservation Traveler
Service Service Application Application
Process Service Process Application

Typical Enterprise Service Bus Advanced Enterprise Service Bus

Hotel Flight Hotel Flight


Book Hotel Book Car Book Hotel Book Car
Availability Availability Availability Availability
Service Service Application Application
Service Service Service Application

…a “standards-based” ESB …you may need an advanced ESB


may do enough that creates services from existing
non-standard assets.
Copyright © 2006 iWay Software 4
SOA, Legacy, and the ESB

iWay Enterprise Service Bus

Web Service connectivity Universal connectivity


and data transformation and transformation
Web Services Tuxedo CICS Baan
JMS JCA Essbase 5250 3270
UDDI HTML Siebel SAP EDIG@S ESRI
EDIINT AquaLogic BizTalk UCCnet
XML SOAP JMS FIX Oracle Google VSAM
Lawson PeopleSoft ebXML DB2/400
WSDL HTTP AS1 GJXML AS2 AS3 HL7

Copyright © 2006 iWay Software 4


iWay’s Two Major Benefits:
Productivity and Interoperability
Productivity Interoperability
 From developer’s perspective,  Different platforms and software
everything looks the same require different plugins
 Requires no extra training or skills  Leaves you open for next steps, e.g.,
 Useful for their tools of choice B2B, post-Web services

Composite
BPM/BPEL B2B Portals EAI Tools
Apps

XML
JCA Plug-in Plug-in
AS2

Service interfaces: business data only

Stateless services

DB2 VSAM CICS CICS IMS DB2/400 JDE Oracle SAP SQL Svr Etc.
Mainframe iSeries Unix Windows
Copyright © 2006 iWay Software 4
SOA and
Business Intelligence

Copyright © 2001 iWay Software Copyright © 2001 iWay Software 2 4


Options:
Traditional ETL
 Supports DW goals: single version of truth, etc.
 Relatively simple conceptually
 Relatively high latency

Data
Flow

Copyright © 2006 iWay Software 4


Options: Real-time, or
“Trickle-feed”, Data Warehousing
 Events captured, cleansed, loaded as they happen
 Supports DW goals: single version of truth, etc.
 Very low latency, from real-time to several minutes

Event
Flow

Copyright © 2006 iWay Software 4


Options: Distributed Query

 One query, many sources: reconciled in real time


 The operational systems’ “version of the truth”
 Need to be wary of performance, contention issues

Copyright © 2006 iWay Software 5


Data Integration vs.
Application Integration

Application Application

Data Data
FTP Load
Dump

Copyright © 2001 iWay Software 5


Data Integration vs.
Application Integration

Application Application

Data Data
FTP Load
Dump

Copyright © 2001 iWay Software 5


Data Integration vs.
Application Integration

Application Application

Transactions
Transactions

Copyright © 2001 iWay Software 5


Application Integration – and SOA –
For Business Intelligence

Application
Transactions

Business
Intelligence
Applications

Data
Warehouse

Copyright © 2001 iWay Software 5


Application Integration – and SOA –
For Business Intelligence

Application
Transactions

Business
Intelligence
Applications

Data
Warehouse

Copyright © 2001 iWay Software 5


Application Integration – and SOA –
For Business Intelligence

Application
Transactions

Business
Intelligence
Applications

Data
Warehouse

Copyright © 2001 iWay Software 5


Application Integration – and SOA –
For Business Intelligence

Application
Transactions Portals

Business
Intelligence
Applications

Composite
Applications

Data Business-to-
Warehouse Business
Interactions

Copyright © 2001 iWay Software 5


What Services Should We Expose,
And When?
 SQL-queryable data models
 Parameterized non-SQL queries
 Queries deployed from BI tools
 Pros and cons of various tool sets
 Business intelligence
 Application integration
 EII / federated data query tools
 Customers:
 Bell Canada
 Iowa Courts
Copyright © 2006 iWay Software 5
Henny Penny

Copyright © 2006 iWay Software Copyright © 2001 iWay Software 2 5


Pre iWay Topology

RIP and read

Rip and
7.3.3
Read

FTP / Form

Trading Receive and print JDE Terminal


orders
Partner I Interface

Value Added Network


DB2
ODBC

FTP / X!2 EDI ISERIES

INOVIS EDI
Translator
Trading
Partner II
Copyright © 2006 iWay Software 6
Solution Topology
Trading Partner I Trading Partner II Trading Partner III

Sales Orders Sales Orders Email Server

Protocol EDI X12 Protocol


Adapter Adapter Adapter
FTP/ XML FTP/ X!2 EDI eMail/File

Validate and Translate Running a process


iWay flow to validate
Service and insert sales
Manager orders.
Trading Partner Runtime
JDE Master Business
JD Edwards Legacy
Functions interface Windows 2003 Server
One World Adapter Adapter

DB2

7.3.3 iSeries
Copyright © 2006 iWay Software 6
Colorado Dept of
Corrections

Copyright © 2006 iWay Software Copyright © 2001 iWay Software 2 6


Pre iWay Topology
Flat files
HL7
GJXML

Call Center
Is there any vendor
that
can help us validate,
transform, and route
Online flat files, HL7, and
Pharmacy GJXML – in and out -
of our Jail Colorado Department
Of Corrections
Management System?
Jail Management System

Colorado
Bureau of
Investigation
Copyright © 2006 iWay Software 6
iWay Solution

Colorado Department of Corrections


Call Center
Wintel Unix

Flat files

HL7 Service RDBMS


Manager Adapter Informix
Online
GJXML
Pharmacy

Jail Management
System
DOC Enterprise Service Bus

Colorado
Bureau of
Investigation*

*Future:
Copyright GJXML
© 2006 exchanges
iWay Software with other departments inside the Colorado Justice supply chain … 6
Wrap-up

Copyright © 2001 iWay Software Copyright © 2001 iWay Software 2 6


What To Do Now: Project Perspective

 Evaluate high-value projects


 Portal, composite application, B2B, BPM, BI
 Evaluate BI applications
 You measure important stuff: walk the process
 Identify the services needed to support them
 Identify other projects that can use them
 Create the services
 Orchestrate them

 Don’t be too timid: you’ll want the ROI and reuse


Copyright © 2001 iWay Software 6
Call to Action
Take us up on . . .
Half Day needs analysis and Review
Our iWay Integration Specialists will
 Analyze your business challenge
 Examine your Enterprise / Environment
 Assess your integration requirements
 Recommend Integration Alternatives
This half day session is free
Hands on Workshops
Note your interest on your evaluations
Copyright © 2001 iWay Software 6

You might also like