• Share
  • Email
  • Embed
  • Like
  • Save
  • Private Content
SOA Architect Summit
 

SOA Architect Summit

on

  • 1,366 views

 

Statistics

Views

Total Views
1,366
Views on SlideShare
1,339
Embed Views
27

Actions

Likes
2
Downloads
120
Comments
0

2 Embeds 27

http://ibmadmin.wordpress.com 26
http://www.slideshare.net 1

Accessibility

Categories

Upload Details

Uploaded via as Microsoft PowerPoint

Usage Rights

© All Rights Reserved

Report content

Flagged as inappropriate Flag as inappropriate
Flag as inappropriate

Select your reason for flagging this presentation as inappropriate.

Cancel
  • Full Name Full Name Comment goes here.
    Are you sure you want to
    Your message goes here
    Processing…
Post Comment
Edit your comment
  • This presentation is intended to introduce the perspectives of SOA important to Enterprise Architects. It is the first in a series of presentations developed for the SOA Summits for Enterprise Architects. These customer events will be scheduled during 4Q2005 in all Geographies. As the first presentation in the series, this presentation will introduce the topics that will be further discussed in the other summit presentations: Model and Assemble, Deploy, Manage, Governance, Getting Started.
  • Slide Objective: Layout the flow of the presentation Details: This presentation will follow the outline as shown on the slide. The key message of the Introduction section is this …. - SOA is a new approach to IT which accentuates the importance of the enterprise architect. The Enterprise Architect must focus on Reference Architectures, Roadmaps, and Governance, since all 3 are critical to the success of an SOA journey.
  • Main Point: Services are repeatable business tasks. Business processes are a series of services snapped together like building blocks. SOA is an architectural style that makes this possible As Gartner says - SOA impacts every aspect of IT and Business. It touches everything that a company does. Let’s start by looking at some base-line definitions so we’re all talking about in the same terms. First of all, what is a service? It’s important to stress that we’re talking about a part of a business process here. Don’t think about software or IT. Think about what your company does on a day to day basis and break those business processes up into repeatable business tasks or components. If you look at the graphic in the middle, this is the analogy of building blocks snapping together to build a structure. Services are the building blocks and they are snapped together into a business process. So SOA is just an IT architectural style that supports integrating your business as linked services. SOA makes it easy to snap together services into a business process just like snapping together building blocks into a structure.
  • Enable new products: 43% Enable compliance 26% Main point: IBM's Institute for Business Value study on the business value of SOA demonstrates that businesses justify investment in projects rooted in SOA because of cost savings but quickly realize improvements in flexibility and innovation IBM recently completed an in-depth survey of X# of its customers who had implemented projects affiliated with SOA. These were detailed, extensive interviews with senior level company representatives into all phases of the projects. The findings revealed insight into what factors were most important in pursuing these projects. First of all, companies didn't describe what they were doing as "SOA projects"; instead, they were undertaking business-focused projects and were using the principles of SOA in doing so. The study found that at the onset, cost reduction is the initial justification for incorporating SOA practices into projects. However, as the projects progressed, companies quickly realized that the projects were also leading to greater flexibility which in turn led to greater innovation and the ability to drive greater revenue. Additionally, the study found that there is still the opportunity to use SOA as a competitive advantage but with adoption of these principles becoming more and more widespread, SOA and the flexibility and cost savings that it brings is quickly becoming table stakes.
  • Main Point: You should choose IBM to help you pursue SOA because we are a leader in every way in this field. Why would you choose IBM for SOA? The biggest reason is that IBM understands service orientation and understands your business. IBM is not following with SOA; we’re leading. This understanding enables our customers to obtain a sustainable competitive advantage through flexibility. IBM has a heritage in providing computing solutions that no other company comes close to. IBM has a ‘footprint’ across entire enterprise so let’s use the same categories we discussed on the previous slide Again, let’s start with infrastructure . IBM has unmatched breadth and depth of software products for SOA. We invest over $1B per year in SOA, This is the kind of investment and leadership that businesses can take advantage of when they choose IBM. IBM not only supports standards but brings true leadership to standards bodies . We are active in over 50 of them and hold many leadership roles within these organizations. We also have over 300 SOA-related patents . Moving up, IBM has extensive industry experience and best practice with over a thousand SOA customers all over the world in a wide variety of industries. Again, this kind of experience is something that no other company can come close to. While others may talk about their theories of SOA, IBM has the real-world experience to make it real today. IBM has a thriving ecosystem of partners . Independent software vendors, systems integrators and resellers are gravitating to IBM as the leader in SOA. We have over a hundred SOA partners and the list keeps growing. This kind of partner ecosystem helps end-user customers ensure interoperability. This leads to the top layer and our expertise in aligning business and IT processes . We have extensive soa consultants, architects, and IT specialists, dozens of soa-enabled business solutions and a unique portfolio of intellectual property and methods . And what we learn through this expertise gets fed back into the software products as well. Other IT vendors have a more disjointed delivery without the ability to really take what they have learned back into their portfolio.
  • Main point: SOA is mainstream. It's not an early adopter phenomenon. Household name companies that are leading innovation in their industries are capturing real business value TODAY with SOA Rather than going through a laundry list of what companies IBM is helping drive greater innovation and operational excellence with SOA, let's look at some broad categories. And before we do, keep in mind that at the other end of this spectrum, there is an equally significant percentage of the world's small and medium sized businesses that are leveraging SOA for the same reasons as the world's largest household names.
  • Slide Objective: “SOA” is a concept that is viewed differently by various people depending on their roles in the organization. The Enterprise Architect, however, must view SOA across all these perspectives and provide the expertise and knowledge that allows these perspectives to bridge cohesively for the good of the business. Details: The most important characteristic of SOA is the flexibility to treat elements of business processes and the underlying IT infrastructure as secure, standardized components (services) that can be reused and combined to address changing business priorities . An Service Oriented Architecture includes all these aspects: An architectural style and a design principle for application development and integration. A way of designing software systems to provide “services” to end-user applications or to other services. A natural evolutionary step to the object-oriented (OO), procedural, and data-centric approaches adopted for solution implementation till now. When creating an SOA system, individual services are typically implemented using one or more of these technologies. The integration of applications and information sources through the exchange of information based on common semantics or a vocabulary used to define the structure of such information exchange. A set of architectural principles and patterns which address characteristics such as modularity, encapsulation, loose coupling, separation of concerns, reuse, composable and single implementation. So when we look at the SOA vision we need to look at 3 aspects: The business view of a service – what is needed to support the business process The Architecture view of a service – how do we define and design these services The implementation view of a service – how do we implement the service through component deployed on the technical infrastructure The most important characteristic of SOA is the flexibility to treat elements of business processes and the underlying IT infrastructure as secure, standardized components (services) that can be reused and combined to address changing business priorities. Services are the building blocks Packaging business functions from new and existing applications in a simple and standardized way creates services that are available for use Services are used to help get the right information to the right people at the right time Services can be reused and combined to deploy composite applications to address new opportunities Increasing use of “Web” services based on open standards complements existing services technology
  • Slide Objectives: The SOA Lifecycle is fundamentally important. It begins with an explicit indication of the importance of modeling business processes and then working those into deployable artifacts that are managed in a way that provides feedback for continuous improvement. Details: Our customers have told us that they take a lifecycle approach to SOA. They start in what we are calling the Model phase by gathering business requirements and designing and optimizing their desired business processes. Once they have optimized the business processes, they implement it by combining new and existing services to form composite applications. The assets are then deployed into a secure and integrated environment taking advantage of specialized services that provide support for integrating people, processes and information. Once deployed, customers manage and monitor the composite applications and underlying resources from both an IT and a business perspective. Information gathered during the Manage phase is used to gain real-time insight into business processes enabling better business decisions and feeding information back into the lifecycle for continuous process improvement. Underpinning all of these lifecycle stages is governance which provide guidance and oversight for the SOA project.
  • Slide Objective: This slide leads to the following slide which sets-up the follow-on sections in the pres. Talk about the alignment of Business and IT goals/objectives and that the Enterprise Architect is a key player in making this alignment a reality. The 3 primary considerations of the EA are the RA, the Roadmap, and Governance. … then move to next slide …. Details: Service Oriented Architecture is an approach to addressing the challenge which has always faced the Enterprise Architects: making sure that the IT resources of an Enterprise are properly aligned so that they serve the needs of the business in the best and most efficient way possible. Enterprise Architects have addressed this challenge by: Constructing Reference Architectures – to serve as the basis of decision-making and technical orientation Documenting Roadmaps – to guide the evolution of IT resources in such a way that they adapt to the changing nature of the business Establishing and supporting Governance – to communicate the plans and choices and ensure compliance of the various initiatives, programmes and projects. Service Oriented Architecture, as an approach, has contributions to make to these three aspects of EA. Throughout the day, we will illustrate this by showing how it offers responses to three main concerns of business: Definition of business function (in SOA, Service Definition) Issues of Security and Regulatory Compliance Issues of Quality of Service (Key Performance Indicators)
  • Slide Objectives: Reference Architecture, Roadmaps, and Governance are three areas of focus for the Enterprise Architect; by focusing on these areas, the EA can provide significant leadership across the various constituencies of the company impacted by the move to SOA. The rest of the presentation is organized to drill into these 3 areas. Details: The SOA Reference Architecture is a high level framework that defines the technical elements required to model, assemble, deploy, and manage SOA based solutions. The SOA Roadmap is a plan that takes into account a company’s current state, their most pressing business needs, and their long term strategic goal. SOA must be addressed incrementally, with return provided to the business with each incremental step. And yet, each of these steps must be done in context of moving the organization consistently toward its long term goals. The SOA Governance Model is an approach to controlling and appropriately managing the transition to SOA.
  • Slide Objectives: The SOA Reference Architecture section is next. In this section, we’ll discuss the SOA lifecycle, IBM’s SOA Reference Architecture, and the key principles underlying the architecture. Details: The key message of the Reference Architecture section is this …. - SOA is a new approach to IT which accentuates the importance of the enterprise architect. The Enterprise Architect must focus on Reference Architectures, Roadmaps, and Governance, since all 3 are critical to the success of an SOA journey. - The Reference Architecture must take into account the full lifecycle needs of running an efficient business. It must allow a new level of separation of concerns to provide the level of flexibility required to achieve the key promises of the SOA value proposition: reduced costs, quicker time to production, ease of re-use, etc.
  • Slide Objectives: The next two slides discuss the evolution through the years to achieve flexibility in IT systems. This slide focuses on showing this evolution from the perspective of the atomic executable components (functions, objects, … services) and the approach for invoking these executable components. Details: The desire to make IT more flexible is not new. Indeed, it is as old as the IT industry itself. Early initiatives involved making monolithic architectures more flexible by breaking them into callable subroutines and procedure calls. The idea was then built upon by the concept of business objects – discrete pieces of code which included data and its behavior which could change depending on context. Object technologies were mostly tightly coupled and so messaging technologies were developed to loosely couple applications from one another. Various EAI techniques were then developed to make applications even more modular. Today, we are at a culmination of all of these architectures with the notion of Service Oriented Architectures. SOA blends the best of all these concepts into one new architecture that promises to make the notion of applications even more flexible.
  • Slide Objectives: This slide continues to show the evolution to achieve flexibility within IT by focusing on separating logic that specializes on particular aspects of the execution (business, connectivity, mediation, control, etc.). Details: As we established at the beginning of this presentation, SOA is not a new concept. It is the next step of a connectivity evolution that has been going on for some time, and indeed, we have already solved much of the problem with existing technologies that you may be using today. The concept of message queuing is a powerful one that you may be using if you are use IBM products like WebSphere MQ. WebSphere MQ decouples applications by abstracting connections through the use for queues. Instead of the application talking directly to another application, it talks to an intermediate queue which can then be directed to any application. Message-queuing also eliminates the need for the application to deal with the intricacies of different platforms or worry whether the other application is busy or even on-line. It also takes care to ensure that message delivery is assured and not duplicated. All of this capability strips out interface code from your application. But message-queuing itself does nothing in itself to help deliver information in the right format. Nor does it help you direct information to different targets based on the message content. You still have to build all of this kind of interface logic directly into your application interfaces. To eliminate this second level of interface logic, you need a different type of intermediary – a traditional broker. Brokers, enable you to remove the transformation and routing logic from the application interfaces. Brokers can also augment content and reroute based on message content. They can also translate between different protocols and programming models. Nevertheless, even with a “traditional” broker, some logic may remain in your applications. To reduce this logic further – down to a bare-bones “service” – some additional standards are needed. First is the use of a Web Services Description Language (WSDL) interface. Second is the programming model for mediating between different programming models such as queue names (used with queuing), topics (used with publish/subscribe), and services (used by Web services). You may also perform other functions for the application such as the automation of request-reply calls. Finally, locating and binding to existing services -- or to the various transformations that may be required -- is another aspect that you may not want to handle from within your application program. The objective of SOA is to reduce the service down to the bare business logic.
  • Slide Objectives: The next two slides show different perspectives of the SOA Reference Architecture. This slide focuses on the capabilities needed to support the SOA Lifecycle. Details: · This slide shows the capabilities perspective of the Reference Architecture that describes the key functionalities that are required to implement comprehensive, enterprise wide SOA solutions and supporting the entire SOA lifecycle (model, assemble, deploy and manage.) - Tools are an essential component of any comprehensive integration architecture. The Development Services are used to implement custom artifacts that leverage the infrastructure capabilities, and Business Innovation & Optimization Services are used to monitor and manage the runtime implementations at both the IT and business process levels. At the core of the SOA Reference Architecture is the Enterprise Service Bus which delivers all of the inter-connectivity capabilities required to leverage the services implemented across the entire architecture. Transport services, event services, and mediation services are all provided through the ESB. The SOA also contains a set of services that are oriented toward the integration of people, processes, and information through Interaction Services which provide the capabilities required to deliver IT functions and data to end users, meeting the end-user's specific usage preferences. Process Services which provide the control services required to manage the flow and interactions of multiple services in ways that implement business processes. and Information Services which provide the capabilities required to federate, replicate, and transform data sources that may be implemented in a variety of ways. Many of the services in an SOA are provided through existing applications via the Access Services; others are provided in newly implemented components via Business Application Services; and others are provided through external connections to third party systems via the Partner Services. Underlying all these capabilities of the SOA is a set of Infrastructure Services which are used to optimize throughput, availability and performance. IT Service Management Services include capabilities that facilitate the management and security of the deployed services, composite applications, and hardware/storage/network resources. These services also provide the capabilities to monitor the deployed environment to collect both technical and business KPI metrics and present these via appropriate “dashboards” for inspection by appropriate personnel and to help them take the necessary actions to optimize the managed environment or the business service/process.
  • Slide Objectives: This slide focuses on the services perspective, showing how a SOA-based solution is realized within the architecture. Details: · The key aspects of this perspective is to show how the key principles of SOA are realized within the Reference Architecture so as to achieve the necessary alignment of IT with business and providing the flexibility within IT to respond to the agile business changes. The key points: The Services layer is the specification of the services that are used by the service consumers and implemented by the service providers. This layer directly supports the principle of “programming to an implementation not to an interface.” As shown in the reference, atomic services can be exposed directly to consumers, or exposed via a business process; and implemented via service components or directly (via a service façade) through the operational systems. The consumer of the service does NOT know how the services are implemented, which facilitates great flexibility in changing implementations without impacting the consumers. The services layer also shows the ability to compose services to achieve increasing levels of behavior. The business process layers shows the ability to separate collaboration/control behavior and logic from the underlying business behavior and logic that is provided by the services themselves. This approach (especially when defined “declaratively”) supports changing of behavior without the need to re-code the underlying logic. The reference architecture directly handles separation of concerns by providing separate “backplanes” that support integration (the ESB), qualities of services, data architecture and governance.
  • Slide Objectives: The separation of concerns demonstrated in the SOA Ref Arch supports a new programming model, a component based model that allows solutions to be created through the composition of functions implemented as services. And this new programming model is significantly different from the traditional model … it allows mush more interaction and overlap between the business process view and the application program view. Details: The IBM SWG Programming Model derives its SOA technical strategy and vision from the basic concept of a service : “ A service is merely an abstraction that encapsulates a software function.” “ Developers build services, use services and develop solutions that aggregate services.” SWG SOA: Programming Model and Architectural Overview
  • Slide Objectives: This slide provides details on how the programming model supports the SOA lifecycle. Details: · The key points to be made: The design of the SOA-based solution focuses on what we have covered in model and assemble parts of the SOA lifecycle. The programming model further supports the definition and use of best practices via models, patterns, and frameworks. The composite applications are developed by integrating people (user interactions), process (composition) and information (information) with reusable business services (business components.) A common invocation model ensures that the services within the composite applications can collaborate and inter-connect. The SCA provides the standard for supporting this common invocation model and the definition of services in the programming model. The SDO provides the standard for data used by services as part of the composite application.
  • Slide Objectives: This slide (and the next) shows the SOA Reference Architecture in action. This slide focuses on the business driven development aspects Details: · The key points to be made: A good architecture begins with a solid understanding of the business requirements; which in turn require a solid understanding of how the business works today, and how it should work in the future. Models (and the associated tools) document the business requirements (and goals and objectives) and create an “as-is” model of the business process. From these models, we can identify deficiencies and pitfalls and create a “to-be” model for how the business can be improved. These models can then be used to simulate the to-be process to validate cost savings, ROI, and other general improvement parameters. Once optimized and validated, the architect exports the to-be model via UML for further manipulation. The architect uses appropriate tools to transform the business requirements into software system requirements and models. This approach will ensure that the system implementation is driven by business requirements and is fully aligned with the business process model. The architect imports business processes and refines application design, based on best practices and existing assets. An operational model will help the operations team plan the future deployment. The developer implements the application by leveraging best practices including highly productive J2EE capabilities (JSF, SDO) . Built-in code analysis & unit testing capabilities enable developers to fix functional, performance, and security problems at the component level – early in the development cycle. Identifying and fixing problems at the component level greatly reduces the overall cost of delivering high quality applications. The application is validated to ensure that it functions as designed with acceptable performance. The functional and manual testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. The application models are assembled and deployed onto the runtime environment. The Deployment team and the runtime specialists ensure that the appropriate qualities of service are implemented by the infrastructure. The Operations Manager monitors application performance and is automatically notified of problems, enabling fast triage to the right stakeholders (application, DB, network, etc.). Appropriate tools provide a centralized view into the network, systems, middleware, and application performance.
  • Slide Objectives To walk through a deployed composite application in an SOA-based environment to show how the different capabilities in the Reference Architecture work together to support the SOA lifecycle. The scenario is a typical ‘Account Open’ service (exposed as a business process.) This walk through highlights the key principles of separation of concerns, reuse, and loose coupling. Note that the scenario is based on JK Enterprises as the customer. Details The following describes the walk through based on the clicks of the animated slide. This represents the model and assemble part of the solution. Here, we model the ‘account open’ process from a non IT perspective. We can also add some parameters to the process in order to simulate the process. This will help understanding the bottlenecks before the system was implemented. The BPEL output from the model is used by the architect and the developers. Architect looks the requirement to determine how the solution can be built with new and existing resources. Integration developer uses the new and existing services to weave them together as a process implementable in a process engine. Developer builds new services as needed in a J2EE platform. This is now implemented in a process engine that can manage the process E2E. This includes both system as well people touch points. This process is now invoked when a end-user comes to the JK Enterprises site to open an account and submits an application. This request could come from any other channel like IVR / PDA as well This is the beginning of the process. The customer request is written to Account Management System. Process Manager now initiates a ‘credit check’ service which is available from ‘service partner’. (B2B) The response from the application is processed and written to Account Management System. A sweep of all existing data is done to gather further information on the applicant. This is done via the information integrator which queries many forms for existing data to see if this client exists all ready. All this information is presented to an Account Open Officer to make the decision. (There can be several levels of auth. Involved in this step) Customer Account is opened in mainframe Accounting System and Siebel CRM System. This is done using the adapters. Customer is informed of the decision All the while, process manager writes to CEI which is used for Business Monitoring Data from the same CEI is also used for IT level monitoring
  • Slide Objectives: With SOA, standards are important and address various levels of function. Details: At the beginning of the presentation, one differentiator between SOA and previous technology trends was the level of industry wide adoption of open standards. These standards are very important, yet there are a growing number of standards which actually may make this topic somewhat confusing. In fact, the confusion can be mitigated by looking at various categories of standards …. - Infrastructure Standards – these are the standards typically thought of in context of SOA. The Web Services standards etc. - Semantic Standards are increasingly important as various industry consortiums work to standardize common functions and representations in their industries.
  • Slide Objectives: This slide summarizes the Reference Architecture discussion as a way to repeat and reinforce the messages. Details:
  • Slide Objectives: The SOA Roadmap section is next. In this section, we’ll discuss the common considerations important in creating an SOA adoption strategy, the common entry points that we have seen many customers use, and a few examples of the offerings IBM has to help customers get started at whatever entry point is appropriate for them. Details:
  • Slide Objectives: The ultimate goal of SOA is better market return through transformation of the enterprise. Business transformation must be focused on the ability to execute common industry processes in a differentiated way. IT transformation must be focused on the ability to implement business driven changes more quickly into production, to lower coasts, and to partner with the business to drive competitive differentiation Details: In order to achieve these goals it is important to think of SOA adoption at two levels. First, the strategic level … it is important to have a strategic vision or a master plan that can be used by the enterprise as a guideline in to be applied as various interests work together to meet specific business goals. And second, the individual project plans … SOA will never be achieved in one big-bang project. Instead it will be implemented incrementally and the business will demand return at each incremental project step. Consequently, the Roadmap must have individual project plans to meet the most immediate goals of the business and yet created in a way that is consistent with and helps the enterprise move toward the goals articulated in the strategic vision.
  • Slide Objectives: This slide provides the main ingredients of establishing a roadmap for the customers’ SOA journey. Details: The key points to be made: To build a roadmap you need to have a well defined model that describes capabilities (vertical Y axis) against maturity levels (horizontal X axis.) Each cell in this model defines the specific characteristics that an enterprise would display. This is a build chart, which basically shows how we plot a customer’s current state against their desired state. From a catalogue of projects and capabilities, we identify those that will move the customer to their desired state. Then we develop a roadmap that prioritizes these projects and creates a step-by-step process and timeline for getting from A to B. Generally, customers advance further in the lower domains such as infrastructure services and common IT services. Such a roadmap provides the overall blueprint for how an organization will move towards SOA.
  • Slide Objectives. To show IBM’s maturity model that we have developed around Services. Details. The SIMM is an IBM definition of a maturity model around services. It defines 7 maturity levels along several capability domains covering both business and IT. Each cell indicates the characteristic that an enterprise will display for that particular capability in the given maturity level. This is the maturity model that we will use later in the getting started presentation to help organization’s build their own SOA roadmaps.
  • “ This would have saved me six hours yesterday…” Starbucks Coffee "...and that's why IBM in announcing today the introduction of a new kind of platform for information - IBM Information Server." IBM Information Server is a platform that helps you derive more value from the complex, heterogeneous information spread across your systems. It does for information what the application server did for eBusiness, providing core services that can be called on to handle difficult integration and management tasks in a repeatable and reliable way. It provides a single layer of shared services that feed trusted enterprise information to all the people, processes, and applications that need it. The productivity benefits of this new platform as extraordinary - as one of the users at Starbucks remarked about the Beta, "This would have saved me six hours yesterday". Here is another quote from Frank Brooks at BCBS TN: "IBM’s information server vision is very important to us. We need a set of integrated tools that we can use that will provide a seamless interaction with our customers to the data. It’s very important that we are able to leverage this vision because... our customers are becoming more demanding as far as the information that they require, they are also becoming extremely sophisticated in the type of information that they need." "The IBM information server allows us to integrate data in a way that provides meaning and also it provides a single source of information and we use these tools to effectively integrate data so that people can make effective decisions." I don't have any good quantified benefits from the Beta right now. I'll let you know if that changes. Overall, IBM Information Server provides enormous advantages to companies dealing with complex heterogeneous information: A comprehensive, unified foundation for enterprise information architectures, scalable to any volume and processing requirement Rapid service deployment across complex, heterogeneous data sources Auditable data quality and traceability as a foundation for trusted information across the enterprise Metadata-driven integration , providing breakthrough productivity and flexibility for integrating and enriching information Consistent, reusable information services —along with application services and process services, an enterprise essential Accelerated time to value with proven, industry-aligned solutions and expertise Broadest and deepest connectivity to information across diverse sources: structured, unstructured, mainframe, and applications
  • WebSphere Process Server is at the very heart of your business process management solutions. It ensures that the processes you design in WebShere Business Modeler or WID are executed consistently, reliably, securely and with transactional integrity. Built upon open standard it deploys and executes processes which orchestrate services (people, information, systems and trading partners ) with your SOA infrastructure. When combined with the power of WebSphere Business Monitor processes can be optimized to meet changing business requirements, giving the business a competitive advantage. More detailed information Until now, customers have been using various technologies and products to integrate business processes that span people, systems, customers and business partners. These invariably result in a complex, inflexible operating environment and need additional skills and resources. WebSphere Process Server, allows customers to create and deploy new business processes and synchronize business information in multiple business applications on diverse platforms. WebSphere Process Server delivers a unique integration framework that simplifies existing IT. Customers have told us that IT assets have grown with their business, and so is the complexity and manageability. We recognize that and in WebSphere Process Server we deliver an SOA based architecture that deliver one common model for to connect, map and execute the underlying IT functionalities. With this, we simplify integration of business processes by leveraging existing IT assets as reusable services, but without the complexities associated with traditional integration methodologies. One of the biggest challenge for businesses is to have the agility to respond On-Demand to business processes. Unlike the traditional integration methodologies, WebSphere Process Server allows customers to dynamically respond to businesses and adapt to business conditions once deployed. This is made possible with the rich features like Business rules, State machines, Interface mapping available in WebSphere Process Server. Its open standards based services architecture allows customers to change underlying IT assets with minimal impact to business processes Version: 6.0.2 GA Date: 22 December 2006 (Distributed) 30 March 2007 (System Z) Enhanced human-centric BPM capabilities Graphical process view New graphical process display and activity drill-down capability Group work Ability to assign tasks to a team for completion by a single member allow flexible work assignment Ad hoc follow-up tasks and sub-tasks Create ad hoc follow-up tasks and sub-tasks on-the-fly within the context of a process Remote client support Support complex IT environments through remote Web client installation configuration option Web Service interface for tasks Web Services interface for tasks enabling additional workflow client platforms, including .NET, C/C++ New dynamicity features, including administration configuration of endpoints and mediations, as well as dynamic endpoint selection Enhanced flexibility to react to rapidly changing business conditions Modify service endpoint and mediation behavior dynamically without redevelopment and redeployment Cross-product integration WebSphere Service Registry and Repository integration Enables dynamic invocation of existing services at runtime Information Server and SQL support thru BPEL New BPEL activities add support for information management capabilities (including DB2, Information Server, IBM DB2 Content Manager) and SQL Expand the reach of BPM solutions into existing corporate information assets Additional WebSphere MQ SCA binding and new MQ JMS support Native MQ and MQ/JMS bindings enable BPM solutions to better leverage investments in enterprise class messaging transport Event sequencing ensures that business events are processed in the order received Ensures that events are processed in the order in which they occur based on user-specified criteria Enhancements to relationships, state machines, business rules and mappings Relationships Improved performance and usability for managing relationships through cursor support and API enhancements Mappings Availability of new data binding samples Business State Machines Enhanced flexibility with the new ability for correlation creation on response Added visibility into BSM instances with new queriable BSM variables, such as current state name and correlation set information Simplified administration with BPC Explorer support for BSM Business Rules Support more common business rule logic scenarios, including specifying initialization logic for a decision table, “otherwise” clause on decision table conditions and using “return” option available in rule sets to force execution of rule list to end Visibility to business rule changes through new audit capabilities which track changes and who made them New business rule import/export capability greatly simplifies the process of maintaining consistency between server or environment instances
  • ESB provides mediation over and above Messaging layer – transforms data – exchanges protocols, recognises and handles business events – for both web services and non web services – or the ESB is fairly unless for most real environments When trying to implement end to end connectivity of assets as part of a SOA, there are times when having a messaging backbone, reliably delivering information unchanged from any point, to any other point in the enterprise might not be enough. Adding an Enterprise Service Bus on top of the messaging backbone provides additional value to the business, allowing it to be more flexible, and responsive. How does it do this? Well, an Enterprise Service Bus, an ESB, further reduces the complexity of applications by offloading mediations and other functions not integral to business logic. Things like transforming data, exchanging protocols, recognizing and handling business events Therefore you can take this code out of the applications and services and let your developers focus on higher value added business logic to give you that competitive advantage. It also allows you to get out of the business of spending so much time coding the spaghetti of custom point to point interfaces between numerous applications as you only need to connect once per application into an ESB. Building on top of the reliable and secure messaging backbone and connecting all parts of the SOA, IBM provides the most comprehensive and complete ESB offerings for an SOA solution for any sized enterprise. We recognized that different companies have different requirements and that even within one company different departments have different needs. Therefore IBM offers two products as ESB solutions. One is called WebSphere ESB, which is the ESB for integrating primarily Web Services and standards based assets, particularly where the latest Web Services standards are to be used, and fast simple connectivity between assets is called for. IBM’s other solution is the advanced ESB, called WebSphere Message Broker. Proven for many years in the market, it is highly capable of integrating any type of asset across your heterogeneous enterprise, delivering high performance and high throughput, while connecting and integrating assets that could be both web services or non-services, non-standards based assets. Its robustness and flexibility, and the range of its potential functionality, make this truly the only advanced ESB available, transforming between multiple protocols, and different data formats, handling any type of business event, and securely connecting all assets, even those which you might have hoped would be easy to connect, such as messages coming from other JMS messaging engines. JMS is a programming interface and unfortunately there is no standard for connecting JMS runtimes together to exchange messages reliably. At IBM we have recognized this problem and to allow us to provide a true end to end connected SOA, even involving other 3rd part JMS engines, our customers can now use WebSphere Message Broker as a mediator between any JMS provider. This ensures that your business data is delivered reliably and securely where it is required, in the right format, at the right time. Let me say it another way, WebSphere Message Broker provides the industry’s first and only solution to connect JMS providers into one messaging network. WebSphere Application Server also has a powerful JMS messaging engine and extensive support for Web services standards so you can connect applications and re-use your existing assets. That JMS engine is well aligned with WebSphere MQ and the two can interoperate seamlessly for connectivity to more heterogeneous environments
  • For a faster time to market, utilize the business catalog to find ready made business models and the best practices available around most industries The SOA Business Catalog is a comprehensive, online resource for clients to find IBM and IBM Business Partner SOA Assets validated for enablement onto IBM’s SOA Foundation Products. The catalog includes adapters, web services, process models, plug-ins, and other assets to help you build your SOA. The catalog will be live on June 13 th with over 300 assets and we have plans to grow the catalog to over 3000 assets that span across 13 different industries.
  • Main point: Introducing the WebSphere Service Registry and Repository which completes the Service Lifecycle Management by enabling dynamic binding of services at runtime and enforcing policies and acting as a system of record for service metadata The lifecycle of a service is similar to the lifecycle of an application with one new major addition. Since Services will be used across many Lines of Business, and the need to reuse Services is the major value of SOA, there is a new requirement to be able to quickly and easily discover services as new sub-systems are being created. Services may be available internally, externally, under development or in-plan. Finding the Service and its owner and status will be critical. To be able to successfully perform the discovery of services, there is a requirement to be able to look and find where Services are either being developed or being used. In SOA, this is called a repository and/or registry. A repository is where Services and related SOA Artifacts, such as policies can be stored. A registry is someplace where you can register that you have a service and a pointer to that service. Definitions: Service metadata is anything used to talk about services - such as descriptions, owner etc. Artifacts are files such as XML docs or XSDs or WSDL docs.  Metadata is a generic concept, ie information about an artifact: a service, a wsdl, an xml schema, a policy etc. A service, then is an example of an artifact (a set of artifacts actually) a coordination of WSDL, SCDL, xsd  Once the processes and infrastructure for SOA Governance are in place, the next requirement is to be able to keep track of the services, processes and policies associated with SOA. The approach that is needed is to have a database that can store the SOA related information. In SOA, there is the requirement for a Service registry and repository. The registry component allows artifacts, such as services and policies to have an entry that has the information about the artifact. This allows for the searching of the registry to find out about services or metadata. The registry can also notify people of changes or potential changes happening to the artifact. During Service Development and Delivery, there is a need to discover services that may already supply a function. In addition, the Service Registry can have policies or processes that are needed to govern the development process. Once a Service is delivered the management of that service, including potential changes can be tracked and controlled by the registry.
  • Slide Objectives: In developing the Strategic Vision as well as the incremental project plans, there are several dimensions that are important to consider. Details: SOA adoption must be done in the context of the enterprise – there isn’t a “one size fits all” model. It is important to consider the business drivers, the current architecture and organization, as well as the readiness (both organizational and operational) of the enterprise to handle the adoption and transformation successfully.
  • Slide Objectives: The SOA Governance section is next. In this section, we will define governance, motivate why its needed and discuss the main capabilities needed to support it. Details:
  • Slide Objectives: This slide defines SOA Governance in the context of IT Governance. Details: Governance establishes decision-making rights along with the associated policies and mechanism to control and measure how these decisions are carried out. SOA governance focuses on the decisions across the entire service lifecycle to enable organizations to realize the business benefits of SOA and mitigate the risks inherent in SOA adoption. Specifically, SOA Governance defines the principles, processes, and roles required to manage, use and update the SOA. The following articulates the key objectives of SOA Governance: The primary goal of SOA Governance is to derive maximum value from Service Oriented Architecture by promoting its implementation, use and evolution. SOA Governance provides the basis to ensure that SOA (and its associated models) are managed and updated in response to changes in business needs and available technologies. SOA Governance is fundamental in enabling an enterprise to make conscious decisions about IT, the acquisition of IT assets, and the design and implementation of new IT solutions to meet business needs There are two fundamental aspects of governance. The first aspect involves the processes established by an organization to determine who is empowered to make certain decisions. The second aspect includes the mechanisms and policies that are used by the organization to measure and control the way those decisions are implemented. Together, these aspects form a governance framework. Governance is usually viewed as an executive function while the execution of the governance framework is the responsibility of managers. For example, governance determines the decision rights for how much the enterprise invests in technology. IT management is responsible for deciding the actual amount invested in a given year and the areas in which the money is spent. IT governance and SOA Governance: IT governance aligns IT activities with the goals of the organization as a whole. This subset of governance includes the decision-making rights associated with IT investment, as well as the policies, practices and processes used to measure and control the way IT decisions are prioritized and executed. Adoption of an SOA raises new issues both in IT decision rights and in measurement and control. IT organizations must consider which operation is best suited to deploy different services under varying conditions and be able to monitor that the services are in fact enhancing the business value. SOA governance is an extension of IT governance that focuses on the life cycle of services and composite applications in an organization’s SOA. Deploying an SOA frequently serves as a catalyst for an organization to start thinking about improved corporate and IT governance and how to best implement SOA governance practices.
  • Slide Objectives: This slide motivates the need for SOA Governance. Details: As should be evident from this presentation, SOA is the key enabler of the alignment of IT to business needs for an enterprise and in facilitating the enterprise to react to its changing business environment in a flexible and agile manner. An enterprises’ SOA journey is a “team sport” requiring all parts of the enterprise to be engaged in its successful implementation. SOA Governance can help ensure that the enterprise realizes its ROI from SOA, mitigate the inherent risks in such an enterprise-wide implementation, and facilitate the team to collaborate and work effectively.
  • Slide Objectives: This slide describes the incremental and iterative SOA Governance lifecycle. Details: The SOA Governance lifecycle facilitates an incremental and iterative approach of determining the focus and scope of SOA governance, defining the governance model to address the scope, implementing the governance model, and measuring & monitoring its effectiveness. This lifecycle is supported by the Governance processes and emerging practices which makes it easy to do things in the right way and difficult to do it the wrong way. The following describes each of the phases: Plan The planning phase of building an SOA governance framework focuses on understanding the overall scope of the governance opportunity within the organization and identifying areas for improvement. This phase includes: • Committing to a strategy for SOA in the context of the overall business goals and IT strategy • Explicitly determining the level of IT and SOA capabilities • Articulating and refining the vision and strategy for SOA • Reviewing current governance capabilities and arrangements Most of these activities are people-centric and involve extensive collaboration. The required interaction can be simplified with sophisticated business modeling tools, as well as collaboration tools such as instant messaging, e-mail, Wiki, dashboards, calendaring and role-based portals. Define Once the opportunities for improved governance are identified, business and IT people can work together to define and modify the current governance arrangements and mechanisms. New approaches to creating policies should be agreed on at this time. Other important governance decisions and mechanisms created during this phase may include: • Establishing or refining an SOA Center of Excellence • Defining any additional capabilities required, such as upgrades to the IT infrastructure • Conducting staff training on an ongoing basis • Agreeing on policies for service reuse across lines of business • Putting funding mechanisms in place for encouraging this reuse • Establishing mechanisms to guarantee service levels These mechanisms and SOA governance decisions can speed the process of translating business design into IT design during the assembly phase of an SOA project. Enable Solutions to governance needs are put into action during this phase of establishing the SOA governance framework. These solutions may include deployment of new or enhanced governance arrangements. It is likely that communication mechanisms and education mechanisms will be rolled out to entrench the new governance arrangements within both the business and the IT decision-making communities. Governance activities within this phase influence how SOAs are deployed by enabling the policy enforcement infrastructure. Measure During this phase, governance arrangements and mechanisms that were identified in the Define phase and deployed in the Enable phase are monitored. Activities occurring in this phase help ensure that the goals of the new governance framework are in fact being realized. If not, there is an opportunity for the business to refine and enhance its governance effectiveness by initiating a new cycle to enhance the SOA governance framework.
  • Slide Objectives: Move to Summary …. Details:
  • Slide Objectives: Final slide summarizing the presentation. Details:
  • Main Point: The time to start is now! IBM SOA Assessment tool evaluates your SOA maturity and gives you valuable information and actionable recommendations – on-line or on site. IBM can then follow up on this assessment with either an IT focused or business focused workshop to help you lay out a roadmap to get from where you are now to where you want to go with SOA. A great way to get started with SOA is to use the IBM SOA Assessment tool. You can use the tool on the web yourself at ibm.com/soa or we bring it to you on-site to walk through the questions and results. Either way, you’ll receive not only an evaluation of your SOA maturity and some things that you can take advantage of with what you already have, but also actionable recommendations customized to your level of SOA maturity so you can help lay out a roadmap for where you might want to go in the future. This is all based on IBM’s extensive experience in real customer engagements and is meant to impart some of this experience to users. To get into more specifics IBM’s subject matter experts and SOA architects can sit down with you at either a business focused or IT focused workshop to spell out the details for implementing a project to achieve your goals. Regardless of the scope of your SOA goals, IBM’s SOA workshops can help you spell out your specific next steps. Maturity Model info: Main point: The SOA Maturity Model helps customers take a project-based approach to SOA to get from where they are today to where they want to be. It progresses from introductory levels of wrapping existing assets for modest reuse all the way up to being able to adapt both business models and the IT systems that support these models dynamically in response to rapidly changing opportunities and threats. The Maturity Model examines both the business philosophy and the IT capabilities separately to represent both domains of service orientation. This maturity model is a simplified view of IBM’s Service Integration Maturity Model (SIMM) which is used by our services teams in SOA engagements and implementations. SIMM has been in use for quite some time and has garnered extensive analyst and industry praise for its utility in representing SOA maturity. It will soon be contributed to the Open Group to encourage industry-wide consensus on an SOA Maturity Model. Details on columns and rows: Ad Hoc Characterized by improvised linkages between applications. While Web services may in some cases be in use, decisions about connecting applications tend to be made on a case-by-case basis Systematic Characterized by standardized service interfaces with robust connectivity. While application silos still exist, users are beginning to look at their IT assets as services and are connecting them in a more consistent manner, usually through an enterprise service bus for interoperability across a heterogeneous environment. Infrequent use of modeling. Composite Characterized by assemblies of reusable services drawing on functionality from multiple source. The business has a sizeable inventory of reusable services – newly created services and service-enabled assets from core systems. These services are linked together to form virtual “composite” applications that draw upon functionality contained in numerous sources and typically support horizontal business processes. Dynamic Characterized by event-driven reconfiguration of services. This very advanced state involves a holistic approach to transformation and business management by alignment of strategic and operational objectives with business activities and supporting IT services. Abundant composite applications span the business and extend beyond to external trading partners. Business Domain The mindset, philosophy, and commitment to the principles of looking at the business as a linked portfolio of service. This includes governance and oversight of SOA projects. A key element of the business domain is to what extent line of business leaders take a componentized view of the business functions in their organization. IT Environment The ability to understand and support business needs through flexible technology and the design patterns in place through the company’s applications, architecture, and infrastructure. This is largely a measure of the prevalence, quality, and organization of services and the ability to quickly and economically assemble them to accomplish valuable tasks.

SOA Architect Summit SOA Architect Summit Presentation Transcript

  • Service Oriented Architecture C. Mohan, Ph.D. IBM Fellow and IBM India Chief Scientist [email_address] http://www.almaden.ibm.com/u/mohan/
    • Introduction
    • SOA Reference Architecture
    • SOA Roadmap
    • SOA Governance
    • Summary
    Agenda
  • The Basics: What is SOA? … a service? A repeatable business task – e.g., check customer credit; open new account … service oriented architecture (SOA)? An IT architectural style that supports integrating your business as linked services “ Anything that changes can do that much better if the system is architected in SOA.”
  • SOA Delivers Business Value … Today A Recent Study from IBM SOA Engagements
    • 97% justified SOA projects based on cost savings & impact to profitability
    Source: IBM Institute for Business Value “The Business Value of Service-Oriented Architecture” 2006 The IBV studied a subset of engagements and found: 100% realized improved flexibility 71% reduced risk 51% experienced increased revenue 97% 100% 51% 71%
  • Why IBM for SOA? Infrastructure Know-how & best practices Skills Partners IBM understands service orientation and your business
    • Unmatched breadth and depth of products
    • Over $1B/yr invested in SOA
    • Leadership in open standards & 300+ SOA-related patents
    • Thriving ecosystem of partners (ISVs, SIs, Resellers)
    • 1200+ partners in SOA community
    • Expertise in aligning business and IT processes
    • SOA consultants, architects and IT specialists
    • Dozens of SOA-enabled business solutions
    • Extensive Industry experience and best practices
    • Over 1800 customers worldwide
    • SOA Entry Points
    Governance
    • Proven Governance & best practices
    • IBM SOA Governance & Management Method that spans services lifecycle
  • Customers Realize IBM SOA Value Across Large Enterprises & SMB 10 of the world's 10 biggest banks 10 of the world's 10 biggest auto manufacturers 80% of the biggest US health plans 9 of the world’s 10 biggest telcos 8 of the world's 10 biggest insurers 4 of the world's 10 biggest retailers 90 SMB references 52% of all federal Governments Half of the world’s 30 biggest electronics companies “ IBM has a strong vision for SOA, with a broad set of enabling technologies and solution entry points. IBM has the most-comprehensive sets of SOA capabilities on the market. Its internal SOA center of excellence is anchored in BCS but stretches to encompass software and services.” Gartner Evaluates IBM, David Cearley October 10,2006
  • Service Oriented Architecture Different Things to Different People A programming model complete with standards, tools, methods and technologies such as Web services Capabilities that a business wants to expose as a set of services to clients and partner organizations An architectural style that requires a service provider, requestor and a service description. It addresses characteristics such as loose coupling, reuse and simple and composite implementations Implementation Architecture Business Operations A set of agreements among service requestors and service providers that specify the quality of service and identify key business and IT metrics Roles
  • The SOA Lifecycle
    • Gather requirements
    • Model & Simulate
    • Design
    • Discover
    • Construct & Test
    • Compose
    • Integrate people
    • Integrate processes
    • Manage and integrate information
    • Manage applications & services
    • Manage identity & compliance
    • Monitor business metrics
    • Financial transparency
    • Business/IT alignment
    • Process control
  • SOA and Enterprise Architecture: A Common Goal Function (Service Definition) Security & Compliance Performance & Quality (KPI) Accelerate Time to Market Increase Revenue Reduce Costs Business Objectives IT Objectives Aligning Business and IT Objectives Enterprise Architecture
      • Reference
      • Architecture
    Governance Roadmap
  • SOA: The Focus of the Enterprise Architect Deliverable Description SOA Reference Architecture The SOA Reference Architecture defines a reference framework and corresponding IT principles for SOA implementation projects Overview SOA Governance Model The SOA Governance Model defines the decision rights along with the associated measurements and controls SOA Roadmap The Roadmap is used to create a tailored transition plan for moving toward the SOA Reference Architecture Strategic Vision Incremental Adoption
  • Agenda
    • Introduction
    • SOA Reference Architecture
      • Providing a comprehensive model
    • SOA Roadmap
    • SOA Governance
    • Summary
  • IT’s Architectural Evolution: Making IT More Responsive Services (SOA) Monolithic Architectures Pre 1950’s To 1960’s 1970’s to mid 1980’s Mid 1990’s to early 2000’s Today Late 1990’s Sub-routines /Remote Procedure Calls Remote Object Invocation Message Processing Enterprise Application Integration (EAI) 1980’s to mid 1990’s Increasing Modularity to Achieve Flexibility
  • SOA: The Next Step on the Connectivity Evolution Message Queuing Abstracts the connectivity logic from the application Message Brokering Abstracts the connectivity + mediation logic from the application Service Orientation Reduces application to its core business functions (i.e. a service) Application Application Direct Connectivity All connectivity, mediation and additional logic buried in the application Application Increasing Modularity to Achieve Flexibility Application Services Connectivity, mediation & process-control logic Mediation & process-control logic Process-control logic Connectivity logic Connectivity and mediation logic Connectivity, mediation & process-control logic Lines of code
  • SOA Reference Architecture Supporting the SOA Lifecycle Apps & Info Assets Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services Integrated environment for design and creation of solution assets Monitor, manage and secure services, applications & resources Facilitates better decision-making with real-time business information Enables collaboration between people, process & information Orchestrate and automate business processes Connect with trading partners Build on a robust, scaleable, and secure services environment Facilitates interactions with existing information and application assets ESB Facilitates communication between services IT Service Management Infrastructure Services Optimizes throughput, availability and performance Manages diverse data and content in a unified manner
  • SOA Solution Layering Leveraging the SOA Reference Architecture Atomic Service Composite Service Registry Services atomic and composite Operational Systems Service Components Consumers Business Process Composition; choreography; business state machines Service Provider Service Consumer Integration (Enterprise Service Bus) QoS Layer (Security, Management & Monitoring Infrastructure Services) Data Architecture (meta-data) & Business Intelligence Governance Channel B2B Packaged Application Custom Application OO Application
  • A New Programming Model Supporting the SOA Abstraction Layering Business Expertise Technical Expertise Limited Overlap Users Define/refine business processes Developers Program applications using core technologies Traditional Software Development Service-Oriented Development Application Developers Translate business processes into applications by assembling and configuring building blocks Extensive Overlap Service Developers Create application building blocks – patterns, templates, and components using core technologies Technical Expertise Users Define/refine business processes Business Expertise
  • SOA Programming Model Aspects Design ( Models, Patterns, Templates, Policy ) Composition Business Components Information User Interaction Invocation
    • Composition of Business-level Applications
      • Wired assembly of services to form business-level applications, workflows, and business orchestration
    • Information
      • Built-in access to service state, disconnected service-data exchange, information composition and transformation
    • Business Components
      • Composable and reusable services
    • User Interaction
      • Dynamic support for people integration into the business design
    • Invocation
      • Loosely-coupled call-style and event-driven interconnection of services with built-in support for topology transparency, mediation, and brokering featuring standards-based interoperability
    • Design
      • Focus on business design modeling, simplification, and role-based collaboration
      • Use of declarative policy to control execution behavior and relationships
  • Business Driven Development An Iterative, Business-focused Development Process Continual Process Improvement Observation Model (KPIs) Requirements Deploy
    • Deployment Team
    • Platform-specific Runtime Specialists
    • Manage Quality of Service
    • Manage Runtime Platforms
    • Business Operations Analysts
    • IT Operations Managers
    • Monitor Business Results
    • Manage IT Performance
    • Create Business and IT Dashboards
    Manage Assemble
    • Development Team
    • Integration Developers
    • Testers
    • Choreograph Services
    • Develop New Services
    • Configure Human Task Manager
    • Develop User Interface
    • Test
    Team Unifying Platform Model Model Business Requirements
    • Business Analysts
    • Software and Data Architects
    Model Software Architecture Unified Modeling Language Run-time Statistics WSDL EAR, DDL Events Business Process Execution Language
  • Separation of Concerns The SOA Reference Architecture in Action Open Account Approved Apps & Info Assets Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services Integrated environment for design and creation of solution assets Manage and secure services, applications & resources Facilitates better decision-making with real-time business information Enables collaboration between people, processes & information Orchestrate and automate business processes Manages diverse data in a unified manner Connect with trading partners Build on a robust, scaleable, and secure services environment Facilitates interactions with existing information and application assets ESB Facilitates communication between services IT Service Management Infrastructure Services Optimizes throughput, availability and performance EJBs Federated Query DB Access DB Access Siebel Adapter CICS Access Business Dashboard Portal Community Manager IT Management Console
  • Key Standards for SOA SOA and Web Service Standards Business Services: Service Offerings and Components e.g. Book Flight, Low Fare Search, Update PNR Data Evolving Industry Semantics (ACORD, FIXML, OTAXML, UCCNet, ebXML) Infrastructure Standards Semantic Standards Security (WS-SEC) Transactions (WS-Tx) Management Service Orchestration (WS-BPEL) Service Discovery (WSIL, UDDI, RAS) Service Invocation & Messaging (WS-I, SOAP) Service Description (WSDL, RAS) XML (Infoset, Namespace, Schema) Network Protocol (HTTP, SMTP, Other) Service Interaction Components (WSRP, JSR 168)
    • Linkage between business and IT through support of the entire SOA Lifecycle
    • Connectivity and Service Isolation through the Enterprise Service Bus
    • Separation of Concerns/Modularity for incremental adoption
    • Component-based Programming and Solution Development
    • Business and IT Monitoring and Management
    • Open Standards
    The SOA Reference Architecture and its Key Principles Providing IT Flexibility to Meet the Demands of Business Apps & Info Assets Business Innovation & Optimization Services Development Services Interaction Services Process Services Information Services Partner Services Business App Services Access Services ESB IT Service Management Infrastructure Services
  • Agenda
    • Introduction
    • SOA Reference Architecture
    • SOA Roadmap
      • Relating business and IT objectives
    • SOA Governance
    • Summary
    • Two Primary Roadmap Perspectives
    • Strategic Vision Business and IT statement of direction which can be used as a guideline for decision making, organizational buy-in, standards adoption
    • Project Plans Implementation projects to meet immediate needs of the current business drivers
    SOA Roadmap: A Plan for Adopting SOA
    • SOA Goal
      • Market return through transformation: quicker time to production, lower costs, competitive differentiation
    Revenue and Profit Time Strategic Vision Market Return through Transformation Incremental Adoption
  • Roadmaps: Building Plans In Context Infrastructure Services Business Function Services Common IT Services Information Services Domain of Capability Scope of Services Partner Collaboration Dynamic Partner Collaboration Partial Integration Enterprise Integration Discrete Business Goals and Imperatives Identify required capabilities and initiatives Determine future state Develop Roadmaps Assess current state
    • Assess your current maturity, across multiple dimensions
      • Business
      • Methodology
      • Technical
    • Establish targets for where you want to be
    • Document important goals and metrics for transitions across the maturity dimensions
    • Recognize that aspects of the Vision may shift with experiences gained
      • Adopt regular checkpoints for Vision re-assessment
    Getting Started Requires Vision IBM’s Service Integration Maturity Model provides a guide for establishing a Vision
  • Service Integration Maturity Model (SIMM) Silo Services Composite Services Virtualized Services Dynamically Re-Configurable Services Componentized Integrated Level 1 Level 4 Level 5 Level 6 Level 7 Level 3 Level 2 Applications Methods Organization Infrastructure Architecture Business View Modules Services Process Integration via Services Dynamic Application Assembly Components Objects Structured Analysis & Design Service Oriented Modeling Service Oriented Modeling Grammar Oriented Modeling Component Based Development Object Oriented Modeling Ad hoc IT Governance Emerging SOA Governance SOA and IT Governance Alignment SOA and IT Governance Alignment Ad hoc IT Governance Ad hoc IT Governance SOA and IT Governance Alignment Service Oriented Modeling Process Integration via Services Platform Specific Platform Specific Platform Neutral Dynamic Sense & Respond Platform Specific Platform Specific Monolithic Architecture Emerging SOA Grid Enabled SOA Dynamically Re-Configurable Architecture Component Architecture Layered Architecture SOA Platform Specific Function Oriented Service Oriented Service Oriented Service Oriented Function Oriented Function Oriented Service Oriented
  • IBM Information Server A Complete Information Infrastructure
    • Rapid information service deployment
    • Auditable data quality and traceability
      • Foundation for trusted information
    • Metadata-driven integration
      • Breakthrough productivity and flexibility
    • Consistent, reusable information services
    • Accelerated time to value
      • Proven, industry-aligned solutions and expertise
    “ Effective SOAs include robust data services within an enterprise information management enabling infrastructure.” Gartner Inc, 2006 People, Processes, Applications Get Customer Info Get Consolidated Risk Get Claim Details
  • WebSphere Process Server The Engine Room of Business Process Management
    • Robust execution of business processes
    • Supports all aspects of process integration
    • Rapid process change ensuring business agility
      • Reuse existing services
      • Business rules can change dynamically
    • What’s New
      • Enhanced human-centric BPM capabilities
      • New dynamicity features
      • Cross-product integration
      • Enhancements to relationships, state machines, business rules and mappings
  • WebSphere ESB & WebSphere Message Broker Enable Every Kind of Application and Data to Participate in SOA
    • Routing messages between services
    • Converting transport protocols
    • Transforming message formats
    • Handling business events from disparate sources
    WebSphere ESB : The ESB for standards and web services integration WebSphere Message Broker : The advanced ESB for web services and non web services assets
    • 500+ Reusable Assets
    Banking & Financial Markets
    • 400+ Reusable Assets
    Insurance IBM SOA Business Catalog The place to find your SOA assets
    • 200+ Adapters
    • 250+ Portlets
    • Rational Patterns and Plug-ins
    • SWG, GTS and GBS SOA Services
    Cross Industry ibm.com/soa/soabusinesscatalog
    • 200+ Reusable Assets
    Government 3665+ IBM & Partner Assets (Over 67% Partner Assets)
  • WebSphere Service Registry and Repository Enabled SOA Governance Infrastructure and Management In Support of SOA Monitor Operational Policies Service Development and Delivery Management Enforce Process and Policies WebSphere Service Registry and Repository
      • Discover services and metadata from other registries
      • Publish newly developed services and artifacts
      • Notify clients of changes
      • Organize service metadata with classification and lifecycle support
    “ We are witnessing the ‘industrialization of software’ with the introduction of products, new as well as enhanced versions, and new services under IBM’s new Service Oriented Architecture package…This is very much a best practices-driven approach to technology … The fact they are bringing the registry and repository together is a good move, is a good approach. That is new.” Judith Hurwitz, for eChannelLine, October 3, 2006 Publish Find Enrich Govern Manage
    • Business Drivers
      • Accelerate time to market
      • Reduce costs
      • Increase revenue
      • Reduce risk and exposure
    • Organizational Readiness
      • Executive support and sponsorship
      • Skills
    • Current Architecture and Environments
      • Build and Runtime
      • Degree of heterogeneity
    • Operational Readiness
      • Ability to monitor and manage current operations
      • Integration of monitoring functions into production environments
    SOA Adoption Considerations
  • Agenda
    • Introduction
    • SOA Reference Architecture
    • SOA Roadmap
    • SOA Governance
      • Executing for success
    • Summary
    • Establishing decision making rights associated with IT
    • Establishing mechanisms and policies used to measure and control the way IT decisions are made and carried out
    What is Governance? SOA Governance is a catalyst for improving overall IT Governance SOA Governance Extension of IT governance focused on the lifecycle of services to ensure the business value of SOA IT Governance
    • Realize business benefits of SOA
      • Business process flexibility
      • Improved time to market
    • Mitigate business risk and regain control
      • Maintaining quality of service
      • Ensuring consistency of service
    • Improved team effectiveness
      • Measuring the right things
      • Communicating clearly between business and IT
    Why SOA Governance Matters SOA Governance empowers teams to innovate
  • SOA Governance Lifecycle
    • Define the Governance Approach
      • Define/modify governance processes
      • Design policies and enforcement mechanisms
      • Identify success factors, metrics
      • Identify owners and funding model
      • Charter/refine SOA Center of Excellence
      • Design governance IT infrastructure
    • Monitor and Manage the Governance Processes
      • Monitor compliance with policies
      • Monitor compliance with governance arrangements
      • Monitor IT effectiveness metrics
    • Enable the Governance Model Incrementally
      • Deploy governance mechanisms
      • Deploy governance IT infrastructure
      • Educate and deploy on expected behaviors and practices
      • Deploy policies
    • Plan the Governance Need
      • Document and validate business strategy for SOA and IT
      • Assess current IT and SOA capabilities
      • Define/Refine SOA vision and strategy
      • Review current Governance capabilities and arrangements
      • Layout governance plan
  • Agenda
    • Introduction
    • SOA Reference Architecture
    • SOA Roadmap
    • SOA Governance
    • Summary
    • Understand your business goals, drivers, and context
    • Understand your current environment
      • Development, Runtime, and Management
    • Establish a Roadmap
      • Find appropriate starting point
      • Determine the development and runtime requirements
        • Leverage Separation of Concerns and the SOA Programming Model
    • Establish Governance
      • Appropriate for your company culture and environment
    SOA for the Enterprise Architect …
    • Establish a Strategic Vision at the appropriate level
    • Assess and address capability gaps:
      • Skills
      • Processes
      • Architecture
      • Infrastructure
      • Application
    • Identify a pilot project
      • Extending Assets
      • Collaboration
      • Application Integration
      • Business Process Management
      • Information Integration
    • Execute the project
    • Approach adoption incrementally
      • Introduce infrastructure, processes as needed – SOA is not about infrastructure and processes, it’s about enabling organizations to be agile in solving business problems
    • IBM is here to help
    Summary
  • Take the Next Step with SOA TODAY! SOA Maturity Model, Assessment Tool and Workshops to Help Project Selection Receive actionable recommendations customized to your level of SOA maturity Free!
    • Lay out your specific game-plan in detail:
    • Line-of-business or IT-led SOA Workshops
    • Overview, assessment, modeling, roadmap, architecture, project plans, benefits analysis, …..
    • On-line at ibm.com/soa/assessment
    • … ..or face to face with an IBM representative by mailing [email_address]
    • Available in 10 languages!
  • Thank You Merci Grazie Gracias Obrigado Danke Japanese French Russian German Italian Spanish Brazilian Portuguese Arabic Traditional Chinese Simplified Chinese Hindi Tamil Thai Korean