Redpaper. Case Study: Business Process Management SOA Scenario. Martin Keen Stuart Jones William Mills

Transcription

1 Redpaper Martin Keen Stuart Jones William Mills Case Study: Business Process Management SOA Scenario This paper is one in a series of service-oriented architecture (SOA) papers that features a case study involving a fictitious company called JKHL Enterprises (JKHLE). The focus of the case study in this paper is the challenges and solutions associated with business process management for opening new accounts. This paper describes how to apply the realization patterns of the Business Process Management SOA Scenario to solve the business and IT challenges as they relate to the case study. Copyright IBM Corp All rights reserved. ibm.com/redbooks 1

2 Introduction to the case study JKHL Enterprises (JKHLE) is undergoing a set of fundamental business changes in an effort to ultimately maximize profits. JKHLE has decided to adopt SOA principles to address the business and IT challenges that it faces. The JKHLE team is focusing on solving the challenges that are presented by creating new customer accounts in a consistent manner throughout each of the sales channels. This SOA adoption initiative is known as the Account Open Project. Using an SOA approach will allow for a more rapid implementation and greater flexibility for future changes that the business might need. Note: For more detailed information on the case study, refer to the Case Study: SOA Account Open Project Overview, REDP-4376 paper. Account Open project challenges The JKHLE Account Open process challenges defined in this paper are associated with building business processes for opening new customer accounts. The case study described in this paper includes the following key actors: Sandy Osbourne-Archer, Chief Technical Architect Ian McCallen, Integration Developer Paige Alvarado, Senior Development Manager Ronnie Espinoza, Business Analyst Peggy Smith, Account Manager Eugene Testrite, Quality Engineer Manager Account Open Project challenges The JKHLE Account Open process challenges that we define in this paper are associated with the Business Process Management SOA Scenario. JKHLE s challenges include accessing outdated and complex applications from a variety of resources. These issues increase the time and cost of processing new accounts, and as a result negatively impact customer satisfaction. 2 Case Study: Business Process Management SOA Scenario

3 The Account Open Project architecture team is focused on solving the significant issues with the existing multiple mechanisms that customers use when opening accounts with JKHLE. They want to simplify this process to provide just two methods for opening accounts: Account Open business process Used by the majority of customers: address the small to mid-size customers. Enterprise Account Open business process Offered only to high-profit, high-value customers. Because of the large amounts of money involved with these customers, the Enterprise Account Open process has stringent auditing requirements, which are currently satisfied with a paper-based manual business process. Account Open project requirements Sandy Osbourne-Archer, Chief Technical Architect, briefed the architecture team on the objectives for the project. We want to better align our IT infrastructure with our business objectives and turn around some of the losses that we have suffered. We have chosen to fix the Account Open process first, because it is hurting customer satisfaction. Paige Alvarado, Senior Development Manager, is working on Sandy s Account Open Project architecture team. Paige s organization has been assigned to work with the line of business (LOB) and operations to automate the new business process. This includes the modeling, assembly, deployment, and management of the new business process to ensure that it meets its business goals. The Account Open process requires the integration of multiple back-end systems, human workflow integration, and composite services to support an end-to-end solution. Sandy has defined some clear requirements for the project. REQ-01: Model the existing business process Sandy wants to understand, through process modeling, how the existing Account Open process is designed. She wants to share this model with key stakeholders to help identify gaps and areas for improvements. Note: For solution details, refer to Process Modeling and Simulation on page 6. Case Study: Business Process Management SOA Scenario 3

4 REQ-02: Model and simulate a new, improved business process Based on the feedback from stakeholders, Sandy wants Ian McCallen, Integration Developer, to model a new, improved process for Account Open. Simulations of this model should be run to determine how well the new model responds to specific business situations. Note: For solution details, refer to Process Modeling and Simulation on page 6. REQ-03: Ensure the business process is adaptable to changing business situations JKHLE wants to make the new Account Open process flexible and adaptable to changing business situations. Changes in business logic should be made in real time without requiring further development effort of the Account Open process. Note: For solution details, refer to Managing Processes through Business Rules Integration and Management on page 9. REQ-04: Implement new business process With the new Account Open business process modeled, a team of JKHLE Integration Developers will need to implement and test the process. Consideration should be given to including both automated and manual activities, a common data model, and access to back-end systems. Note: For solution details, refer to Process Automation and Execution on page 11. REQ-05: Monitor the new business process The JKHLE business analysts require real-time information about the status and results of the new Account Open process. They need this information to judge the success of the new process and to quickly recognize problem areas. Note: For solution details, refer to Business Activity Monitoring on page Case Study: Business Process Management SOA Scenario

5 REQ-06: Incorporate business policies into the Account Open process The JKHLE Account Open process contains pricing calculations and approvals for accounts opened that are country specific. As additional geographies are incorporated, JKHLE needs to incorporate these countries and to select the appropriate provider for a given request without having to change the business process implementation. Note: For solution details, refer to Handling points of variability in the business process on page 15. REQ-07: Integrate content with the Enterprise Account Open business process The JKHLE Enterprise Account Open process consists of a significant amount of unstructured paper-based content and content from multiple silos. Sandy is looking for a solution to manage the large amount of content and better integrate it with automated business process activities. Note: For solution details, refer to Content-Centric Processing on page 17. Applying the SOA realization patterns to the case study Paige explains the advantages of introducing the Business Process Management SOA Scenario to JKHLE. Business Process Management is a discipline for combining software capabilities and business expertise to accelerate process improvement and facilitate business innovation. Using Business Process Management JKHLE can construct an Account Open process that solves their existing business problems, and can continue to monitor and change this business process to adapt to a changing business climate. JKHLE will use the following realization patterns from the Business Process Management SOA Scenario: Process Modeling and Simulation Managing Processes through Business Rules Integration and Management Process Automation and Execution Business Activity Monitoring Content-Centric Processing Case Study: Business Process Management SOA Scenario 5

6 Process Modeling and Simulation Sandy explains the problems with the current process that is used to open customer accounts at JKHLE. The current process takes over 20 days to activate a new account. The Account Open process requires significant human intervention, making the process both costly in terms of time and resources. Each organization within JKHLE has a slightly different way of opening accounts, which has led to inconsistent and redundant data within JKHLE. Sandy has challenged Paige to design a better Account Open process for JKHLE that solves all of these problems. Sandy has two key requirements: JKHLE needs a way to diagram their current Account Open process, so that they can identify gaps and areas for business process optimization. When designed, JKHLE requires the ability to share the new improved Account Open process with stakeholders within the different lines of business for review and approval. Proposed solution Paige introduces Sandy to Ronnie Espinoza, Business Analyst. Ronnie tells Sandy that the best way to diagram a process is to model it. Ronnie describes three reasons for modeling a process: Modeling for documentation By documenting the Account Open process through modeling, the model can help areas of the JKHLE organization understand what the business process does. This model can be used for training of new employees and to meet compliance regulations such as Sarbanes-Oxley and Basel II. Modeling for analysis Ronnie will model the current state of the business process (known as the As-Is model) and the future state of the business process (known as the To-Be model). She can then simulate workload through the To-Be model to see how it fairs. Modeling for analysis helps JKHLE understand what can and should change in their processes to meet JKHLE s business goals such as reductions in cost and improved processing times. Modeling for execution Another benefit of modeling the To-Be business process is the ability to generate artifacts from this model, and make those artifacts available to technology development tools to construct the new Account Open process. By generating technical artifacts from the model, the overall implementation time of building the new Account Open process is reduced. 6 Case Study: Business Process Management SOA Scenario

7 Ronnie explains to Sandy how she will use modeling to design a new and improved Account Open process (Figure 1 on page 8): 1. Ronnie will model the current Account Open process (the As-Is model) in WebSphere Business Modeler Advanced. 2. Ronnie will work together with Ian to create a To-Be model. Ian will also create the model in WebSphere Business Modeler Advanced, based on JKHLE business goals, and based on Ronnie s analysis of the shortcomings of the As-Is model. Ronnie and Ian will test the To-Be model using the simulation capabilities of WebSphere Business Modeler Advanced to see how the model reacts to different business situations. By using the WebSphere Process Server mode of WebSphere Business Modeler Advanced, Ronnie and Ian can define a model that provides the basis of a WS-BPEL process for assembly in WebSphere Integration Developer. 3. When Ronnie and Ian have completed the To-Be model to their satisfaction, Ian will export the model to WebSphere Business Compass. Stakeholders can retrieve the model from the WebSphere Business Compass and provide feedback to Ronnie and Ian. 4. As Ronnie and Ian receive feedback from the JKHLE stakeholders, they can incorporate that feedback into the To-Be model until the model is finalized. 5. Ronnie and Ian plans to work with the JKHLE Account Manager Peggy Smith to specify a set of key performance indicators (KPIs) alongside the To-Be model using the Business Measures Designer. These KPIs will be used later to monitor how well the new Account Open process is meeting its targets. 6. With the To-Be model complete, and the KPIs specified, Ian can export artifacts from WebSphere Business Modeler to WebSphere Business Monitor (where they can be further developed and tested in the Monitor Model Editor and Unit Test Environment) and to WebSphere Integration Developer where artifacts such as WS-BPEL and WSDL files will be used by Ian s development team as the starting point to build the actual Account Open process. Case Study: Business Process Management SOA Scenario 7

8 Export model for development Model Account Open To-Be process Process Editor Simulation WebSphere Integration Developer Deploy to runtime WebSphere Business Modeler Advanced WebSphere Business Compass Figure 1 Modeling and simulation Review and feedback JKHLE stakeholders Sandy is a little confused about the differences between Ronnie and Ian s roles. Paige explains: As the Business Analyst, Ronnie s responsibilities include identifying and documenting requirements and analyzing these requirements from a business perspective. She defines current and future operational scenarios (including processes, models, use cases, plans, and solutions) and ensures proper translation of business requirements to IT solution requirements As the Integration Developer, Ian works hand-in-hand with the Business Analyst. Ian is responsible for the assembly of assets and application components into a complete solution and preparing this solution for thorough testing and subsequent deployment. To provide the end solution, Ian works with other groups such as test, release deployment, software, and database development teams. Sandy can see that by using WebSphere Business Modeler Advanced, JKHLE can document their current Account Open process, analyze it, and then model an improved process. She also sees that this To-Be model forms a starting point for the actual development effort of the new Account Open process. 8 Case Study: Business Process Management SOA Scenario

9 Managing Processes through Business Rules Integration and Management Having modeled the To-Be Account Open business process in Process Modeling and Simulation on page 6, Ian the JKHLE Integration Developer is preparing his team to build the new Account Open process in WebSphere Integration Developer. Paige is concerned about the integration of business logic in the new Account Open process. She is aware that the Account Open process will need to embed business logic to support business policies and rules, security rules and so forth. However, she is concerned that hard-coding this business logic will limit the flexibility of the Account Open process as the needs of the business change. Ian explains that business logic can be captured as separate business rules, and these business rules can be modified and managed without modifying the Account Open business process. Proposed solution Ian explains that the Account Open business process will run in WebSphere Process Server. Business rules can be defined into WebSphere Process Server and WebSphere ILOG JRules depending of the requirements WebSphere Process Server Business Rules Using this support, the business rules are defined in WebSphere Integration Developer using a simple rule format language, and incorporated into the Account Open business process. As these business rules are externalized from the business process they can be easily updated without modifying the business process structure. WebSphere Process Server Business Rules provides runtime management for JKHLE s business analysts through a Web application that allows the analysts to make changes to the business rules and, therefore, change how the Account Open process behaves at runtime (see Figure 2). Case Study: Business Process Management SOA Scenario 9

10 WebSphere Integration Developer Business Rule Manager Update Legacy Account Open process with business rules CRM Account Rep (Create customer checking account) Update SAP Third Party Web Service (Send customer a checkbook) Order Credit Card Notification Start Batch Business Rules Rule repository DB2 WebSphere Process Server Figure 2 WebSphere Process Server Business Rules As changes occur in the business and the new Account Open process needs to be modified, the business rules can be updated using the Business Rule Manager Web application. Ian can also enable security on the business rules as the Business Rule Manager Web application role is mapped to a group or user for all rules. WebSphere ILOG JRules WebSphere ILOG JRules is the leader in the Business Rules Management Systems (BRMS) market and supports the definition of business rules in a high level language deployed in an inference rule engine. It supports a complete set of tools directly used by business analysts to maintain the rules, and deploy them in the ILOG Rule Execution Server (see Figure 3 on page 11). Everything is controlled by a governance process. WebSphere ILOG Rule Studio is used to define a rule project which includes a data model definition for rules, the rule flow and the business rules. A rule project is mapped to a business rule task in WebSphere Business Modeler. The Account Open business process has such tasks. Ian then sets up the roles that will be responsible for changing different rules, and for performing an approval process on the rules used in the Account Open process 10 Case Study: Business Process Management SOA Scenario

11 ILOG Rule Studio ILOG Rule Team Server WebSphere Integration Developer Update Legacy Account Open process with calls to ILOG JRules CRM Account Rep (Create customer checking account) Update SAP Third Party Web Service (Send customer a checkbook) Order Credit Card Notification DB2 Rule repository ILOG Rule Execution Server Start Batch Business Rules WebSphere Process Server Figure 3 WebSphere ILog JRules With the business rules deployed, Ian enables security on the roles. In the ILOG Rule Team Server the different rules can be mapped to specific users and groups allowing JKHLE to keep tight control on who can modify the rules of the Account Open process. This also allows Ian to implement an approval process on the business rules that the Account Open process uses. As changes occur in the business, authorized users can update and deploy the business rules used in the Account Open process using the ILOG Rule Team Server. Process Automation and Execution With the To-Be Account Open process modeled in WebSphere Business Modeler ( Process Modeling and Simulation on page 6), and the business logic for the new process defined as business rules ( Managing Processes through Business Rules Integration and Management on page 9), Ian and his development team are ready to begin the implementation of the Account Open business process. The To-Be Account Open process has been modeled to meet the following business challenges and requirements: To improve customer satisfaction by reducing the service time to open a new customer account. To increase staff productivity by automating manual processes. Case Study: Business Process Management SOA Scenario 11

12 To improve consistency and currency of enterprise data by automating integration across multiple applications and back-end systems. To capture and monitor metrics on staff productivity and service time. Proposed solution Ian and his development team will implement the Account Open process using IBM WebSphere Integration Developer and Rational Software Architect. The Account Open process constructed in this tool will then be deployed to WebSphere Process Server. Figure 4 shows the development topology. WebSphere Integration Developer WSDL, XSD Rational Software Architect Account Open process EAR files + process KPIs Update Legacy BPEL CRM Account Rep (Create customer checking account) Update SAP Third Party Web Service (Send customer a checkbook) Order Credit Card Notification Human Tasks Start Batch BSMs Maps WebSphere Process Server JRules WebSphere Business Monitor Process metrics SCA CEI Adapters Figure 4 Process Automation and Execution topology Ian uses the artifacts from the Account Open To-Be model as a starting point. These artifacts were generated in WebSphere Business Modeler and can be imported into WebSphere Integration Developer. From there, Ian can build a business process that makes use of automated and manual activities (activities completed through human intervention), adapters to communicate with 12 Case Study: Business Process Management SOA Scenario

13 back-ends, and a common data model. WebSphere Integration Developer provides the necessary tools: A BPEL editor to complete process flows. A Business Object editor to complete data model implementation. An Interface editor to finalize interfaces. A Human task editor to finalize the definition of human interactions. An Assembly editor to hook up the BPEL processes, human tasks, selectors (defining which components to call), and required services. A Business State Machine (BSM editor) to define state-centric business processes. Rational Software Architect is used as the primary development tool to develop new services for the Account Open process as well as the visual interfaces (such as portlets and Java Server Faces solutions). Ian and his team can test each individual component in the Account Open process, and the process in its entirety, using the test environment and test client facilities of WebSphere Integration Developer. When the unit testing is complete, Ian can export the enterprise applications from WebSphere Integration Developer and provide them to Eugene Testrite, Quality Engineer Manager, for quality assurance testing. Business Activity Monitoring JKHLE management and the team of JKHLE business analysts have a requirement for real-time information about the status and results of the new Account Open process. They need this information to: Make informed business decisions on the success of the new Account Open process. Recognize problem areas quickly and reposition the organization to take full advantage of emerging opportunities. Case Study: Business Process Management SOA Scenario 13

14 Proposed solution Paige tells Sandy that Business Activity Monitoring can meet these requirements. The monitoring process is based on a set of KPIs, or business measures in the context of the Account Open process. KPIs can be measures of time to complete a number of activities in a process and is defined in terms of the execution of those activities. In addition to tracking performance through KPIs, Business Activity Monitoring allows JKHLE to establish notification alerts for violations of business policies. These alerts allow the JKHLE business analysts to adapt the Account Open process to fix problem areas. Information obtained through Business Activity Monitoring can be viewed through a graphical representation of business performance in dashboard views. Dashboards can be viewed as portals or AJAX Web clients. Paige describes how JKHLE can implement Business Activity Monitoring (Figure 5): 1. A monitor model defining KPIs and business measures for the Account Open process is defined in WebSphere Integration Developer or Rational Application Developer. 2. Additional KPIs and metrics can be inserted into the process to produce real-time events (known as Common Base Events on CBEs). The monitor model is then imported into a Monitor Server, to make it aware of the business policies. 3. Dashboard views are designed, built, and tested. 4. Users view the events from the Monitor Server using the customized Dashboard views. Process Portal can be used for a rich WebSphere Portal user interface to interact with tasks that are running on IBM WebSphere Process Server. 14 Case Study: Business Process Management SOA Scenario

15 Tooling Monitor toolkit plus either: Rational Application Developer WebSphere Integration Developer Monitor Model Continously improve and adapt business policies and processes to changing environment Common Base Events (CBE) Common Event Infrastructure (CEI) CBE Monitor Server Dashboards Monitor Figure 5 Business Activity Monitoring Paige tells Sandy that WebSphere Business Monitor provides all of these capabilities, and its tight integration with WebSphere Process Server (where the Account Open process will run) makes it an ideal candidate. Handling points of variability in the business process During development of the Account Open process, Ronnie commented that there was a section of the process that seemed to be unduly complicated. This apparent complexity shows up when JKHLE makes pricing calculations and generates approvals for accounts as the accounts are opened. It turns out that this processing needs to be specific to the country in which the account is opened due to local country laws and practices. From Ronnie s viewpoint, there is a single business service of Pricing and Approval, but the process needs to call different endpoints based on the country concerned and the selection process shows up in the business process. Case Study: Business Process Management SOA Scenario 15

16 Proposed solution Ian tells Ronnie that he has a solution for this issue. He can use the WebSphere Business Services Fabric product to provide a business service policy based endpoint selection component, which provides the following benefits: The endpoint selection activity is removed from the business process, making the business process simpler to understand and to modify in the future. The business service policy based to select between different pricing and approval endpoints is exposed to the business and can be modified as required. If there is a requirement to use additional pricing and approval endpoints, this is a simple addition, requiring no changes to the business process. This benefit will become important in the future as the Account Open process is used in more geographies. Ian shows Ronnie some examples of how the business process might be simplified. Figure 6 shows the current process with three separate pricing and approval tasks in the business process. Provide pricing and approval USA What geography should handle pricing? Provide pricing and approval Australia Provide pricing and approval Brazil Figure 6 Current process 16 Case Study: Business Process Management SOA Scenario

17 Using WebSphere Business Service Fabric, the business process would appear as shown in Figure 7. In this proposed process there is only a single Pricing and Approval business service, which gives a cleaner, more understandable business process definition. Provide pricing and approval Figure 7 Improved process incorporating WebSphere Business Services Fabric Ian and Ronnie agree to take this proposal to Sandy. She likes what she sees but is concerned that another component is being added to the environment. Ian explains that WebSphere Business Services Fabric is an extension to their existing WebSphere Integration Developer development environment and an extension to their existing WebSphere Process Server environment. Thus, there are minimal additions. This solution satisfies Sandy, and the team gets her approval to proceed. Content-Centric Processing Sandy explains that the Account Open process for high-value enterprise customers (the Enterprise Account Open process) is labor-intensive and paper-based. These manual labor-intensive business processes involve multiple documents, records, and transactions, and there are concerns that this content is frequently hard to find and costly to obtain. In addition JKHLE corporate policy mandates a reliable way to demonstrate that processes comply with regulations and required service levels, and the acquired organization is having a hard time meeting these requirements. The intricate weaving of how this content should be initiated, stored, routed, reviewed, updated and versioned, retrieved, and archived within the context of the business process is critical to keeping the company functioning fluidly. Case Study: Business Process Management SOA Scenario 17

18 Sandy relates to Paige some of the technical problems they are facing: Significant data duplication. Multiple hard copies of documents are maintained creating inconsistencies and versioning issues. Difficulty managing unstructured data. Content is often saved in multiple repositories. Data in one department s repository is usually inaccessible to other departments. Under pressure to reduce costs in all areas. Hardcopy offsite storage is expensive and has a tendency to retain records indefinitely. Significant performance improvements requested. The manual processing times needs to be shortened, and process bottlenecks need to be identified. Sandy requests that Paige design a new Enterprise Account Open process to replace the current manual process. Proposed solution Paige recommends a solution using IBM FileNet P8. Content-Centric Processing assumes a general sequence of events that steers the progress of a document from some initial state to some final state. The initial state might be the capture or creation of a document through FileNet s Business Process Framework (BPF) and the subsequent creation of a Case Object or a virtual container containing all the pertinent case information. FileNet BPF is a rapid application development and deployment environment, providing a consistent framework for producing higher quality and easier to maintain applications, critical to the time constraints imposed on JKHLE s development cycles. Due to FileNet BPM's active content infrastructure the creation or capture of the document can automatically trigger events, launch or modify business processes, or interact with other enterprise applications. This feature can significantly reduce JKHLE s Account Opening cycle times by automating the process upon content arrival, modification, and exceptions. Interim steps might include multiple levels of Review or Approval within the workflow or collaboration with other individuals and teams. These interim steps could result in additional documents added to the Case Folder. Upon process completion selected documents within the Case Folder might be automatically archived for compliance purposes, further eliminating the chance of human error. FileNet P8 supports a unified platform around content, process, and compliance to ensure architectural consistency. Because FileNet P8 manages both process and content together, it captures the synergy and relationship between process and content, thereby creating new business value not available when separately implemented. Paige proposes an architecture that incorporates FileNet Business Process Manager and Content Manager within a tightly integrated environment 18 Case Study: Business Process Management SOA Scenario

19 as shown in Figure 8. Paige also recommends the use of FileNet Business Process Framework and FileNet eforms for P8 because they are under stringent deadlines to produce an error-free, case-based application that can be deployed rapidly and maintained easily. FileNet Connector for MS Visio WebSphere Business Modeler Process metrics BPMN XPDL XPDL FileNet Process Designer WorkPlace FileNet Application Engine FileNet P8 eforms Business Process Framework Account Open Process Optimization Lifecycle Business Activity Monitor Process Analyzer Process Simulator FileNet BPM Process Engine FileNet Content Manager Content Engine Content Repositories APIs/Listeners APIs/Listeners WebSphere Business Monitor Process metrics Process Svcs CEI Library Svcs Event Launcher Figure 8 Content-Centric Processing topology The topology shown in Figure 8 contains the following components: FileNet Process Engine The FileNet BPM Process Engine provides JKHLE with the software services for managing all aspects of business processes. The Process Engine communicates with the FileNet CM Content Engine to maintain business processes and content. The Process Engine also maintains a Rules Connectivity Framework if JKHLE chooses to integrate with Business Rules Management System from an external provider, as well as notification interfaces for process related events. FileNet Content Engine The FileNet CM Content Engine accepts incoming JKHLE requests to create, update, and retrieve objects such as documents, folders, and business Case Study: Business Process Management SOA Scenario 19

20 objects. The Content Engine supports JKHLE LDAP server and single-sign-on (SSO) functionality. This pass-through approach simplifies configuring directory services by centralizing it for both Content Engine and Process Engine. FileNet Application Engine The Application Engine hosts the Workplace Web application, Workplace Java applets, and application development tools. This is the JKHLE presentation layer for both process and content. The Application Engine protects user credentials passed between Workplace and Content Engine and provides SSL security. Process Designer runs here and is the application tool that enables the creation, transfer, and retrieval of process workflows. FileNet eforms for P8 FileNet eforms for P8 allow JKHLE to create and manage online forms in a Web browser that can appear the same as hard copy paper forms, yet are more advanced, easier to use, and less costly to implement. FileNet Business Process Framework (BPF) FileNet BPF provides a highly configurable framework for rapidly developing BPM applications and tightly integrated with eforms, which is a requirement of JKHLE. The BPF Web Application is built around an AJAX (Asynchronous JavaScript and XML) development model and exposes Case Management services through an Action Dispatcher servlet. Process Optimization By using FileNet Process Analyser, JKHLE are able to analyze their current processes to identify opportunities for improvement rapidly and identify areas that will benefit from process changes. JKHLE can then use FileNet Process Simulator to simulate how these changes will impact other parts of the business. From this simulation, the process improvement can be validated and subsequently deployed using Process Designer. For JKHLE Business Analysts interested in modeling, they can choose WebSphere Business Modeler because there are export capabilities to FileNet Process Designer after the model has been completed. JKHLE can also choose to use FileNet Microsoft Connector for Visio for the Business Analyst who are invested in Business Process Modeling Notation (BPMS) stencils within a Microsoft Visio environment. With the tightly integrated capabilities of the FileNet Architecture for JKHLE, coupled with common key components such as WebSphere Business Modeler and WebSphere Service Registry and Repository, JKHLE can implement existing content-centric projects successfully and can also foster new innovation through the integration of services with WebSphere Process Server. 20 Case Study: Business Process Management SOA Scenario

21 Summary The proposed Business Process Management solution architecture fulfills the identified requirements. This approach enables JKHLE to model and implement an improved Account Open process, monitor how the process is faring, and adjust the process dynamically to meet changing business needs. JKHLE was able to design a superior Enterprise Account Open business process that tightly manages unstructured content within the context of the business. JKHLE has future plans to integrate the Account Open and Enterprise Account Open processes. The strong integration capabilities between WebSphere Process Server and FileNet make this cross pollination possible. In summary, JKHLE will use the following IBM products to provide Business Process Management in the environment: Model: IBM WebSphere Business Modeler Advanced IBM WebSphere Business Compass IBM WebSphere ILOG JRules IBM WebSphere ILOG JRules Rule Team Server Assemble: IBM WebSphere Integration Developer IBM Rational Software Architect IBM Rational Application Developer IBM WebSphere ILOG JRules IBM WebSphere Business Services Toolpack IBM FileNet Process Designer IBM FileNet Connector for Microsoft Visio IBM FileNet Business Process Framework IBM FileNet eforms for P8 Deploy: IBM WebSphere Process Server IBM WebSphere ILOG JRules IBM WebSphere Business Services Fabric IBM FileNet Business Process Manager IBM FileNet Content Manager Manage: IBM WebSphere Business Monitor IBM WebSphere ILOG JRules Rule Team Server Case Study: Business Process Management SOA Scenario 21

22 References This section includes reference information for further reading materials that are related to the Business Process Management SOA Scenario: IBM SOA Sandbox found at: opic=/com.ibm.soln.soasandbox.nav.fw.doc/home_pages Business Process Management: Modeling through Monitoring Using WebSphere V6.0.2 Products, SG Getting Started with IBM WebSphere Business Services Fabric V6.1, SG Case Study: SOA Account Open Project Overview, REDP-4376 The team that wrote this IBM Redpaper This paper was produced by a team of specialists from around the world working with the International Technical Support Organization (ITSO). Martin Keen is a Senior IT Specialist for the IBM ITSO in Raleigh, NC, U. S. Stuart Jones, IBM Worldwide WebSphere BPM Technical Sales Leader, U. S. William Mills, IBM FileNet Product Marketing and Technology Alliances, U. S. Thanks to the following people for their contributions to this project: Erica Carmel, IBM Program Director, SOA Platform Consumability, U. S. Cindy Macrafic, IBM Senior Project Manager, SOA Platform Consumability, U. S. Veronique Moses, IBM Product Manager, SOA Scenarios, U. S. Selorm Agudu, IBM SOA Specialist, U. S. Eric Erpenbach, IBM WebSphere Process Server Development, U. S. Michele Chilanti, Senior Consultant, IBM WebSphere Services, U. S. Alan Hui, IBM Senior IT Architect, SOA Foundation, U. S. Scott Simmons, IBM Executive IT Architect, SOA Technical Sales, U. S. Steve Schaffer is a Certified Software IT Architect in New York, U. S. Amod Bhise, IBM Product Manager, WebSphere Business Services Fabric, U. S. John Ganci, Architect and Specialist, Scenario Analysis Lab, Raleigh, NC, U. S. Jerome Boyer, ILOG Technical Director, U. S. 22 Case Study: Business Process Management SOA Scenario

23 Linda Robinson, Graphics Artist, IBM ITSO, Raleigh, NC, U. S. Case Study: Business Process Management SOA Scenario 23

24 24 Case Study: Business Process Management SOA Scenario

25 Notices This information was developed for products and services offered in the U.S.A. IBM may not offer the products, services, or features discussed in this document in other countries. Consult your local IBM representative for information on the products and services currently available in your area. Any reference to an IBM product, program, or service is not intended to state or imply that only that IBM product, program, or service may be used. Any functionally equivalent product, program, or service that does not infringe any IBM intellectual property right may be used instead. However, it is the user's responsibility to evaluate and verify the operation of any non-ibm product, program, or service. IBM may have patents or pending patent applications covering subject matter described in this document. The furnishing of this document does not give you any license to these patents. You can send license inquiries, in writing, to: IBM Director of Licensing, IBM Corporation, North Castle Drive Armonk, NY U.S.A. The following paragraph does not apply to the United Kingdom or any other country where such provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND, EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this statement may not apply to you. This information could include technical inaccuracies or typographical errors. Changes are periodically made to the information herein; these changes will be incorporated in new editions of the publication. IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this publication at any time without notice. Any references in this information to non-ibm Web sites are provided for convenience only and do not in any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part of the materials for this IBM product and use of those Web sites is at your own risk. IBM may use or distribute any of the information you supply in any way it believes appropriate without incurring any obligation to you. Information concerning non-ibm products was obtained from the suppliers of those products, their published announcements or other publicly available sources. IBM has not tested those products and cannot confirm the accuracy of performance, compatibility or any other claims related to non-ibm products. Questions on the capabilities of non-ibm products should be addressed to the suppliers of those products. This information contains examples of data and reports used in daily business operations. To illustrate them as completely as possible, the examples include the names of individuals, companies, brands, and products. All of these names are fictitious and any similarity to the names and addresses used by an actual business enterprise is entirely coincidental. COPYRIGHT LICENSE: This information contains sample application programs in source language, which illustrates programming techniques on various operating platforms. You may copy, modify, and distribute these sample programs in any form without payment to IBM, for the purposes of developing, using, marketing or distributing application programs conforming to the application programming interface for the operating platform for which the sample programs are written. These examples have not been thoroughly tested under all conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these programs. You may copy, modify, and distribute these sample programs in any form without payment to IBM for the purposes of developing, using, marketing, or distributing application programs conforming to IBM's application programming interfaces. Copyright International Business Machines Corporation All rights reserved. Note to U.S. Government Users Restricted Rights -- Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp. 25

26 This document REDP was created or updated on March 15, Send us your comments in one of the following ways: Use the online Contact us review Redbooks form found at: ibm.com/redbooks Send your comments in an to: Mail your comments to: IBM Corporation, International Technical Support Organization Dept. HYTD Mail Station P099, 2455 South Road Poughkeepsie, NY U.S.A. Trademarks Redpaper The following terms are trademarks of the International Business Machines Corporation in the United States, other countries, or both: FileNet IBM Rational Redbooks (logo) WebSphere The following terms are trademarks of other companies: FileNet, and the FileNet logo are registered trademarks of FileNet Corporation in the United States, other countries or both. Java, JavaScript, and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both. Microsoft, Visio, and the Windows logo are trademarks of Microsoft Corporation in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others. 26 Case Study: Business Process Management SOA Scenario