© 2010 IBM Corporation IBM BPM f.k.a. WebSphere Lombardi Edition f.k.a. Lombardi Teamworks V7 V7 What’s New, Hints & Tips

© 2010 IBM Corporation

IBM BPM

f.k.a. WebSphere Lombardi Editionf.k.a. Lombardi Teamworks V7

V7 What’s New, Hints & Tips

Confidential© 2010 IBM Corporation

WebSphere Lombardi Edition

‣ Improving process efficiencyamong people and systems

‣Driving continuous improvementthrough visibility and analysis

has always been about …

is about scaling up your BPM success, program-wide …

‣ Improving developer productivityto keep up with growing demand

‣Managing delivery complexityacross more projects with Reuse

Successleads to increased demand …

Lombardi Edition

Lombardi Edition


Many Assets

Many Authors

Many Processes

Obstacles to Scaling Up BPM Success …

•1000’s of application assets•Growing disorganization•Poor reuse

Managing Assets &Dependencies •Multiple dev teams

•Multiple dev systems•Parallel development

Developer Productivity

•Dozens of active process projects•Multiple versions per project•Many servers across multiple environments

Complexity ofProcess Lifecycle


Many Assets

Many Authors

Many Processes

Lombardi Edition

Confidential© 2010 IBM Corporation“A Platform for Execution”

Design-Time Scale

New Paradigm for Model Management

Massive Reuse

100,000’s of Assets

100’s of Authors

1,000’s of Processes

Lombardi Edition

© 2010 IBM Corporation

Lombardi Teamworks V7 Tour

Lombardi Edition


Lombardi 7 – Summary Key Concepts

1) Improved Asset Organization

2) Managing Process Change

3) Maximizing Reuse

4) Simplified Deployment

• Process Apps • Tags & Smart Folders

• Library Organization • New Services Types

• Snapshots • Revision History

• Back-in-time • Revert

• Toolkits • Refactoring

• Dependency mgmt

• One-click deploy • Environment Variables

• Installation Services • Managed files


Lombardi 7 – Process Center

• Single shared model repository• Common development system• Centralized deployment control

Teamworks Runtime Environments


Lombardi 7 – Key Concepts


2)

3)

4)


Process Apps & Toolkits


Library Organization


Tags and Smart Folders


New Service Types




2)

3)

4)




Hints & Tips – Asset Organization

‣No need to use prefixes for naming conventions – Process Apps provide unique namespaces

‣Check for Validation Errors in your Process Apps

‣No need to call the WebAPI or TW Java API within process implementations – use new JavaScript API (JSAPI)

‣Tag your assets – makes them easier to find & manage (read community wiki article)

‣Use new Lombardi Service types - they enable additional validation checks





3)

4)




User Presence


Snapshots


Back-in-time


Revert


Snapshot Deployment





3)

4)






Hints & Tips – Managing Process Change

‣Don’t copy a BPD or service to start working on a new version – use snapshots & edit in-place

‣Archive Process Apps and Snapshots that you don’t want to see any more – you can restore them later

‣Take Snapshots at meaningful development milestones

‣Use Snapshot descriptions to help you remember at a glance the main changes you’ve made





3) Maximizing Reuse






Toolkits


Dependency Management


Refactoring





3) Maximizing Reuse

4)






• Dependency mgmt


Hints & Tips – Maximizing Reuse

‣Don’t copy things that you want to reuse into other Process Apps – put them in a Toolkit

‣Replace uses of Service->Integration Def->Connector pattern with Integration Services – they are simpler & easier to maintain

‣Define convention for naming for Toolkit Snapshots that are available for general use

‣Tag items intended for reuse within a Toolkit (versus internal implementation details)





3) Maximizing Reuse







• Dependency mgmt


One-click Deployment


Installation Services


Environmental Variables


Managed Files





3) Maximizing Reuse







• Dependency mgmt




Hints & Tips – Simplified Deployment

‣Backup your Process Center databases. Your revision history and deployment registry include valuable information.

‣Use Installation Services to initialize environments for Process Apps or Toolkits

‣Use Environment Variables to parameterize values for different environments instead of EPVs

‣Use managed files for storing server-side files (JAR, JavaScript libraries) and client-side files (CSS, images, etc.)


Lombardi 7 – Summary Key Concepts



3) Maximizing Reuse







• Dependency mgmt




The gap between deciding and doing is where nothing gets

done.“”


Typical Approach: Tools for the Few to Interview the Masses


IBM BlueworksLive.com: A Place to Talk Process Improvement


How is Process Discovery done today?

‣Figure it out yourself‣Lock the team in a

conference room for day(s)‣Sticky notes‣Butcher paper‣Whiteboard drawings‣Back and forth till you finally

understand your process‣Scribe it all down‣Convert it to a

diagram/drawing


Focused on participation

Single repository, built for process

Easy for novices, rich enough for experts

Confidential© 2010 IBM Corporation43

‣ Intuitive, easy-to-use views enable business users to document and analyze process details – immediately

‣ Single, shared repository becomes the “system of record” for process documentation – always up-to-date

‣ Real-time collaboration and feedback between teammates on “shared whiteboard”

‣ Cloud-based access makes it easy to add participants – on demand

‣ Export process diagrams to other modeling and implementation tool.

Inventory and Map Processes … On DemandIBM’s http://BlueworksLive.com

Template Library includes APQC Process Maps


BlueworkLive.com Simple Enough for Novices…Rich Enough for Experts“Process Discovery…Blueprint your process”


45

Merci

Grazie

Gracias

Obrigado Danke

Japanese

French

Russian

German

Italian

Spanish

Brazilian Portuguese

Arabic

Traditional Chinese

Simplified Chinese

Thai

Documents

© 2010 IBM Corporation IBM BPM f.k.a. WebSphere Lombardi Edition f.k.a. Lombardi Teamworks V7 V7 What’s New, Hints & Tips