This document discusses how Barclaycard uses WSO2's open source middleware to power its enterprise by integrating numerous internal and external systems through messaging and APIs. It describes how Barclaycard leverages various WSO2 components like the ESB, Governance Server, and Business Activity Manager for use cases including integrating prepaid platforms, core domain services, and account aggregators. Over 2 billion requests are sent monthly to their backend provider, TSYS, demonstrating the large scale of their integrations.

1. Powering
an
Enterprise
with
Messaging
and
APIs
Alexander
Brown
Barclaycard
Group
Lead

2. BarclaycardUS Introduction
• US
Credit
card
division
of
Barclays
PLC
• Issues
primarily
branded
accounts
for
partners
including
Apple,
LL
Bean
and
USAirways
• 7th
largest
issuer
of
credit
cards
in
US.
• $15b+
outstanding
loans
• 8.5m+
accounts
• IntegraLons
with
• Numerous
Vendors
(Credit
checks,
rewards,
fulfillment
etc.)
• Partners
(LL
Bean
Apple
etc)
• Banking
PlaSorms
(TSYS)

3. Middleware Integrations
• Customer
Website
-­‐
Java
interfacing
with
SOAP
services
• Mobile
-­‐
Android/IOS
interfaces
using
REST
• IVR
-­‐
Avaya
interfacing
with
Voice
XML
• Customer
Care
-­‐
C#
applicaLon
using
SOAP
web
services
• BPM
-­‐
Metastorm/IBM
leveraging
SOAP
web
services
• 60+
Partners
-­‐
Many
of
whom
use
web
service
of
different
types
• Account
Aggregators
-­‐
ULlize
OFX
interface
to
pull
customer
account
data
at
their
request
(mint.com
etc)
• 10+
Vendor
-­‐
Using
web
service
of
different
types
• We
perform
over
2b
requests
to
our
backend
provider
TSYS
monthly

4. Competitors
Open
Source
• MuleESB
• Spring
IntegraLon
• Apache
Camel
• ServiceMix
Commercial
• ProgressESB
• AquaLogic
• IBM
Process
Server

5. Why WSO2
• Open
Source
• Inexpensive
(ComparaLvely)
• Ability
to
extend,
insight
into
source
code
• Not
Led
to
vendor
for
any
and
all
extensions
to
product
• Complete
SOA
PlaBorm
• ESB
• Governance
• IdenLty
Management
• Monitoring
• Follows
the
Enterprise
IntegraLon
Pacerns
(EIP)
and
encourages
ESB
best
pracLces.

6. Leveraged WSO2 Components
Enterprise
Service
Bus
(ESB)
• Proxies
to
exisLng
services
• TransformaLons
between
APIs
• Security
Policies
• APIs
(REST<-­‐>SOAP)
• Load
Balancing
(Service
Providers)
Governance
Server
• Manage
APIs
• Manage
API
promoLon
(Future)
Business
AcLvity
Manager
• View
service
acLvity

7. Use
Cases
• Prepaid Platform
•
Integrate with three vendors via REST/SOAP using security
•
Mobile device integration (REST/JSON)
•
Client/Server transport security
• Core Domain Services (In Progress)
•
Integrate with backend processor TSYS with SOAP over MQ
•
Integrate with Spring-WS/Hibernate data services
•
Begin façade of all existing services to standardize security and service headers.
• Account Aggregators (In Progress)
•
Provide OFX customer financial data to extremely high volume aggregators like Intuit/Yodlee.
•
Extensive use of throttling and Clone/Aggregation

8. Prepaid
PlaSorm
• Supports
balance
inquiry
and
mobile
apply/originaLon
• Mobile
bill
payment
plaSorm
leveraging
external
prepaid
vendor
• Mobile
(REST/JSON)
to
ESB
• IntegraLon
into
IBM
BPM
(SOAP)
for
tracking
originaLon
progress,
process
restarts
• IntegraLon
mulLple
backend
service
providers
with
SOAP
(WS-­‐
Security)
and
REST

9. Core
Domain
Services
• Services
exist
in
the
following
forms
“Legacy”
Services
(J2EE/EJB/PL-­‐SQL/Weblogic)
Newer
Spring-­‐WS/Hibernate
based
services
.NET
Services
• Services
source
data
from
MulLple
Oracle
Databases
MulLple
Vendors
(SOAP/XML/REST)
• High
volume
of
calls
(100m
daily
target)
• ULlize
WS-­‐Security,
Canonical
Data
Model

10. TSYS
“XMLM”
Packets
(Per
Month)
Single
vendor,
less
than
half
of
total
traffic
to
vendor

11. Account
Aggregators
• Aggregators
peak
at
over
500
screen
website
logins
per
minute
(Screen
Scraping)
• Convert
core
SOAP
services
to
OFX
protocol
• ULlize
throcling
to
limit
peak
volume
on
core
services
• Extensively
uLlizes
clone/
aggregaLon
for
concurrent
execuLon
of
service
calls
to
achieve
speedy
responses
• Goes
live
by
end
of
year

12. ESB
IntegraLon
Plan

13. Future
• Complete
Ongoing
Projects
• Further
enhance
exisLng
services
and
further
use
of
composite
services
• IntegraLon
of
IdenLty
Server
OAuth
for
RESTful
services
• API
Manager
PotenLally
use
of
the
API
Manager
to
gain
insight
into
metering
and
monitoring
of
different
service
consumers.
This
product
does
not
yet
support
WS-­‐Security
based
monitoring
so
it
cannot
current
be
leveraged.