Cover image for Continuous Business Process Management with HOLOSOFX BPM Suite and IBM MQSeries Workflow.
Continuous Business Process Management with HOLOSOFX BPM Suite and IBM MQSeries Workflow.
Title:
Continuous Business Process Management with HOLOSOFX BPM Suite and IBM MQSeries Workflow.
Author:
Redbooks, IBM.
Personal Author:
Physical Description:
1 online resource (558 pages)
Contents:
Front cover -- Contents -- Notices -- Trademarks -- Preface -- The team that wrote this redbook -- Notice -- Comments welcome -- Part 1 Introduction -- Chapter 1. Overview -- 1.1 Continuous Business Process Management -- 1.2 BPM Suite architecture -- 1.3 HOLOSOFX company overview -- 1.4 Product information -- 1.4.1 BPM Suite V4.1 -- 1.4.2 BPM Suite V4.2 new features overview -- 1.4.3 MQSeries Workflow -- 1.5 Case study -- 1.5.1 Company background -- 1.5.2 Current environment -- 1.5.3 Process overview -- 1.5.4 Interview notes -- 1.5.5 Business rules -- 1.5.6 Goals -- 1.5.7 Sales Order process (To-Be) -- Chapter 2. Environment setup -- 2.1 BPM Workbench lab architecture and setup -- 2.1.1 Prerequisites -- 2.1.2 BPM Workbench installation -- 2.2 BPM Server lab architecture and setup -- 2.2.1 Prerequisites -- 2.2.2 BPM Server installation -- 2.2.3 BPM Server configuration -- 2.2.4 Publisher Server installation and configuration -- 2.3 MQSeries Workflow Runtime lab architecture and setup -- 2.3.1 Workflow Server - tier 2 -- 2.3.2 Web Client - tier 1 -- 2.3.3 Workflow System Group -- 2.3.4 Queue manager clustering -- 2.3.5 MQSeries Workflow Runtime object naming convention -- 2.3.6 MQSeries Workflow Runtime setup: step-by-step approach -- 2.3.7 Web Client - tier 1 -- 2.4 BPM Monitor lab architecture and setup -- 2.4.1 Prerequisites -- 2.4.2 DB2 configuration -- 2.4.3 MQSeries Workflow client configuration -- 2.4.4 BPM Monitor installation -- 2.4.5 BPM Monitor configuration -- Part 2 Create -- Chapter 3. Phase 1: Establish process modeling methodology -- 3.1 Overview -- 3.1.1 Description -- 3.1.2 Timing -- 3.1.3 Roles and responsibilities -- 3.1.4 Tools -- 3.1.5 Outputs -- 3.2 Determine the modeling objectives -- 3.3 Process knowledge -- 3.4 Documenting procedures -- 3.4.1 Elgin procedure documentation -- 3.5 Process redesign.

3.5.1 Automation/Implementation of new technology -- 3.5.2 Correction of an inefficient process -- 3.5.3 Integrating different processes -- 3.6 Define process boundaries -- 3.7 Number of subprocesses -- 3.8 Process boundaries diagram -- 3.9 Identify key process issues -- 3.9.1 Process group interviews -- 3.9.2 SWOT analysis -- 3.9.3 Problem statement -- 3.10 Set process performance targets -- 3.11 Outline the data collection plan -- 3.11.1 Data required for all models -- 3.11.2 Data collection interviews -- 3.11.3 Data collection team meetings -- 3.12 Plan for the modeling phase -- 3.13 Develop the modeling policies -- 3.13.1 Naming conventions -- 3.13.2 Organizational data -- 3.13.3 Process data -- 3.13.4 Documentation data -- 3.14 Determine the modeling approach -- 3.14.1 High-Level Decomposition -- 3.14.2 Strawman -- 3.14.3 Combination -- 3.15 Next steps -- Chapter 4. Phase 2: Create the As-Is business process -- 4.1 Overview -- 4.1.1 Description -- 4.1.2 Timing -- 4.1.3 Roles and responsibilities -- 4.1.4 Tools -- 4.1.5 Output -- 4.2 Model As-Is process -- 4.2.1 Develop As-Is models -- 4.2.2 What you need to know before you start modeling -- 4.2.3 The processes at a glance -- 4.2.4 Opening BPM Workbench and creating an organization file -- 4.2.5 Naming and saving a new process -- 4.2.6 Modeling the High-Level Sales Order (As-Is) process -- 4.2.7 BPM Workbench features useful after process modeling -- 4.2.8 Develop As-Is process documentation -- 4.2.9 Validate the As-Is model -- 4.2.10 Add the data to the As-Is models -- 4.2.11 Sign off -- 4.3 Perform analysis on the As-Is model -- 4.4 Next steps -- Chapter 5. Phase 3: Create the To-Be business process -- 5.1 Overview -- 5.1.1 Description -- 5.1.2 Timing -- 5.1.3 Roles and responsibilities -- 5.1.4 Tools -- 5.1.5 Outputs -- 5.2 Define redesign goals -- 5.3 Model To-Be process.

5.3.1 Develop To-Be models -- 5.3.2 Develop To-Be process documentation -- 5.3.3 Validate the To-Be model -- 5.3.4 Add the data to the To-Be models -- 5.3.5 Sign off -- 5.4 Perform analysis on the To-Be model -- 5.5 Next steps -- Chapter 6. Phase 4: Define business measures -- 6.1 Overview -- 6.1.1 Description -- 6.1.2 Timing -- 6.1.3 Roles and responsibilities -- 6.1.4 Tools -- 6.1.5 Output -- 6.2 Understanding business measurement systems -- 6.2.1 Business impacts of an effective measurement system -- 6.2.2 Benefits of an effective measurement system -- 6.2.3 Measures characteristics -- 6.3 Identify the business measures -- 6.3.1 Identify goals -- 6.3.2 Identify important process issues -- 6.3.3 Determine categories and required measures -- 6.3.4 Determine available data required for business measures -- 6.4 Business measures analysis -- 6.4.1 Explanation of business measures -- 6.4.2 Identify business measures for To-Be order process -- 6.5 Next steps -- Part 3 Collaborate -- Chapter 7. Phase 5: Communicate and verify business process model -- 7.1 Overview -- 7.1.1 Description -- 7.1.2 Timing -- 7.1.3 Roles and responsibilities -- 7.1.4 Tools -- 7.1.5 Output -- 7.2 Using the BPM Repository Web Client -- 7.2.1 Logging on to the BPM Repository Web Client -- 7.2.2 Importing process models into the BPM Repository -- 7.2.3 Checking out processes from the BPM Repository -- 7.2.4 Creating new versions of your process models -- 7.2.5 Checking in process models -- 7.2.6 Copy and check out with key update -- 7.2.7 Administrative functions -- 7.3 Publishing process models in BPM Web Publisher -- 7.3.1 Logging on to the BPM Web Publisher Web Client -- 7.3.2 Import your process model into the BPM Web Publisher -- 7.3.3 Viewing process models in the BPM Web Publisher -- 7.3.4 Viewing policies in the BPM Web Publisher.

7.3.5 Viewing procedures in the BPM Web Publisher -- 7.3.6 Viewing organization units in the BPM Web Publisher -- 7.4 Next steps -- Part 4 Automate -- Chapter 8. Phase 6: Build the MQSeries Workflow model -- 8.1 Overview -- 8.1.1 Description -- 8.1.2 Timing -- 8.1.3 Roles and responsibilities -- 8.1.4 Tools -- 8.1.5 Output -- 8.2 Conversion of the To-Be model -- 8.2.1 To-Be Model Review -- 8.2.2 Setting editing mode -- 8.2.3 MQSeries Workflow model conversion -- 8.2.4 Converted MQSeries Workflow model -- 8.3 Define topology -- 8.4 Define Application objects -- 8.5 Define data/control flow -- 8.5.1 Defining data fields and data structures -- 8.5.2 Defining data flow model -- 8.5.3 Defining control flows -- 8.5.4 Control flow and data flow -- 8.5.5 Data flow only -- 8.5.6 Mappings between activities -- 8.5.7 Mappings within activities -- 8.5.8 Data mappings for the case study -- 8.6 Create staffing and organization models -- 8.6.1 Organization -- 8.6.2 Function -- 8.6.3 Level -- 8.6.4 Roles -- 8.6.5 Employees -- 8.7 Define implementation attributes -- 8.7.1 WF Sales Order process (high-level process) -- 8.7.2 WF Credit rating check subprocess -- 8.7.3 WF Credit Review subprocess -- 8.8 Business measures for MQSeries Workflow process -- 8.8.1 Define data field metrics -- 8.9 Define location -- 8.10 Define business measures -- 8.11 Define expressions -- 8.12 FDL generation -- 8.12.1 Model verification -- 8.12.2 Validating the MQSeries Workflow data -- 8.12.3 FDL generation -- 8.13 Next steps -- Chapter 9. Phase 7: Model the user interfaces -- 9.1 Overview -- 9.1.1 Description -- 9.1.2 Timing -- 9.1.3 Roles and responsibilities -- 9.1.4 Tools -- 9.1.5 Output -- 9.2 Getting around in Xform Designer -- 9.2.1 Determine required new interfaces at the activity level -- 9.2.2 Model activity user interfaces -- 9.2.3 Associate forms with activities.

9.2.4 Obtain user approval and validation for the new interfaces -- 9.3 Next steps -- Chapter 10. Phase 8: Build the object models -- 10.1 Overview -- 10.1.1 Description -- 10.1.2 Timing -- 10.1.3 Roles and responsibilities -- 10.1.4 Tools -- 10.1.5 Output -- 10.2 Getting around in UML Modeler -- 10.3 Requirements analysis -- 10.4 Use case diagrams -- 10.4.1 Use case definition -- 10.4.2 Use case analysis -- 10.4.3 Identifying actors -- 10.4.4 Identify use cases -- 10.4.5 Identify relationships -- 10.4.6 Complete the use case diagram -- 10.5 Interaction diagrams -- 10.5.1 Interaction diagram analysis -- 10.5.2 Identifying objects -- 10.5.3 Identifying object links -- 10.6 Class diagrams -- 10.6.1 Class definition -- 10.6.2 Identifying attributes -- 10.6.3 Identifying operations -- 10.6.4 Identifying relationships -- 10.7 Import any existing models -- 10.8 Export models to continue component development -- 10.9 Next steps -- Chapter 11. Phase 9: Model partner interfaces -- 11.1 Overview -- 11.1.1 Description -- 11.1.2 Timing -- 11.1.3 Roles and responsibilities -- 11.1.4 Tools -- 11.1.5 Output -- 11.2 Identify partner touch points -- 11.3 Create partner interfaces process models -- 11.4 Next steps -- Chapter 12. Phase 10: Automate the MQSeries Workflow model -- 12.1 Overview -- 12.2 Configuring the Sales Order process -- 12.2.1 Installing and setting up the Java environment -- 12.2.2 Importing the Sales Order FDL -- 12.2.3 Creating a user ID as the process starter -- 12.2.4 Executing our MQSeries scripts -- 12.2.5 Granting access to the MQSeries Workflow Runtime database -- 12.3 Sales Order process model architecture -- 12.4 Executing the Sales Order process -- 12.4.1 Test data -- 12.4.2 Starting the Check For Credit Availability activity -- 12.4.3 Starting CreditRequest simulator -- 12.4.4 Stepping through MQSeries Workflow activities.

Part 5 Manage.
Local Note:
Electronic reproduction. Ann Arbor, Michigan : ProQuest Ebook Central, 2017. Available via World Wide Web. Access may be limited to ProQuest Ebook Central affiliated libraries.
Electronic Access:
Click to View
Holds: Copies: