Build a Flexible Payment Network

Build a Flexible Application
Infrastructure Environment –
WebSphere Connectivity
Solutions

Business Challenge

Your payments network
Our payments business is is too brittle, making it
growing fast, our payments difficult and costly to
network needs to keep up! improve.

Service Oriented Finance IBM
CIO
05 Build A Flexible Application Infrastructure Environment - Connectivity
2

Service Oriented Finance Payment Systems -
Connectivity Requirements
Extend the reach of the payment network
Connect to any enterprise resource, using any protocol
Integrate with existing departmental connection solutions
Use existing applications, regardless of data format
High performance
Support increasing demand
Transactional
Maintain data integrity
Use service lookups for resilient business operations
End points are sometimes not available or not responsive
Dynamically select alternatives
3

Current Service Oriented Finance Payment
Network Is Not Flexible

Departmental Change Departmental
Enterprise Service Bus Enterprise Service Bus

Many point-to-point connections between applications
Connectivity logic is coded into applications
One change requires many other changes
Existing departmental connection solutions are not integrated
4

Vision For A New, Flexible Service Oriented
Finance Payment Network

Enterprise Service Bus
Mediation Services:
Routing, Transformation, Transport Switching,
Augmentation, Transactional, Resilience

Departmental ESB Change Departmental ESB

Connect anything to anything using fewer connections
Use existing applications
Fewer changes as requirements change
Work seamlessly with existing departmental ESB solutions
5

IBM Enterprise Service Bus Extends Reach By
Connecting To Your Entire Enterprise
Devices Data Formats Messaging Systems
ACORD
COBOL Copybook XML WebSphere MQ
Telemetry
SWIFT EDIFACT MIME Sonic MQ
Mobile
Any JMS TIBCO EMS
HIPAA IDoc HL7
TIBCO Rendezvous
C Header X12 TLOG
WebSphere platform
Custom Binary
messaging

IBM Enterprise Service Bus Databases
File Systems
DB2 SQL Server
Platforms Oracle Sybase
z/OS AIX Linux Appliance
Solaris HP/UX Windows Enterprise
Protocols Applications
SOAP FTP Point-to-Point UDDI SAP
Pub / Sub
TCP/IP Sockets Enriched JD Edwards
Message
HTTP Oracle PeopleSoft
LDAP Multicast Models Registries
SMTP Siebel

Microsoft BizTalk Server Has Limited Reach
ACORD
Telemetry
Mobile
Any JMS TIBCO EMS
HIPAA IDoc HL7
TIBCO Rendezvous
C Header X12 TLOG
WebSphere platform
Custom Binary
messaging

Microsoft BizTalk Databases
File Systems
DB2 SQL Server
Pub / Sub
TCP/IP Sockets Enriched JD Edwards
Message
SMTP Siebel

Oracle Service Bus Has Limited Reach
ACORD
Telemetry
Mobile
Any JMS TIBCO EMS
HIPAA IDoc HL7
TIBCO Rendezvous
C Header X12 TLOG
WebSphere platform
Custom Binary
messaging

Oracle Service Bus Databases
File Systems Need adapter for updates
DB2 SQL Server
Pub / Sub
TCP/IP Sockets
EM
Enriched JD Edwards
Message O
SMTP Siebel

Many Enterprises Have “Islands” With Multiple
ESBs Deployed
Requesters cannot easily call service providers on other ESB islands

IBM ESB
R
R
S
S

Requester on
Oracle ESB Oracle wants to call Sonic ESB
service on Sonic
R S
R R
S R
S R
S S

TIBCO ESB
R
R = service requester S
R
S

S = service provider
9

IBM Extends Reach By Federating Multiple
ESBs Into A Single, Logical ESB
Provides any-to-any connectivity between ESB islands
Federated ESB
Requester on Oracle
IBM ESB successfully calls
service on Sonic
R
R
S
S

Oracle ESB Sonic ESB
R S
R R
S R
S R
S S

TIBCO ESB Oracle, Microsoft,
R
S
and JBoss can’t
S
R do this!

10

Federating ESBs With IBM Middleware
Connectivity
Web services
WebSphere MQ asynchronous messaging
WebSphere Message Broker for JMS interconnectivity
Benefit – connect to any application or platform

Security and governance
WebSphere Services Registry and Repository
Benefit – consistent governance across applications

Monitoring
Tivoli management
Benefit – consistent monitoring across applications

11

Content-Based Routing Mediation Service
Example: Route payment based on payment amount

High Value
Receiver
> 100


XML Content
<amount>
Sender 56.83
274.25 Based
</amount>
Routing

< 100
Low Value
Receiver

12

Transformation Mediation Service
Example: Transform XML to Automated Clearing House format


Sender XML
ACHData
Receiver
<amount>
56.83 Transformation
005683
Binary Format
XML Format </amount>

Transform message format into any other format
No changes to existing sender or receiver applications
Transformations are centralized and re-usable

13

WebSphere Transformation Extender Makes
Creating Data Transformations Even Easier
COPYBOOK PROPRIETARY TABLE
01
03
TP-API-CB.
TP-AGAPI-CB.
CASH RECONCILATION
05 TP-AGAPI-REQUEST PIC X(40). Make Model PKG Extended_F
88 TP-AGAPI-INITIALIZE-REQUEST
VALUE 'INITIALIZE-MAPPING'. eatures
88 TP-AGAPI-PERFORM-MAPPING
VALUE 'PERFORM-MAPPING'. 10029847 - $100,000,000.00
Ford Prefect 3489 2984782q,
05
88 TP-AGAPI-FINISH-MAPPING
VALUE 'FINISH-MAPPING'.
TP-AGAPI-VERSION PIC X(04).
DUNS 0123 13948589 - $679,495,094.98 0 93847920,
88
88
TP-AGAPI-VERSION-VALID
TP-AGAPI-VERSION-0100
VALUES ARE '0100' '0200'.
VALUE '0100'.
F046000INV for 2 13950967 - $588,345,058.00 3438084
05
10
88 TP-AGAPI-VERSION-0200
TP-AGAPI-RESPONSE.
TP-AGAPI-RESPONSE-CODE
VALUE '0200'.

PIC 9(04) COMP.
months 120799 13950968 - $000,000,000.00 Ford Prefect 3489 2984782q,
88 TP-AGAPI-ALL-OKAY
88 TP-AGAPI-REQUEST-ERROR
VALUE 0.
VALUE 1.
12 718-339-1700I43989D-2 14001321 - $098,957,038.12 0 93847920,
3438084
88 TP-AGAPI-INITIALIZE-ERROR
88 TP-AGAPI-MAP-ERROR
VALUE 2.
VALUE 3. 120799999-b
88 TP-AGAPI-FINISH-ERROR
88 TP-AGAPI-UNKNOWN-LOOP-ID
VALUE 4.
VALUE 5.
003000010000 AAA: HT4459
Ford Prefect 3489 2984782q,
88 TP-AGAPI-NO-ALGORITHM
88 TP-AGAPI-NO-PARTNER
88 TP-AGAPI-NO-APPLICATION
VALUE 6.
VALUES 7 15.
VALUE 8. DUNS 4445 P55590 AAA: B33566 0 93847920,
88 TP-AGAPI-ALGORITHM-IO-ERROR VALUE 9.
88 TP-AGAPI-FATAL-GATEWAY-ERROR VALUE 10.
120799499QR AAA: C4058G 3438084
88 TP-AGAPI-GATEWAY-WRITE-ERROR VALUE 11.
88 TP-AGAPI-PARTNER-IO-ERROR
88 TP-AGAPI-BAD-VERSION
VALUE 12.
VALUE 13. 000004004000 AAB: 948409 Ford Prefect 3489 2984782q,
88 TP-AGAPI-BAD-NUMERIC-TYPE
88 TP-AGAPI-NO-ALIAS
VALUE 14.
VALUE 15. AAB: 874931 0 93847920,
88 TP-AGAPI-ACCESS-ERROR VALUE 16. 3438084
10 TP-AGAPI-RESPONSE-MESSAGE PIC X(80).
05 TP-AGAPI-APPLICATION-ID PIC X(10).
03 Ford Prefect 3489 2984782q,
01
0 93847920,
3438084

Takes any kinds of data from their native
DDA Application Updates formats BINARY
00011110010010011010010
10010010010010010000011

<MSG 19934749> Transforms the data into any desired 11010100101010110010010
10010010010010001010010
<ACCT BAL RPT> 10010010101010101000100
<ACCTNUM><“14001321”>
<ENDBALANCE><” $098,957,038.12”>
<DEBIT><“103048382$394,394.00”>
format 11100010100010010001001
00100100100100101010010
01010100100010010010010
No coding required for the data map
<DEBIT><“103048383$001,293.65”>
<CREDIT><“987463921$928,943.67”> 01001001110001010010101
</ACCTNUM> 01010101010010010101001
00100010010100101000010
</MSG>
Maps can be tested independent of the 10101010001001010001001
01001010100101010100101
01100101000000000001111
mediation flow 10010010010101110010010
01010101001010101101111

Integrates with IBM ESB offerings
Excellent for advanced transformation maps
14

WebSphere Transformation Extender Vertical
Product Packs Provide Industry Standard Formats

Financial Services Health Care
SWIFTNet FIN HIPAA
SWIFTNet Funds NCPDP
SEPA HL7
FIX Services Solutions
NACHA • HealthCare Hub
ACORD • Payment Processing
• Clearing House Processing

EDI Enterprise Applications

X12
EDIFACT SAP
TRADACOMS PeopleSoft
ODETTE Siebel
EANCOM

15

IBM Leads In ESB Data Transformation
Built-in graphical mapping tools for typical data transformation
requirements
Optional WebSphere Transformation Extender add-on
For advanced data transformation requirements
Industry Packs provide 16 standard industry data formats
Plugs into IBM ESB Eclipse design tool
Oracle provides only basic data transformation
Must use either external XQuery tool or self-built XSLT files
Only SWIFT, FIX, and SEPA industry data formats
Microsoft provides only basic data transformation
Simple graphical mapping tool, not appropriate for advanced
transformations
Only SWIFT, RosettaNet, HL7, and HIPAA industry data formats
16

Transport Switching Mediation Service
Example: Switch from SOAP/HTTP to a JMS message

SOAP/HTTP Enterprise Service Bus JMS

SOAP Envelope JMS Message Receiver
Sender XML Transport
XML
<amount>
Binary
<amount>
56.83 Switch
56.835683
JMS
Web Service </amount> </amount> Application
Point-to-Point or
Publish/Subscribe

17

Eclipse Development Tool Makes Creating ESB
Mediation Services Easy
Extensive palette for building mediation services

Graphical canvas for mediation flow design
Drag & drop objects from palette
Common tooling platform for IBM

Disconnected
development
allows you to
work anywhere 05 Build A Flexible Application Infrastructure Environment - Connectivity
18

Implementing An IBM Enterprise Service Bus
Depends Upon Your Requirements

WebSphere WebSphere WebSphere
Requirements ESB Message Broker DataPower

Built on WebSphere Application Server
Rack-Mountable Appliance
Available on Wide Range of Platforms
Federates Other ESBs
WebSphere Transformation Extender Option
Transactional Mediation Flows
Dynamic Service Lookup at Run Time
Adapters for Enterprise Applications
Database Read/Write
Non-IBM JMS Messaging Systems
TIBCO Rendezvous

Multicast Output (Native)

19

ESB Offerings From IBM WebSphere Deliver A
Common Set Of ESB Capabilities

Mediations to enable Leading web services
common patterns standards

Transformation of First class
common data formats interoperability

Connectivity via common Mission-critical qualities
protocols of service

Support for WebSphere Transactional integrity
Service Registry and
Repository
20

DataPower Models Provide Powerful ESB
Capabilities
Business to Business (B2B) Appliance XB60
All capabilities of XI50, plus …
Standalone B2B Gateway with support for AS2, AS3 and
Web Services
Trading Partner Management for B2B Governance

Integration Appliance XI50
All capabilities of XS40, plus …
Optimized to bridge between leading standard protocols at
wire speed
Enables transformation between a wide range of data
formats
Captures and emits events to facilitate web services
management

XML Security Gateway XS40
Web service threat protection and message security
Validates XML schemas and messages, providing advanced
XML threat protection
Enables encryption and decryption and signing and
verification of entire messages or individual XML fields
Supports fine-grained access controls
21

Typical Deployment Pattern For DataPower
External Internal Secured Enterprise Zone
DMZ
TCP/IP TCP/IP
Firewall Firewall
Malicious Message
TCP/IP DataPower
Broker Server
Malicious XML Firewall Application
XML SOAP/HTTP SOAP/HTTP
Decrypt / Route /
SOAP/HTTPS Encrypt Transform

Authorized
Client
Application

A requesting application communicates to DataPower using SOAP over
HTTPS with the message body encrypted using WS-Security
The DataPower appliance decrypts the body of the message and this
content is then passed to WebSphere Message Broker
Message Broker receives the SOAP message and transforms it and routes it
to the final application
22 05 Build A Flexible Application Infrastructure Environment - Connectivity
22

ESB Performance Is An Important Consideration

We offer the fastest ESB in the
industry. This allows you to
We process a lot of process more payments on the
payments every hour. same hardware compared to
How well does your ESB other ESB offerings.
perform?

CIO
23

High performance
Transactional
24

DEMO: WebSphere Message Broker vs. Oracle
Service Bus And Microsoft BizTalk Performance
WebSphere Message Broker
Content XML
Based Transform
Routing

Microsoft BizTalk Receive
Content Messages
Send XML
and Record
Based Transform
Messages Routing Elapsed Time

Oracle Service Bus
Content
XML
Based
Transform
Routing

Send 100 messages to ESB
ESB routes and transforms messages
Receiver displays elapsed time for 100 messages

25

A Transactional ESB Connection Assures Data
Integrity

Our ESB can execute mediation
Our payments are logged flows as distributed
for audit purposes. transactions. This assures data
integrity.
Our logs must be accurate!

CIO
26

High performance
Transactional
27

Transactional ESB Mediation Flow Assures
Data Integrity


Roll back transaction if
Log Update Send to
Payment to Audit Payment
delivery to gateway fails
Payment
Application DB DB Gateway

Prepare
to commit
Log
Database
Payment
Database X
SWIFT
Network error

Gateway

All updates are either committed or rolled back within a single transaction
Including database and messaging operations
Oracle Service Bus transactional scope excludes many end points
Microsoft BizTalk transactional scope does not include any end points
28

DEMO: IBM Transactional Mediation Flow With
Network Failure
WebSphere MQ is the transaction coordinator
Databases are updated using the two-phase commit protocol

Mediation Flow
Submit
Error
order
Returned
application
WebSphere
Message
WebSphere MQ Broker

Database
Network
Database
Data always consistent failure
Recovery is possible
Problem is logged Table Table Table Table
1 2 1 2

DB2 Oracle
IBM maintains data consistency
29

DEMO: Microsoft Transactional Mediation Flow
With Network Failure
BizTalk’s Atomic Transaction support refers to update of its internal message database
Downstream messages are sent asynchronously, with no follow up tracking or recovery

Container
Mediation Flow
Submit
Order
order
submitted
application
BizTalk
Atomic Transaction Manager Server
Transaction
BizTalk Message Database

Database
Network
Database
Data inconsistent failure
No follow up recovery
No indication of problem Table Table Table Table
1 2 1 2
Flow instance is lost
DB2 Oracle
Microsoft fails to maintain data consistency
30

Service Lookups Ensure Resilient Operation

Our payments network Our ESB can dynamically route
must have resiliency in the payments based on information
event of service outages. about each end point.

CIO
31

High performance
Transactional
32

Service Lookup Dynamically Routes Messages
To Registered End Point Services
Route payment to best payment gateway receiver
Receiver 1
IBM Enterprise Service Bus

Payment Payment
Sender = $75.34 Service
= $75.34
Receiver 2
Lookup

Query: $75.34 Return: address of best
Receiver service (Receiver 2)

Lookup best Receiver
SOA Service service for payment
Registry amount

Payments are not routed to fixed end point destinations
ESB dynamically selects the best end point service by comparing
message content with information about registered end point services
Fewer mediation design changes are needed as end points change
33

WebSphere Service Registry And Repository
(WSRR) Is The IBM SOA Registry
WSRR provides five capabilities for managing your end point services

Find services
based on
search
Publish criteria Enables
completed selection of
services to a services based
common on service
registry metadata

Service Govern
classification transitions in
and service life
versioning cycle
34

IBM Enterprise Service Bus Integrates With
WebSphere Service Registry And Repository
Design Time
Find published end point services in WSRR
− Search WSRR from within ESB design tool
− Import service documents (WSDL, XSD, etc.) into design tool
Publish ESB mediations as services to WSRR
Run Time
Connection from ESB run time engine to WSRR
Lookup information about an individual end point service
Query service metadata for all matching end point services
Receives end point information for matching services
Query results can be cached for higher throughput
Oracle Service Bus and Oracle Service Registry are not integrated at
run time
Microsoft BizTalk does not integrate with any UDDI registry at run time

35

DEMO: Dynamic, Flexible Routing And
Transformation Of Payments Using Service Lookup
Original payment message Original
WebSphere Message
MQ Payment (XML Format)
IBM Enterprise Service Bus
Application
SWIFT
SWIFT
SWIFT Transform from
XML MQ
Payment
Service XML to SWIFT MQ
Gateway
Service Call
Lookup Service
ACH ACH
XML SOAP/HTTP ACH Transform from
Service XML to ACH
Payment
MQ
Gateway
Web Service
Payment
Application

WSRR
Payments are dynamically routed to end point services by comparing payment amount to
payment limits stored in WSRR service metadata
Transformation from XML to SWIFT and ACH formats using WebSphere TX maps
Payments are processed exactly the same for both a WebSphere MQ payment application
and web service payment application
36

Adding Or Removing An End Point Requires
Minimal Changes
Example: Add a SEPA payment gateway end point
WebSphere
MQ Payment
IBM Enterprise SWIFT
Application SWIFT Transform from SWIFT
Payment
Service Bus Service XML to SWIFT MQ
Gateway
XML MQ

Service Call ACH ACH
ACH Transform from
Lookup Service Service XML to ACH
Payment
MQ
Gateway
XML SOAP/HTTP
SEPA SEPA
SEPA Transform from
Web Service Service XML to SEPA
Payment
Payment MQ
Gateway
Application

Create SEPA end point
WSRR Register SEPA end service
point service
Adding an end point only requires a new end point service and registry
change. No code or design changes
Removing an end point requires no code or design changes
Neither Microsoft norA OracleInfrastructure Environment - Connectivity service lookup
05 Build Flexible Application
have dynamic
37

Integration With Service Monitoring Assures
That Only Responsive End Points Are Called
Example: Multiple SWIFT payment gateway end points

SWIFT
SWIFT
IBM Enterprise SWIFT Transform from
Payment
Service Bus Service 1 XML to SWIFT MQ
Gateway 1

Service SWIFT
Call SWIFT Transform from SWIFT
Lookup Payment
Service Service 2 XML to SWIFT MQ
Gateway 2

SWIFT
SWIFT
SWIFT Transform from
XML to SWIFT
Payment
Service 3 MQ
Gateway 3

Response
Time Alerts ITCAM for Monitors end point
WSRR SOA service performance

Service Lookup only returns responsive end point services
Can use other WSRR service metadata to select from multiple returns
Oracle and Microsoft do not have monitoring integration with ESB
38

Use Response Time Alert Information In WSRR
To Improve Throughput

Response Time Alert
End Point Priority Service Lookup
Information in WSRR

SWIFT
Response Time Critical
1 Not Returned
Service 1 15.87 sec. response time

SWIFT
Service 2
None 2 Returned

SWIFT None
Service 3
3 Returned

Only SWIFT Service 2 and SWIFT Service 3 end point services
are returned
Mediation flow design can then select which end point service
to call
Example: select end point with highest priority
39

DEMO: Service Lookup Based On Response
Time Alerts

Route payments only to end point services without
response time alerts from ITCAM for SOA monitoring
If multiple end point services are returned, select
service with highest priority (lowest priority number)
An end point can be added or deleted without changing
the ESB mediation flow design
40

IBM Provides Superior Connectivity Solutions
For Smarter Planet Solutions

Reach – Connect Anything to Everything #1
Best Performance

Best Transaction Integrity

Resiliency – Dynamic End Point Detection

41

Build a Flexible Payment Network

Empfohlen

Empfohlen

Weitere ähnliche Inhalte

Was ist angesagt?

Was ist angesagt? (19)

Ähnlich wie Build a Flexible Payment Network

Ähnlich wie Build a Flexible Payment Network (20)

Mehr von Carly Snodgrass

Mehr von Carly Snodgrass (6)

Kürzlich hochgeladen

Kürzlich hochgeladen (20)

Build a Flexible Payment Network