2014 IBM Corporation

Top Practices to Ensure a

Successful BPM Migration
Migrate to IBM BPM 8.5.5.0
Allen Chan, IBM BPM SWAT and Lead Architect Install, Config and Migration
Brian Petrini, IBM BPM Technical Product Manager
Jerome Boyer, IBM Software Services, BRMS - BPM Technology,
Please Note
IBMs statements regarding its plans, directions, and intent are subject to change
or withdrawal without notice at IBMs 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 users 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.
Agenda
BPM 8.5.5 and Migration Support
Migration Approches
Migration Enhancement
Top Practices
2
Summary of IBM BPM 8.5.5
3
Dynamic Processes &
Basic Case Mgmt
Unstructured ad-hoc
work
Basic case folder &
document handling
Web-based Case
Editor
Custom Instance UIs
Mobile Ready End-
User Experience
WYSIWYG Coach
Designer &
Responsive Coach
Views
Lite Coach Views
Client-side Human
Services
BPMN2
Enhancements
Correlation
Latency
optimizations
Various
Improvements
Business Monitor
Migration Tooling
Configuration
Management
Various other
items
WPS Upgrade & Migration Paths
From To
Version EOS BPM BPM BPM BPM BPM
751x 800x 801x 850x 855
WPS 602 10/2010
WPS 610 04/2013 Yes
WPS 612 10/2013 Yes
WPS 620 04/2014 Yes Yes Yes Yes Yes
WPS 700 04/2015 Yes Yes Yes Yes Yes
migration
upgrade
For WPS 602 and 61x, we currently do not provide a direct upgrade path for
runtime migration (i.e. preserve existing process instances) to BPM 8xx. However,
customers can still use IID 8xx and manually update the applications to get it
working on the latest BPM level, and then use the drain approach (see later
charts for details).
WLE Upgrade & Migration Paths
From To
Version EOS BPM BPM BPM BPM BPM
751x 800x 801x 850x 855
TW 61x 10/2013 Yes Yes Yes
As needed As needed
TW 62x 10/2013 Yes Yes Yes Yes Yes
WLE 71 10/2013 Yes Yes Yes Yes Yes
WLE 72 04/2016 Yes Yes Yes Yes Yes
migration
upgrade
BPM Upgrade & Migration Paths
From To
Version EOS BPM BPM BPM BPM BPM
751x 800x 801x 850x 855
BPM 750 n/a Upgrade Yes Yes Yes Yes
BPM 751 n/a Upgrade Yes Yes Yes Yes
BPM 800 n/a Upgrade Upgrade Yes Yes
BPM 801 n/a Upgrade Yes Yes
BPM 850 n/a Upgrade Upgrade
migration
upgrade


Migration Approaches
7
Engage IBM EAS and ISSW for a migration assessment and assistant
Plan your migration
8
Plan your migration
1. Understand Your
Reqts and Environment
2. Migration
Assessment
Team Regular Communication
3. Identify Project Team
and Project Plan
4. Develop Migration
Strategy and Documents
7. Test Migration and
Recovery Plan
5. Migration and Test
Your Applications
6. Clean up
Source Environment
8. Go Live Planning
and Execution
Landscape
1- Current product version used to
support existing production
applications
Current
Process Server
(Test/ Staging/
Production)
Current
Process Center
2- New applications are developed on new
version.
New Dev
Process Server
New
Process Center
New Process Server
(Test/Staging/Production)

1
2
4
3
3- Export/import Toolkit for
refactoring
4- Migrate artifacts and/or business data
5- Deploy new and
migrated apps
5
Migration Approach
Drain - Application migration and drain existing instances
Let existing instances in V-old run to completion, start new
instances in V-new system.

Milestone Transfer - Transfer process state mid-stream using custom
logic to new version.
A variation of the Drain approach.
Let existing instances in V-old run to a designated set of business
milestones, start new instances in V-new system from those
milestones.

Runtime Migration - Application migration followed by Runtime
migration
Once ALL applications are working in V-new, convert the existing
database to make it compatible with V-new in one shot.
What to Migrate?
Pros Cons
Artifacts Only
Migration
(Drain or
Milestone
Transfer)
Start with a clean database.
Leave messy data behind.

Parallel production environment
allows for app-by-app migration
and no production downtime.

Process history are not
transferred to the new system.

Parallel production environment
requires additional maintenance
and resources.
Business
Data and
Applications
Migration
(Runtime
Migration)
Source environment applications
and data are migrated to the
target environment.

Process and human tasks can
start in the source environment
and complete in the target
environment.
Bringing over all data depending
on size and complexity can
increase migration risks which
requires additional testing.

Downtime required. All
applications must be ready
before you can start migrating
the system.
Process Center Migration
Observing that Process Center contains playback instances only, there is really no
business needs to migrate playback instances to the new product version. Based on this
assumption, we are simplifying the Process Center migration to application-only migration.

Setup a new PC target environment with new database.
Migrate individual application artifact by exporting active snapshots from source
environment to target environment in chronological order.
Runtime data (instances, tasks, tracking groups, etc) and offline server deployment
information will not be migrated.

Advantages:
One can setup Process Center right away and start working on application migration.
Application can be moved to new product version one application at a time.
Existing V-old Process Center is still available to handle fixes for production system.
No downtime for Process Center.


Not applicable if
Process Center is not
used in your system.


Migration Enhancement
13
BPM 8.5.5 Migration Enhancement
Improve migration robustness, ease-of-use and planning
Revised documentation with enhanced interactive migration guide and guidance on migration
methodology to better guide customers and services on how to plan their migration project.
Migration Pre-Validation Tool + Post-Validation Health Center
Pre-check and report migration potential failures
Save cost of migration late phase failure, recovery and redo
Post-Validation via BPM Health Center, speed up target environment health check
Easier environment setup via Configuration Migration Tool
Migration paths support with a target environment that is set up with about 400 source-
environment basic properties around database, security, and the most important performance
parameters to the clients environment.
Reduce about 50% post-migration actions on properties


Speeding up migration
Quicker migration via multi-thread enablement
Migration from BPM v7.5.1 migration shows 2x ~ 3x improvements
Migration from TW v6.2 migration can see up to 20x improvements


14
Interactive Migration Guide
Help you determine the expected document that matches your
migration scenario, save your effort to search infocenter and
navigate between different topics.

15
Two steps wizard
Validate source environment before migration
We introduced migration pre-validation tool to help you find
potential issues before real migration, and what you should take
care during migration
Validate current environment to make sure its ready to do
migration
Read required information that will be used in latter migration
steps
Show error if itll block migration, or the source environment
isnt in the expected status
Show warning if you need to take care before or after migration
Show warning if there is some big number of data will have
performance impact during migration


16
Validate source environment before migration
Report sample 1 for migration prevalidation
17
Validate source environment before migration
Report sample 2 for migration prevalidation
18
Understand configuration migration
Source environment information
Map to the supported target based on what your source environment was.
Make sure itll reuse old database on the target.
Security
Federated LDAP
LTPA
File registry
Performance tuning
Customized XML files (e.g. 100Custom.xml)
Some properties will be moved to WCCM
Keep remaining customization and copy to each node on the target
Business Process Choreographer
Business Flow Manager
Human Task Manager
19
Understand configuration migration
20
Source Target
Move configuration


Edit the exported properties
file using Configuration
Editor
BPMConfig -migrate
BPMConfig -create
WebSphere Process Server
6.2.x or 7.0.0.x
WebSphere Lombardi
Edition 7.1 or 7.2
IBM Business Process
Manager 7.5.x or 8.0.x
Express/Standard/Advanced
IBM Business Process
Manager 8.5.5.0
Express/Standard/Advanced
/AdvancedOnly
Understand database upgrade
For Standard database: Process Server and PDW database
DBUpgrade will cover both schema update and data transform
Tune the script to get better performance (thread or batch size)
For Advanced database: Common/BPC/BusinessSpace
upgradeSchemaAll will run all required upgrade SQL files
upgradeSchemaAll will also run the initialization SQL for newly
added capability if any
Support to test and validate migration using cloned database
BPMMigrate will update the topology information in the
database
Import SIB messages to the target
Recreate WAS scheduler tasks


21
Understand database upgrade
22
Do other configuration
customization
Estimate migration
window
...
Source


Target
Cloned
Target
Cloned Cloned
Clone database


BPMConfig update -dataSource
Test database upgrade using cloned
database, and finally retarget your
current environment to the original
database to do the last run.
Test migration against
cloned databases
Understand database upgrade
Performance improvement on database upgrade
DBUpgrade have much performance improvement, and you
can add more threads to handle the transform of large number
of instance and task











23

Wang Lei ok, thanks 4:53:22
PM
Cleaning up before migration
The more data we have in the BPM system, the longer it will take
migration to run. So it is important that before we run migration,
remove information that are not required anymore in the new
system.


ProcessInstancesCleanup command to remove completed process
instances.
Performance Data Warehouse prune command for removing PDW
data.
BPMDeleteDurableMessages command to remove durable events
that are no longer needed.

24
BPM Health Center
Check the health status of the deployment environment after
migration, should be the first step to validate migrated
environment before other planned testing
25


Migration Top Practices
26
IBM Services Migration Project Roadmap
Goal:
To provide a high-level
understanding of migration options;
Capture the information that is
relevant to the migration
Recommend next steps.

Steps:
Review current infrastructure &
project goal

Input:
Migration Discovery Questionnaire

Output:
A documented understanding of the
current infrastructure; a
commitment by the client to invest
their time in a Migration
Assessment/Pilot

Goal:
To provide ROM estimates for
migrating selected process
applications and service
integrations in a like for like
fashion from the current
environment to the target
environment

Steps:
Process Application business and
functional review
Process App. architectural review
Process App. source code review

Output:
High level migration approach
ROM estimation

Goal:
To migrate selected process
applications and service
integrations from the current to
target environment

Steps:
Install and configure selected
environments and tools
Migrate code to the new
environment
Perform testing & defect
resolution

Output:
Migrated applications and
environment
Team enabled

Discovery Call
Duration: 2 hours
Discovery Workshop
Duration: 1 to 2 days
No charge
Implementation
Duration: varies, depending on scope
and complexity
Questionnaire: 30 questions to discover the potential
scope
Version
Runtime
Application
Operational model
Test


Converged with WAS
migration
questionnaire
28
Migration Workshop
Goals Review the migration baseline Define application and asset inventory.
Identify customizations
Review current physical architecture
Assess Hardware / Software requirements
Review deployment strategy
Define migration validation strategy
Define migration approach Determine runtime migration approach
Recommend solution architecture.
Recommend BPM topology
Identify key improvement opportunities enabled by
new/enhanced product features.
Define staffing skills needed
Determine next steps Workshop report with recommendations and findings
Rough Order Of Magnitude estimate and project
approach (WBS)
Define the best migration approach
Who IBM Migration Specialist
<IBM BPM Developer>
IBM Client Partner
IT Architect
BPM Developer
Project manager

Format 1 to 2 days No charge
29
Top Practices for Successful Migration
Minimize Refactoring we are often tempted to make significant
changes to the applications as part of a migration project. This
can lead to un-intended delay in projects or make it impossible
to migrate runtime data.
Having a comprehensive regression test plan, including non-
functional tests such as stress and performance tests, can help
eliminate surprises in the project.
Review and playback often and regularly with business and IT
stake holders, this avoids last minute surprises such as user
experience expectation, security concerns, etc.
Use good quality data for in-flight migration testing (UAT or
production databases). Database from development
environment contains a lot of development noise which causes
problems
30
Top Practices for Successful Migration
Test database upgrade using cloned database of production
environment, estimate migration windows and verify the migrated
environment
Carefully test migrated instances for each Application. Some problems
can be revealed only with specific development patterns unique to
specific process application (e.g. serialization changes between TW6
and BPM8 affected event correlation)
There is no fixed formula to estimate the time up front as the migration
depends on a number of factors such as number of process instances,
tasks, users, groups, durable subscriptions, tracking groups, size of
your data and execution context, etc.
Applications should be upgraded and running correctly in target
system at least 2 months before go-live date. Migration and
Performance testing should start as soon as possible, not just a couple
weeks before go-live.


31
Other special considerations
Account of changes in security model early want to switch to
LDAP from file-based repository?
Account for non-standard cluster configuration if youre not
following the IBM recommended golden topology for your setup.
BPM + Monitor. If your source BPM environment is augmented
with Monitor in the same cell, but in BPM 8550, we dont
support BPM and Monitor in the same cell any longer, you have
to follow two separate procedures to migrate BPM and Monitor
to separate cells on BPM 8550.


32
Other special considerations
Test the cases that some instance arrives at an activity that waiting for
some event (UCA), make sure the messages can still be consumed
after migration.
If youre migrating from multiple deployment environments, you need
to do the migration procedure for each of your deployment
environment.
Port number maybe changed after migration, you need to update them
manually or use the new ports.
BPMMigrate command can rerun if it doesnt import SIB messages yet
or you can clean SIB tables before the second run.
Backup fileRegistry.xml if you want to enable LDAP after migration, or
will meet with some errors when try to access the document tables.
We dont support the migration of IID UTE
33
Additional In-depth BPM Sessions
1114 Case Management in IBM BPM Tue 1pm-2pm, Wed 10:30-11:30am
2732 Mobile Smarter Processes Tue 10am-11am, Wed 1pm-2pm
1489 Good bye tw_admin Whats new in BPM Security Mon 10:30-11:30am
1115 Integrating BPM with Enterprise Content Management Wed 2:15-3:15pm
1300 Business Activity Monitoring with IBM Business Monitor Tue 1-3:15pm
1425 High Availability and Disaster Recovery with IBM BPM Mon 5:15-6:15pm
1427 BPM Performance and Scalability: Best Practices Tue 2:15-3:15pm
1563 Maintaining IBM BPM Data With Archiving & Purging Mon 4pm-5pm
1568 Smarter Processes Through Best Practices With IBM BPM Tue 5pm-6pm
1572 Hands-on Introduction to IBM Business Process Mgr Mon 10:30-11:30am
1786 Technical Deep Dive Best Practices for Visibility & Insight Tue 5pm-6pm
1797 Hands-On with New Support for Unstructured Processes Tue 3:45pm-6pm
1905 Using Smarter Process on System z to Achieve Agility Wed 2:15-3:15pm
2770 Top Practices for a successful BPM Migration Mon 4-5pm, Wed 3:45-4:45pm
2832 Business Process Manager Production Topologies Thu 1pm-2pm
2976 WebSphere Foundation and BPM Thu 2:15pm-3:15pm
34
Questions?
We Value Your Feedback
Dont forget to submit your Impact session and speaker
feedback! Your feedback is very important to us we use it to
continually improve the conference.
Use the Conference Mobile App or the online Agenda Builder to
quickly submit your survey
Navigate to Surveys to see a view of surveys for sessions
youve attended
36
Thank You
Legal Disclaimer

IBM Corporation 2014. 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 IBMs 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 IBMs 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.
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.