Presentation is loading. Please wait.

Presentation is loading. Please wait.

SOA Tools Landscape ... across Business and IT SOA & End-2-End Business Driven Development using Java, Web Services, Modeling, BPM, Portal, Web 2.0,

Similar presentations


Presentation on theme: "SOA Tools Landscape ... across Business and IT SOA & End-2-End Business Driven Development using Java, Web Services, Modeling, BPM, Portal, Web 2.0,"— Presentation transcript:

1 SOA Tools Landscape ... across Business and IT SOA & End-2-End Business Driven Development using Java, Web Services, Modeling, BPM, Portal, Web 2.0, Legacy & more… Go to for presentations, demos, tutorials and other resources Sr. Consulting Developer/Architect (IBM Certified SW IT Specialist Profession) for more resources

2 Prioritize Plan Manage Measure
The Business Driven Development Lifecycle IBM Rational Software Development Platform Prioritize Plan Manage Measure Business End User Executive Model the Business Define Requirements Analyst Operations Manager Optimize Govern Architect Design Application Support Project Manager Manage change & assets Manage Developer Last updated: 12/18/04 The business-driven development life cycle is iterative in nature. Each iteration combines a mix of analysis, design, construction and testing activities and results in a demonstrable form of the software that can be validated and refined by users. Producing multiple iterations reduces project risk by providing tangible checkpoints along the pathway to a complete solution. A typical iteration includes the following steps. Model the Business Process IBM solutions enable you to capture current business activities and workflows and simulate alternative scenarios to determine the best opportunities for business transformation. Analyze Requirements Once a solution has been identified, the next step is to define its supporting business and IT requirements. IBM solutions help you generate a financial analysis for your proposed solution and document both its business and technology requirements. By modeling user interactions using the industry-standard UML, your team will share a common and precise understanding of proposed changes. Design and Construct The next step is to translate requirements into technology solutions. Because no single tool fits all team needs, IBM offers the broadest spectrum of code-based, model-driven and rapid application development solutions for developing high-quality software. You choose the toolset optimized for your technology environment, skill level and development paradigm. Test Each iteration is validated to ensure that it functions as designed with acceptable performance. IBM testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. Deploy IBM deployment tools support a managed approach to planning and executing migrations to your production environment. Automated provisioning and configuration management capabilities ease the implementation of coordinated changes to business processes and IT systems. Manage Once deployed, IBM monitoring tools monitor applications and essential system resources across your multiplatform environment to detect potential problems and automate recovery from critical situations. A closed-loop development cycle provides developers, operations managers and network engineers with a consistent set of correlated data to pinpoint application problems and facilitate their rapid repair and redeployment. Optimize Successful organizations not only automate business processes, but also monitor their execution and dynamically adjust them in response to real-time feedback. A performance-based feedback cycle allows you to compare the projected value of an investment to actual business results and make the necessary adjustments to maximize business value. Construction Deployment Manager Deploy SW Quality & Testing Tester Operations Development Optimize Iterate

3 Quick Reference: End-2-End SOA Tools & Server Middleware
SOA Overview SOA Business View SOA tools bridge the gap between business and I/T (i.e. common language of “Process Integration”) SOA Solution Space Lifecycle [ Model > Assemble > Deploy > Manage > Governance ] Roles [ Analyze > Architect > Develop > Integrate > Orchestrate ] SOA Tools In Action [Model] Analyze > Business Process Modeling with WebSphere Business Modeler (WBM) Architect > Application Architecture Modeling with Rational Software Architect (RSA) [Assemble] Develop > Service Implementation with Rational Application Developer (RAD) Integrate > UI, Data, Service and Enterprise Integration with RAD related tools Orchestrate > Service Orchestration with WebSphere Integration Developer (WID) SOA Infrastructure [Deploy] SOA Services Runtime with WebSphere Process Server & ESB SOA End User Experience with WebSphere Portal Server [Manage] WebSphere Business Monitor and Tivoli Composite Application Monitors [Governance] IT View: SW development process/project/portfolio management (RUP) and Tivoli Systems/Service Monitoring Business View: ROI controls and KPI visibility through business-friendly dashboards (i.e. WebSphere Business Monitor)

4 SOA Across Business and IT
Mod 1 Mod 2 WID 1 RSA RAD Java WS RAD Mkt Sim WID Wire WID Wire 2 ProcPort RPM BizDemo SOA Across Business and IT Business Models Identify Process Tasks How do I optimize my business processes? Business and I/T can use a common language a.k.a. “Process Integration” # of Business Process Tasks = # of IT Services (aka Granularity) How do I integrate to my existing systems? I/T Components exposed as SOA Services

5 Using SOA to Bridge the Gap Between Business and I/T The SOA Lifecycle
Discover Construct & Test Compose Integrate people Integrate processes Manage and integrate information Gather requirements Model & Simulate Design Our customers have told us that they think about SOA in terms of a lifecycle. They start in the Model phase by gathering business requirements and designing their business processes. Once they have optimized the business processes, they implement it by combining new and existing services. The assets are then deployed into a secure and integrated environment for integrating people, processes and information. Once deployed, customers manage and monitor from both an IT and a business perspective. Information gathered during the Manage phase is fed back into the lifecycle for continuous process improvement. Underpinning all of these lifecycle stages is governance which provides guidance and oversight for the SOA project. Manage applications & services Manage identity & compliance Monitor business metrics Financial transparency Business/IT alignment Process control

6 SOA is a Team Sport Roles Across Business and I/T
Title Role Business Analyst Provide comprehensive and structured view of the business requirements Architect Provide architecture for a software application or service Integration Developer Creation of new business function by combining existing services Application Developer Develop the business services according to the Architects' design, incorporating both functional as well as presentation aspects of the offering CIO / Project Manager Gain visibility into the business benefits, costs and risks of the portfolio of SOA services from proposal to retirement There are many roles involved in SOA development…. Read the slide. We have tools that will support all of the roles and we will take a brief look at them. However, we do not recommend that you adopt all of the tools at once. Depending on your goals you will most likely pick a few of the tools to get started and then branch

7 SOA Foundation – Development Roles
Description Benefits & Skill Requirements Business Analyst Modeling business processes for optimization or to reengineer existing business processes or define new business processes No programming experience required Can focus on business performance & process Integration Developer / Specialist Visual tools to configure integration logic with existing and new applications and humans in the network Some basic programming experience (loops, conditions, string manipulation) No J2EE skill required Expect tools to simplify and abstract advanced IT implementation details Software Architect Model-driven development environment that automates the translation from design to implementation. Includes requirements and business modeling integrations with RequisitePro and WBI Modeler Focused specifically on UML modeling and J2EE implementation J2EE / Java Application Developer Comprehensive integrated development environment, for Web, Java, Web services, Portal, and EJB development with visual tools that accelerate application development. Focused specifically on J2EE implementation

8 SOA Foundation – Development Tools
Role Description Development Tool Business Analyst Modeling business processes for optimization or to reengineer existing business processes or define new business processes WebSphere Business Modeler No programming experience required Can focus on business performance & process Integration Developer / Specialist Visual tools to configure integration logic with existing and new applications and humans in the network WebSphere Integration Developer Some basic programming experience (loops, conditions, string manipulation) No J2EE skill required Expect tools to simplify and abstract advanced IT implementation details Software Architect Model-driven development environment that automates the translation from design to implementation. Includes requirements and business modeling integrations with RequisitePro and WBI Modeler Rational Software Architect Focused specifically on UML modeling and J2EE implementation J2EE / Java Application Developer Comprehensive integrated development environment, for Web, Java, Web services, Portal, and EJB development with visual tools that accelerate application development. Rational Application Developer Focused specifically on J2EE implementation

9 SOA Business Driven Development – Roles and Primary Tools
Business Analyst Defines, models Processes Optimizes Processes through simulations Solution Architect Defines business contract and system use cases Models Service Implementation WebSphere BI Modeler Rational Software Architect Integration Developer Implements Processes and Composite Applications Defines/Connects Services & Interfaces J2EE Developer Implements Services Constructs other J2EE artifacts WebSphere Integration Developer Rational Application Developer

10 IBM SOA Foundation Part of a broader portfolio to meet your SOA needs
Process: WebSphere Process Server WebSphere ESB People: WebSphere Portal Information: WebSphere Information Integrator Application Infrastructure: WebSphere Application Server & XD WebSphere Integration Developer Rational Application Developer WebSphere Business Modeler Rational Software Architect The SOA Foundation is built with software that was carefully selected from a broader software portfolio. These are the specific, targeted software products that support each stage of the SOA lifecycle. They are interoperable and fully modular so you can select just what you need today with the comfort that it will work well with other additions you may want to make in the future. WebSphere Business Monitor Tivoli Composite Application Manager Tivoli Identity & Access Manager Rational Unified Process Rational Team Unified Platform Rational Portfolio Manager

11 SOA Business Driven Development – Key Roles and Tools
Demo 1 Demo 3 Demo 6 Demo 7 Demo 8 Demo 4 Demo 5 Demo 1 Demo 2 Demo 3 SOA Business Driven Development – Key Roles and Tools Business Analyst Defines, models Processes Optimizes Processes through simulations Solution Architect Defines business contract and system use cases Models Service Implementation WebSphere BI Modeler Rational Software Architect Integration Developer Implements Processes and Composite Applications Defines Services J2EE Developer Implements Services Constructs other J2EE artifacts WebSphere Integration Developer Rational Application Developer

12 SOA Business Driven Development – Key Roles and Tools
Demo 8 Demo 1 Demo 2 Demo 3 Demo 4 Demo 5 Demo 6 Demo 7 Demo 8 Demo 9 Demo 10 Demo 11 Demo 12 Demo 13 SOA Business Driven Development – Key Roles and Tools Business Analyst Defines, models Processes Optimizes Processes through simulations Solution Architect Defines business contract and system use cases Models Service Implementation WebSphere BI Modeler Rational Software Architect Integration Developer Implements Processes and Composite Applications Defines Services J2EE Developer Implements Services Constructs other J2EE artifacts WebSphere Integration Developer Rational Application Developer

13 Business Models Driven into J2EE Workflows
Demo 1 Demo 2 Business Models Driven into J2EE Workflows Business process model - Simulate cost/time savings and assign business measures (KPIs) Re-use business process model in visual workflow tools to build SOA J2EE web services WebSphere Business Modeler WebSphere Integration Developer

14 SOA Composite Application Landscape
WebSphere Integration Developer Java Application Sell additional services based on customer profile Human Task Human intervention on suspect applications to prevent fraud get Approved Approved/ Denied Imported EIS System Call Credit Rating service from an existing application WS-BPEL Business Process If Approved then Send letter offering gold If NOT Approved Send letter offering Credit counseling service Business State Machine Adapting to business events Flexibly building business processes based on standards Business Rules Enable rapidly changing customer decision point

15 SOA Business Driven Development – Key Roles and Tools
Demo 4 Demo 3 Demo 1a Demo 1b Demo 2 Demo 3 Demo 1 Demo 5 Demo 1 Demo 2 SOA Business Driven Development – Key Roles and Tools Business Analyst Defines, models Processes Optimizes Processes through simulations Solution Architect Defines business contract and system use cases Models Service Implementation WebSphere BI Modeler Rational Software Architect Integration Developer Implements Processes and Composite Applications Defines Services J2EE Developer Implements Services Constructs other J2EE artifacts WebSphere Integration Developer Rational Application Developer

16 Model the Business Document business processes and user interactions
Analyst models “as is” business process and explores alternative “to be” business processes Analyst models “as is” and “to be” user interactions through use cases Last updated: 10/12/04 A good architecture begins with a solid understanding of the business requirements. And good business requirements require a solid understanding of how your business works today, and how it should work in the future. WebSphere Business Integration Modeler helps you create an “as-is” model of your current business process. From there, you can identify deficiencies and pitfalls and create a “to-be” model for how the business can be improved. WebSphere Business Integration Modeler can then be used to simulate the to-be model to validate cost savings, ROI, and other general improvement parameters. Once optimized and validated, the to-be model is exported to Rose XDE Developer, where the business requirements are transformed into software system requirements and models. All this will ensure that your system implementation is driven by business requirements and is fully aligned with your Line of Business Process Model. IBM WebSphere Business Integration Modeler IBM Rational Software Architect

17 IBM Design & Construction Offerings
Benefits Capabilities Drive higher levels of productivity and time to value Maximize quality, robustness, reusability Maximize value from both code & models Choice of development styles Design > Build > Test > Deploy Code visualization & visual editing Modeling & round-trip engineering Legacy integration Rapid application development Model execution Level of abstraction Business modeling & model execution Rapid Application Development Last updated: 9/2/04 IBM provides a range of Design and Construction offerings to make development faster and easier, to maximize quality, robustness and re-usability, to maximize the value of both code and models and to allow development teams to choose the development paradigms that fit them best. These solutions include tools for traditional coding, Code Visualization and Visual Editing, Modeling & Round-Trip Engineering, Legacy Integration, Rapid Application Development and Model Execution. IBM Rational offers the following design and construction solutions, each designed for specific development roles: Rational Web Developer: Offers an easy-to-use integrated development environment with high productivity RAD tools for building and maintaining dynamic Web applications, Web services and Java applications. Rational Application Developer: Adds to Rational Web Developer comprehensive tools for building and maintaining portals and Java TM 2 Enterprise Edition (J2EE) applications as well as UML visual editing, performance testing tools and entry-level version control and team support. IBM Rational Professional Bundle: includes all of the desktop tools your enterprise needs to design, construct, and test J2EE/Portal/Service-oriented applications, in a single purchase vehicle with one maintenance contract to manage. Rational Software Architect: Offers software architects and senior developers a rich set of model-driven development capabilities for unifying all aspects of software architecture. Rational Rose Technical Developer: Provides a complete UML-based design and development environment optimized for engineering and other types of technical applications developed in C or C++. Because no single tool or technology satisfies all team development requirements, IBM offers the broadest spectrum of analysis, design and construction solutions for rapidly delivering architecturally sound and resilient systems. This broad spectrum of solutions enables each development team to choose the right solution for their technology environment, skill level, and modeling needs. SPEAKER NOTE: This "spectrum" is a little contrived for the sake of simplicity. Things such as "Model Execution" and "Business Modeling" are orthogonal and it is a bit of a stretch to put them as different points along the same dimension. A simple linear graph suggests these notion are mutually exclusive, but clearly, one should be able to choose both. A multi-dimensional view of our solutions would be more technically accurate, but for a CxO and decision maker audience, more complex to take in. [adapted from Bran Selic feedback] Traditional coding. Modern IDEs offer many tools such as visual designers, language-sensitive editors, wizards, form builders and other GUI controls to raise developer productivity. While these tools are not “models” in the strict sense of the term, they nonetheless raise the level of abstraction above source code, make developers more productive, help create more reliable code and enable a more effective maintenance process. All these attributes are the essence of model-driven development. Code visualization and visual editing. A step above the IDE functions is the ability to visualize source code in graphical form. Here, a picture is worth a thousand lines of code, in a sense. Developers have used graphical forms of abstraction above their code for many years. Traditional flow charts are a common method for depicting the algorithmic control flow of code. Structure charts, or even simple block diagrams with arrows, are often used on whiteboards—using boxes to represent functions and subprograms, arrows to indicate calling dependencies and so on. For object-oriented software, boxes typically denote classes and lines between boxes denote relationships between those classes. Coupled closely with code visualization is visual editing, in which developers edit code through the diagrams instead of through conventional IDE text windows. Visual editing is well suited for changes that have systematic effects on other pieces of code. For example, in an object-oriented system that has a set of classes related in an inheritance hierarchy, certain features of the classes (the field members, methods or functions) may need to be reorganized into different classes (a process called refactoring) as the application evolves. Using conventional code editors to enact such changes can be tedious and error-prone. But an effective visual editor allows developers, for example, to drag and drop a member function from one class to its base class and automatically adjust all code that is affected by such a change. In one sense, code visualization and visual editing are simply alternative methods for viewing and editing the code. Changes to the code are immediately reflected in corresponding diagrams and vice versa. Although some may argue that such depictions do not constitute a “model,” the essence of modeling is abstraction and any visualization of code is indeed an abstraction—selectively exposing certain information while suppressing details deemed unnecessary or unwanted. Some practitioners prefer to use terms such as code model, implementation model or platform-specific model (PSM) to qualify such abstractions from other, higher-level forms of modeling that do not have such direct relationships to the code. Modeling and round-trip engineering. The next step on the modeling spectrum represents the state of conventional model-driven development. Here, visual models are created from a methodological process that begins with requirements and delves into a high-level architectural design model. Developers then create a detailed design model from which skeletal code is generated to an IDE. The IDE is used to complete the detailed coding. Any changes made to the code that affect the design model are synchronized back into the model; any model changes are synchronized into the existing code. Legacy integration. When developers are ready to integrate systems—whether all legacy or some new systems—they must understand the systems in place, know how the business intends for these systems to work together and prioritize those integrations. Modeling legacy systems does not necessarily mean that the entire system and all its components must be incorporated; however, developers should understand the legacy systems’ architectures, how they work and how they interface with others. Understanding what the system does and what other software is dependent on it will help determine suitable steps moving forward. Several methods can be used to model legacy systems. Developers can reverse-engineer code into models to understand them, manually model them or use some combination thereof. Rapid Application Development (RAD). The practice of RAD has been around since the early 1980s. The premise is simply to provide highly productive ways to generate and maintain code. RAD can be accomplished through easy-to-use visual layout and design, drag-and-drop components, and automatic code generation, of an advanced IDE. RAD, distinct from both traditional coding and model-driven development, raises the level of abstraction above the code, but does not use “models” per se. Business modeling and model execution. Before the need to develop software is even known, business and engineering analysts often find it useful to create “as-is” models of how their systems work today. From that model, they can analyze what works and what needs improvement. Special-purpose tools can simulate these models along several key variables, such as time, cost and resources. From the analysis, “to-be” models can be built to prescribe how new, improved processes should work. Generally, new software development is needed to implement the new processes, and the “to-be” models serve as key drivers for the ensuing development. For some application domains, the “to-be” models are specified to such rigor that complete applications can be generated from the models. Modeling at this level of abstraction offers the greatest potential for productivity and integration between the business or engineering problem domains and the technology or implementation domains. Legacy Integration Modeling & Model-Driven Development Code visualization & visual editing Conventional coding Adopt the right development style for your needs

18 Build Tools - End-2-End Design & Construction
Demo 3 Demo 4 Demo 5 Demo 1 Demo 2 Build Tools - End-2-End Design & Construction Applications, Transactions and Processes Directory and Security Servers Integration Servers Customers Partners Suppliers Employees Transaction Servers Edge Servers Web Services: SOAP, WSDL, UDDI Web Presentation Servers Web Application Servers Data Servers Relational and Non-relational Data GUIs, Pervasive Devices, Voice, etc. XML, Web Services, Portlets, Servlets, Java Server Faces/Pages Services, EJBs, and SOA Work Flows Application Modeling Java/J2EE Development Web/Portal XML Web Services Database App Business Process SOA Integration Cobol, CICS/IMS, 4GL Development Development Roles

19 Model Driven Development With A Focus On Architecture
Create models at various levels of abstraction Implement with component-oriented and service-oriented architectures Visualize as-built architecture Validate or refine & iterate Application System Information Business Implementation Last updated: 4/1/04 We’ve talked about the first of the four software development imperatives: Develop Iteratively. The second software development imperative is “focus on architecture”. An application’s architecture is the most critical determinant of its success or failure. A properly designed architecture ensures the application will meet business needs, perform acceptably, scale with the business, and be adaptable over time. To accomplish this, software teams should: Create models at various levels of abstraction –Modeling creates abstractions that help manage complexity. Abstractions are needed from multiple viewpoints to serve multiple stakeholders. Models can be created at the business, system, application, data, and code levels of abstraction. Use component- and service-oriented architectures – architectural building blocks that enable organizations to selectively combine and expose functionality outside the firewall. Visualize as-built architecture – by visualizing and/or reverse engineering applications as they have been built, you can better understand the implementation, document the design, and enable a more reliable and productive change process. Validate or refine and iterate – Often, the implementation does not perfectly match the models that originally drove code development. Analyzing the as-built architecture provides an opportunity to validate and refine it to keep model and code in sync. A focus on architecture enables software development teams to: Design for change -- Component-based architectures, including emerging service-based architectures (SOA) designed to support Web Services and grid computing, allow the software to be changed quickly, because components can be switched readily, or modified, without compromising overall system integrity. This is a fundamental requirement to adapt quickly to evolving business needs. Reduce complexity -- Visual modeling allows project managers to focus on the core requirements of a software application, leaving the functional details to the coding specialists on the team. Together, visual modeling and component-based design allow all teams reduce complexity by working at the right level of “abstraction”. This in turn allows teams to better focus on what really matters to the business– creating strategic advantage. Ensure architectural Integrity and quality – Experience shows that an application’s architecture is the single largest determinant of its quality. A good architecture allows the application to meet the organization’s reliability and scalability requirements, without compromising its integrity. Business Benefits Technology Benefits Better align projects with business needs Higher-level reuse for improved productivity Faster, more reliable changes Enables model-driven architecture and development Scales better than focusing only on code Facilitates traceability across the lifecycle

20 Build Tools - End-2-End Design & Construction
Demo Demo 8 Demo 9 Demo 1 Demo 2 Demo 3 Demo 4 Demo 5 Demo 6 Build Tools - End-2-End Design & Construction Applications, Transactions and Processes Directory and Security Servers Integration Servers Customers Partners Suppliers Employees Transaction Servers Edge Servers Web Services: SOAP, WSDL, UDDI Web Presentation Servers Web Application Servers Data Servers Services, EJBs, and SOA Work Flows Relational and Non-relational Data GUIs, Pervasive Devices, Voice, etc. XML, Web Services, Portlets, Servlets, Java Server Faces/Pages Application Modeling Java/J2EE Development Web/Portal XML Web Services Database App Business Process SOA Integration Cobol, CICS/IMS, 4GL Development Development Roles

21 Simplifying J2EE, Web and Portal/Portlet Development
Demo 3 Demo 4 Demo 1 Demo 7 Simplifying J2EE, Web and Portal/Portlet Development Data (relational and non) drag-n-drop ease-of-use 1 2 Web Services development drag-n-drop ease-of-use 1 2 Portals drag-n-drop ease-of-use 1 2

22 Richer Thin Clients (Portal, Portlets and Web Apps)
Spreadsheet Control Tabbed Panels Database Query Web Service Graphing Controls

23 Build Scenarios – J2EE, Web Services and Data
Web Services – Creating, testing and consuming Data - Relational and non-relational data integration via Service Data Objects (SDO) JavaBeans and EJBs – Creating, testing and JavaServer Faces (JSF) MVC app design

24 Build Scenarios – Banking & Finance (Applying End-2-End Development)
Demo 1 Demo 2 Build Scenarios – Banking & Finance (Applying End-2-End Development) Account Management - Transfer Funds, Web Services, Service Data Objects (SDO), JavaServer Faces (JSF) ) Accounts Summary - SDO custom queries, Portlet User session/state, personalization Portfolio Management & Financial Advisor Dashboard - Portlet wiring click-2-action, charts/graphs Portal Site Design - Themes, skins, navigation, look-n-feel

25 Build Tools - End-2-End Design & Construction
Applications, Transactions and Processes Directory and Security Servers Integration Servers Customers Partners Suppliers Employees Transaction Servers Edge Servers Web Services: SOAP, WSDL, UDDI Web Presentation Servers Web Application Servers Data Servers Relational and Non-relational Data GUIs, Pervasive Devices, Voice, etc. XML, Web Services, Portlets, Servlets, Java Server Faces/Pages Services, EJBs, and SOA Work Flows Application Modeling Java/J2EE Development Web/Portal XML Web Services Database App Business Process SOA Integration Cobol, CICS/IMS, 4GL Development Development Roles

26 The Business Driven Development Lifecycle Business Process Integration – Full Circle
Last updated: 12/18/04 The business-driven development life cycle is iterative in nature. Each iteration combines a mix of analysis, design, construction and testing activities and results in a demonstrable form of the software that can be validated and refined by users. Producing multiple iterations reduces project risk by providing tangible checkpoints along the pathway to a complete solution. A typical iteration includes the following steps. Model the Business Process IBM solutions enable you to capture current business activities and workflows and simulate alternative scenarios to determine the best opportunities for business transformation. Analyze Requirements Once a solution has been identified, the next step is to define its supporting business and IT requirements. IBM solutions help you generate a financial analysis for your proposed solution and document both its business and technology requirements. By modeling user interactions using the industry-standard UML, your team will share a common and precise understanding of proposed changes. Design and Construct The next step is to translate requirements into technology solutions. Because no single tool fits all team needs, IBM offers the broadest spectrum of code-based, model-driven and rapid application development solutions for developing high-quality software. You choose the toolset optimized for your technology environment, skill level and development paradigm. Test Each iteration is validated to ensure that it functions as designed with acceptable performance. IBM testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. Deploy IBM deployment tools support a managed approach to planning and executing migrations to your production environment. Automated provisioning and configuration management capabilities ease the implementation of coordinated changes to business processes and IT systems. Manage Once deployed, IBM monitoring tools monitor applications and essential system resources across your multiplatform environment to detect potential problems and automate recovery from critical situations. A closed-loop development cycle provides developers, operations managers and network engineers with a consistent set of correlated data to pinpoint application problems and facilitate their rapid repair and redeployment. Optimize Successful organizations not only automate business processes, but also monitor their execution and dynamically adjust them in response to real-time feedback. A performance-based feedback cycle allows you to compare the projected value of an investment to actual business results and make the necessary adjustments to maximize business value.

27 SOA Business Driven Development – Roles and Primary Tools
Business Analyst Defines, models Processes Optimizes Processes through simulations Solution Architect Defines business contract and system use cases Models Service Implementation WebSphere BI Modeler Rational Software Architect Integration Developer Implements Processes and Composite Applications Defines/Connects Services & Interfaces J2EE Developer Implements Services Constructs other J2EE artifacts WebSphere Integration Developer Rational Application Developer

28 SOA Business Driven Development – Roles and Supporting Tools
Analyst Defines and models processes and concepts Optimizes processes through simulations Solution Architect Defines services for business and system use cases Models service implementation Business Goals and Objectives Service Design Model Business Design Model Software Architecture Websphere Business Modeler WebSphere Business Monitor Business Requirements Enterprise Architecture Rational Requisite Pro Rational Software Architect Rational Requisite Pro Rational Software Architect Integration Developer J2EE Developer Implements processes and composite apps Defines services Implements services Constructs other J2EE artifacts Implementation Model Service Flow Model Service Assembly Model Deployment Model Websphere Integration Developer Rational Application Developer Rational Portfolio Manager Rational Unified Process Rational ClearCase Rational ClearQuest Portfolio Resource Model Shared Assets Common Process

29 IBM Rational Software Development Platform
Lifecycle tools views are integrated into a single IDE Industry challenges addressed Requirements: 70 – 80 % of project failures are tied to poor analysis of requirements Development: 65% of development projects fail to meet expectations SW Quality/Testing: Developers make up to 150 errors in every thousand lines of code SW Quality/Testing: Only 14% of new web applications perform as planned in production SW Quality/Testing: The average new web application is down nearly one day per week Change Mgmt: Over 70% of build errors are because of poor SW Config management. Portfolio Mgmt: Nearly 75% of problems are not identified by traditional project mgmt SW

30 Prioritize Plan Manage Measure
The Business Driven Development Lifecycle IBM Rational Software Development Platform Prioritize Plan Manage Measure Business End User Executive Model the Business Define Requirements Analyst Operations Manager Optimize Govern Architect Design Application Support Project Manager Manage change & assets Manage Developer Last updated: 12/18/04 The business-driven development life cycle is iterative in nature. Each iteration combines a mix of analysis, design, construction and testing activities and results in a demonstrable form of the software that can be validated and refined by users. Producing multiple iterations reduces project risk by providing tangible checkpoints along the pathway to a complete solution. A typical iteration includes the following steps. Model the Business Process IBM solutions enable you to capture current business activities and workflows and simulate alternative scenarios to determine the best opportunities for business transformation. Analyze Requirements Once a solution has been identified, the next step is to define its supporting business and IT requirements. IBM solutions help you generate a financial analysis for your proposed solution and document both its business and technology requirements. By modeling user interactions using the industry-standard UML, your team will share a common and precise understanding of proposed changes. Design and Construct The next step is to translate requirements into technology solutions. Because no single tool fits all team needs, IBM offers the broadest spectrum of code-based, model-driven and rapid application development solutions for developing high-quality software. You choose the toolset optimized for your technology environment, skill level and development paradigm. Test Each iteration is validated to ensure that it functions as designed with acceptable performance. IBM testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. Deploy IBM deployment tools support a managed approach to planning and executing migrations to your production environment. Automated provisioning and configuration management capabilities ease the implementation of coordinated changes to business processes and IT systems. Manage Once deployed, IBM monitoring tools monitor applications and essential system resources across your multiplatform environment to detect potential problems and automate recovery from critical situations. A closed-loop development cycle provides developers, operations managers and network engineers with a consistent set of correlated data to pinpoint application problems and facilitate their rapid repair and redeployment. Optimize Successful organizations not only automate business processes, but also monitor their execution and dynamically adjust them in response to real-time feedback. A performance-based feedback cycle allows you to compare the projected value of an investment to actual business results and make the necessary adjustments to maximize business value. Construction Deployment Manager Deploy SW Quality & Testing Tester Operations Development Optimize Iterate

31 Test application Validate functional requirements
Demo Test application Validate functional requirements Deployment Manager leverages operational model to provision the test lab Browser UI Host UI Java UI Tester performs automated and manual functional testing based on use cases derived from business requirements Tracing Monitoring Logging Last updated: 12/18/04 Step five is to test the application. The application is validated to ensure that it functions as designed with acceptable performance. IBM functional and manual testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. IBM Rational Manual Tester IBM Rational Functional Tester IBM Rational Performance Tester

32 Prioritize Plan Manage Measure
The Business Driven Development Lifecycle IBM Rational Software Development Platform Prioritize Plan Manage Measure Business End User Executive Model the Business Define Requirements Analyst Operations Manager Optimize Govern Architect Design Application Support Project Manager Manage change & assets Manage Developer Last updated: 12/18/04 The business-driven development life cycle is iterative in nature. Each iteration combines a mix of analysis, design, construction and testing activities and results in a demonstrable form of the software that can be validated and refined by users. Producing multiple iterations reduces project risk by providing tangible checkpoints along the pathway to a complete solution. A typical iteration includes the following steps. Model the Business Process IBM solutions enable you to capture current business activities and workflows and simulate alternative scenarios to determine the best opportunities for business transformation. Analyze Requirements Once a solution has been identified, the next step is to define its supporting business and IT requirements. IBM solutions help you generate a financial analysis for your proposed solution and document both its business and technology requirements. By modeling user interactions using the industry-standard UML, your team will share a common and precise understanding of proposed changes. Design and Construct The next step is to translate requirements into technology solutions. Because no single tool fits all team needs, IBM offers the broadest spectrum of code-based, model-driven and rapid application development solutions for developing high-quality software. You choose the toolset optimized for your technology environment, skill level and development paradigm. Test Each iteration is validated to ensure that it functions as designed with acceptable performance. IBM testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. Deploy IBM deployment tools support a managed approach to planning and executing migrations to your production environment. Automated provisioning and configuration management capabilities ease the implementation of coordinated changes to business processes and IT systems. Manage Once deployed, IBM monitoring tools monitor applications and essential system resources across your multiplatform environment to detect potential problems and automate recovery from critical situations. A closed-loop development cycle provides developers, operations managers and network engineers with a consistent set of correlated data to pinpoint application problems and facilitate their rapid repair and redeployment. Optimize Successful organizations not only automate business processes, but also monitor their execution and dynamically adjust them in response to real-time feedback. A performance-based feedback cycle allows you to compare the projected value of an investment to actual business results and make the necessary adjustments to maximize business value. Construction Deployment Manager Deploy SW Quality & Testing Tester Operations Development Optimize Iterate

33 Managing Change: The Challenge
Did requirement 462 make it into this release ? How many severity 1 bugs are left? Add promotion calculation Bug 849 Bug 527 New customer transaction New platform New GUI button New web design Bug 98 Bug 179 Bug 348 Analyst Bug 251 Project Manager Of course I didn’t forget a file... Why did the build break? Is bug 873 fixed in this build? Last updated: 9/23/04 What’s the big deal with change? Software development is an increasingly complex and dynamic activity. Development frequently occurs in teams that perform concurrent development on the same application, often in geographically distributed locations. Multiple versions of applications need to be supported, and they often must run on different machines and operating systems. Increased economic pressures, increased focus on auditory and regulatory compliance, and increased complexity of development processes and technologies further intensify today’s development challenges. As a result, many problems can occur during software development. These include: • Bugs that have been corrected reappear. • Previous releases of software are impossible to find or cannot be rebuilt. • Files mysteriously change or disappear altogether. • Work from one developer is replaced (lost) by work from another developer. • Builds that previously worked, suddenly break. • Development team workload cannot be easily tracked. • Project status cannot be easily monitored and assessed. If you think about how artifacts move through the software development process, you see that each member of the team experiences all these changes differently. Project managers try to assess the project status and analysts want to know what features are arriving in builds. Developers change a huge collection of different files, and they have to assure they have them all checked in for the builds. The integrator, or build manager, has to figure out why builds break, and testers who receive new builds on a regular basis need to know what’s new and needs testing. SCM tools can help to simplify and manage the software development process. By providing capabilities such as version control, build management, defect and change tracking, release management, and process control, SCM can help deliver: • Increased productivity through parallel development and automated processes. • Improved operational efficiency through team collaboration, support for large distributed teams, enhanced reliability and minimized downtime. • Reduced cost through leveraging existing investments and increased software reuse. • Faster time to market through streamlined development and reduced release/build cycle times. • Better software quality by preventing users from making mistakes and having fewer bugs in delivered code. • Improved customer retention through improved customer responsiveness. • Increased ability to meet compliance requirements with a well-defined, repeatable, auditable process. Build 3 Build 2 Build 1 Testers Developers Integrator

34 Unified Change Management: The Solution
Activities carried out to plan and track project status Never forget a file again Artifacts Activities Activity Organize Projects Track Project Status Easy to Adopt ClearQuest ClearCase Finally, Unified Change Management is an out of the box process framework supported by both Rational ClearCase and Rational ClearQuest that enables teams to easily and automatically take the Assets – requirements, models, source code, test scripts, etc. – created throughout the development lifecycle -- and associate the changes to those assets with the Activities – such as work items, change requests or defects – that prompted those changes in the first place. Assemble Systems Consistently Manage Baselines Maintain Build Audit Trail Assets generated and modified throughout the development lifecycle

35 ClearCase Integration Inside RAD/RSA/WID/WBModeler
ClearCase Toolbars Provides ClearCase perspective with multiple Eclipse views Improved performance in a WAN environment Leverages existing CC Web infrastructure Better support for disconnected mode and remote users Supports ClearCase  ClearQuest interaction (UCM) in a WAN environment ClearCase Details view ClearCase Navigator view ClearCase Search & Synchronize views

36 ClearQuest Integration Inside RAD/RSA/WID/WBModeler
CQ Toolbar Workspace view A new client interface for ClearQuest based on Eclipse 3.0 Provides complete CQ capabilities for developers and testers in the Eclipse IDE Replaces existing ClearQuest Result Set plugin, Result Set view Record Details form view Properties view Console view

37 Prioritize Plan Manage Measure
The Business Driven Development Lifecycle IBM Rational Software Development Platform Prioritize Plan Manage Measure Business End User Executive Model the Business Define Requirements Analyst Operations Manager Optimize Govern Architect Design Application Support Project Manager Manage change & assets Manage Developer Last updated: 12/18/04 The business-driven development life cycle is iterative in nature. Each iteration combines a mix of analysis, design, construction and testing activities and results in a demonstrable form of the software that can be validated and refined by users. Producing multiple iterations reduces project risk by providing tangible checkpoints along the pathway to a complete solution. A typical iteration includes the following steps. Model the Business Process IBM solutions enable you to capture current business activities and workflows and simulate alternative scenarios to determine the best opportunities for business transformation. Analyze Requirements Once a solution has been identified, the next step is to define its supporting business and IT requirements. IBM solutions help you generate a financial analysis for your proposed solution and document both its business and technology requirements. By modeling user interactions using the industry-standard UML, your team will share a common and precise understanding of proposed changes. Design and Construct The next step is to translate requirements into technology solutions. Because no single tool fits all team needs, IBM offers the broadest spectrum of code-based, model-driven and rapid application development solutions for developing high-quality software. You choose the toolset optimized for your technology environment, skill level and development paradigm. Test Each iteration is validated to ensure that it functions as designed with acceptable performance. IBM testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. Deploy IBM deployment tools support a managed approach to planning and executing migrations to your production environment. Automated provisioning and configuration management capabilities ease the implementation of coordinated changes to business processes and IT systems. Manage Once deployed, IBM monitoring tools monitor applications and essential system resources across your multiplatform environment to detect potential problems and automate recovery from critical situations. A closed-loop development cycle provides developers, operations managers and network engineers with a consistent set of correlated data to pinpoint application problems and facilitate their rapid repair and redeployment. Optimize Successful organizations not only automate business processes, but also monitor their execution and dynamically adjust them in response to real-time feedback. A performance-based feedback cycle allows you to compare the projected value of an investment to actual business results and make the necessary adjustments to maximize business value. Construction Deployment Manager Deploy SW Quality & Testing Tester Operations Development Optimize Iterate

38 Deploy Plan capacity and ensure compliance with Service Level Agreements
Tester evaluates the scalability of the new application based on Service Level Agreements captured in business model Deployment team builds capacity plans based on performance tests Last updated: 12/18/04 Step six is to plan capacity and deploy the application to production environments. Tester evaluates the scalability of the new application based on Service Level Agreements captured in business model. The deployment team builds capacity plans based on performance tests IBM Tivoli Composite Application Monitor IBM Rational Performance Tester

39 Manage and Monitor Monitor service levels with a centralized view into your network, systems, middleware, and application performance Operations Manager monitors application performance and is automatically notified of problems, enabling fast triage to the right stakeholders (application, DB, network, etc.) Last updated: 12/18/04 Step 7 is to manage the application. The Operations Manager monitors application performance and is automatically notified of problems, enabling fast triage to the right stakeholders (application, DB, network, etc.). IBM solutions provide a centralized view into your network, systems, middleware, and application performance. IBM Tivoli Enterprise Console IBM Tivoli Monitoring for Transaction Performance

40 Advanced WebSphere Portal Monitoring
ITCAM for J2EE Portal Monitoring Highlights Portal Overview page/tab Trend views of recent performance of critical metrics Links to new trend PAR reports: Gateway Servlet, Building Models, Page Loading, Authentication, Authorization Powerful Drill-down for deep portal diagnostics Nested Request support for instance-level tracing on Pages and Portlets Key trends and performance Metrics for portal applications and portal engine health In-context drill down to portal application trace and reporting

41 Advanced Transaction Monitoring
Portlets Performance Analysis Rich historical data Interactive graphical presentation Application demand characterization for accurate infrastructure sizing Problem Determination Quickly isolate problematic application components Drill-down from portlets to components to methods with few clicks Transaction Tracing Track and correlate portlet-initiated transactions throughout computing infrastructure Portal Framework Page Services User Identity Content Services i EJB’s EJB’s EJB’s EJB’s EJB’s EJB’s EJB’s Servlets JSP Applications EJB’s EJB’s EJB’s EJB’s EJB’s EJB’s LDAP JDBC EAI << Managed Transaction Pathways Data Services

42 Prioritize Plan Manage Measure
The Business Driven Development Lifecycle IBM Rational Software Development Platform Prioritize Plan Manage Measure Business End User Executive Model the Business Define Requirements Analyst Operations Manager Optimize Govern Architect Design Application Support Project Manager Manage change & assets Manage Developer Last updated: 12/18/04 The business-driven development life cycle is iterative in nature. Each iteration combines a mix of analysis, design, construction and testing activities and results in a demonstrable form of the software that can be validated and refined by users. Producing multiple iterations reduces project risk by providing tangible checkpoints along the pathway to a complete solution. A typical iteration includes the following steps. Model the Business Process IBM solutions enable you to capture current business activities and workflows and simulate alternative scenarios to determine the best opportunities for business transformation. Analyze Requirements Once a solution has been identified, the next step is to define its supporting business and IT requirements. IBM solutions help you generate a financial analysis for your proposed solution and document both its business and technology requirements. By modeling user interactions using the industry-standard UML, your team will share a common and precise understanding of proposed changes. Design and Construct The next step is to translate requirements into technology solutions. Because no single tool fits all team needs, IBM offers the broadest spectrum of code-based, model-driven and rapid application development solutions for developing high-quality software. You choose the toolset optimized for your technology environment, skill level and development paradigm. Test Each iteration is validated to ensure that it functions as designed with acceptable performance. IBM testing tools accelerate quality assurance activities as they build a valuable foundation of reusable test artifacts. Deploy IBM deployment tools support a managed approach to planning and executing migrations to your production environment. Automated provisioning and configuration management capabilities ease the implementation of coordinated changes to business processes and IT systems. Manage Once deployed, IBM monitoring tools monitor applications and essential system resources across your multiplatform environment to detect potential problems and automate recovery from critical situations. A closed-loop development cycle provides developers, operations managers and network engineers with a consistent set of correlated data to pinpoint application problems and facilitate their rapid repair and redeployment. Optimize Successful organizations not only automate business processes, but also monitor their execution and dynamically adjust them in response to real-time feedback. A performance-based feedback cycle allows you to compare the projected value of an investment to actual business results and make the necessary adjustments to maximize business value. Construction Deployment Manager Deploy SW Quality & Testing Tester Operations Development Optimize Iterate

43 Prioritize, Plan, Manage and Measure Align priorities, projects and people
Scope Management For executives Visualize and balance portfolios Make objective “save/kill” decisions Move smoothly from initiatives to measurable programs and projects For project and program managers Quickly ramp projects with reusable processes based on best practices Balance workload and manage demand Manage skills inventory and usage Actively manage risks and issues For team members Communicate, coordinate and collaborate globally Proposal Management Portfolio Management Resource Management Portfolio Management Dashboard Project Management Work Management Time & Expense Tracking Last updated: 12/18/04 The business-driven development approach aligns project investments and teams with business goals. IBM Portfolio Management solutions help: - Executives visualize and balance portfolios and make objective “save/kill” decisions - Project and program managers quickly ramp projects, balance workloads, inventory skills and actively manage risks - Individual contributors communicate, coordinate and collaborate globally This gives your organization the correlated data it needs to align priorities, projects and people. Exception Management Service Request Management Issues Management IBM Rational Portfolio Manager

44 Rational Portfolio Manager Align priorities, projects and people
Demo 1 Demo 2 Demo 3 Rational Portfolio Manager Align priorities, projects and people Scope Management Proposal Management Portfolio Management Resource Management Project Management Work Management Time & Expense Tracking Last updated: 12/18/04 The business-driven development approach aligns project investments and teams with business goals. IBM Portfolio Management solutions help: - Executives visualize and balance portfolios and make objective “save/kill” decisions - Project and program managers quickly ramp projects, balance workloads, inventory skills and actively manage risks - Individual contributors communicate, coordinate and collaborate globally This gives your organization the correlated data it needs to align priorities, projects and people. Exception Management Service Request Management Issues Management IBM Rational Portfolio Manager

45 Summary Highlights of the SOA Tools Landscape

46 Build  RUN  Manage your SOA
WebSphere Integration Developer (WID) WID + RAD + RSA Construct SOA Apps, composite services and dynamic/adaptive business processes Clean hand-off to IT with Business Models, Metrics WebSphere Business Modeler Service Service 2 Generate Decline WebSphere ESB WebSphere Process Server, Portal Server, Business Services Fabric WebSphere Business Monitor Business Process Management Key Messages Now we progress to the next level of integration, Business Process Management. This is where business agility takes place. We are going to focus on Business Process Management in an SOA Environment, along with the IBM offerings that help you perform it. These are the four phases of Business Process Management, or Process Integration: Model: This is where you capture, simulate, analyze, and optimize business models to reduce risk and increase flexibility. In this phase you also define the key business measures and metrics that will quantify the success of your deployed business processes. Assemble: Once the business processes have been optimized, they are implemented by combining new and existing services to form composite applications. Easy-to-use tools are needed to simply and speed the assembly of composite applications. Run: now the composite application is ready to be deployed. You need a flexible connectivity infrastructure for integrating applications, data, and services as part of your service oriented architecture. You need to make plug and play of components a reality. You also need the ability to dynamically modify your deployed processes and component services. You need to change business rules quickly and easily. Monitor: Once the SOA solution has been put into production, our next set of tasks is to monitor and examine the qualities of the business process. We need to determine how good or how bad our system is executing, based on the measures and metrics we set in the modeling phase. Once we have the data from the environment, we need the capability to analyze that information and make decisions based on the results. Real-time visibility into process performance enables process intervention and continuous improvement Review the slide, then do the integrated demo, then click to reveal the names of the products that were just demonstrated. Now let’s look at the products just demonstrated in more detail. Feedback for continuous improvement Real time management of business processes Managing Your Business Processes with a Service Oriented Architecture

47 WebSphere Business Modeler
Easy-to-use (multiple modes, business friendly, multi-user support) Robust Analysis with a Powerful Simulation Engine Collaboration Support-Web Publishing Business Measures (Metrics, KPIs, Aggregations) Export model to WebSphere Business Monitor Import WebSphere Business Monitor Run-Time Metrics Integration… WebSphere Integration Developer – BPEL Tivoli IT Process Management-CEI Event Catalog WebSphere Studio Application Developer Integration Edition – BPEL WebSphere Business Modeler Key Messages Websphere Business Modeler is a best-in-class business modeling, simulation, and analysis tool. It is a simple to use business modeling tool, which Allows the people who know the business to model the business You can attach resource, roles, and costs to each activity in the process It provides sophisticated simulation and analysis Which allows you to fully understand your business models and make informed decisions before deployment You can compare simulations against historical actual deployments of previous versions of the business process It allows collaborative modeling-which enables communication and partipation across your enterprise via web-based collaboration. You can create business measures, Key Performance Indicators (or KPIs) and Metrics, which define, at a business level, what is to be monitored during the execution of the business process Websphere Business Modeler provides a clean hand-off to IT Which should facilitate rapid and accurate deployment of your solutions Because the business model is the starting port for I/T deployment V6 has all of V5 functionality w/enhancements and new features. The product is geared to business analysts, but we still have IT friendly views. New functionality: Crystal Reports integration Collaboration support-web publishing Ability to define Business Measures Ability to import runtime metrics from WebSphere Business Monitor. Tivoli IT Process Management-CEI (Common Event Infrastructure) Event Catalog Common Event Infrastructure – which is the foundation for monitoring applications. IBM uses this infrastructure throughout its product portfolio and Monitoring Products from Tivoli as well as WebSphere Business Monitor exploit it. The event definition (CBE – Common Business Event) is being standardized through the OASIS standards body – so that other companies as well as customers can use the same infrastructure to monitor their environment. Rational Software Architect – UML WebSphere MQ Workflow-FDL

48 WebSphere Integration Developer
Rapid assembly of composite applications Streamline process design hand-off between business and IT (BPEL support) Simplify and speed development (J2EE programming skills not needed) Maximize re-use WebSphere Integration Developer Key Messages Rapid assembly of composite applications-The platform provides the ability to compose applications from reusable assets, reducing the need for advanced implementation skills Streamline process design hand-off between business and IT (BPEL support)-Import and work with business process models directly from the business analyst (WebSphere Modeler) Simplify and speed development - J2EE programming skills not needed-Some basic programming experience needed (loops, conditions, string manipulation) -- No J2EE skill required Maximize re-use-Ability to leverage existing services and develop for future reuse The WebSphere Integration Developer is the build and construction time tooling used to create the SOA based solution. Through this Eclipse based tool, all functions necessary to build and test an integrated SOA environment are available. This product provides an environment in which to describe the services that will be composed and the rules used to govern their execution. It streamlines process design hand-off between business and IT. The tool can import and work with business process models directly from the business analyst, using WebSphere Modeler. The tooling does not require any Java Programming skills nor does it overwhelm the new user. Included in the product are a wealth of tutorials and samples that cover the majority of scenarios and situations. The user will be able to be productive in a very short time. The core capability of the product is to describe the relationship between services that are to be composed to build a Business IT solution. This is primarily achieved through an easy to use Process Description editor that is based upon and utilizes the industry standard BPEL language. Experience has taught IBM that there is much more to building SOA based solutions than simply having some services and wiring them together through a process. To simplify and extends the capabilities, the product includes powerful additional functions including the ability to map from one service interface to another, to describe externalized business rules without having to hard-code them inside the process, to accommodate state machines, to describe the inclusion of people into the process and much, much more. In addition to providing the tools necessary to build and assemble these artifacts, the product includes a full test framework that allows the results to be executed in a seamless fashion in an environment that is identical to that which would be found in production but without having to perform the steps to administer and configure such an environment. The capabilities of this tool are rich and its place in the SOA and Process Integration solution is core. WID can help reduce cost of IT skills and accelerate implementation and deployment.

49 WebSphere Process Server
Built on WebSphere Application Server Powered by the Enterprise Service Bus (ESB) Flexible deployment of processes Dynamically modify deployed services WebSphere Process Server Key Messages The WebSphere Process Server, which we will shorten to WPS, is the product which provides the run-time environment for your business processes. A user will use the WID product to describe, construct and test the SOA solution and export that solution for execution in WPS. WPS is the engine necessary for driving your SOA solutions. It is based upon the proven WebSphere Application Server product which implements the industry standard J2EE platform. By basing WPS on WAS, IBM is leveraging the base set of high-performance and high-availability functions found within. This allows WPS to operate with the same qualities of services that are found in WAS. WPS extends WAS by providing the features and functions necessary to host the processes described in WID. These functions include a powerful BPEL engine capable of choreographing business processes securely and recoverably. Deployment of solutions to the server is straight-forward and includes rich features such as versioning, IT monitoring, resource configuration, tuning and much more. WPS extends the WAS supplied Administration Console to make WPS an integral extension to the base WAS environment. Process Server has an open standards-based Enterprise Service Bus (ESB) (this is the new product, “WebSphere ESB”) built into it. It gives you the flexible connectivity infrastructure you need for integrating applications, data, and services as part of your service oriented architecture. Process Server also lets you dynamically modify your deployed processes. It lets you plug and play services on the fly and change business rules quickly and easily. It should be stressed, that if you are not a J2EE or Java user, the installation and execution of business processes does not require those skills. Low level details of technology need not be exposed in order to realize a business based upon the SOA concepts.

50 WebSphere Business Monitor
Real-time visibility into process execution Management dashboards, reporting, and trending Active intervention in process execution Exports results to WebSphere Business Modeler WebSphere Business Monitor Key Messages Rounding off our story on SOA and Process Integration is the WebSphere Business Monitor. Once you have designed, implemented and put into production your solution, you will have the obvious questions … how is it doing? How well is it working? How is my business running? Where can I improve? Once we have the data from the environment, we need the capability to analyze that information and make decisions based on the results. WebSphere Business Monitor is designed to capture and present the key measurements of your business in a series of graphical dashboard views. These views are fully customizable and reflect the key measurements of your own particular business. It is important to realize that the Business Monitor is NOT monitoring your IT infrastructure. It won’t tell you about CPU utilization or network rates or disk capacities, these are what IBM considers to be IT monitoring, and we have excellent solutions for these areas. Instead, the Business Monitor is measuring core Business measurements or Key Performance Indicators at the business level. Examples of these include call volumes, warehouse capacity, staff utilization, sales per region and more. These are the business artifacts that control the quality of a business as opposed to the technical artifacts that control the operation of the IT world. Through the monitor, you can view the health and status of your business in a near real-time fashion. The insight these measurements provide are critical to the executive and business analysts in order for them to make the operating decisions. Rather than wait for extensive after the fact reports, the Business Monitor can demonstrate the areas that need attention much quicker allowing changes to be realized on the fly. The Business Monitor product works in concert with both WebSphere Modeler and WebSphere Process Server. WebSphere Business Modeler is used to capture and describe the key business measurements, WebSphere Process Server executes the production work and generates the appropriate information which is then consumed by WebSphere Business Monitor to present the information necessary to make decisions. The Business Monitor product will be available from IBM in the 1st Quarter of 2006.

51 Business Systems Management
Business focused versus technology centric Prioritization of IT activities Planning investments and changes Consolidate status consoles into business views Understand the impact of outages to business Business Service Management Key Messages: Do you know what one hour of downtime would cost you? Do you know which applications are affected if you lose a particular server? or router? Business Service Management focuses on your business, not the technology. Tivoli Business Systems Manager gives you that view of your organization. Demo Updated 2/18 CD

52 IT Management of Business Process Management
IT Operations Application Subject Matter Expert ITCAM for SOA Web Services automated mediation & problem identification ITCAM for Response Time Tracking End-to-end transaction tracking isolates problems ITCAM for WebSphere WebSphere application performance problems IBM Tivoli OMEGAMON XE for WebSphere Business Integration Resource analysis for WebSphere MQ environments IBM Tivoli Business Systems Manager Manage resources with Business views

53 Quick Reference: End-2-End SOA Tools & Server Middleware
SOA Overview SOA Business View SOA tools bridge the gap between business and I/T (i.e. common language of “Process Integration”) SOA Solution Space Lifecycle [ Model > Assemble > Deploy > Manage > Governance ] Roles [ Analyze > Architect > Develop > Integrate > Orchestrate ] SOA Tools In Action [Model] Analyze > Business Process Modeling with WebSphere Business Modeler (WBM) Architect > Application Architecture Modeling with Rational Software Architect (RSA) [Assemble] Develop > Service Implementation with Rational Application Developer (RAD) Integrate > UI, Data, Service and Enterprise Integration with RAD related tools Orchestrate > Service Orchestration with WebSphere Integration Developer (WID) SOA Infrastructure [Deploy] SOA Services Runtime with WebSphere Process Server & ESB SOA End User Experience with WebSphere Portal Server [Manage] WebSphere Business Monitor and Tivoli Composite Application Monitors [Governance] IT View: SW development process/project/portfolio management (RUP) and Tivoli Systems/Service Monitoring Business View: ROI controls and KPI visibility through business-friendly dashboards (i.e. WebSphere Business Monitor)

54 Resources (IBM developerWorks for technologies and/or products) Java, J2EE, Web Services and other technology zones are on the left hand side WebSphere Zone: Rational Zone: Free Education Portal: (How-To Step-by-step Practical Implementation Books) (a.k.a. JavaDevTools.com, RationalCentral.com, WebSphereCentral.com) (Tutorials, Links, Presentations, White Papers, Articles, etc.) So what do we mean by "build to integrate?" The first set of capabilities we've delivered in WebSphere Application Server V5 is the ability to build, manage, publish and manage applications as web services. To do this, WebSphere Application Server V5 is compatible with the J2EE 1.3 standards specification. In addition, WebSphere Application Server V5 has a number of Web services standards and other additions that actually make it almost compatible with the J2EE 1.4 standards specification. WebSphere Application Server V5 also has the ability to take any type of J2EE asset -- whether that's a servlet, an EJB -- and rapidly turn that into a reusable Web service. In addition, once these application assets have been turned into Web services, WebSphere Application Server V5 has the industry's strongest set of capabilities to deploy these applications. This includes a private UDDI repository which allows companies to implement a full Web services infrastructure within the boundaries of their firewalls relying on a UDDI registry as the "yellow pages" in which they publish all their application services. In addition, WebSphere Application Server V5 provides a secure and manageable Web services gateway, which allows companies that want to expose internal applications to the outside world as Web services to do so in a very secure and very manageable fashion. Finally, WebSphere Application Server V5 builds on top of the J2C or the Java Connector architecture set of adapters with advanced capabilities to coordinate multiple linkages into backend systems in a transactional fashion. A second set of categories for build to integrate centered around the ability to become more flexible in the dynamic integration of applications. To achieve this WebSphere Application Server V5 includes a higher performance Java messaging service with advanced messaging capabilities.. This Java messaging service is delivered through technology that we derive from MQ Series. As such, WebSphere Application Server V5 gains some of the key characteristics such as guaranteed one time message delivery and a high speed pub sub messaging chain switch. The Web services invocation framework allows customers to use Web services communication over an existing communications infrastructure. So instead of having to rely on SOAP over HTTP, which is per say a rather unreliable protocol, customers can rely on the strength of underlying MQ Series or the JMS environment to get guaranteed communication between different applications. WebSphere Application Server V5 also provides dynamic routing of Web service requests based on a set of rules that allow a customer to give higher priority to requests coming from a highly valuable business partner or customer, for example. The third set of capabilities in build to integrate are centered around the ability to visually compose and choreograph application workflows. What this means is that you can define through a visual tool interaction between different J2EE assets such as Web services, servlets, EJBs or linkages to legacy systems. You can even interrupt these workflows to allow human interaction with the application flow. In addition, these applications can be adapted in real time through things like business rules, application profiling, et cetera. What this means is that applications become much more flexible and they change in a business decision like what defines a gold level customer -- is it someone who has 30,000 air miles or 50,000 air miles? That decision can be quickly implemented in an application without the need to recode and re-deploy the application itself. WebSphere Application Server V5 provides advanced transactional capabilities in addition to this application workflow such as the ability to cleanly back out of a flow if something goes wrong. All of these workflows can be quickly turned into reusable Web services or into EJBs that can be integrated with other applications.


Download ppt "SOA Tools Landscape ... across Business and IT SOA & End-2-End Business Driven Development using Java, Web Services, Modeling, BPM, Portal, Web 2.0,"

Similar presentations


Ads by Google