OFMP The Road To OSGi Eclipse Democamp Luxembour 2008

Loading...

Flash Player 9 (or above) is needed to view presentations.
We have detected that you do not have it on your computer. To install it, go here.

0 comments

Post a comment

    Post a comment
    Embed Video
    Edit your comment Cancel

    1 Favorite

    OFMP The Road To OSGi Eclipse Democamp Luxembour 2008 - Presentation Transcript

    1. OFMP: the road to OSGi Eclipse Democamp Luxembourg 2008 Frederic Conrotte Covariance Luxembourg
      • Middle Office Financial Market Platform in Kaupthing Bank Luxembourg started in April 2006
      • Eclipse RCP / J2EE based on JBoss
      • Prototype ready on October 2006
      • Implementation started on October 2006
      • First release on March 2007 for Forex Desk
      • Second release on February 2008 for Money Market Desk
      Main features STP Front Office to Back Office workflow Treasury Coverage (Forex and Money Market Desks) Spot, Forward, Swaps products supported Deal Monitor, Profit and Loss, Position Keeping services CLS compliancy On-Demand Reporting Project background
    2. Reuters Dealing Front Office Mid Office Back Office EBS Bloomberg Flat files manual entries [other systems] Middle Office Financial Market Application (Foreign Exchange / Money Market / Capital Market) Back Office System Front to Back Workflow
      • Eclipse RCP for client side
      • Eclipse Data Binding
      • Equinox runtime J2EE services based on Spring/Spring DM framework
      • Spring Security
      • Spring IDE
      • IBatis persistence framework
      • RCML ( www.rcml.net )
      • JUnit tests suites
      • Client notifications and STP workflow with JMS
      • BIRT Report Engine
      • Maven and m2eclipse
      • Eclipse AspectJ
      • Eclipse API Tooling
      Technology Behind
    3. TIG : Captures trades from Front Office platforms, BackOffice or any other input trade provider. CDG: Provides contextual data like various Market Data TOG: Send processed trades to BackOffice, Risk Management platforms or any other system. Global Architecture
    4. RCLM allows to express higher level DSL langages useful in several areas like testing, reports generation and UI databinding <doAuthenticateAs userName=&quot; fx -dealer&quot; /> <setBusinessDate date=&quot;03-09-2007 08:00&quot; init =&quot;true&quot; /> <addHoliday currency=&quot;USD&quot; date=&quot;10-09-2007&quot; /> <addHoliday currency=&quot;ISK&quot; date=&quot;13-09-2007&quot; /> <spotDeal id=&quot;spot01&quot;> <buySellIndicator value=&quot;BUY&quot; /><!-- BUY, SELL --> <negociatedPart currency=&quot;EUR&quot; amount=&quot;1000000.00&quot; /> <secondPart currency=&quot;USD&quot; amount=&quot;1350000.00&quot; /> <spotRate value=&quot;1.35&quot; /><!-- BigDecimal --> <rateDirection value=&quot;NORMAL&quot; /><!-- NORMAL, INVERSE --> <tradeDate value=&quot;03-09-2007&quot; /><!-- Date --> <valueDate value=&quot;05-09-2007&quot; /><!-- Date --> <counterpartyId value=&quot;9994&quot; /><!-- Integer --> <message><!-- String --> This is a test deal entered by RCML. </message> <source value=&quot;TOF&quot; /> </spotDeal> <assertFXSpotPosition portfolioURL=&quot;${fx_spot}&quot; currency=&quot;USD&quot; value=&quot;-1350000&quot; /> <assertFXSpotPosition portfolioURL=&quot;${fx_spot_sales}&quot; currency=&quot;USD&quot; value=&quot;-1350000&quot; /> <assertDealBook portfolioURL=&quot;${fx_spot}&quot; containDeals=&quot;spot01&quot; /> Rich Client Markup Language
    5. Old architecture 1 single EAR deployed on JBoss exposing several stateless EJBs using RMI Pros: - Standard JEE services provided by JBoss Cons: - Production Server restart required to update a single service - Services interdependency management issues due to growing codebase. - System tend to be synchronous From EAR to OSGi
    6. OSG – What?
      • OSGi™: „A dynamic module system for Java“
      OSGi Overview
    7. OSGi is …
      • … a module system for Java that allows the definition of …
        • Modules (called „bundles“),
        • Visibility of the bundle contents (public-API vs. private-API)
        • Dependencies between modules
        • Versions of modules
      OSGi Overview
      • … dynamic
        • Bundles can be installed, started, stopped, uninstalled and updated at runtime
      OSGi is … OSGi Overview
    8. OSGi is …
      • … service oriented
        • Bundles can publish services (dynamically)
        • Bundles can find and bind to services through a service registry
        • The runtime allows services to appear and disappear at runtime
      OSGi Overview
    9. What does OSGi look like? (Low Level) OSGi Overview
    10. New architecture Multiple OSGi bundles defining a single group of related services using Spring DM and exposing them thru Spring HTTPInvoker Pros: - True hot services upgrade - Services status management improved - Asynchronous communication/separation of concerns - Improve modules dependency design Cons: - OSGi is great, but tooling is not quite there yet:
        • JAR to OSGi bundle automated conversion using BND tool; Service querying, Runtime visualisation
      - Lack of properly OSGified JARs => Thanks SpringSource - Strict import/export versioning discipline required - Number of bundles quickly reach more than 100 or 200 => distributed runtimes coming in next OSGi spec 4.2 From EAR to OSGi
    11. Current Status
        • Maven External Dependencies management infrastructure
        • OSGi based standard JEE services
          • Datasources
          • Transaction Management
          • JMS
          • Logging
          • Security
        • Spring DM Integration Testing Framework
        • Currency bundle migrated including Unit and Integration Tests
        • Goal to release to full set of OSGified bundles by end of year
        • IP Issues
        • Move under umbrella of Eclipse Financial Project
    12. Future plan – Technical level
        • FPML (fpml.org) Data Structure
        • Replace iBatis with EclipseLink for modular persistency support
        • Asynchronous inter modules communication using Enterprise Integration Pattern solutions like Apache Camel
      • Asset/Liability Management (ALM)
      The ALM is a set of tools that allow to the bank management to: - Reach return’s objectives - Manage their liquidity risk - Manage their interest rate risk - Stress test their balance sheet - Meet Basle II requirement  Will become essential in banks regarding to the current events
      • T rader books, Limits management, Reports Set
      • Treasury products (TRS, currency options, IRS, ...)
      • Enhancement of Derivative products coverage :
      Swaps structures, CFDs, structured products Future plan – Business level
    13. More information
        • Website: http://www.eclipse.org/ofmp
        • Project wiki: http://wiki.eclipse.org/OFMP
        • Eclipse OFMP Newsgroup
      Demos
        • Foreign Exchange functionnalities
        • Portfolio Management functionnalities
      Contacts: [email_address] Credits: Martin Lippert, akquinet agile GmbH [email_address]

    + Frederic ConrotteFrederic Conrotte, 2 years ago

    custom

    831 views, 1 favs, 1 embeds more stats

    More info about this document

    © All Rights Reserved

    Go to text version

    • Total Views 831
      • 825 on SlideShare
      • 6 from embeds
    • Comments 0
    • Favorites 1
    • Downloads 13
    Most viewed embeds
    • 6 views on http://www.covariance.lu

    more

    All embeds
    • 6 views on http://www.covariance.lu

    less

    Flagged as inappropriate Flag as inappropriate
    Flag as inappropriate

    Select your reason for flagging this presentation as inappropriate. If needed, use the feedback form to let us know more details.

    Cancel
    File a copyright complaint
    Having problems? Go to our helpdesk?

    Categories