XML Messaging

1
XML Messaging

• Universal data Universal data interchange
• vs. Linear development
• Richard Campbell

2
Why is XML Messaging Important?

• Convergence replaces proprietary methods
• Similar to ethernet
• Similar to TCP/IP
• Commoditization
• Standardization
• Allows for application de-coupling

3
BackgroundTwo sides to XML technology

• Data
• XML is a universal data format
• Interchange of messages
• interchange is the logic and mechanism of
  moving data between applications and systems,
  both internal and external.
• XML is ideal for interchanging

4
XML Universal Data Interchange/Messaging

• Sounds Good
• But-
• we lack the mechanism(s) to do the interchange
• we lack the infrastructure to handle XML data
• some standards are lacking
• e.g. XP (XML Protocol)

5
Need to understand interchange

• Everything moved is a message
• Every message is interchanged
• What happens at an interchange?
• Transformations
• Data mapping
• Metadata lookups
• How do we do it now?
• Cement this logic into every system, i.e, linear
• Reinvent message formats

6
Sample XML
ltUpdategt ltCaseManagergtMr. Examinerlt/CaseManagergt
ltBankNamegtFirst Fishery Banklt/BankNamegt
ltURLgtwww.ffb.bizlt/URLgt ltEffDategtNovember 3,
2000lt/EffDategt ltBankOfficergtPresidentlt/BankOfficer
gt ltBankOfficerNamegt J. Tompkinslt/BankOfficerNamegt
lt/Updategt
7
Handling a Message
Someone sends an email Dear Mr. Johnson Please
update all FDIC records for First Fishery Bank to
reflect our new name and web address,
www.ffb.biz, effective November 3, 2000.
Sincerely, President Jill Tompkins Which could
actually look like the following ltUpdategt Dear
Mr. ltCaseManagergtJohnsonlt/CaseManagergt Please
update all FDIC records for ltBankNamegtFirst
Fishery Banklt/BankNamegt to reflect our new name
and web address ltURLgtwww.ffb.bizlt/URLgt, effective
ltEffDategtNovember 3, 2000lt/EffDategt. Sincerely,
ltBankOfficergtPresidentlt/BankOfficergtltBankAuthorize
dNamegt Jill Tompkinslt/BankAuthorizedNamegt lt/Update
gt Which could be transformed into this XML
document (or any other format) ltUpdategt ltCaseMana
gergtMr. Examinerlt/CaseManagergt ltBankNamegtFirst
Fishery Banklt/BankNamegt ltURLgtwww.ffb.bizlt/URLgt ltE
ffDategtNovember 3, 2000lt/EffDategt ltBankOfficergtPre
sidentlt/BankOfficergtltBankAuthorizedNamegt J.
Tompkinslt/BankAuthorizedNamegt lt/Updategt
8
Efforts to Date

• Reflect lack of interchange engine
• Forces others to adapt
• Examples
• Portal
• Vision
• FFIEC ReXML

9
Problems of Linear Development

• Difficult to cross applications
• Difficult to avoid linear design
• No means to deconstruct linear design
• Exchanging data means another linear link
• Reinventing data formats
• Data sharing between apps is not facilitated
• No infrastructure to leverage XML

10
Linear Design Spaghetti
11
XML Message Bus addresses the architecture
problems

• Is a multi-purpose engine for interchanging data,
  information and processes
• Facilitates cooperation, componentization
• By design, is bi-directional and
• one to one
• one to many
• many to one
• De-couples applications from the interchange,
  supports iterative development

12
Extend to any application
13
Goal of the Message Bus is to

• let any application talk to any other
• talk to any business partner
• facilitate non-linear development
• allow simultaneous data updates
• permit application replacement
• leverage efficiencies of components
• lower maintenance costs

14
How is this different from EAI?

• EAI is proprietary
• Middleware engine
• Connectors to applications are proprietary
• Proprietary messages
• Message Bus is open
• Messages and envelopes are open XML
• All applications can be connected
• The BUS is the common interface

15
The Envelope W3Cs XML Protocol(www.w3c.org/2000
/xp)

• The goal of XML Protocol is to develop
  technologies which allow two or more peers to
  communicate in a distributed environment, using
  XML as its encapsulation language. Solutions
  developed by this activity allow a layered
  architecture on top of an extensible and simple
  messaging format, which provides robustness,
  simplicity, reusability and interoperability.
• The initial focus of theXML Protocol Working
  Group is to develop a framework for XML-based
  messaging systems, which includes specifying a
  message envelope format and a method for data
  serialization, directed mainly, but not
  exclusively, to RPC applications, and conforming
  with the above mentioned principles. More
  specifics are available from the Charter.

16
Next Steps

• Build recognition of XML MB technology
• Evaluate existing messaging applications
• ETV, EPRIS
• Evaluate data interchange efforts
• MAAP, Platinum Repository
• Evaluate future messaging applications
• CALL, E-Invoices, FDICConnect, Corporate Data
  Sharing
• Develop POC or Pilot to address these, show data
  applications flexibility with XML MB