Your SlideShare is downloading. ×
0
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
LiquidHub - IBM Service Oriented Architecture Presentation 06 ...
Upcoming SlideShare
Loading in...5
×

Thanks for flagging this SlideShare!

Oops! An error has occurred.

×
Saving this for later? Get the SlideShare app to save on your phone or tablet. Read anywhere, anytime – even offline.
Text the download link to your phone
Standard text messaging rates apply

LiquidHub - IBM Service Oriented Architecture Presentation 06 ...

1,580

Published on

Published in: Technology
0 Comments
0 Likes
Statistics
Notes
  • Be the first to comment

  • Be the first to like this

No Downloads
Views
Total Views
1,580
On Slideshare
0
From Embeds
0
Number of Embeds
3
Actions
Shares
0
Downloads
93
Comments
0
Likes
0
Embeds 0
No embeds

Report content
Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
No notes for slide

Transcript

  1. our business revolves around you Service Oriented Architecture: Building your Web Services and SOA Roadmap Tuesday, June 29th 2004
  2. Topics of Discussion 2 Understanding Services Oriented Architectures The Business Case for a Service Oriented Architecture Web Services a Foundation Technology for SOA The Impact of SOA on Enterprise Architecture Getting Started About LiquidHub
  3. our business revolves around you Understanding Service Oriented Architectures How SOA Works Back to the Future: Best in Class SOA Roadmap Planning
  4. Setting the Stage for SOA 4 Service-Oriented A set of design and organizational principles that guide companies around the corner to Service Orientation, a Architecture (SOA) roadmap to achieving the vision of business driving IT. An approach to information technology that considers IT resources as being available and discoverable as Service Orientation location-independent Services on the network, providing a layer of abstraction that masks the complexity of the technical implementations. The key enabling technologies that underlie SOAs, XML and representing both extensible formats for data and Web Services content as well as standards-based approaches to distributed computing. Source: ZapThink
  5. What makes up SOA? 5 Treating applications and processes as defined components that can be mixed and matched at will Supports a federated approach to governance Allows smaller, incremental projects Supports business flexibility and optimized IT infrastructure Characteristics: Loosely coupled Reduced interdependency between software assets Shared services Allows individual software assets to become building blocks that can be reused in developing other applications (application assembly) Federated control Federated and policy based security, management and deployment Standards based Leverages open standards to represent software assets as services (XML, SOAP, WSDL, UDDI, …) Source: IBM
  6. How Does SOA Work? 6 In a Service Oriented Architecture – SOAs build on previous 3-tier architectures to become more flexible, less redundant – The services then provide black-box functionality for business processes with location transparency – Location transparency provides the window of opportunity to incrementally sunset legacy applications and/or to access 3rd party services Typical 3 tier application Client Business Objects Data / Persistence Client Comparable Service Oriented Implementation Client Business Objects Data / Persistence Business In House Systems Client Services Client Business Objects Data / Persistence 3rd Party or Business Partner Client Systems Source: Adapted from Microsoft
  7. our business revolves around you The Business Case for a Service Oriented Architecture IT Economics and Portfolio Management Why Consider SOA?
  8. IT Economics and Portfolio Management: 8 The Potential Value of SOA 20% New Projects Organizations spent 80% (or 20% For Business Process Improvement more) of their IT budgets on Maintenance, Stability, Support 80% Maintenance, Operational Stability & and Operations, with only 20% 80% Support remaining for New Development Initiatives. If you could improve re-usability 50% New Projects for to leverage key IT assets more 50% Business Process Improvement & Value Add effectively and reducing impact of change impact, you would free 50% Maintenance, Operational Stability & 30% of your expenditure for new 50% Support projects or savings back to the business. Source: Adapted from James Martin
  9. Why Consider a Service Oriented Architecture? 9 Define business rationale, not technical features Focus on the Find a pragmatic balance between technical rigor and time- Business to-market Value ongoing flexibility and agility over a one-time efficiency gain With a little planning, you can get immediate return for each service you build via the “Network Effect” Increase ROI And you can get increasing return as your architecture – and that of your customers, suppliers, and partners – evolves to SOA
  10. Why Consider a Service Oriented Architecture? 10 SOA is about reuse of existing assets: Legacy, Client Server, and Web Reuse You can “wrap” existing applications, re-using existing functionality of legacy systems to increase their reach and longevity And build new services on any and multiple supported platforms Invest in a diversified portfolio of applications, not a single packaged application or a technology platform Achieve Applications are less fragile, more adaptive to Rapidly Changing Flexibility Business Requirements Facilitate standards based integration with trusted business partners (B2B) Ease integration needs necessitated by M&A activity Future-Proof Complexity is encapsulated Your Code is mobile Enterprise Enhancements and changes can be added incrementally without a negative ripple effect across the application infrastructure
  11. our business revolves around you Web Services: A Technology Foundation for SOA What Are Web Services? Why Web Services as Part of an SOA? Web Services Examples
  12. What are Web Services? 12 Web Services are software components that are loosely coupled and distributed, encapsulate business functionality and are programmatically accessible using standard Internet protocols Technically, Web Services are a stack of emerging standards that describe a service oriented, component-based application architecture, enabling SOA in an enterprise Web Services Telephone 1 2 3 4 5 6 7 8 9 * 8 # Network
  13. Why Web Services as Part of SOA? 13 Based on ubiquitous Industry Standard Protocols with universal support Leverage the internet for low cost Additional Standards WSXL communications Deliver platform and technology Business Process Execution independence BPEL4WS, WFML, WSFL, BizTalk, etc. Loosely Coupled Services Publishing & Discovery – Migration from direct calls to architectural Universal Description, Discovery & Integration (UDDI) service reduces dependency on specific applications and packages Services Description Web Services Description Language (WSDL) – Supporting multiple application connection and information sharing scenarios Services Communication Fosters re-use through publication Simple Object Access Protocol (SOAP) of interfaces Meta Language – Services are self describing eXtensible Markup Language (XML) – Reduces the time for developers to properly understand the interface Network Transport Protocols TCP/IP, HTTP, SMTP, FTP, etc. – Richer specification of the service can be accessed programmatically – Reduces the impact of change by providing dynamic service consumption Source: CBDI
  14. Example of a Service Oriented Architecture 14 Discoverable Services Specific Web Services Abstract Business Online Store Services Business Objects Book Client Book Store Order Service Order Detail Business objects represent binary and legacy assets (pre-web services) Specific web services wrap binary objects and legacy API adapters with XML/SOAP to achieve greater re-usability and heterogeneous interoperability Abstract business services aggregate multiple web services in the orchestration of real business operational workflow through: – Business Process Mapping Discoverable Services… – Data Transformation (XSLT) • Are URLs for Applications that can be redirected • Can be modified to add new attributes and – Transactional Routing methods without ripple effect on existing applications • Allow you to add new “Presentation Services” more rapidly
  15. our business revolves around you The Impact of SOA on Enterprise Architecture Organizational Perspectives that Influence EA Strategic and Shared Service Impacts on EA Infrastructure/Security Impacts on EA
  16. What is Enterprise Architecture Planning? 16 Current State Results es cipl High Complexity Prin s ces High Cost Pr o le & e op Platform P Project Portfolio Future State People & Principles Process Managed Complexity Managed Cost Platform Increased Business Value
  17. Enterprise Architecture and SOA 17 Organizations believe that Enterprise Architecture can help improve: – The Business/IT alignment gap – IT Project success rate – Business and technology communication Organizations believe that Enterprise Architecture benefits are: – Cost reduction & technology standardization – Process improvements – Strategic differentiation SOA approaches espoused by tool and product vendors provide the opportunity for organizations: – To re-think their approach to architecture – To enable real portfolio planning for technology-enabled enterprise business processes.
  18. SOA Enterprise Architecture Principles 18 Shift from monolithic applications ENTERPRISE ARCHITECTURE to application services Business Architecture – Client Applications role shifts Governance & Management to presentation for managing and submitting requests Technology Architecture Business Applications Identify discrete business functions within applications and separate Shared Services them to application services – Separation allows alternate business workflows to co-exist – Separation of application from business logic allows more responsive change to processes – Service transparency is a key attribute given a ever-changing enterprise architecture Application Services call other infrastructure services as necessary
  19. SOA and Enterprise Architecture 19 Shared Services: a breakdown of services to support enterprise applications – Application Presentation Services – Enterprise Application Services – Data Services – Enterprise Platforms & Integration Services – Application Infrastructure Services – Network Infrastructure Services ENTERPRISE ARCHITECTURE Business Architecture Governance & Management Value Chain Business Process Relationship Product/ Service Structure Structure Structure Structure Enterprise Portfolio Structure Technology Architecture Business Applications Corporate Vertical Architectural SRM ERP CRM Applications Applications Principles and Standards Shared Services Vendor and SLA Enterprise Presentation Enterprise Application Data Structure Services Services Services Enterprise Platforms & Integration Services Application Infrastructure Services Resource Structure Network Infrastructure Services
  20. SOA: Perspectives that Influence Enterprise Architecture 20 Each perspective needs to be considered in order to optimize current IT investments and ensure future investments are aligned with business goals and objectives ENTERPRISEARCH ECTU IT RE B ess A itecture usin rch Governance & B usiness P uct/ rod M anagem t en Value Chain Relationship P rocess Service All four perspectives must be Structure Structure Structure Structure Ente rise rp Portfolio S tructure Techn ology Architecture Bu ess A sin pplications SM R ERP C orate orp A plications p CM R Vertical A lications pp A P rchitectura rinciples a Standards l nd considered to create a single cohesive Enterprise Architecture SharedServices Enterp P ntation rise rese Enterprise Application Vend and or Data Se rvices SLAStructure Services Services view Enterp Platform &Integ tionS rise s ra ervices Resource Ap p licationInfrastructure Services Structure N orkInfrastructure S etw ervices Benefits are – Reduced complexity – Time to market – Increased flexibility – Lower cost! Source: Adapted from Marks/Warrell
  21. Business Perspective 21 Business architecture define business rules to determine which service requests are handled by which Application Services. Business Applications rely on Application Services to provide the core functionality. During Business Process modeling analysts discover Application services and determine which object should be invoked for a given business need. ENTERPRISE ARCHITECTURE Business Architecture Governance & Business Business Product/ Management Value Chain Relationship Structure Process Process Structure Service Structure Structure Structure Enterprise Portfolio Structure Technology Architecture Business Applications Corporate Vertical Architectural SRM ERP Applications CRM Applications Principles and Standards Shared Services Vendor and Enterprise Presentation Enterprise Application Data SLA Structure Services Services Services Enterprise Platforms & Integration Services Resource Application Infrastructure Services Structure Network Infrastructure Services
  22. Applications Perspective 22 Groups of services are differentiated to define which services implement an appropriate interface. Services must implement all the methods that an object may expect to call. Business logic and infrastructure services are also isolated and infrastructure services are exposed as separate services. Application Developers design applications to request services. Component developers focus on design of services to that consume and fulfill requests. ENTERPRISE ARCHITECTURE Business Architecture Governance & Business Product/ Management Value Chain Relationship Process Service Structure Structure Structure Structure Enterprise Portfolio Structure Technology Architecture Business Applications Corporate Vertical Architectural SRM ERP CRM Applications Applications Principles and Standards Shared Services Vendor and Enterprise Presentation Enterprise Application Data SLA Structure Services Services Services Enterprise Platforms & Integration Services Resource Application Infrastructure Services Structure Network Infrastructure Services
  23. Infrastructure Perspective 23 ENTERPRISE ARCHITECTURE Business Architecture Business Product/ Governance & Management Network infrastructure supporting HTML/XML Value Chain Relationship Process Service Structure Structure Structure Structure Enterprise Technology Architecture Portfolio Structure already in place, but . . . Security standards are Business Applications Corporate Vertical Architectural SRM ERP CRM evolving, so security must be Applications Applications Principles and Standards Shared Services Vendor and a design consideration. Enterprise Presentation Enterprise Application Data SLA Structure Services Services Services Enterprise Platforms & Integration Services Resource Application Infrastructure Services Structure Network Infrastructure Services Source: Reactivity
  24. Information Perspective 24 Information is now more highly visible. – Federated data model allows just-in-time information joining – Business Intelligence Data Store loads can be transactional – Operational and reporting ENTERPRISE ARCHITECTURE data can coexist in the channel Business Architecture Governance & Business Product/ Management Value Chain Relationship – Analytical data/Dashboards Structure Process Structure Structure Service Structure are more easily assembled Enterprise Portfolio directly from key services Technology Architecture Structure with real time data Business Applications Corporate Vertical Architectural SRM ERP CRM Applications Applications Principles and Standards Shared Services Vendor and Enterprise Presentation Enterprise Application Data SLA Structure Services Services Services Enterprise Platforms & Integration Services Resource Application Infrastructure Services Structure Network Infrastructure Services
  25. our business revolves around you Getting Started A Study in Implementation Tactical Bottom-up Approaches Strategic Top-Down Approaches
  26. A Study in Implementation of an SOA 26 A well-known financial business – Required 30 systems and 300,000 lines of Cobol and C code to make an address change for a customer – The firm applied SOA to that one problem and reduced the lines of code to 20,000 – In addition, rather than taking 24 hours to update all 30 systems, it now takes no more than 35 seconds
  27. A Tactical Bottom-up Approach SOA Migration Strategy 27 The Layered Scope Model (LSM) Progressing through the ROI of SOA and SOS layers, builds an increasingly increases as you broader SOA broaden scope SOA SOA and SOS (Service Oriented SOS Security) standards are established incrementally Beyond the intrinsic layer is the building Each layer is a block for the logical architecture standardized SOS boundary model Source: Thomas Erl
  28. Steps in Applying a Tactical Bottom-up Approach 28 – Use a high business value application such as a Legacy Mainframe system, ERP or CRM and identify the data and processes that should be shared and common across the enterprise. – Separate the potential shared data/methods and expose them as Web Services. – Implementation steps: 1. Create XML/Web Service standards within one architecture boundary 2. Determine which Data/Methods to expose outside of the intrinsic application 3. Perform impact analysis to assess the cost, effort and impact to the existing technical environment 4. Publish standards and guidelines by incorporation any existing standards. This will establish re-usable application logic and utility services that can be used by other applications 5. Deploy the application and publish the Web Service methods in a Discoverable Directory (UDDI) 6. Repeat steps one thought four for each incremental release and broaden step 5 until you are ready to move on to the next architectural layer Source: Thomas Erl
  29. Strategic Top-Down Approaches: 29 Portfolio Management, Governance, and the EA Stack ENTERPRISE ARCHITECTURE – Starting from the Enterprise Business Architecture Governance & Architecture level, you can Value Chain Business Process Relationship Product/ Service Management strategically identify services Structure Structure Structure Structure Enterprise Portfolio key to the technical and Technology Architecture Structure business aspects of your Business Applications Corporate Vertical Architectural operation SRM ERP Applications CRM Applications Principles and Standards – You can also identify Shared Services application opportunities Enterprise Presentation Services Enterprise Application Services Data Services Vendor and SLA Structure within your portfolio as you Enterprise Platforms & Integration Services plan for your future Application Infrastructure Services Resource Structure architectures Network Infrastructure Services – Implementation Steps: 1. Planning Initiation 2. Business Modeling 1 Planning Initiation 3. Current Systems and 2 3 Technology Review Business Modeling Current Systems 4. Data Architecture Design & Technology 5. Applications Architecture 4 5 6 Design Data Applications Technology 6. Technology Architecture Architecture Architecture Architecture Design 7 7. Implementation and Migration Implementations / Migration Plans Planning Source: Adapted from Steven Spewak
  30. Further Considerations for Implementing SOA 30 IT Assets What are the assets that are shared throughout the enterprise? Service Identification What is the business functionality to be provided by a given IT Asset? What is the optimal granularity of the service? Where should a service be located within the enterprise? Domain Definition How should services be grouped together into logical domains? (Business Units, Divisions, Departments etc.) Packaging How is existing functionality within legacy mainframe systems re-engineered or wrapped in reusable services? Orchestration How are composite services to be orchestrated? (Workflow/Collaboration) Transaction Routing How are requests from service consumers to be routed to the appropriate service and/or service domain? Governance How will the enterprise exercise governance processes to administer and maintain services? Messaging Standards How will the enterprise adopt a given standard consistently? (Security, Interface Standards etc.)
  31. our business revolves around you About LiquidHub
  32. LiquidHub at a Glance 32 LiquidHub is a systems integrator and technology consultancy delivering Strategy, Applications, Data, and Infrastructure Solutions that revolve around the needs of the global enterprise. Supporting clients in Life Sciences & Healthcare, Financial Services, Retail, Media, High Technology and other key industries, our solutions are designed to integrate new technology frameworks with enterprise and legacy systems. With offices in Philadelphia, Boston, and Hyderabad, India, our associates serve clients globally, at their site or on ours. Since being founded in January 2001, LiquidHub has grown into one of the region’s premier consultancies, with over 150 associates. –April 2004 - Philly Business Journal ranks LiquidHub as 6th largest Systems Integrator and 17th largest technology employer in region –November 2003 - Named "Start-up Company of the Year" by Eastern Technology Council
  33. IBM and LiquidHub 33 our business revolves around you LiquidHub values IBM’s applications development, SOA, middleware and multi- platform strengths for our clients in a variety of industries. We are pleased to have them here with us today to talk about their SOA direction and the benefits of an IBM infrastructure in implementing Service Oriented Architectures.
  34. Services Oriented Architecture: Architecture a new model for Engagement Jim Ryan IBM SWIC © 2003-2004 IBM Corporation
  35. Service Oriented Architecture and Web services How two critical ingredients map to the on demand operating environment Integration Consume Service Oriented Architecture Software Development Industry Standards Manage Secure Build Deploy Web services Infrastructure Management Service Oriented Architecture IBM is committed to investing over $1 billion next year on Web services 35 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  36. Service Oriented Architecture Portal Service SOAP Service Request (e.g. .NET) B2B Interactions Service Flow Data Existing Applications New Service Logic 36 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  37. Service Oriented Architecture and WebSphere Portal Service SOAP WebSphere Business IntegrationRequest Service Server (e.g. .NET) •Create and deploy new business processes B2B WebSphere •Synchronize business events in multiple Interactions Business systems Integration Server •Integrate applications on diverse platforms Data •Transform information formats en-route between applications Existing •Link people into a new business approach Applications New Service Logic 37 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  38. Service Oriented Architecture and WebSphere Portal Service DB2 Information Integrator SOAP Service Request Provides integrated, real-time access (e.g. .NET) to diverse data as if it were a single database, regardless of where it B2B WebSphere Interactions Business resides. Integration Server •The federated server lets users create an abstract relational view *DB2 Information across diverse data. Integrator •The replication server lets users Existing Applications manage data movement strategies including distribution and consolidation models. New Service Logic 38 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  39. Service Oriented Architecture and WebSphere Portal Service SOAP Enterprise Modernization Offerings Service Request WebSphere Business Integration (e.g. .NET) Adapters •Host Integration Software •Application adapters •WebSphere Host Publisher B2B WebSphere Interactions •WebSphere Host Access •e-business adapters Business Transformation Services Integration •Mainframe adapters Server •WebSphere Host on Demand •Technology adapters *DB2 Information •WebSphere Studio Software Integrator •WebSphere Studio Enterprise Developer WebSphere Business •WebSphere Studio Asset Analyzer Integration Adapters + EM Offerings •WebSphere Development Studio for iSeries New Service Logic •CICS Transaction Gateway 39 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  40. Service Oriented Architecture and WebSphere Portal Service SOAP Service Request WebSphere Application Server (e.g. .NET) •A next-generation application server that simplifies B2B WebSphere Interactions Business build-to-integrate tasks, accelerates application Integration development, and enables dynamic application Server flexibility. *DB2 Information Integrator WebSphere Business Integration Adapters + EM Offerings WebSphere Application Server 40 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  41. Service Oriented Architecture and WebSphere WebSphere Portal Server SOAP Service Request (e.g. .NET) B2B WebSphere WebSphere Portal Server Interactions Business Integration •Portlets can exploit WebSphere Web service functions Server •Supports pluggable, interactive, user-facing Web services *DB2 Information •Can publish Integrator portlets as Web services using admin UI WebSphere Business Integration Adapters + EM Offerings WebSphere Application Server 41 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  42. Service Oriented Architecture and WebSphere WebSphere Portal Server WebSphere Web Services Gateway B2B WebSphere Interactions Business Integration Server WebSphere Web Services Gateway *DB2 Information component that provides configurable mapping based •A run-time on Integrator WSDL documents. It maps any WSDL-defined service to another service on any available transport channel. It is usually deployed at the WebSphere Business firewall andAdapters Integration has access to internal services. + EM Offerings WebSphere Application Server 42 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  43. Service Oriented Architecture and WebSphere WebSphere Portal Server WebSphere Web WebSphere Business Integration Connect Services Gateway •Enables operational B2B based on communities of trading partners. WebSphere Business WebSphere Integration Connect Business •Connect to and integrate with communities of Integration trading partners . Server •Support Information range of industry standard *DB2 for a wide protocols including RosettaNet, AS2 and XML Integrator •Support WebSphere Business interactions over for trading partner transportsIntegration Adapters such as HTTP(S), FTP and SMTP + EM Offerings WebSphere Application Server 43 SOA: a new model for Engagement © 2003-2004 IBM Corporation
  44. Service Oriented Architecture and WebSphere WebSphere Messaging WebSphere Portal Server (MQ, WBI brokers) WebSphere Web Services Gateway WebSphere Business WebSphere Integration Connect Business Integration Server *DB2 Information Integrator WebSphere Business Integration Adapters + EM Offerings WebSphere Application Server 44 SOA: a new model for Engagement © 2003-2004 IBM Corporation

×