impact 2013 2963 - ibm business process manager top practices

© 2013 IBM Corporation

IBM BPM Top Practices Brian Petrini - IBM Software Services for WebSphere

Paul Pacholski – Worldwide WebSphere BPM Tools Technical Sales Lead

Michele Chilanti - Worldwide Technical Sales Organization

2963

2 2 © 2013 IBM Corporation

Please Note

IBM’s statements regarding its plans, directions, and intent are subject to change or withdrawal without notice at IBM’s sole discretion.

Information regarding potential future products is intended to outline our general product direction and it should not be relied on in making a purchasing decision.

The information mentioned regarding potential future products is not a commitment, promise, or legal obligation to deliver any material, code or functionality. Information about potential future products may not be incorporated into any contract. The development, release, and timing of any future features or functionality described for our products remains at our sole discretion.

Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user’s job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.


3

Out-of-box Process Portal

Configurable Business Space

Optional Microsoft Add-ons

BPMN Rules Monitoring BPEL ESB

Process Server

IBM Business Process Manager

Process Designer

Governance of Entire BPM Life Cycle

Shared Assets Versioned Assets Server Registry

Design Deploy Improve

Measure

Business & IT Authors IT Developers

Authors & Admins

Process End-Users Process Owners

Integration Designer

Process Center

BPM Repository

Backward compatibility,

easy migration from WLE &

WPS

IBM BPM widgets work

with IBM WebSphere

Portal


•  Design and Development: ‒  Getting Ready for Your Project ‒  Architecture and Design ‒  Modeling and Implementation

•  Administration and operations:

‒  Deployment Architecture Best Practices ‒  BPM Solution Administration Best Practices ‒  BPM Infrastructure Design Best Practices

Agenda


Design and Development Best Practices: Getting Ready for Your Project


Business Analyst Process

Owner Review

Business Designer

Carefully select processes that are good candidates for automation

•  Model Process •  High level Analysis •  Heat map impact assessment of duration, cost, systems, risk •  Identify Pain points •  Common Vocabulary

•  Enhance Process •  Detailed Analysis •  Simulation •  Analysis of historical info (for executed processes) •  Design and Develop processes for Execution Real

“Historical” data

•  Automated Processes •  Collection of real time metrics •  Interact with executing processes •  Review reports and dashboards

Processes

People Knowledge

High Value Processes Identified

Processes for Automation

Business User

Blu

ewor

ks L

ive

Proc

ess

Des

igne

r Pr

oces

s Se

rver


Develop a Project Glossary – the Importance of a Common Vocabulary

•  Ensure your project team is on the same page when it comes to defining: ‒  SOA ‒  A service ‒  A process ‒  An Enterprise Service Bus ‒  A Service Registry ‒  A Service Gateway

•  During process discovery, develop vocabularies ‒  Unequivocally define business items

Ø  Customer, Claim, Order, etc. ‒  Verbs

Ø  Acquire, cancel, terminate, etc. ‒  Trigger events

Ø  Decisions, conditions, timers, etc. ‒  Activities

Ø  Cancel claim, submit order, etc.


Basic Characteristics for Processes

• Time-span

• Granularity

• Human interaction

• Principal objects

• Application integration

• Complexity

• Monitoring

• Flow ownership

• Dynamicity • Performance • Volumes • Business value • State management • Security •  Infrastructure

Note the similarity in style with the collection and analysis of “interface characteristics”

Planning estimates that have not been based on a discussion of at least these characteristics could well be wrong by one or even two orders of magnitude


Basic characteristics for processes with example detailed questions •  Time-span

‒  Max, min, average for process? ‒  Expected length of human tasks? ‒  Long breaks in process?

•  Granularity ‒  Is the granularity consistent? ‒  Are the steps business relevant? ‒  Are the steps really integration logic? ‒  Are the steps actually screen flow?

•  Human interaction ‒  Sophistication of User Interface? ‒  Number of users? ‒  Number of concurrent users? ‒  Location of users? ‒  Grouping of users?

•  Principal objects ‒  What is/are the primary business objects involved? ‒  Does the primary object change during the process? ‒  What’s the size/complexity of the object structure?

•  Application integration ‒  Where do we interact with a back end system? ‒  See “Integration Characteristics”

•  Complexity ‒  Number of steps? ‒  Merges, joins, choices? ‒  Loops - how many iterations?

•  Monitoring ‒  What statistics need to be gathered (counts, sums) ‒  Across what dimensions (dates, regions etc.)

•  Flow ownership ‒  Who/what owns the flow as the process progresses (user, GUI, back end systems etc.) ‒  What other process based capabilities are in situ for other processes in the organisation?

•  Dynamicity ‒  What could change over time (values, logic, data structure)? ‒  How quickly would changes need to be implemented? ‒  Who would initiate the change? ‒  Who would authorise the change? ‒  Who would perform the change (business, IT)? ‒  How testable is the change?

•  Performance ‒  What transaction rates are anticipated (e.g. tps)? ‒  What concurrency/parallelism issues are there?

•  Volumes ‒  What are the volumes of data over time? ‒  How much of that data should be retained? ‒  What is the archiving policy?

•  Business value ‒  How much money does each transaction make/save for the business? ‒  How much will it cost if transactions are delayed or fail? ‒  What other types of cost effects are there (e.g. reputational)

•  State management ‒  Where are the principle objects currently stored? ‒  Are we creating/storing new information? ‒  Where will the new information be stored? ‒  What triggers changes to the data (how event driven is the process)?

•  Security ‒  Who is authorised to see the data? ‒  What level of privacy is attached to the data?

•  Infrastructure ‒  What infrastructure is already in place?


Understand Characteristics of Services and Interfaces

Service Exposure Characteristics (candidates for registry meta-data)

•  Soft attributes Ø ID Ø Short name Ø Description Ø Expected re-usability

•  How do I use it? Ø Interaction type Ø Transport Ø Protocols Ø Data formats Ø Principal data objects Ø Physical Address Ø Validation Ø Error responses

•  Service level agreements

Ø Response times Ø Expected processing time Ø Reliability Ø Availability Ø Downtime windows Ø Recoverability Ø Monitoring/Visibility

•  Governance Ø Consumers and subscribers Ø Versioning strategy Ø Notification strategy Ø Ownership Ø Privacy

Interface Characteristics (basic or “first pass” characteristics)

•  Principal data objects •  Request/response objects •  Operation/function •  Validation •  Transactionality •  Statefulness •  Event Sequence •  Idempotence •  Data Ownership •  Privacy •  Mean time between failures •  Maintenance schedule •  Delivery assurance

•  Synchronous or Asynchronous

•  Request/Response or Fire/Forget

•  Batch or real-time •  Response times •  Throughput •  Availability windows •  Volumes •  Message size •  Known exception

conditions •  Error management

capabilities •  Transport •  Protocols •  Data formats

Integration is all about handling the differences between consumer and provider

Capturing integration complexity for BPM and SOA solutions http://www.ibm.com/developerworks/websphere/techjournal/1112_clark/1112_clark.html


Design and Development Top Practices: Architecture and Design


Carefully plan packaging decisions

• When making the packaging decisions, think how to avoid future implementation refactoring and versioning needs

•  Remember! ‒ Processes and services packaged within the same Business Process

Applications will have to be versioned together ‒ Dependencies between Process Apps and Toolkit snapshots are static

•  Recommendations: ‒ Package “private services” within the same Process App (SIMM level 2) ‒ Package in a Toolkit to accomplish reuse (SIMM level 3)

Ø  Package related AIS in the same Toolkit ‒ Use the façade pattern (discussed later) to let processes interact with

services at higher SIMM levels Ø  Decouple service invocation and implementation


Consider How you Split up SCA Modules •  You need to strike the right balance between:

‒  Total number of SCA modules ‒  Number of components in a module

•  Large number of modules (>100 on a cluster) impact SI Bus, server

performance ‒  Administrative burden too

•  Large number of components in a module limit concurrent access by

different developers ‒  Assembly diagram is one per module

•  Toolkits containing Advanced Integration Services:

‒  Each snapshot results in an SCA module!


Adopt the Service Façade pattern for AIS reuse

Use the “Service Façade” pattern: ‒  To enable processes and services to be versioned independently ‒  To limit the number of modules deployed to Process Server ‒  To promote isolation of private service interfaces used for AIS implementations

•  For a complete discussion on this pattern: http://www.ibm.com/developerworks/websphere/bpmjournal/1112_pacholski/1112_pacholski.html


Façade Pattern Example: Late Binding to Implementation

Service Facade

Service Impl

Façade Impl.

Gateway Impl.

i

Module Process App Toolkit


Do Business Logic in the right layer

Operational Systems (Applications & Data)

Requesters

Integration Hub Adapter Adapter Adapter

Business Process Manager

Service Exposure Gateway So where should we do orchestration?


Break Down Your Project into the Right Type of Modules

•  Think about mediation logic vs. process logic

•  Use Mediation Modules (WebSphere ESB & Process Server) for integration / mediation logic:

‒  Short-running, minimal choreography ‒  Supports header manipulation ‒  “Litmus test”

Ø  If you remove the mediation, consumer and provider should be able to understand each other, if you forgive routing and protocol/data transformation

•  Use (Integration) Modules (WebSphere Process Server only) for business / process logic:

‒  Can be long-running, powerful choreography and business logic

•  More Information: ‒  http://www.ibm.com/developerworks/websphere/library/techarticles/

0803_fasbinder2/0803_fasbinder2.html


Design and Development Best Practices: Modeling and Implementation


Keep the Structure of BPMN Processes Simple

•  Make sure you capture only the key steps of business processes within your executable process model

‒  At the top level, process flows should be as simple as possible (few activities)

‒  The process data model should only deal with process-relevant information (discussed later)

•  Do not over-use BPMN for integration ‒  Avoid sequences of system tasks ‒  Delegate complex orchestrations to Integration Designer artifacts ‒  But you can construct page flows within BPMN activities in Process Designer

•  Each human tasks should represent a significant step in the process

‒  Typically, a step where the process flow experiences a hand-over to a different participant

‒  Avoid modeling synchronous page flows as sequence of human tasks Ø  Page flows should be implemented within an activity as a flow of coaches


Good Modeling Practice: Example

Process Level: only the key steps (activities) are

modeled

Activity Level: the fine grained

implementation and page flows are modeled here


Questionable Modeling Practice

•  Multiple consecutive human activities on the same swimlane:

Synchronous service call

These should be coaches


Make use of “ad-hoc”, event-driven semantics, and collaboration

•  These constructs can greatly simplify and de-clutter process models ‒  In cases where certain steps or activities may occur at any point in time

within a process flow

Manager may cancel order at any time

ERP may signal updates at any time

“Ad-hoc” start event

Event sub-process


Modeling Data: Expose only process-relevant information as process state

•  Do not capture the entire application data model in process variables

•  Ideally, process state should only contain information necessary for: ‒  Process navigation

Ø  Information necessary to support decisions on which path needs to be taken

‒  Visibility Ø  Information needed for monitoring, dashboards, SLAs, KPIs, etc.

‒  Searches

Ø Business data needed to retrieve process instances or tasks

•  Everything else should go in the Systems-of-Record or in a custom database ‒  And retrieved or made persistent when and where appropriate


Deal Appropriately with Large Data

•  Objects in excess of 5MB are considered large ‒  But in high-volume environments, even much smaller objects (few

hundred KB) can cause issues

•  Large objects pose significant challenges: ‒  Performance, memory management

•  Best practices ‒  Use the “claim check pattern”: store large objects in a DB as soon as

you can, and carry a reference in the processes ‒  Explore fragmenting large objects into smaller objects before sending

them to BPM ‒  Ensure that exceptionally large objects are dealt with one at a time

Ø  If possible, reduce poll time and set poll quantity to 1 in adapters ‒  Increase JVM heap size

Ø Use 64-bit platforms to overcome heap size limitations of 32-bit JVMsc


Expose Complex Services to Processes via AIS

•  When invoking directly complex Services into Process Designer (PD) my be problematic

•  The data types exposed to PD may be too complex to handle in PD •  The data types my not all be business process relevant •  The binding my bot be handled well or handled at all in PD (i.e. MQ, or CICS via

J2C Adapter) •  Dealing with technical faults in human centric processes is a challenge

•  Use Integration Designer to import the Complex Service •  Define AIS with only the data that the business process required (canonical

view) •  Hide the IT business objects or complex XSD structures (technical data) using

Mirrored Libraries •  Use data transforms to convert canonical data to technical data •  Translate technical faults to business faults for use in business process

Challenge

Suggested Good Practice


Business Process View of Complex Integration

AIS SAP Service retrieves “Net Sales Amount”

Global fault handler process

AIS is defined in this Toolkit


IT View of Complex Integrations – Imlement AIS

Right clicks to select the implementation type. Integration designer generates desired implementation type


Connectivity to Backend Systems - Bindings

BPLE Process orchestrates complex integrations


Hide Complex IT Data in Private Libraries

This folder contains a

large number of complex SAP types!

Since these SAP data types are in private library they are not visible to Business Author!

Simple business process data types defined by business user

Complex IT data in private library!

Simple business data in shared library!


IT View: Data Mapping, Error Handling

BPEL component is exposed as AIS and invokes the SAP Web Service

Create data maps

Author fault handler


Data Mapping

XSLT Map maps from complex SAP instance returned by the Web Service to the data object defined by the Business Author

Sophisticated transforms available in the mapper – i.e. in this case different data type representation used in SAP and defined by Business Author

Complex, Large, All Data

Simple, Small, Required Data


Faults

•  How to handle technical and business faults that are coming from complex integrations in a business process?

•  Remember: unhandled faults can lead to failed process instances and cause operational chaos!

•  Modelled (aka Business) faults ‒  Explicitly exposed in interfaces ‒  Normally have business significance ‒  Handle modelled faults where appropriate

Ø  Translate to Business Faults (typically can be handled by the calling process)

•  Un-modelled (aka Technical) faults ‒  Do not appear in interfaces ‒  Should have only a technical purpose ‒  Handle un-modelled faults as close to the source as possible

Ø  Translate to Business Faults (typically un-recoverable)

Challenge



Technical and Business Faults

Technical Faults – Unrecoverable, handled outside of the process

Business Faults – Recoverable, handled by the process


Service orchestration: What’s Best?

•  There are a number of options to orchestrate multiple automated service invocations: –  You can do it in BPMN

•  Each service call in a separate activity •  Multiple service calls within the same activity

–  You can do it in BPEL •  “Macro-flows” •  “Micro-flows”

•  What’s best?

•  Privilege BPEL over BPMN for service orchestration •  Privilege micro-flows over macro-flows •  Privilege BPMN for human workflow •  Watch out for the well-known “straight-through processing with exception

handling” pattern!

Challenge



Implemented as Integration Services in Process Designer BPMN: Three Integration Services

BPMN: Single Integration Service


Implemented as BPEL Processes

BPEL: Long Running

BPEL: Microflow


BPMN: ThreeIntegrationServices

BPMN: SingleIntegrationService

BPEL: LongRunning BPEL:

Microflow

How much faster? VERY FAST

FAST

SLOW

Relative Performance

VERY SLOW


BPMN Process Handles Business Faults

AIS SAP Service retrieves “Net Sales Amount”

Global fault handler process

AIS is defined in this Toolkit


Administration and Operations Deployment Architecture Best Practices


Adopt the Recommended Product Topology

•  How do I set up a development environment with a large number of business and IT developers? ‒  Process Center may need to accommodate 10 or 100s or concurrent Business Authors

and Integration Developers

•  How do I ensure the Process Center does not become a bottleneck? ‒  Integration Designers that develop and test complex integrations may put a large strain

on the Process Center when testing their applications

•  Implement the Recommended IBM BPM Topology: http://www.redbooks.ibm.com/redpieces/abstracts/sg247976.html?Open

•  Cluster Process Center (in 8.5, you will have to)

•  Optimize Process Center database

•  Use local Test Environment Process Server for unit testing of AIS implemented in Integration Designer

•  Use Satellite Feeder Process Centers for mutisite developement

Challenge



Recommended IBM BPM Topology

Process Server QA Test

Process Center Centralized repository Centralized deployment

Centralized governance

Process Server Staging Test

Process Server Production

Integration Designer Workstation

Process Designer Workstation

Process Center Console

Unit Test Environme

nt

IT Developers

Administrators

Business & IT Authors

Administrators

Process Admin Console

Runtime Environments

Administrators


“Satellite” Feeder Development Process Centers

PS QA Test

PS Staging Test

PS Production

Canada Main PC


Process Designer


Process Designer

Europe Feeder PC

Australia Feeder PC

China Feeder PC

P

P

P C

Consumer PC Provider PC P

C


Administration and Operations BPM Solution Administration Best Practices


Become Familiar and Use Process Admin

•  The Process Admin console offers a powerful interface that allows for monitoring, managing, and troubleshooting process applications

•  Web application available on all Process Server and Process Center environments ‒  Monitor process execution ‒  Look after individual process instances ‒  Repair “broken” process instances (retry/skip activities, change data,

and more) ‒  Define and manage deployed application settings

Process status summary on the main page allows you to quickly view the status of apps and navigate down to the corresponding instances


Adequately Design your Physical System Topology

•  Define the number of run-time environments, clustered structures, high availability requirements, disaster/recovery objectives

•  Privilege higher-level clustered topologies ‒  Three-cluster “Application, Remote Messaging, and Support”

•  Make your QA and Performance Test environments look like production

•  Consistently use the same database SW and other supporting systems across all

environments

•  Plan for load balancers in front of Process Server clusters

•  What other systems are you connecting to and how will they ensure failover / scalability?

‒  Redbook that discusses production topologies: Ø  http://www.redbooks.ibm.com/abstracts/sg247413.html?Open


Clustered Topology Choices – IBM BPM V8.5

IBM BPM V7.5 STEW

Recommended pattern

Why no more 4-cluster pattern? The clustered topologies of BPM have been consistently analyzed and refined since the WPS v6.0.x timeframe. In v8.5, it became necessary to move a significant component from the Web cluster into the AppTarget cluster. This left very little in the Web cluster, and became difficult to justify the additional JVMs.

• Significant simplification in terms of topological choices in V8.5 • Fewer moving parts, simpler choice of topological patterns

• In V8.5, no more Standalone topologies! • You will always have a clustered topology (albeit initially with a single node)

• Also, there are only two possible topological choices (single or three-cluster topology)


Deploym

entEnvironm

entBus

BPM v8.5 Advanced 3-Cluster Topology

Sprayer IP

IHS

IHS dmgr

Node Agent

ME.mbr1

App.mbr1

Sup.mbr1

Dmgr Node

Custom Node01

ME

(PC Console) Process Admin Process Portal, BSpace, widgets, EmbeddedECM, BPC, SCA, BRM

PDW, CEI, BPC Explorer

Node Agent

ME.mbr2

App.mbr2

Sup.mbr2

Custom Node01

ME

(PC Console) Process Admin Process Portal, BSpace, widgets, EmbeddedECM, BPC, SCA, BRM

PDW, CEI, BPC Explorer

AppCluster

MECluster

SupCluster

CMNDB (cell)

CMNDB (DE) BPC, FEM, ES, BSpace, MEDB

BPMDB Process Server, EmbeddedECM

PDWDB Performance DW

AppSched, Mediations, Rels


Summary for Design and Development

•  Start with a domain decomposition and understand the maturity of your services

•  Spend time to understand service characteristics, designing interfaces, and selecting bindings

•  Architecture and packaging choices are crucial to the success of your project ‒  Consider the façade pattern ‒  Privilege Integration Designer to implement integration services and

orchestrations

•  Follow modeling best practices ‒  Avoid clutter in your process and data model in Process Designer

•  Handle faults appropriately and perform rigorous and repeatable

testing


Summary for Administration and Operations

•  Adopt the recommended product architecture ‒ Process Center, and a number of Process Server

environments ‒ Consider “federating” multiple Process Centers if needed

•  Follow deployment best practices ‒ Use scripted approach with off-line Process Servers

•  Process Admin is your friend – get to know it!

•  Implement clustered topologies for availability and failover ‒  Including for Process Center


We love your Feedback!

Don’t forget to submit your Impact session and speaker feedback!

• Your feedback is very important to us – we use it to improve next year’s conference

• Go to the Impact 2013 SmartSite (http://impactsmartsite/com): ‒  Use the session ID number to locate the session ‒  Click the “Take Survey” link ‒  Submit your feedback


BPM Sessions at Impact 1193 High-Volume, Fast Decision Management for Your System z Applications: Exploring the Why and How Wed, 1/May 03:45 PM - 04:45 PM 1198 Case Study: Sun Life Financial - Shifting from Customization to Configuration with IBM ODM 1201 Meet the Experts: Rule Validation Approaches Tue, 30/Apr 02:30 PM - 03:30 PM 1226 Case Study: Large-Scale Complex Events Processing at USAA Tue, 30/Apr 02:30 PM - 03:30 PM 1365 Hands-On Lab: BPM & ODM Installation, Deployment and Usage Patterns in a Private Cloud Mon, 29/Apr 01:00 PM - 03:30 PM 1366 Smarter Process in the Cloud: BPM and ODM Patterns & SaaS Tue, 30/Apr 01:00 PM - 02:15 PM 1388 Maximizing the Business Value of SAP Using IBM BPM Thu, 2/May 08:45 AM - 09:45 AM 1390 Panel Discussion: IBM BPM for SAP Thu, 2/May 10:15 AM - 11:15 AM 1539 Hands-On Lab: Exploring IBM BPM for SAP Capabilities Mon, 29/Apr 02:30 PM - 03:30 PM 1584 Case Study: IBM Enables Business Process Excellence for eBay Mon, 29/Apr 04:00 PM - 05:00 PM 1752 Meet the Experts: IBM BPM for SAP Wed, 1/May 05:00 PM - 06:00 PM 1781 Introduction to IBM Blueworks Live Mon, 29/Apr 04:00 PM - 05:00 PM 1868 Case Study: Elevations CU's Great Game of Process: The Cool Kids Guide to Making Process Stick Wed, 1/May 03:45 PM - 04:45 PM 2061 Taking Your Processes and Rules Mobile Wed, 1/May 02:15 PM - 03:15 PM 2066 Panel Discussion: Migrating to IBM BPM - Practical Experiences and Lessons Learned Wed, 1/May 10:15 AM - 11:15 AM 2088 Roundtable: BPM Upgrade and Migration Discussion Mon, 29/Apr 02:30 PM - 03:30 PM 2089 Securing Your BPM Installations Thu, 2/May 01:00 PM - 02:00 PM 2102 Improving Business Processes by Aligning BPM and MDM Wed, 1/May 03:45 PM - 04:45 PM 2113 High Performance and Scalability with IBM BPM Wed, 1/May 05:00 PM - 06:00 PM 2147 Roundtable: Blueworks Live Feedback Tue, 30/Apr 02:30 PM - 03:30 PM 2149 Meet the Experts: Using IBM BPM and IBM Blueworks Live Together Wed, 1/May 03:45 PM - 04:45 PM 2191 Integrating BPM with ECM Mon, 29/Apr 10:30 AM - 11:45 AM 2217 Discovering and Automating Decisions Using IBM Blueworks Live and IBM Operational Decision Manager Thu, 2/May 10:15 AM - 11:15 AM 2247 BPM Cloud and Virtualization Technical Update Mon, 29/Apr 02:30 PM - 03:30 PM 2250 Migration Best Practices for BPM Solutions Wed, 1/May 01:00 PM - 02:00 PM 2290 IBM Business Process Manager Production Topologies Tue, 30/Apr 05:15 PM - 06:15 PM 2309 BPM for the Enterprise on System z: Process Hub and Hybrid Deployments Mon, 29/Apr 05:15 PM - 06:15 PM 2388 Process Governance and Deployment Visibility with IBM BPM Process Center Thu, 2/May 08:45 AM - 09:45 AM 2425 Roundtable: Business Process Manager - Tell Us What You Want Mon, 29/Apr 05:15 PM - 06:15 PM 2429 What's New in IBM Business Process Manager Mon, 29/Apr 01:00 PM - 02:15 PM 2440 Governing Operational Decisions in an Enterprise Scalable Way Tue, 30/Apr 04:00 PM - 05:00 PM 2442 Developing Compelling BPM UIs for Tasks and Dashboards Thu, 2/May 02:15 PM - 03:15 PM 2465 What's New in IBM Operational Decision Manager? Wed, 1/May 03:45 PM - 04:45 PM


BPM Sessions at Impact (continued) 2496 Roundtable: Getting Social with IBM Operational Decision Manager Tue, 30/Apr 10:15 AM - 11:15 AM

2510 Extending IBM Business Process Manager with Case Manager to Address New Range of Business Processes Wed, 1/May 10:15 AM - 11:15 AM

2541 Roundtable: Let's Talk Mobile Processes & Decisions Mon, 29/Apr 02:30 PM - 03:30 PM 2554 Hands-On Lab: Introduction to IBM Business Process Manager Tue, 30/Apr 04:00 PM - 06:15 PM 2567 Hands-On Lab: BPM to Go with Worklight and BPM Thu, 2/May 10:15 AM - 11:15 AM 2600 Case Study: Nationwide Rule Authoring Capabilities using IBM ODM Wed, 1/May 05:00 PM - 06:00 PM 2613 Roundtable: IBM Operational Decision Manager - Tell Us What You Want Mon, 29/Apr 04:00 PM - 05:00 PM 2629 Case Study: Johnson Controls Enterprise Approach to Modeling for the Masses Thu, 2/May 01:00 PM - 02:00 PM 2646 Building a Business Rules Application Using ODM Live on Stage! Wed, 1/May 03:45 PM - 04:45 PM 2657 Meet the Experts: The Doctor Is in the House: Operational Decision Manager Rules Open Hours Mon, 29/Apr 02:30 PM - 03:30 PM 2813 Best Practices: Developing Solutions for Comprehensive Visibility with IBM Business Monitor Mon, 29/Apr 05:15 PM - 06:15 PM 2819 Case Study: Banco Espirito Santo Democratizes Processes for Increased Visibility and Control Thu, 2/May 10:15 AM - 11:15 AM 2827 Roundtable: Operational Visibility across Orchestrated and "Virtual" Processes Tue, 30/Apr 10:15 AM - 11:15 AM 2837 For Better Results, Enhance Your Decision Management System with Analytics Thu, 2/May 08:45 AM - 09:45 AM 2847 Decision Management for Customer Analytics and Fraud Wed, 1/May 05:00 PM - 06:00 PM 2850 Hands-On Lab: From Spreadsheet to Business Dashboard in 60 Minutes or Less! Mon, 29/Apr 01:00 PM - 02:15 PM 2856 Hands-On Lab: Building Business Rules and Events Applications Using IBM ODM or IBM ODM for z/OS Thu, 2/May 01:00 PM - 03:15 PM 2865 Meet the Experts: Business and Process Visibility with IBM Business Monitor Mon, 29/Apr 04:00 PM - 05:00 PM 2963 Best Practices: IBM BPM Top Practices to Achieve Smarter Process Tue, 30/Apr 02:30 PM - 03:30 PM 2996 Case Study: PENSCO Creates Insourcing Opportunity with IBM BPM Mon, 29/Apr 04:00 PM - 05:00 PM 3047 Hands-On Lab: Integrate Dynamic Business Rules into Your Other Products to Extend Your Solution Tue, 30/Apr 01:00 PM - 03:30 PM 3098 IBM Operational Decision Manager 101: Taking Business Rules to the Next Level Mon, 29/Apr 04:00 PM - 05:00 PM 3130 Meet the Experts: The Doctor Is in the House: BPM Open Hours Tue, 30/Apr 04:00 PM - 05:00 PM 3131 Meet the Experts: BPM Mobile Tue, 30/Apr 01:00 PM - 02:15 PM 3142 Meet the Experts: Smarter Process Tue, 30/Apr 10:15 AM - 11:15 AM 3187 Tomorrow's Digital Enterprises Will Live or Die by Their Processes. Are You Set? Tue, 30/Apr 10:15 AM - 11:15 AM 3188 Decision Management Cases: Agility and Adaptability in Insurance, Travel and Healthcare Tue, 30/Apr 04:00 PM - 05:00 PM 3220 Panel Discussion: Adopting BPM Wed, 1/May 02:15 PM - 03:15 PM


Legal Disclaimer

•  © IBM Corporation 2013. All Rights Reserved. •  The information contained in this publication is provided for informational purposes only. While efforts were made to verify the completeness and accuracy of the information contained in

this publication, it is provided AS IS without warranty of any kind, express or implied. In addition, this information is based on IBM’s current product plans and strategy, which are subject to change by IBM without notice. IBM shall not be responsible for any damages arising out of the use of, or otherwise related to, this publication or any other materials. Nothing contained in this publication is intended to, nor shall have the effect of, creating any warranties or representations from IBM or its suppliers or licensors, or altering the terms and conditions of the applicable license agreement governing the use of IBM software.

•  References in this presentation to IBM products, programs, or services do not imply that they will be available in all countries in which IBM operates. Product release dates and/or capabilities referenced in this presentation may change at any time at IBM’s sole discretion based on market opportunities or other factors, and are not intended to be a commitment to future product or feature availability in any way. Nothing contained in these materials is intended to, nor shall have the effect of, stating or implying that any activities undertaken by you will result in any specific sales, revenue growth or other results.

•  If the text contains performance statistics or references to benchmarks, insert the following language; otherwise delete: Performance is based on measurements and projections using standard IBM benchmarks in a controlled environment. The actual throughput or performance that any user will experience will vary depending upon many factors, including considerations such as the amount of multiprogramming in the user's job stream, the I/O configuration, the storage configuration, and the workload processed. Therefore, no assurance can be given that an individual user will achieve results similar to those stated here.

•  If the text includes any customer examples, please confirm we have prior written approval from such customer and insert the following language; otherwise delete: All customer examples described are presented as illustrations of how those customers have used IBM products and the results they may have achieved. Actual environmental costs and performance characteristics may vary by customer.

•  Please review text for proper trademark attribution of IBM products. At first use, each product name must be the full name and include appropriate trademark symbols (e.g., IBM Lotus® Sametime® Unyte™). Subsequent references can drop “IBM” but should include the proper branding (e.g., Lotus Sametime Gateway, or WebSphere Application Server). Please refer to http://www.ibm.com/legal/copytrade.shtml for guidance on which trademarks require the ® or ™ symbol. Do not use abbreviations for IBM product names in your presentation. All product names must be used as adjectives rather than nouns. Please list all of the trademarks that you use in your presentation as follows; delete any not included in your presentation. IBM, the IBM logo, Lotus, Lotus Notes, Notes, Domino, Quickr, Sametime, WebSphere, UC2, PartnerWorld and Lotusphere are trademarks of International Business Machines Corporation in the United States, other countries, or both. Unyte is a trademark of WebDialogs, Inc., in the United States, other countries, or both.

•  If you reference Adobe® in the text, please mark the first use and include the following; otherwise delete: Adobe, the Adobe logo, PostScript, and the PostScript logo are either registered trademarks or trademarks of Adobe Systems Incorporated in the United States, and/or other countries.

•  If you reference Java™ in the text, please mark the first use and include the following; otherwise delete: Java and all Java-based trademarks are trademarks of Sun Microsystems, Inc. in the United States, other countries, or both.

•  If you reference Microsoft® and/or Windows® in the text, please mark the first use and include the following, as applicable; otherwise delete: Microsoft and Windows are trademarks of Microsoft Corporation in the United States, other countries, or both.

•  If you reference Intel® and/or any of the following Intel products in the text, please mark the first use and include those that you use as follows; otherwise delete: Intel, Intel Centrino, Celeron, Intel Xeon, Intel SpeedStep, Itanium, and Pentium are trademarks or registered trademarks of Intel Corporation or its subsidiaries in the United States and other countries.

•  If you reference UNIX® in the text, please mark the first use and include the following; otherwise delete: UNIX is a registered trademark of The Open Group in the United States and other countries.

•  If you reference Linux® in your presentation, please mark the first use and include the following; otherwise delete: Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both. Other company, product, or service names may be trademarks or service marks of others.

•  If the text/graphics include screenshots, no actual IBM employee names may be used (even your own), if your screenshots include fictitious company names (e.g., Renovations, Zeta Bank, Acme) please update and insert the following; otherwise delete: All references to [insert fictitious company name] refer to a fictitious company and are used for illustration purposes only.


Questions?

As a reminder, please fill out a session evaluation


Appropriately Configure Process Center

•  Use the 64-bit product version ‒  32-bit version will only give you access to 4GB of memory (less on Windows)

JVM max operating heap of 1GB

•  Cluster Process Center (this is the only option in 8.5) ‒  For scalability, failover, high availability and redundancy. ‒ Refer to the IBM Business Process Manager Production Topologies Redbook:

http://www.redbooks.ibm.com/redpieces/abstracts/sg247976.html?Open

•  Allow enough memory for your Process Center JVMs ‒  Adequately size your heap

•  Dedicate adequate CPU resources to your BPM developers ‒  In average, two CPU cores adequately serve 25-30 developers in version 8


Carefully Configure the Process Center Database • Prefer the 64-bit database product version

• Use a separate database server with at least 2 cores and fast disks dedicated to your database

• Tune the database appropriately to distribute the work over the available disks

• Segment your work so that all of the work isn't happening in one Process App ‒ Use multiple toolkits for reusable services ‒ This way your 5-10 developers will not be always working on the same

ProcessApp or Toolkit

impact 2013 2963 - ibm business process manager top practices

Software

ibm corporation ibm

ibm corporation design

ibm websphere portal

executed processes design

standard ibm benchmarks

wle wps ibm bpm widgets

development best practices

potential future products