Creating an SOA with IBM WebSphere

2,276 views
2,117 views

Published on

0 Comments
2 Likes
Statistics
Notes
  • Be the first to comment

No Downloads
Views
Total views
2,276
On SlideShare
0
From Embeds
0
Number of Embeds
1
Actions
Shares
0
Downloads
136
Comments
0
Likes
2
Embeds 0
No embeds

No notes for slide
  • Objectives The Governance Framework defines the principles, processes, and roles required to manage, use and update the Service Oriented Architecture. The primary goal is to derive maximum value from the Service Oriented Architecture asset by promoting its implementation, use and evolution. Defines how the Service Oriented Architecture (and its associated models) should be managed and updated in response to changes in business needs and available technologies. The Governance processes are fundamental to enabling the business to make conscious decisions about IT, the acquisition of IT assets, and the design and implementation of new IT solutions to meet business needs In order to achieve these objectives the governance needs to establish 4 distinct processes: SOA Definition Process – This process specifies the architectural design activities that define, build, and deploy components of the SOA. This process includes modeling of business components, business services, and the design of service components that will enable the business model activities. It also defines the different organizational roles required to support the process. SOA Vitality Process – This process maintains the applicability and currency of the architecture. This requires the architecture to be current, reflecting the business and IT direction and strategy, as well as anticipated changes in outsourced non-core processes. It must also refine the Architecture Management Process and supporting roles, organization and business functions to ensure its on going usage and relevance. The architectural principles are used to help guide this process SOA Compliance Process – This process reviews and approves/rejects the design of a solution against the Service Oriented Architecture. This process can be performed at various points during the Business / Project cycle. In many cases, it is an add-on to an existing enterprise architecture review/quality process. This process also allows for projects to appeal the non-compliance of a solution design or an IT investment with the architecture and be granted an exception SOA Communications Process – This process is aimed at educating and communicating the architecture across the organization. This also includes ensuring that the process is acknowledged within the associated processes as well as setting up environments and tools to allow easy access and use of architectural information These processes enable the enterprise to maintain alignment of business and IT. ... click action to bring the influence factors into view .... For example, the Vitality Process ensures that Business Directions and IT Strategies from the enterprise leadership are examined against the backdrop of existing technologies and new trends and define new requirements and changes to the Enterprise Architecture stakeholders (generally in IT) for its implementation and update of the SOA vision The Compliance Process , as another example, assures that IT Investments required to provide compliance with the enterprise vision are assessed against the impact on other enterprise initiatives. Finally, a consistent and frequent communication of the Business Value of the SOA and its Principles, Models, Standards, Plans is essential to achieve and maintain the SOA vision and the expected benefits to the business.
  • There is an emergence of SOA tools to drive the complete end-to-end service lifecycle for successful SOA implementations. As the diagram indicates: Service inception Service reuse Service versioning Service retirement are all new phases that are unique to services that need to be effectively managed. This notion of a “macro” lifecycle that interacts with existing lifecycles, such as: System/Service Design Life Cycle (SDLC) Asset management lifecycles Service release and change management lifecycle Service operational lifecycle is increasingly becoming the norm in today’s SOA. Customers need more and more automation and are seeking a single tool to start their successful management of overall service lifecycles (or macro lifecycle).
  • INSTRUCTOR: At this point many people will ask: why are you talking about CBM and SOMA? The answer in slide # 16. Just defer the answer and take the time to describe the overlap between the various methods. The items on the list on the left of the slide are called “domain areas” in GSMethod and “disciplines” in RUP (they do not map one-to-one between the two methods). Note that the scope and applicability of the GSMethod is much wider than RUP, which is primarily a software development set of best practices (methodology). Question to introduce the next slide: RUP for SOA is included in RUP But are these methods (RUP for SOA) and techniques (CBM, SOMA) all what I need for SOA? Obviously not. See next slide. Remember that the SDCC (Service Design, Creation and Connectivity) STEW focuses on the Analysis and Design of Services, which is the focus of interest of SOMA and RUP4SOA.
  • INSTRUCTOR: Slides are annotated in the top right corner with the methodology under discussion, e.g. CBM in this case. Point this out to students so they can always follow which methodology is being covered. An IT Architect would not typically use CBM, but the output of a CBM engagement can be the input to an SOA engagement.
  • Speaker notes not required for this chart.  Contact content owner listed on title page if you need assistance or additional details.
  • Speaker notes not required for this chart.  Contact content owner listed on title page if you need assistance or additional details.
  • Speaker notes not required for this chart.  Contact content owner listed on title page if you need assistance or additional details.
  • 3 major activities (on the left) - set of steps for each activity (right) SOMA activities are grouped into 3 major steps: Identification, Specification, and Realization decisions. At the heart of SOMA are identification and specification of services, service components and flows (or processes). As many other architectural activities, SOMA activities are performed iteratively. The steps apply one or more complementary techniques, that can be done in parallel. The first major SOMA step identifies candidate services and flows. In this lecture, we will be focusing on this step. The second step selects and specifies the services that will be exposed and service components that will realize them. The third step captures realization decisions.
  • Speaker notes not required for this chart.  Contact content owner listed on title page if you need assistance or additional details.
  • Service Specification - Elaborates the Service Model , for example, service dependencies, composition, non-functional requirements, service message specifications, design decisions, and so on - Includes Service Litmus Test that “gate” service exposure decisions Subsystem Analysis - Partitioning into service components that will be responsible for service realization Component Specification - Detailed component modeling, flow, information architecture, and messages
  • Speaker notes not required for this chart.  Contact content owner listed on title page if you need assistance or additional details.
  • Note that there is SOMA content for RMC available – IBM internal only. Note: The proprietary nature of SOMA may make it inappropriate for use in SWG Services engagements where the client must follow the same method as IBM consultants
  • Rational learned what works and what does not work from over twenty years of consulting experience in software development projects with clients. Use Case driven: many people have a limited knowledge of Use Cases, and think that Uses Cases apply only at the System level. On the contrary, RUP best practices start at the Business Modeling Level , where Business Use Cases (otherwise known as business processes, or business components) are used to define the very early business requirements, associated with business objectives. Go to developerWorks to find the available RUP plug-ins for RMC: http://www-128.ibm.com/developerworks/rational/library/05/1206_ibmstaff/#1 and for RUP 2003: http://www-128.ibm.com/developerworks/rational/library/5823.html
  • FROM: RUP in RMC, search: “Activity Refine the Architecture”, select Work Breakdown Structure FROM: RUP in RMC, search: “Activity Design Services”, select Work Breakdown Structure An example of the detailed steps inside one of the main activities that the Architect is responsible for (Identify Services) is expanded in the box: notice the similarity of the steps in RUP “Identify Services” with the related steps in SOMA (Service Identification). In parallel changes are being made to the RUP Business Modeling discipline that would make the connection between BM and SOA stronger, however it was decided not to wait for the BM changes before completing the SOA plug-in. The integration of both sets of changes will be made for the commercial release.
  • We can’t go through RUP for SOA in detail in this lecture. These are a few of the most important elements in RUP for SOA, but there is lots more. Artifacts are a kind of RUP work product [IGS term].
  • Reference: http://www-306.ibm.com/software/awdtools/rmc/
  • Once the governance process is defined, it can be implemented as a BPEL workflow by rewriting it using WebSphere Business Modeler. Once in WBI Modeler, it is then imported into WID as a staging environment for WebSphere Process Server.
  • Federation framework to support WSRR, LDAP, UDDI, etc. Maintain Referential integrity – through 2-way replication(?) OWL differences : WSRR: OWL-taxonomy only (basically Metadata classifications only (although OWL-based)) BSR: OWL full indsutry ontologies Governance. Must differentiate. Governance of what? (SOBAs vs. ws) UDDI differences: BSR - does Discovery API. WSRR - Scripts to do a one-time dump Fabric Bundled with WPS, WID, WSRR This Year: Basic Bluewash Next Year: Integrated Bluewash
  • <<Get this from Bill C. – rich speaker notes>> Many of these assets are going over to GBS. Global Software Solutions Centers will tasked with cranking these out for multiple industries. Consulting service will become more “asset based”.
  • Creating an SOA with IBM WebSphere

    1. 1. SOA From a Business Centric Perspective Vladimir Ergovic Software IT Architect IBM CEMAAS South East Area [email_address]
    2. 2. Agenda <ul><li>IBM’s view of SOA </li></ul><ul><ul><li>t he business alignment and enterprise wide trend </li></ul></ul><ul><li>SOA entry points </li></ul><ul><ul><li>governance and how it impacts many aspects of an organization </li></ul></ul><ul><li>Methodologies and products </li></ul><ul><ul><li>CBM, SOMA, RUP, GS Method, RUP4SOA </li></ul></ul><ul><li>Business services </li></ul><ul><ul><li>WebSphere Business Services Fabric </li></ul></ul><ul><li>Summary </li></ul><ul><ul><li>current and future industry trends </li></ul></ul>
    3. 3. Key Takeaways <ul><li>SOA is one of IBM’s long term strategies to enable innovation that matters </li></ul><ul><ul><li>Continuing to deliver SOA centric offerings </li></ul></ul><ul><li>IBM’s view of SOA is business centric </li></ul><ul><li>How to get started is crucial </li></ul><ul><ul><li>People, process and information </li></ul></ul><ul><ul><li>Reuse & connectivity is critical </li></ul></ul><ul><li>Entry points are accelerated by SOA Foundation products and business insight </li></ul><ul><ul><li>new and enhanced products </li></ul></ul><ul><ul><li>new service offerings </li></ul></ul><ul><ul><li>90,000 G BS skills trained </li></ul></ul><ul><ul><li>Best practice customer examples </li></ul></ul><ul><ul><li>Enhancements to SOA Standards Roadmap </li></ul></ul><ul><ul><li>Many more… </li></ul></ul><ul><li>SOA Governance is a key to success </li></ul>SOA impacts Business and IT… But that doesn’t mean everything is SOA. This presentation is about how IBM enable s customers to take an SOA approach to solving problems across business domains.
    4. 4. Enable Business Flexibility Easy to enhance reconfigure and maintain Able to be deployed in incremental steps Increase the speed of the decision making Improve collaboration Reduce administrative time Deploy end-to-end business process The business alignment and enterprise wide trend projects snapshot Web Services Interoperability across Heterogeneous Environments Service Components Simplified Composition and Implementation of Services and Data Business Processes Business Process Modeling & Management Enterprise Governance Aligning business strategy <ul><li>ESB Mediation of services </li></ul><ul><li>Security Federation for Telco Partner Integration </li></ul><ul><li>Enterprise SOA Transformation including setup of SOA Governance Organization (large insurance company) </li></ul><ul><li>Enterprise Wide SOA Portfolio Management for automotive industry </li></ul><ul><li>Container Shipping Company transformation </li></ul><ul><li>Airport Ramp Control </li></ul><ul><li>Trucks Customer Order process </li></ul><ul><li>Electronic Industry Contracts management </li></ul><ul><li>Telco “Meet me Service” </li></ul><ul><li>Service Registry & Repository </li></ul><ul><li>Components for Car Dealers </li></ul><ul><li>Service Portfolio for Heavy Industry </li></ul>Business Technology 2003 2007
    5. 5. IBM's View of SOA: Business Centric Built on SOA Lifecycle <ul><li>Enable human and process interaction with consistent levels of service </li></ul><ul><li>Achieve greater efficiency and effectiveness with business model innovation </li></ul>Recent studies of over 1900 customers showed SOA starting points of people, process, information or a combination of all three <ul><li>Deliver trusted information in business context to enable innovation </li></ul>
    6. 6. Entry Points Based on Real Customers’ Engagement Poor integration between channels and desire to optimize E2E processing Financial Programs that map to Marketing Promotions can be done faster and cheaper Harley Davidson Financial Services Process Competition and regulatory pressures forced to improve their understanding of and relationships with customers Rapid project payback from reuse – second interface was delivered within 10 weeks, at 2.5% of the cost of the first interface Information Reduce cost of business with multiple channels Make data in existing systems available to sales portal Savings of 4M pounds to date, 1M pounds a quarter Reuse Applications in silos, can’t communicate with each other Routing of requests through multiple data centers Standardize application integration estimate saving $720,000 annually and 25% less application development time Connectivity: Web Services based Infrastructure reduce nearly 50% application deployment and 30% operations cost Customer Value Post merger standardization of application development & deployment infrastructure People Business Challenge Example Pattern 3 1 2 5 4
    7. 7. Information Centric Approach – Greater Value through SOA Delivering Information as a Service to People & Processes Value Improve business operations and reduce risk with trusted information services delivered in-line and in-context Start with Discover and understand information sources, relationships & business context– Choose reusable high value data for first services Next steps Expand number and scope of services across internal and external processes Why SOA? Trusted information packaged as services are embedded inline within processes or delivered to people 1
    8. 8. Process Centric Approach - Greater Value through SOA Business Process Management for Continuous Innovation Value Innovative business models deployed quickly with flexible and optimized processes. Measure performance to drive improvement. Start with A single process – Model an underperforming process. Optimize and deploy as enhanced process. Next steps Flexibly link multiple processes across the enterprise & to suppliers / partners. Monitor the process to measure & track performance. Why SOA? Modeled processes, converted into services, are re-used, connected and re-deployed more flexibly and quickly with SOA 2
    9. 9. People Centric Approach - Greater Value through SOA Intuitive & Adaptive User Experience Value Improve people productivity by aggregating views that deliver information and interaction in the context of a business process Why SOA? Composite applications created, deployed, and updated faster with SOA portlets Start with Build a view of a key business process by integrating information in front of people to improve decision making Next steps Manage performance more tightly with alert-driven dashboards tied to processes 3
    10. 10. Connectivity - Greater Value through SOA Underlying Connectivity to Support Business-centric SOA * Software Strategies “ Enterprise Integration Challenge” 2005 <ul><li>Value </li></ul><ul><li>Deliver services through new business channels for a secure, consistent user experience </li></ul><ul><li>Service-based connections with trading partners </li></ul><ul><li>Potential savings of 2X-4X over custom-built integration or FTP* </li></ul><ul><li>Start with </li></ul><ul><li>Messaging backbone leveraging messaging and web services protocols as the foundation for SOA connectivity </li></ul><ul><li>Enable mediated exchange between services, by leveraging an ESB </li></ul><ul><li>SOA appliances for ESB functions in a hardware form factor </li></ul>4
    11. 11. Creating & Reusing Services - Greater Value through SOA Create Flexible, Service-based Business Applications * Software Productivity Research (SPR) <ul><li>Value </li></ul><ul><li>Flexibility and elimination of duplication for reduced cycle times </li></ul><ul><li>Expanded access to core applications </li></ul><ul><li>Consultant studies have found it 5X less expensive to re-use existing applications than to write new applications* </li></ul><ul><li>Start with </li></ul><ul><li>What services are needed to run your business? </li></ul><ul><li>Identify high-value existing IT assets and service-enable them for reuse </li></ul><ul><li>Fill in gaps by creating new services for today's business needs and future reuse </li></ul><ul><li>Registry/repository to facilitate centralized access and control of reusable services </li></ul>5
    12. 12. Governance is critical to success with SOA <ul><li>For business services and composite apps/services to become reused, they must be “trusted” </li></ul><ul><li>Trust is enabled by effective governance for compliance to Service Level Agreements, and nonfunctional requirements (e.g. security, reliability, performance, etc.) </li></ul>Funding Service Domains Categorization of Services Roles and responsibilities Services Ownership and Domains Service Oriented Development Lifecycle Operational Life-cycle Management Service management SLA Capacity and Performance Security Monitoring Identification and Maturity of Services Service Assembly and Deployment Change Management Governance
    13. 13. Creating effective SOA governance is challenging <ul><li>Examples of key questions to address: </li></ul><ul><li>What common business services are needed? </li></ul><ul><li>What potential applications (service consumers) will reuse these service(s)? </li></ul><ul><li>Which policies are common, which are unique? </li></ul><ul><li>Can the differences be isolated to maximize consistency? </li></ul><ul><li>What services already exist and are candidates for reuse? </li></ul><ul><li>Who decides which existing LOB service has the best customer data for the new shared process to be used by all LOBs? </li></ul><ul><li>Who owns the shared service(s)? </li></ul><ul><li>Who should fund it? </li></ul><ul><li>Who is responsible for upgrades? </li></ul><ul><li>How to motivate each LOB to reuse the service (rather than their own unique version because they feel they have unique needs)? </li></ul><ul><li>Who decides who can use the service and how often? </li></ul><ul><li>How to organize the shared services/assets so they can be effectively reused at a later date? </li></ul><ul><li>Who is allowed to change a service reused by others? </li></ul><ul><li>Who is using a service and what will be impacted by changes to that service? </li></ul><ul><li>Who needs to approve any changes? </li></ul><ul><li>Who will be responsible for funding upgrades to meet a specific user's requirements? </li></ul><ul><li>Key aspects to control: </li></ul><ul><li>Service registration </li></ul><ul><li>Service versioning </li></ul><ul><li>Service ownership </li></ul><ul><li>Service funding </li></ul><ul><li>Service monitoring </li></ul><ul><li>Service auditing </li></ul><ul><li>Service diagnostics </li></ul><ul><li>Service identification </li></ul><ul><li>Service modeling </li></ul><ul><li>Service publishing </li></ul><ul><li>Service discovery </li></ul><ul><li>Service development </li></ul><ul><li>Service consumption </li></ul><ul><li>Service provisioning </li></ul><ul><li>Service access </li></ul><ul><li>Service and composite app deployment </li></ul><ul><li>Service security </li></ul>
    14. 14. Governance impacts many aspects of an organization Roles Organization Compliance Definition Communication Vitality External Effects Business & IT Strategies Architecture Stakeholders Business Directions IT Strategies Key Requirements Technology Changes New Requirements & Options IT Investments Compliance Assessment & Impacts Business Value Principles Models Standards Plans Architectural Compliance, Relevance & Value Service Model
    15. 15. Service Lifecycle Management Flow <ul><ul><ul><li>Service Creation leads into a focused development lifecycle </li></ul></ul></ul><ul><ul><ul><li>Service Deploy and Availability focus on change and release mgmt </li></ul></ul></ul><ul><ul><ul><li>Service Operational Management focuses on system management </li></ul></ul></ul><ul><li>As SOA practices mature, a the “Service Lifecycle” view has emerged </li></ul><ul><li>Service lifecycle management is a component of an overall SOA Governance Strategy, and provides control and rigor appropriate to the nature of services </li></ul>Service Lifecycle Model Service Reuse / Use Existing? Service Creation (Development Lifecycle) Service Inception (Organization Needs) No Yes Yes, but... Service Deploy Service Availability Service Variation Request Service Versioning Service Operational Summary Service Retirement
    16. 16. Two types of methodology are needed, with different delivery options <ul><li>The Rational Unified Process (RUP) for SOA, and other RUP methodologies </li></ul><ul><li>Very comprehensive methodology for managing the lifecycle of services, both from bottom-up and top-down perspectives </li></ul><ul><li>Separate tasks and deliverables provided as in plug-ins </li></ul><ul><li>Rational Method Composer hosts the plug-ins, and facilitates tailoring the collection of methodology elements to the specific needs of the enterprise </li></ul><ul><li>Methodology for the Identification, Design, Creation, Deployment, and Management of services </li></ul><ul><li>Methodology for the creation of a governance strategy and approach for SOA </li></ul>Customer Delivery Services Delivery <ul><ul><li>IBM’s CBM, SOMA, and other GS Method methodologies </li></ul></ul><ul><li>GBS and GTS use proprietary intellectual capital and tools, which can be very specific to industry requirements </li></ul><ul><li>The RUP plug-in for SOA Governance </li></ul><ul><li>Accessed and customized via the Rational Method Composer </li></ul><ul><li>Guides the design and implementation of an end-to-end Governance approach through a series of tasks and deliverables </li></ul><ul><li>Leveraged by Rational Portfolio Manager (RPM) to create project templates that are in alignment with the established governance policies and procedures (ensures that all projects are in conformance) </li></ul><ul><ul><li>Governance aspects of IBM’s SOMA methodology </li></ul></ul><ul><li>GBS and GTS use proprietary intellectual capital and tools </li></ul>
    17. 17. IBM’s SOA Methodology Organizations Business Modeling Requirements Analysis and Design Implementation Test Deployment Configuration & Change Mgmt. Project Management Environment Operations RUP GS Method RUP4SOA CBM SOMA domain areas CBM – Component Business Modeling SOMA – Service Oriented Modeling and Architecture RUP for SOA – Rational Unified Process for SOA IBM Confidential
    18. 18. Component Business Modeling <ul><li>CBM is a business consultancy method used by IBM Global Business Services </li></ul><ul><li>CBM is a technique to decompose an Enterprise into its constituent building blocks (business components) </li></ul><ul><li>A component is a logical grouping of people, technology, and resources that delivers specific business value, and can operate independently </li></ul><ul><li>The output of a CBM engagement can be the input to an SOA engagement </li></ul>To-Be Business Process Model SOMA Heat Map Component Business Model RUP for BM/SOA CBM CBM
    19. 19. Enterprise Architecture “ the city plan” <ul><li>Solution Architecture </li></ul><ul><li>functional aspects </li></ul><ul><li>operational aspects “the infrastructure and Single building design” </li></ul>Business Strategy Information Technology Strategy Business Opportunity Technology Availability <ul><li>Processes </li></ul><ul><li>Information </li></ul><ul><li>People </li></ul><ul><li>Locations </li></ul><ul><li>Applications </li></ul><ul><li>Data </li></ul><ul><li>Technology </li></ul>Planning Design and Delivery Enterprise wide focus Project focus Strategy IT Solutions Transition Plan Enterprise Architecture embraces both Business and IT Architectures, providing the “city plan” for “building projects” Domain Architectures “ regions of the city plan” SOA Reference Architecture Business Operating Environment and IT Infrastructure Enterprise Architecture Business Map Infrastructure Map Business Architecture Application Map
    20. 20. Strategic Capabilities Network (SCN) V V V C C C C C C C C R R R R R R R R R R R R R R R R R EA Engagement: During enterprise architecture activities, we focus on refining the needed capabilities and identifying the resources (capability enablers) the client needs to meet its strategic objectives. The SCN is created and developed in Strategy engagements and Enterprise Architecture engagements. In each of these, the focus is slightly different. Strategy Engagement: During strategy activities the focus is on understanding the client’s existing capabilities, evaluating their strengths and weaknesses and identifying new capabilities required.
    21. 21. How does an SOA engagement use CBM work products? <ul><li>CBM can identify where to focus attention in an SOA engagement – e.g. areas of key strategic value (heat map) </li></ul><ul><li>CBM gives a loosely coupled architecture – an SOA should not bind the business components in a way that compromises the business architecture. </li></ul><ul><li>If CBM has identified business services, these can be analyzed to identify the software services needed to support them </li></ul><ul><li>If CBM has identified business processes then these act as requirements on the functionality that must be offered by a service-oriented solution </li></ul>CBM
    22. 22. SOMA <ul><li>Service-Oriented Modeling and Architecture </li></ul><ul><li>It is a method with roles and activities that produces artifacts ( workproducts ) relating to the identification, specification and realization of services, components and flows (processes) </li></ul>SOMA Realization Decisions Specification of Services, Components, and Flows Identification of Candidate Services and Flows Domain Decomposition Subsystem Analysis Service Specification message & event specification component flow specification service flow specification Realization Decisions Goal-Service Modeling Existing Asset Analysis Component Specification information specification service allocation to components component layering technical feasibility exploration
    23. 23. More about SOMA <ul><li>SOMA is aimed at enabling target business processes through the identification, specification and realization of business-aligned services that form the SOA foundation. </li></ul><ul><li>It introduces new and innovative techniques where gaps exist in existing techniques, in order to specifically address SOA needs. SOMA enables creation of composable services. </li></ul><ul><li>It creates continuity between the business intent and IT implementation by extending business characteristics (e.g. goals and key performance indicators) into the IT analysis and architectural decisions. </li></ul><ul><li>Analysis and modeling performed during SOMA does not impose any product , but establishes a context for making technology and product specific decisions in later phases of the lifecycle. </li></ul><ul><li>Its goal is to provide guidance in the modeling (analysis and design) of SOA. </li></ul>SOMA
    24. 24. SOMA Activities SOMA <ul><li>SOMA activities are grouped into three major steps: Identification, Specification, and Realization </li></ul><ul><li>At the heart of SOMA is the identification and specification of flows , services , and components </li></ul><ul><li>SOMA activities are performed iteratively. Each step is carried out by applying one or more complementary techniques. </li></ul>Domain Decomposition Subsystem Analysis Service Specification message & event specification component flow specification service flow specification Realization Decisions Goal-Service Modeling Existing Asset Analysis Component Specification information specification service allocation to components component layering technical feasibility exploration Realization Decisions Specification of Services, Components, and Flows Identification of Candidate Services and Flows
    25. 25. Service Identification <ul><li>A combination of three strategies is used </li></ul><ul><ul><li>Goal-Service Modeling </li></ul></ul><ul><ul><li>Domain Decomposition (Top down Analysis) </li></ul></ul><ul><ul><li>Existing Asset Analysis (Bottom-up Analysis) </li></ul></ul>SOMA Top-down Analysis Bottom-up Analysis Align Services with Business Goals Domain Decomposition Existing Asset Analysis Goal-Service Modeling Service Specification next step:
    26. 26. Service Specification <ul><li>Service Specification </li></ul><ul><ul><li>Elaborates the Service Model. For example: service dependencies, composition, non-functional requirements, service message specifications, design decisions, etc. </li></ul></ul><ul><ul><li>Includes Service Litmus Test that “gate” service exposure decisions </li></ul></ul><ul><li>Subsystem Analysis </li></ul><ul><ul><li>Partitioning into service components that will be responsible for service realization </li></ul></ul><ul><li>Component Specification </li></ul><ul><ul><li>Detailed component modeling, flow, information architecture, and messages </li></ul></ul>SOMA Service Realization Subsystem Analysis Component Specification information specification component flow specification Service Specification service flow specification message & event specification next step:
    27. 27. Service Realization <ul><li>Review the Service Model to determine how each Service is realized </li></ul><ul><ul><li>Decide how Services are Realized: buy, build, integrate, transform, subscribe, outsource </li></ul></ul><ul><ul><li>Document the Service Realization Decisions </li></ul></ul>SOMA Service Implementation Realization Decisions component layering technical feasibility exploration service allocation to components next step:
    28. 28. SOMA delivery <ul><li>SOMA is intended to be used by IBMers (especially IGS) working on client engagements </li></ul><ul><li>Can be left with customers provided contracts and licenses are in place </li></ul>SOMA IBM Confidential
    29. 29. Rational Unified Process <ul><li>It’s a set of software development best practices collected over twenty years of client engagements </li></ul><ul><li>It’s an IBM Product </li></ul><ul><li>RUP is iterative </li></ul><ul><ul><li>executable releases at each iteration (risk reduction) </li></ul></ul><ul><li>RUP is Use Case based </li></ul><ul><ul><li>business or system use cases </li></ul></ul><ul><ul><li>use cases are used to define scope, plan, test and documentation </li></ul></ul><ul><li>RUP is Architecture driven </li></ul><ul><li>RUP is modular </li></ul><ul><ul><li>plug-ins for SOA, Systems Engineering, etc. </li></ul></ul>RUP always needs to be tailored to the specific project RUP
    30. 30. RUP for SOA <ul><li>It’s a RUP plug-in, available in Rational Method Composer 7.0 </li></ul><ul><li>Focuses on the Analysis and Design of Services </li></ul><ul><li>Activities in all the RUP disciplines have been updated with Service-Oriented content </li></ul><ul><li>Shares many concepts, activities and artifacts with SOMA </li></ul><ul><li>Top-Down, Business Process Driven </li></ul><ul><li>Top-Down, Use Case Driven </li></ul><ul><li>Data Driven </li></ul><ul><li>Rule Driven </li></ul><ul><li>Bottom-Up, Exposing Existing Assets </li></ul>RUP for SOA Refine the Architecture Design Services
    31. 31. RUP for SOA – Some key elements RUP for SOA
    32. 32. Rational Method Composer <ul><li>RMC is an Eclipse-based tool for creating and customising development processes </li></ul><ul><li>RMC includes RUP and several RUP plug-ins including RUP for SOA </li></ul><ul><li>Processes are deployed (“published”) as HTML and Java applet web sites </li></ul>
    33. 33. RUP for SOA Governance Plug-in (IBM SOA Governance and Management Method)
    34. 34. IBM’s foundation SOA technology provides support for governance <ul><li>WebSphere Business Modeler </li></ul><ul><li>Define and document the governed processes </li></ul><ul><li>Roles, Decision Rights, Process </li></ul><ul><li>WebSphere Integration Developer </li></ul><ul><li>Enable the governed process as executable business process </li></ul><ul><li>Lifecycle state machine </li></ul><ul><li>WebSphere Process Server </li></ul><ul><li>Execution runtime for governance workflow </li></ul><ul><li>Manages the SOA Lifecycle through enforced workflow </li></ul><ul><li>WebSphere Portal </li></ul><ul><li>UI Interface for decision rights </li></ul><ul><li>Authentication and Authorization for workflow and checkpoints </li></ul><ul><li>WebSphere Monitor </li></ul><ul><li>Monitor results and KPIs of the governed process </li></ul><ul><li>WebSphere Registry and Repository </li></ul><ul><li>Definitive source of state for services as they progress through governed workflow </li></ul><ul><li>Development Sub-Process </li></ul><ul><li>Rational Tools, enforcing a defined development process as defined during the governance process </li></ul><ul><li>ClearCase, ClearQuest, Requisite Pro, RAM, BuildForge </li></ul><ul><li>Development workflow managed by Process Server </li></ul><ul><li>IT Service Mgmt Sub-Process </li></ul><ul><li>Tivoli Management products, enforcing defined ITSM processes as defined during the governance process </li></ul><ul><li>CCMDB, TPM, ITCAM </li></ul><ul><li>Systems Management workflow managed by Process Server </li></ul>
    35. 35. <ul><li>Composition Studio </li></ul><ul><li>A visual modeling environment where domain-experienced software architects can easily create and manage industry specific service meta-data models and policies. </li></ul><ul><li>Subscriber Manager </li></ul><ul><li>Controls and automates entitlement of Business Services for subscribers. </li></ul><ul><li>Enables creation, control, and management of service packages to subscribers across the ecosystem. </li></ul><ul><li>Governance Manager </li></ul><ul><li>Provides powerful visual zooming and panning models of hierarchies and service dependencies so that technical and business users can monitor business SLAs & performance. </li></ul><ul><li>Business Services Repository </li></ul><ul><li>A standards-based, enterprise SOA metadata repository to manage ontologies, service descriptions and policies. </li></ul><ul><li>Enables developers to publish, reuse, & manage services. </li></ul><ul><li>Dynamic Assembler </li></ul><ul><li>A highly scalable, semantic services broker that enables dynamic service assembly and provides service behavior personalization based on content, context, and contract. </li></ul><ul><li>Performance Manager </li></ul><ul><li>Provides visibility and monitoring of service oriented processes and applications. It includes multi-perspective views and enables drill-down analysis of events and exceptions. </li></ul>WebSphere Business Services Fabric
    36. 36. WBSF leverages and extends WSRR .wsdl .xsd Bpel Metadata Classifications CBS Metamodels Industry Ontologies Subscription Policies Business Policies WSRR BSR Web Service Details Discovery WSRR API Web Service Technical Artifacts Business Service Metadata <ul><li>Business Services Repository (BSR) </li></ul><ul><li>Focus on business service metadata, policies, and subscribers </li></ul><ul><li>Foundation for &quot;housekeeping of business services&quot; throughout their lifecycle </li></ul><ul><li>Spans design-time to run-time and manage-time usage scenarios </li></ul><ul><li>Federation framework for scalable/extensible SOA that supports other authoritative data sources; WSRR, LDAP, and others </li></ul><ul><li>Websphere Service Registry & Repository </li></ul><ul><li>Focus on Web service technical artifacts </li></ul><ul><li>System of record repository to physically store assets such as WSDL, XSD, BPELs, etc </li></ul><ul><li>Metadata classifications to enable easy search and storage </li></ul>WBSF and WSRR provide differentiated and comprehensive registry/repository capabilities through the runtime use and management of both business and technical metadata
    37. 37. The Need: A simple and reusable process
    38. 38. The Reality: Different variations are needed in the process Channels A B C D E
    39. 39. Option 1: Write many different processes (low reuse) Channels A B C D E
    40. 40. Option 2: Write processes with complex decision paths (difficult process creation and management) Channels A B C D E
    41. 41. Option 2: Write processes with complex decision paths (difficult process creation and management) Channels A B C D E
    42. 42. The Best Option: Dynamic Assembly P Repository for Policies, Rules, etc. A B C D E
    43. 43. Pre-Built Industry-Specific SOA Assets <ul><li>Categories of SOA assets that speed time-to-market and instill industry standards and best practices </li></ul>Categories of Pre-Built Industry SOA Content Business Processes Executable processes and workflows Visio/WBI modeler-based, BPEL compliant Business Services Data, process, visibility, optimization services Pre-built semantic mediation services Business Rule Assets Configurable business rule templates By line of business, product and state Industry Message Sets ACORD and IAA-based (insurance example) Configurable, XML-based schemas Ontology and Data Models Pre-built SOA meta models OWL-based configurable ACORD and IAA models Policies and Assertions Multi-tier PRISM policies WS-Policy based models 3rd Party and BPO Service Interfaces Insurance interfaces to key services MVR, CLUE, Credit, Locations, and others Legacy Adaptors 300+ adaptors to legacy and ERP systems Sourced within Business Services Catalog
    44. 44. Benefits of the Business Services Fabric <ul><li>Storage of business services, subscribers and policies to enable assembly of composite business services </li></ul><ul><li>Central repository for business service meta-data, domain ontologies, policies, and subscribers </li></ul><ul><li>OWL/RDF-based, meta-model, which allows for capturing semantics and easy extensibility </li></ul><ul><li>Ontology-driven semantic mediation and interoperability </li></ul><ul><li>Ability to federate meta-data from other repositories such as LDAP systems and WebSphere Service Registry and Repository </li></ul><ul><li>Conflict detection during collaborative development </li></ul><ul><li>Powerful search, dependency, and impact analysis </li></ul><ul><li>Source and syndicate ISV and third-party IT assets into the catalog </li></ul><ul><li>Role-based, context and namespace level security that leverages existing access control systems </li></ul><ul><li>Support for entire meta-data life cycle including comprehensive versioning, change tracking, and collaborative governance of service meta-data </li></ul>
    45. 45. Benefits of the Business Services Fabric (cont.) <ul><li>Comprehensive business service governance </li></ul><ul><li>Governs and manages the set of services, policies, and processes that drive reuse of business services, define and enforce policies, control proliferation of services, provide composite business service visibility, and manage the life cycle of business services </li></ul><ul><li>Leverages components of WebSphere Business Services Fabric to govern life-cycle changes, particularly for design-time promotion of services to run-time and for recording service performance and changes </li></ul><ul><li>Governs all aspects of business services: performance, reliability, interoperability, security, and management </li></ul><ul><li>Manages life-cycle changes to business services </li></ul><ul><li>Controls meta-data promotion between environments </li></ul><ul><li>Validates meta-models to ensure accuracy and correctness before publishing </li></ul><ul><li>Ensures meta-data integrity while modeling composite business services in a multi-authoring environment </li></ul><ul><li>Defines policies for meta-data visibility in collaborative development environments </li></ul><ul><li>Notifies users when changes are made </li></ul><ul><li>Offers change management process for service versioning, validation, and performance management </li></ul><ul><li>Includes open APIs for integration with change management systems, such as IBM Rational ClearCase ® </li></ul>
    46. 46. Benefits of the Business Services Fabric (cont.) <ul><li>Meta-data-driven assembly of composite business services </li></ul><ul><li>Enables publishing and managing service models, policies, and service portfolios </li></ul><ul><li>Designed to work with WebSphere Integration Developer and tools such as IBM Rational® Software Architect, providing architects, developers, and system integrators with a common meta-data life-cycle management fabric for connecting services, exchanging meta-data, and aligning context across different applications and domains </li></ul><ul><li>Achieves rapid and secure assembly of disparate IT assets into composite business services </li></ul><ul><li>Supports both top-down business domain decomposition and bottom-up analysis of underlying IT systems </li></ul><ul><li>Creates and enforces design-time, runtime, and change-time policies </li></ul><ul><li>Composes unique multi-channel services that power multiple access modes such as Web, business-to-business (B2B), IVR and fax </li></ul><ul><li>Delivers model and manage meta-information about business services including WSDL-, WS-Policy- and BPEL-defined declarations, and actual behavior of services </li></ul><ul><li>Includes model policies as a basis for dynamic discovery, matching, and binding of services based on content, context, and contract </li></ul><ul><li>Simulates service behavior based on different usage scenarios </li></ul><ul><li>Manages run-time meta-information for matching service requestors and service providers using policies </li></ul><ul><li>Applies policies at various levels; for example, business ecosystem, application, business service, or service end point </li></ul><ul><li>Assembles policies in a unified, flexible and extensible grammar to express the capabilities, requirements, and characteristics of entities within an SOA </li></ul>
    47. 47. Benefits of the Business Services Fabric (cont.) <ul><li>Dynamic business service personalization and delivery </li></ul><ul><li>A highly optimized semantic mediation engine enabling meta-data-driven service discovery, matching, and interoperability during both design-time and run-time. </li></ul><ul><li>Leverages business service policies to replace hard-coded service bindings in enterprise service bus, Business Process Execution Language (BPEL), and B2B connections with dynamic end-point selection based on content, context and contract of the service request </li></ul><ul><li>Dynamic service behavior adaptation that is based on business context, content, and contract </li></ul><ul><li>Policy-based customization across multiple domains, business processes, and service end points </li></ul><ul><li>Policy enforcement that is based on performance, reliability, interoperability, security, and manageability of business services </li></ul><ul><li>Dynamic business service and process customization without affecting larger subscriber base </li></ul><ul><li>Elimination/reduction of hard-coded binding changes with policy-based process customization </li></ul><ul><li>Reduced integration complexity through ontology-based classification and data transformation rules </li></ul><ul><li>Multi-protocol support for HTTP and JMS, and can be extended to other protocols </li></ul><ul><li>Multi-message support, for example, ACORD, HIPAA, HL7 </li></ul><ul><li>Out of the box support for SOAP, Java™ Messaging Service (JMS) topics, Remote Method Invocation, and MQ </li></ul>
    48. 48. Benefits of the Business Services Fabric (cont.) <ul><li>Real-time business service visibility and control </li></ul><ul><li>Business visibility and monitoring of composite business services and service oriented processes for business analysts and IT administrators </li></ul><ul><li>Multi-perspective views and drill-down analysis of events and exceptions with respect to business context in a loosely coupled, service-oriented business ecosystem </li></ul><ul><li>Subscriber- and role-based drill-down performance visibility against business goals and service level agreements </li></ul><ul><li>Business service support for billing and metering of composite business services at business service level </li></ul><ul><li>Central performance monitoring console customizable by business need </li></ul><ul><li>Domain, subscriber, and service-based performance and Service Level Agreement (SLA) reporting </li></ul><ul><li>Business content monitoring and alert notification </li></ul><ul><li>Context specific error handling across multiple messages and protocols </li></ul><ul><li>Configurable audit trails on service invocations for security, SLA, and compliance monitoring </li></ul><ul><li>Real-time monitoring of aggregate or individual level traffic including faults, throughput response, and availability </li></ul>
    49. 49. Summary <ul><li>IBM’s view of SOA is business centric </li></ul><ul><li>Governance is critical to success with SOA </li></ul><ul><li>Various methods, future improvement </li></ul><ul><li>Alignment between Enterprise Architecture and SOA </li></ul><ul><li>Business Services are in focus for the next generations of SOA project </li></ul>
    50. 50. Questions ?
    51. 51. Backup
    52. 52. WebSphere Business Services Fabric complements IBM’s foundation SOA technology WebSphere Process Server WebSphere Service Registry & Repository Business Service Repository is loosely coupled with WSRR to consume service metadata and policies 2. Business Services Repository Ontologies <ul><li>Business Policy Data </li></ul><ul><li>Subscription Data </li></ul>6. Semantic Mediation Plug-in (Dynamic Assembler) Performance Data, Usage Data and Extensions WebSphere Business Modeler WebSphere Integration Developer Process &/or Flow Models 1. Composition Studio Eclipse BPEL Editor, WSDLs, and Deployment Web Service or JMS Connections Composeable Business Services Common or Core Services Tooling 3. Governance Manager 4. Subscriber Manager 5. Performance Manager Local Test Instance Fabric
    53. 53. WBSF Design-Time Perspective Design Tools Business Services Definition Tooling: Composeable Business Service-based <ul><li>3. Governance Manager </li></ul><ul><li>Publish Business Service adds, changes and deactivations </li></ul><ul><li>4. Subscriber Manager </li></ul><ul><li>Add, Change, Deactivate Business Service subscribers </li></ul><ul><li>5. Performance Manager </li></ul><ul><li>View existing performance metrics </li></ul>WebSphere Process Server WebSphere Service Registry & Repository Business Service Repository is loosely coupled with WSRR to consume service metadata and policies 2. Business Services Repository Ontologies <ul><li>Business Policy Data </li></ul><ul><li>Subscription Data </li></ul>6. Semantic Mediation Plug-in (Dynamic Assembler) Usage Extensions WebSphere Business Modeler WebSphere Integration Developer Process &/or Flow Models <ul><li>1. Composition Studio </li></ul><ul><li>Access to the </li></ul><ul><li>Business Services </li></ul><ul><li>Repository </li></ul><ul><li>Create Business Service assembly definition </li></ul>Eclipse BPEL Editor, WSDLs, and Deployment WebSphere Process Server is required to run the web-based tooling Local Test Instance Fabric
    54. 54. WBSF Run-Time Perspective WebSphere Process Server 2. Business Services Repository 6. Semantic Mediation Plug-in (Dynamic Assembler) Business Service Repository is loosely coupled with WSRR to collect service metadata and policies <ul><li>Industry Fabric Runtime: </li></ul><ul><li>WebSphere Process Server includes WAS, BPEL Engine and WESB </li></ul><ul><li>Loosely Coupled using JMS </li></ul>Exposed Business Services WebSphere Service Registry & Repository Web Service or JMS Connections Common or Core Services Composeable Business Services <ul><li>Fabric Common Services </li></ul><ul><li>Common Industry Services </li></ul><ul><li>Usage data with Performance Manager </li></ul><ul><li>LDAP Services </li></ul>Ontologies <ul><li>Business Policy Data </li></ul><ul><li>Subscription Data </li></ul>Performance & Usage Data Run-time Tools
    55. 55. WBSF Manage-Time Perspective Management Tools Business Services Definition Tooling: Composeable Business Service-based <ul><li>3. Governance Manager </li></ul><ul><li>Publish Business Service change lists </li></ul><ul><li>Manage Business Service Lifecycle approval/rejections </li></ul><ul><li>Track and Audit Change history </li></ul><ul><li>5. Performance Manager </li></ul><ul><li>View existing performance and utilization metrics </li></ul><ul><li>View Billing and Metering information </li></ul>WebSphere Process Server WebSphere Service Registry & Repository Business Service Repository is loosely coupled with WSRR to consume service metadata and policies 2. Business Services Repository Ontologies <ul><li>Business Policy Data </li></ul><ul><li>Subscription Data </li></ul>6. Semantic Mediation Plug-in (Dynamic Assembler) Performance & Usage Data WebSphere Service Registry & Repository User Interface <ul><li>1. Composition Studio </li></ul><ul><li>Access to the </li></ul><ul><li>Business Services </li></ul><ul><li>Repository </li></ul><ul><li>View Business </li></ul><ul><li>Service assembly </li></ul><ul><li>definitions </li></ul>Eclipse Loosely connected through the Eclipse IDE using plug-ins WebSphere Process Server is required to run the web-based tooling

    ×