XML Messaging

Document Sample
XML Messaging Powered By Docstoc
					                XML Messaging
            Universal data & Universal data
                      interchange
               vs. Linear development

                  Richard Campbell


3/25/2010           Research & Development Section
            Why is XML Messaging
                  Important?
• Convergence: replaces proprietary methods
     – Similar to ethernet
     – Similar to TCP/IP
• Commoditization
• Standardization
• Allows for application de-coupling


3/25/2010           Research & Development Section
            Background:
    Two 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

3/25/2010          Research & Development Section
               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)



3/25/2010               Research & Development Section
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

3/25/2010                 Research & Development Section
             Sample XML
<Update>
<CaseManager>Mr. Examiner</CaseManager>
<BankName>First Fishery Bank</BankName>
<URL>www.ffb.biz</URL>
<EffDate>November 3, 2000</EffDate>
<BankOfficer>President</BankOfficer>
<BankOfficerName> J.
Tompkins</BankOfficerName>
</Update>

3/25/2010      Research & Development Section
                      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
<Update>
Dear Mr. <CaseManager>Johnson</CaseManager>
Please update all FDIC records for <BankName>First Fishery Bank</BankName> to reflect our new name
and web address <URL>www.ffb.biz</URL>, effective <EffDate>November 3, 2000</EffDate>. Sincerely,
<BankOfficer>President</BankOfficer><BankAuthorizedName> Jill Tompkins</BankAuthorizedName>
</Update>


Which could be transformed into this XML document (or any other format):
<Update>
<CaseManager>Mr. Examiner</CaseManager>
<BankName>First Fishery Bank</BankName>
<URL>www.ffb.biz</URL>
<EffDate>November 3, 2000</EffDate>
<BankOfficer>President</BankOfficer><BankAuthorizedName> J. Tompkins</BankAuthorizedName>
</Update>
  3/25/2010                          Research & Development Section
                Efforts to Date
• Reflect lack of interchange engine
     – Forces others to adapt
• Examples
     – Portal
     – Vision
     – FFIEC ReXML


3/25/2010          Research & Development Section
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

3/25/2010         Research & Development Section
            Linear Design = Spaghetti




3/25/2010          Research & Development Section
      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
 3/25/2010          Research & Development Section
                 Extend to any application
                           XML                   Case
                           EDI                  Manager
             Call
                                                            Portal
            Report




                        Equal Access to XML Messages
                                                            Bank
   Exam
                                                          Regulatory
  Reports            <BankName>FirstFishery</BankName>
                                                          Agencies
                          <SSN>222-33-1111</SSN>




       Regulatory
       Databases                                            Travel
                                                 FDIC
                        Statistics               WWW
                                                 Page
3/25/2010                Research & Development Section
    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
3/25/2010         Research & Development Section
  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
3/25/2010          Research & Development Section
    The Envelope: W3C’s 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.

3/25/2010                Research & Development Section
                  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
 3/25/2010        Research & Development Section