Building a Case Management Solution

Transcription

1 Presented by IBM developerworks ibm.com/developerworks/ Building a Case Management Solution Information Management IBM Corporation

2 Case Manager Builder A tool for business users Easy to use interface Wizard driven Templates are used for providing pre-built applications 2

3 3

4 4

5 Case Designer: Tasks Triggers A variety of events can trigger case tasks Case Worker Actions New Content Case Updates 5 20 IBM C onfidential IBM IBM Corporation Corporation

6 Swim lanes are used for defining Roles in a workflow 6

7 Deployment Solutions are then Deployed into Test, Development or Production Environments 7

8 Case Object Model - Overview 8

9 Case Object Model 9

10 Solution 10 A collection of case types that have related properties and roles Implemented in a PE isolated region and a CE object store One to one relationship between the isolated region and the object store Corresponds to a PE application space

11 Case A generic term to refer to an an instance of a case type Include document-centric artifacts: collection of properties, tasks, and documents. A case can be in one of 5 states: New, Initializing, Working, Complete, Failed An instance of a case type implemented by a CE folder class Associated with a PE roster and event log Folder properties are the master case data Case state transition 11

12 Properties Data that is stored as part of the case Properties are stored in the CE case folder but can be read and updated from Process Engine Data types are singletons and arrays of the following types Boolean Integer Float String Date 12

13 Space A collection of related pages that form the user interface for processing a case Initial set of spaces created in the Mashup Server automatically when a case is deployed for the first time 13

14 Tasks An action that must be completed as part of a case Two possible implementations A Case Builder workflow A WebSphere component or process Can be in one of 5 states: Waiting, Ready, Working, Complete, Failed A task implemented using the Case Builder step editor can be modified using PE Process Designer Round Tripping A task implemented by a WebSphere component is an empty task in Case Builder Implemented using the WebSphere Integration Developer (WID) 14

15 In-Basket The bucket containing the activities that must be processed. Roles are associated with inbaskets or individual case workers Similar to PE queue inbaskets 15

16 Role Grouping of individuals with a common job function A group of users that work on some aspect of the case Implemented as a PE role and PE Queue Swim Lane One role's job within a process 16 Has at least two PE in-baskets One for the inbox queue One for the role queue

17 Connection Definition Defines the Case Builder or CMAC association with the Target Object store Process Engine Connection Point The Process Engine and process store to which the solutions are deployed Mashup Server The server containing the spaces and pages associated with the solution Object store The object store in which the cases will be instantiated 17

18 Design Object Store The object store in which configuration data is persisted: the container for the case collateral: e.g. mashup layouts, pages, solution templates, etc Each case solution is represented by a set of files, the solution package including the Solution Definition File (SDF) Configuration files XML files Workflow definition files XPDL files One per case type One design object store per P8 domain Only object store that Case Builder reads from and writes to Configured using Case Manager Admin Client (CMAC) 18

19 Target Object Store The object store To which a solution is deployed Against which case workers operate In which case instances are stored Can be new or existing object store Multiple solutions can be deployed to a single object store A P8 domain supports multiple target object stores When a solution is deployed, the various definition files in the design object store are user to generate all the required artifacts (classes, folders, workflow instances, subscriptions, etc.) in the target object store and process region Configured using Case Manager Admin Client (CMAC) 19

20 Developing a Case Management Solution 20

21 1- High-Level Installation and Configuration Process Performed by: IT Staff in each environment (dev, test, production, etc.) 1.Complete the pre-requisites defined in the Plan and Prepare Guide; for example, install and configure the operating system, directory server, WebSphere, and databases 2.Install and configure CE 5.0 Includes creating two object stores: Design and Target 3.Install and configure PE 5.0 Includes initializing a process store and associating it with the target object store via the connection point 4.Install and configure WP XT Install and configure Mashup Center Use the Case Manager 5.0 Integrated Installer to install: Case Builder Case Client Case Manager Admin Client (CMAC) Case Manager API 7.Use CMAC to configure the Design and Target object stores 21

22 2- Case Builder Performed by: Business Analyst Design the artifacts needed for the case: case types, document types, properties, and tasks Save the design files (solution package) to the design object store 22 Deploy the case to the development target object store Registers OOTB or custom spaces/pages end user UI for the solution Transfers the workflow definitions for the tasks Instantiates task, event handler, and other case object model object types Allows you to test case logic Clicking the Test button opens the Mashup Center/Case Client and allows the Business Analyst to modify the end user interface, assign role membership, create cases and visualize the case solution.

23 Case Builder Manage Solutions Page 23

24 3 Case Client Assign users to roles and create cases Test the solution by emulating different roles Optionally, customize the OOTB pages 24

25 4- (optional) Process Designer Case Builder to Model Human Tasks. Process Designer for Business Process Choreography Full round tripping support with Case Builder 25

26 5- Deploy solution to a new environment Use CMAC to deploy the solution to a different target object store in the same P8 domain Use CMAC and FileNet Deployment Manager (FDM) to move the solution to a different P8 domain Use CMAC to upload spaces from Mashup Server to the design object store Use FDM to export the solution from the current design object store to the design object store in the new P8 domain Use CMAC in new environment to deploy the solution to the new target object store and Client Client to update users and roles as appropriate 26

27 How Does a Case Solution Map to a P8 Environment IBM Case Manager assets are stored in a associated Content Engine object store and Process Engine process store Associated via PE connection point Each object store/isolated region pair can host multiple solutions A solution maps to a PE application space In an object store, the solution consists of a set of: Property templates, class definitions, case type classes, task type classes, event actions, subscriptions, event handler code modules In an isolated region, the solution consists of a set of: Application space, roles, rosters, event logs, work queues, in-baskets The workflow instances and content associated with a case instance have a common case and task IDs 27 The Case Runtime UI is comprised of a set of spaces and pages stored in a Mashup Server

28 Deploying a Solution from Development to Production Development Domain Case Builder Initiates Deployment Production Domain CMDOS CMAC Initiates Deployment FDM CMDOS Target OS PE Sandbox 28 Target OS Target OS PE PE Production Target 1 Production Target n

29 Object Model A Detailed View 29

30 Simplified Architecture with Object Model (CE: Deployed ACM Solution) 30

31 Design Object Store Folder Structure 31

32 Target Object Store Folder Structure 32

33 Case Object Model Classes Case definitions Symbolic names for all ACM based classes and properties begin with the prefix CmAcm Deployed solution and cases are managed as folders Folder SubClasses CmAcmBaseCase (abstract) CmAcmCaseFolder (abstract) CmAcmCaseSubfolder CmAcmDeployedSolution CmAcmDeployedCaseType CmAcmCaseTypeSubfolder Case comments are managed as case folder annotations Annotation Subclasses CmAcmCaseComment CmAcmTaskComment (Note: Not supported in runtime UI for v1) CmAcmWorkItemComment CmAcmVersionSeriesComment

34 Case Object Model Classes Case definitions cont d Tasks are managed using a new Content Engine Task object Task Subclasses CmAcmCaseTask (abstract) CmAcmTaskWithInitiatingDocument (abstract) New property added to base document class and all document subclasses New Object Value Property CmAcmAssociatedCase

35 Case Object Model Classes Case definitions cont d Other ACM classes Custom Event Subclass CmAcmCaseFileEvent ClassSubscription Subclasses: CmAcmDocumentCreateCaseSubscription (synchronous CREATE event on document classes) CmAcmTaskWorkflowLaunchSubscription (asynchronous CHANGE STATE event on Case Task subclasses) Choice List Instances: CmAcmCaseStateChoiceList, CmAcmLaunchModeChoiceList, CmAcmDeploymentStateChoiceList, CmAcmGroupModeChoiceList, CmAcmRequiredStateChoiceList, CmAcmDisabledStateChoiceList, CmAcmActionChoiceList

36 Task Types, States, and Groups Types Discretionary Manual Automatic Repeatable Required Optional States Ready Working Failed Disabled DisabledByExclusive DisabledByUser DisabledAborted Groups Ungrouped Mutually Exclusive Inclusive 36

37 Task Launch Modes System Manual System Automatic User Automatic System Manual Repeatable System Automatic Repeatable System Automatic Launch Modes These modes occur when Preconditions are designed into the case solution. Precondition types are document filing and case metadata triggers 37

38 Case States New Initializing Working Complete Failed 38

39 Deployment States When Deploying from CMAC or Case Builder allowable states are Initiated Complete Failed 39

40 Platform Support Matrix Component Minimum Component Level Minimum Level Component Workplace XT ilog Jrules 7.1 OS Content Engine 5.0 IBM Content Analyzer 2.2 AIX 6.1 Process Engine 5.0 Case Analyzer 5.0 RHEL 5.4 Case Builder 5.0 Cognos RTM 10.1 Case Manager API 5.0 Cognos BI 8.4 Tivoli Directory Server 6.2 Case Client 5.0 Process Simulator 5.0 Active Directory 2008 Lotus Mashups 3.0 P8 eforms x Websphere x Lotus Sametime Websphere Process Server 7.0 Websphere Integration Developer 7.0 w/feature Pack 2 40 Minimu m Level LDAP Database Oracle 11g DB2 9.7

41 Q&A 41