Published on

  • Be the first to comment

  • Be the first to like this

No Downloads
Total views
On SlideShare
From Embeds
Number of Embeds
Embeds 0
No embeds

No notes for slide


  1. 1. Agenda • About Us • Reasons to Consider JBoss Implementing an Open Source SOA • Share our experience and challenges Migrating to JBoss Operations with JBoss ON A JBoss Success Story Implementing an Open Source SOA Bruno Georges, Glencore International AG • Next Steps • Key Messages © JBoss Inc. 2006 2 About Us Application Landscape • Founded in 1984 • Client Server • One of the biggest Accounting/Finance privately owned commodity trading Traffic and Physical Operations companies in the • Web Applications world IT Governance • US$ 91.0 billion turnover in 2005 Price Feeds • 2000 employees New Trading Applications worldwide • J2EE Based Service Architecture • 50 offices in 40 Core Business Services countries Infrastructure Services 3 4 Physical Architecture Layout Implementing JBoss primary node secondary node Sun T-2000 (4 CPU, 16GB RAM) Sun T-2000 (4 CPU, 16GB RAM) Zone 1 Zone 2 Zone 1 Zone 2 HOT COLD COLD HOT How did we get there? Solaris 10 Solaris 10 Solaris 10 Solaris 10 Sun E20K Sun E20K RAID RAID Disks Disks Redundant Fibre Optic Link 4GB/sec 5 6 1
  2. 2. Reasons to consider JBoss Reasons to consider JBoss • SOA Workshop • Support Global Commitment to investigate open Need for responsiveness source alternatives Network of certified partners • Business Context • Development Licensing / Total Cost of Ownership Strong preference for Open Source Promoting SOA to other sites optimizing Relies on externals rather than internals costs Complexity and dependence on Time to Market infrastructure code Training 7 8 Migrating to JBoss Communicating the changes • Migration Project initiated • Who likes changes? • Phased Approach Communicate vision and direction Conduct Initial Assessment • Buy-in Build a Team Inform and promote Prepare Planning and scoping Education and Training Decision – Go / No Go • Transparency Migrate Communicate clearly and regularly • Collaboration Build a TEAM 9 10 Open Source SOA Moving Towards Services Open Source SOA – Where did we start? 11 12 2
  3. 3. Moving Towards Services Moving Towards Services Services Service 1 Service 2 Service 3 Console B2B Business Level Processes - Reusable enterprise processes Integration - Asynchronous, Stateful in many cases - Business level logging (auditing) and exception management Business Integration Defined API Defined API Technical Processes Technical - Data synchronisation and read oriented processes Integration - One back end system involved - Synchronous or Asynchronous. Primarily Stateless - Technical logging and exception management Connector 1 Connector 2 Connector 3 Connector 4 Connector 5 JMS JCA XML/HTTP Web Services EJB EIS SYSTEM 1 SYSTEM 2 SYSTEM 3 SYSTEM 4 SYSTEM 5 13 14 Roles & Responsibilities JBoss Integration • Business Integration Architect • Technical Integration Developer • Additional roles, to support the successful deployment and operation: How did we integrate our SOA? Project Management Build Management and Deployment Testing Operations Support 15 16 Integration Requirements Integration – How ? • Decouple Services from consuming Business MSG MSG Integration Layer Enrichment Transformation applications Application MSG Orchestration • Fast transformation and orchestration biz evt • Transactional, Resilient and Robust int api • Common network infrastructure Service Layer • Common standards such as XML and Trade SOAP to aid reuse Accounting Treasury Market Data EIS Accounting Finance Trading &Traffic Rate System System System Feed 17 18 3
  4. 4. Promoting Reuse Integration Patterns Pub/Sub Publish/Subscribe - Loosely coupled integration PROCESS Service - Coarse grained messages - Event based - Enterprise Data Synchronisation Integration • Message Broker Trading App Technology choices: Layer - XML/JMS • Integration Patterns System - Message Broker B • Exception Management Asynchronous Request/Reply Asynchronous Request/Reply - Loosely coupled integration - Coarse grained messages REUSE Trading App Integration - Message correlation - Inter system conversation Service Layer Technology choices: CONNECTIVITY - XML/JMS DATA - Message Broker • Standards based Synchronous Request/Reply Synchronous Request/Reply - Low latency requirements • Enterprise Data Model • Off the shelf adapters - More tightly coupled integration - Fine grained messages • Fine and coarse Integration - Portal oriented use cases • Referencing and Mapping Web App Trading App Layer grained interfaces Technology choices: - SOAP/HTTP (Web Services) - EJB (JCA Application View) 19 20 Process Management with jBPM Transaction with JBoss TS primary node secondary node • jBPM business analyst In the integration R Zone 1 Zone 2 R Zone 1 Zone 2 layer for Process e q Forex App + Forex App + Rate Feed + Rate Feed + e q Forex App + Forex App + Rate Feed + Rate Feed + Flow Orchestration. u e Services Services Services Services u es Services Services Services Services Best of breed st ts s solution for both developer Integration + Integration + Trade App Trade App Integration + Integration + Trade App Trade App Services Services + + Services Services + + Developer and Services Services Services Services Analyst. <process-definition Fast Iteration name=“booking-request"> HOT COLD COLD HOT Lightweight .. <start-state name="start"> Communicate on a <end-state name="success“/> level of the picture </process-definition> between the developer and the business Transaction log Replication analyst = JMS Provider 21 22 JBoss Components Development Framework Business/Client Integration Layer Services EIS Application Apache Tomcat JBoss jBPM Hibernate JBoss Transaction JBoss Application Server JBoss Operation Network 23 24 4
  5. 5. Measuring success and ROI Next Steps • Investment in Quality and Staff • Architecture Development not in Licenses Integration Standards. JBI? • Changes are not only in the binaries, JBoss ESB they are reflected at every layer of • Application Development the IT organization EJB3 • Faster delivery cycle AOP • Increase response time • Operations with JBoss ON Monitoring Provisioning 25 26 Key Messages Questions? • Build on existing assets and common network infrastructure Use of Standards to leverage existing application logic to remote process/clients • Flexibility to orchestrate composite applications across the enterprise Choose the right BPM for your needs • Challenges are not only technical The success of an SOA relies on the Enterprise to agree on a set of common, corporate wide business processes, rules and logic • Keep It Simple and Standard 27 28 5