Effectively Manage and Scale IBM BPM Infrastructure to Support 30,000+ Users WUG - Edinburgh

Transcription

1 Effectively Manage and Scale IBM BPM Infrastructure to Support 30,000+ Users WUG - Edinburgh Pundarik Ranchhod 25 September 2012 v2-1

2 Agenda Introductions! IBM BPM Deployment Challenges" Good Practices" IBM BPM Topologies" Automation with IBM RAF" RAF Overview" IBM BPM Extensions for RAF" Summary & Questions" Close"

3 Introduction Pundarik Ranchhod BPM Practice Europe Focus of this talk: IBM BPM Specifically infrastructure Some practices for Scaling and Managing IBM BPM

4 Agenda Introductions" IBM BPM Deployment Challenges! A Solution" IBM BPM Topologies" Automation with IBM RAF" RAF Overview" IBM BPM Extensions for RAF" Summary & Questions" Close"

5 IBM BPM Challenges

6 IBM BPM Challenges Components Mobile Process Coaches Core BPM Portal Business Space Optional Microsoft Add-ons Advanced Automation & Integration Performance BPMN Process Rules Data Warehouse BPEL ESB Adaptors Deploy Measure Governance / Visibility Define Improve Process Center Network Multiple Process Centers Process Designer / Optimizer Process Center Console Integration Designer

7 BPM Deployment The Challenges Business Cannot quickly deploy process applications to production Large demand for BPM from the business Delays due to lack of stable development & environment BPM Development Poor collaboration with BPM Admin team Process Center not treated as Production system QA Lack of clear QA process, additional strain on fragile infrastructure Lack of monitoring of environments Need to learn IBM BPM Administration and complex topologies Admin Need to maintain large amount of custom Admin scripts Lack of skills in WebSphere to support IBM BPM infrastructure

8 Agenda Introductions" IBM BPM Deployment Challenges" Good Practices! IBM BPM Topologies! Automation with IBM RAF! RAF Overview" IBM BPM Extensions for RAF" Summary & Questions" Close"

9 Good Practices for IBM BPM Infrastructure 1. Start well before first BPM QuickWin Pilot 2. Investigate and select the IBM BPM topology relevant to you 3. Create golden master topologies for Dev, Test, Staging and Prod Pattern based approach 4. Use environment build automation instead of more custom scripts 5. Enforce topology using Automation tool Eliminate environment configuration drift

10 Topology growing from this

11 Topology to this

12 Topology Horizontal Scaling New node, more cluster members

13 Topology Vertical Scaling Existing node, more cluster members

14 Complexity increases very quickly Multiple deployment environments

15 But how do you enforce the topology? Topology selected DEV Performance tuning done Environment configuration drift still a major issue QA VCS Need a way to enforce and manage the selected topology PRD

16 Agenda Introductions" IBM BPM Deployment Challenges" Good Practices" IBM BPM Topologies" Automation with IBM RAF" RAF Overview! IBM BPM Extensions for RAF! Summary & Questions" Close"

17 Rational Automation Framework (RAF) Core Capabilities Environment build-out automation Administration automation Deployment automation Over 900 out-of-the-box automation actions for: WebSphere Foundation: WAS, ND, IHS, WVE WebSphere BPM Suite: WPS, WESB, WSRR WebSphere Portal WebSphere Message Broker and MQ Series Weblogic, Jboss Ensure configuration consistency Facilitate administration for: Scheduling, unattended execution, notifications, role-based security and audit logging

18 RAF Extensions for IBM BPM RAF Actions and Templates IBM BPM 7.0, 7.5 and 8.0 Supports Process Classic Supports Process Center (Lombardi Capability) For IBM BPM WebSphere Topologies Single Cluster Remote Messaging Remote Messaging and Remote SupportRemote Messaging, Support and Web Cluster Topology (for Process )

19

20

21 RAF Architecture Physical Environments Virtualized Environments Cloud Deployment Manager Agent Deployment Manager server server server server Deployment Manager server server Rational Asset Manager (RAM) Existing Investment in Custom Admin is Preserved RAF Agent Web Browser Custom Admin Database Application Web Browser Agent Source Control Mgmt RSA/Zephyr Rich Client Web Browser

22 How RAF Works 1. RAF tasks are ant under the covers 2. Every ant task is divided into 1 of three types: install, configure and deploy 3. Ant tasks dynamically bind data from the environment with the execution runtime of RAF 4. Modes control how the action is run Import? Promote? Execute? 5. Push or pull with the target environment 22

23 Import, Execute and Compare Modes RAF Framework execute DEV Env QA Env import STG Env PRD Env compare 23

24 Promote mode Leverages new Augment mode RAF Framework STG Env apply Filter promote QA Env import 24

25 Wizard to define a cell from an existing environment Deployment Manager server server RAF 2 Custom Admin Database Application 25 25

26 Configuration Drift Detection: Monitor Live WAS Configuration Every night RAF executes a scheduled comparison of the live cell configuration against the Master. Any difference causes an notification to be generated and sent to WebSphere administrator for that cell. Rational Automation Framework WebSphere Application (and derivatives) Deployment Manager ND Cell Master (approved) configuration stored under change control Deployment Manager Cell Source Control System or RSS feed notification of results of configuration comparison

27 Deployment Processes and SDLC Connect builds with configuration Configuration tagged together with built releases Several approaches to promotion in SDLC Standard promote mode Custom User Templates (CUTs) Cell-kits Hybrid approach Ultimately it's just the environment tree that needs to get updated. This can done in an entirely custom way as well 27

28 Agenda Introductions" IBM BPM Deployment Challenges" Good Practices" IBM BPM Topologies" Automation with IBM RAF" RAF Overview" IBM BPM Extensions for RAF" Summary & Questions! Close"

29 Summary Supporting 30K+ BPM users Not only about topology Or performance tuning Combine with Automation IBM RAF part of the solution Allows for managing multiple IBM BPM environments

30 References IBM BPM Production Topologies Dawn Ahukanna & Kerri Carlson-Neumann IMPACT 2012 Session 2261 IBM Redbook : IBM BPM 7.5 Production Topologies Leveraging the Rational Automation Framework to Accelerate your Migration to IBM Business Process Manager 7.5 Scott Bybee, Ascendant

31 3

32 Additional Useful Capabilities in RAF Command-line, Web interface and new Eclipse UI Predefined automation libraries Environment generation wizard Extensive on-line help Security layers (custom roles & isolation of roles) WebSphere Administrator Release Engineer Application Developer Ability to thread tasks (horizontal clustered environment) Notifications and RSS Highly customizable end-to-end Automation solution! RAF 32

33 Eclipse User Interface Manage configurations interactively Edit XML entities in rich editors Drag-&-drop capability for making new items Must adjust configuration after drop Compare contents in different environments Previous versions could only compare RAF cell against the runtime for the same cell Can use to leverage the embedded Build Forge engine in RAF as well Run jobs, edit projects, see results, etc Need licensing for BF if to use for build/release capabilities

34 Custom User Templates CUT versioned Contains templated versions of configuration Property files contain unique information for each environment CUT s can include other templates Supports increased variability between environments DEV QA PRD VCS CUT 34

35 Promote Mode Best for homogenous environments Apps, topology and basic configuration same for all environments Promotion from dev all the way through production Single promote.properties file for each environment Contains unique information (jdbc urls, passwords and so on) DEV VCS QA PRD VCS: Version Control System 35

36 Cell kits Best for heterogenous environments Different kits applied in different environments Kits are versioned in VCS Contain templated version of configuration plus the apps Kits are then installed into an existing cell configuration Kits can then be versioned separately from the environments and follow their own release cycles App1 DEV VCS App2 QA App3 VCS: Version Control System 36