ibm operational decision manager - websphererus.com€¦ · ibm operational decision manager v8.5...

IBM Operational Decision Manager

November 2013

Subhajit MaitrazChampion

► What is Decision Management?

► Introducing IBM Operational Decision Manager

► Business Decisions Defined

► Components, Architecture and Technical Dive

► ODM on z/OS

Agenda

IBM ODM 8.0.1 Technical Presentation© IBM 2012

Operational Decision Management Transforms Business Outcomes

Providing an easily manageable, single source of truth foroperational business decisions

Enables changes to be easily made by business people

Codifies business policies, practices and regulations

Automates decision making with the fidelity of an expert

4

5

Business Rules in organizations

Spreadsheets Databases

ManualProcesses

Batch / COBOL

Online Transactions

Can get quite large

Are scattered everywhere

Are subject to change

Challenges for a Change Request

Changes are costly, resource & time-intensive

• Rules are hidden in COBOL code

• Most changes have to be programmed –costly

Lack of consistency

• No central management

• No reuse of decision logic

Gap between business analysts & IT administrators

• Knowledge fades over time

Lack of audit ability

No easy way to test/simulate changes

People

6

Operational Decision Management approach

Spreadsheets Databases

ManualProcesses

Batch / COBOL

Online Transactions

Operational Decision Manager Platform

Repository

User Tools

Execution Runtime

Decision logic is defined,

analyzed andmaintained

Decision logic is stored and

shared

Decision logic is deployed,

executed andmonitored

People


Externalizing Decisions from Applications into Business Rules Manage decision logic independently from applications

Business Rules

ApplicationApplication

Decision logic

Natural language rules can be easily read

Externalized rules are easy to change

Centralized rules enable reuse and consistency

Rules written in software code cannot be read by business people

Hard coded rules are difficult to change

Rules intertwined within applications cannot be reused by other systems

Without Decision Management With Decision Management

7


DesignConstruct

Test

ValidateAuthor

Analyze

ChangeRequest

Manage and Monitor

Functional enhancements

DesignConstruct

Test

Deploy

DeployDeployDeployDeploy

Deploy

ValidateAuthor

Analyze

ValidateAuthor

Analyze

ValidateAuthor

Analyze

ChangeRequest

ChangeRequest

ChangeRequest

Software Development Lifecycle

Rule Management Lifecycle

> 4-6 months

< 1 month

8

Decisions Need to Change Faster Than Software Applications

Functional enhancements


Harness the Strengths of Business Users & IT ExpertsWithout Business Rules

Business Analyst Writes requirement

Make changes in monthsMake changes in months

Information Analyst Creates specificationsApplication Developer Codes implementation

Functional TesterValidates feature

Integration TesterRe-validates entire application

Business Analyst Runs user acceptance test

Performance Tester Ensures application scalability

IT Systems Administrator Puts full application into production


Eliminate rework from misinterpreted requirementsSpeed up rule changes

Harness the Strengths of Business Users & IT ExpertsWithout Business Rules With Business Rules

Business users (SMEs) take control of the decision logic & minor rule updatesBusiness users (SMEs) take control of the decision logic & minor rule updates

Subject Matter Expert

Reads existing rules in natural languageEdits or adds new rules without any codingRuns testing and simulation

Performance Tester

Ensures application scalability

SME or IT Systems Administrator

Puts updated rules into production

IT experts ensure application availability, reliability & new application developmentIT experts ensure application availability, reliability & new application development

Make changes in monthsMake changes in months Make changes in weeks or daysMake changes in weeks or days

Business Analyst

Information Analyst

Application Developer

Functional Tester

Integration Tester

Business Analyst

Performance Tester

IT Systems Administrator


Simple Decision Artifacts Supporting Complex Decisions

Rule Flows

11


Why Operational Decision Manager?

Operationalize policy changes in days versus monthsDecrease cost of implementing business practices, policies & regulations

Improve straight-through-processingInvolve business users for change requests with built-in governance

Implement more fine-grained, targeted decisionsPerform what-if and impact analyses prior to deployment

Automate and consistently enforce decision policiesEnsure policies and associated semantics are consistent across channels

Track what decisions were made and why (runtime)Track what policies were changed and by whom (rule management)

Agility

Efficiency and Productivity

Decision Quality and Precision

Consistency

Transparency, Auditability, Compliance

12


Achieve clearer line-of-sight to business operations

Foster cross-functional and cross-divisional outcomes

Align business operations with strategic intent in the face of change

Business Policies Built for Change vs. Built to LastThe Consumerization of Change through Visibility, Collaboration and Governance

Easily readable business rules in natural language

Testing and simulation to assess impact of rule changes

Rule versioning and snapshots to safely and reliably change rules

Auditability of changes to ensure traceability

Social media style UI to tap into organizational business expertise

Single repository for business and IT users to collaborate

13

Agenda





► ODM on z/OS


IBM Operational Decision Manager v8.5

To flexibly and reliably manage repeatable, automated decisions

When decisions change frequently

To increase straight-through processing

When decision services can be shared across systems

To manage and govern large numbers of rules

When real-time events require immediate actions

Apply Operational Decision Manager…

Manage business policies at scale

Capture, automate and operationalize your business expertise

Enable social collaboration to manage and govern business change

15


IBM ODM v8.5

VisibilityNew business interface to bring more visibility on how decisions are being changes across the team

Designed to meet decision management challenges

CollaborationNew social based communication capabilities to improve interactions across the business team

GovernanceEnriched controls and governance capabilities simplifying version management at the rules and project level

16


Full text search across all decision assets

Decision Center

“What’s New” quickly displays deployed assets

Search can return rules, tables and folders

Visibility Through Operational Decision Manager v8.5


Collaboration Through Operational Decision Manager v8.5

Decision Center enables collaboration on assets of interest and change notifications

Details on the Activity Stream in the ‘New Features’ section


Department 1

Timeline enables a quick view of version history

Governance Through Operational Decision Manager v8.5

Decision Center

Details on the Timeline in the ‘New Features’ section


Model

Validate

Deploy

Mon

itor

BusinessAnalyst

Policy Manager

System Administrator

Full Decision Lifecycle ManagementManage changes in a safe and predictable environment

ComplexDecisions

Rule Administrator

Developer


Why Operational Decision Manager?

Operationalize policy changes in days versus monthsDecrease cost of implementing business practices, policies & regulations

Improve straight-through-processingInvolve business users for change requests with built-in governance

Implement more fine-grained, targeted decisionsPerform what-if and impact analyses prior to deployment

Automate and consistently enforce decision policiesEnsure policies and associated semantics are consistent across channels

Track what decisions were made and why (runtime)Track what policies were changed and by whom (rule management)

Agility

Efficiency and Productivity

Decision Quality and Precision

Consistency

Transparency, Auditability, Compliance

21


Achieve clearer line-of-sight to business operations

Foster cross-functional and cross-divisional outcomes

Align business operations with strategic intent in the face of change

Business Policies Built for Change vs. Built to LastThe Consumerization of Change through Visibility, Collaboration and Governance

Easily readable business rules in natural language

Testing and simulation to assess impact of rule changes

Rule versioning and snapshots to safely and reliably change rules

Auditability of changes to ensure traceability

Social media style UI to tap into organizational business expertise

Single repository for business and IT users to collaborate

22





► ODM on z/OS

Agenda


Rul

esE

vent

sWhat is a Business Decision ?

Contextual DecisionsApplication, Process, Service invokes a specific Decision, passing information to be processed by the rules,

The contextual rules process the information are form a result

Once complete the Decision passes a result back to the Application, Process or Service to take action on

Combination of contextual and/or time-based rule artifacts

Validation DecisionEligibility

Calculation DecisionPricing

Classification DecisionGold, Silver, Bronze

Occurrence of DecisionIf customer asks for 3 quotes in 24 hoursthen

provide 2% discount for immediate acceptance

Missing Events DecisionIf medical equipment eventis not receive every 1 hourthen send alert to medical staff

Situational DecisionsSpecific situations are defined in event rules looking for specific known sequences which should be correlated from a real-time stream of events.

When the known sequence of rules matches a specific sequence of events, then either

1. This simple decision takes some immediate Action

2. A synchronous decision is invoked to do additional processing, prior to making a decision and taking some action.

24


IF the enterprise value of Customer is GOLDAND the Loyalty of Customer is LOW THEN the personalization action is “Call”ELSE the personalization action is “email”

IFpast occurrences the Customer returned a product

in the last 2 months is more than 3THEN classify Customer as a LOW LOYALTY Customer

IF the Total purchases of Account > $2,500 THEN the enterprise value of Customer is GOLD

= GOLD

+ LOW LOYALTY

Business Decision - ExampleA process or application is required to contact a customer. It needs guidance on the most appropriate method to contact them.

Use Classification Decision passing in the customer information3 or more alternative results may be returned to process or application

DECISION RESULT = CALL

25


Decision Tables and Scorecards

Built-inGap/Overlap

Checking

Automatic Rule

Generation

Actions

26


Actions

Condition

Values

Automatic Rulegeneration

Built-in Gap/Overlap

checking

Rule Authoring: Decision TreesVisualize decisions and all possible outcomes

27


FunctionTask

Pre/Post Conditions

RuleTask

FlowConditions

Rule Authoring: Visual RuleflowsModel and control rule execution sequence

28





► ODM on z/OS

Agenda



Rule DesignerEvent Designer

Rule Solutions for Office

Decision Center Versioned Assets

Rule Execution Event Execution Decision Monitoring Connectors

Manage

Decision ServerConsole

Design Monitor

Decision Server

Deploy Measure

VisibilityCollaborationGovernance

Define Update

Web Services – API - GUI

DevicesEnterpriseApplication

POS BPM CRM

Social

Event Widgets Space Business Console

Enterprise Console

Access and ControlDecision Artifacts

30


Rule Designer

Developers

Business Analysts

Eclipse-based Development Environment

31


GeneratedScenario Document

Configurationediting

Detailed ScenarioReports

Test Suite and execution reportsRule Designer

32


High performance and scalable rule executionSupport transactional and batch rule executionInference (forward-chaining) and sequential rule engine Cluster enabled

Integrate with Java, XML, WSDL, Enterprise COBOL

Exposes rule services asRule Session (POJO, EJB or MDB)Transparent Decision Services (Web Services)

Rule services management & monitoringRule Persistence and VersioningRule Execution statistics & traceJMX-based administration console

High Performance and ScalabilityRule Execution Server

33



Decision Server

Leverage a wide range of platforms to meet the varying needs of enterprise architectures

Decision Center(Windows, AIX, Linux, z/Linux, z/OS)

Multiple z/OS deployment options

Windows AIX Linux, z/Linux

z/OS

Runtime support

Repository

34


Decision Center – Business ConsoleSocial Medial Style Collaboration

Maintain awareness across the team

Ensure automatic notificationsof changes

Ensure team collaboration

35


Decision Center – Enterprise Console

Rule and Event experts

Analysts

Policy Manager

Web-based Business Policy Management Environment

36


Decision Center - Enterprise Console

AuthoringPlain English, Decision Table, Decision TreeQuick edit mode using MS OfficeTemplates

ManagingQueriesSmart ViewsVersion ManagementBaseline

ValidatingSyntactic CheckSemantic CheckSemantic Queries

Testing / SimulatingDecision Validation Services

AuditingVersion ManagementBaselineQuery-based reporting

DeployingQuery base ExtractionRule service management

Administration and configurationAuthorization policiesRule ServiceDisplay Options

A complete Set of Capabilities

Enterprise Console

37


Multiple Release Management

Enable business users to make changes to a deployed rule application without interfering with work they are doing on an upcoming release

Merge and diff between releases

Greater flexibility for deploying business decisions

38


Decision Center Console

Out-of-the-box ruleset testing in Rule Team Server

Business impact simulation in Rule Team Server

Scenario configuration and customization in Rule Studio

Audit - Decision Warehouse in Rule Execution Server

Integrated decision validation services

39





► ODM on z/OS

Agenda

How does it work?Rule Authoring Concepts

November 20, 2013

Rule Authoring – XOM options

4 options for the underlying execution model– Java object graph

– XML schema

– COBOL copybook

– PL/I Structures

Java – Standard approach

• Engine always uses Java regardless of choice

– Best performance

XML Schema– Java dynamically created at runtime

November 20, 2013

Rule Authoring – COBOL Copybook XOM

Support Enterprise COBOL 3.4, 4.1 & 4.2A Java is created from the copybook structure

– Java XOM & Java code to marshal between COBOL <-> Java

– 01 level structures mapped to class in BOMRedefines statements supported

– Select which redefines structure to importCOBOL Table support

– Mapped to Java List<type> structuresCOPY statements supportedLevel 88 supported

– Mapped to methods in BOM

4444 © 2013 IBM Corporation

Starting from a COBOL copybook or PL/I include

Deploy Decision Service

Import copy book

Authoring Business Rules

Execution

Scenario• Existing COBOL containing business rules• Data model defined in COBOL copybook• Use ODM to modernize the business policy

Benefits• Modernize business policies in ODM• Rules can be invoked ‘naturally’ from existing

application• Business policy/rule lifecycle detached from

application lifecycle

New In V8.5


Rule Authoring COBOL & PL/I -> XOM

• Support Enterprise COBOL & PL/I

• Java is created from the copybook or include structure

• Java XOM & Java code to marshal

between COBOL or PL/I <-> Java

• 01 level structures mapped to class in BOM

• Redefines statements supported

• Select which redefines structure to import

New In V8.5


Starting With an Existing Java Project

Scenario• Existing Rule projects exist that are currently

in use on distributed platforms• Concurrent execution of rules required on

System z

Benefits• Consistent decision rules where ever

executed• Rules can be invoked ‘naturally’ from existing

applications on all platforms• Enables central rule management across

System z and distributed execution• Business policy/rule lifecycle detached from

application lifecycle

Deploy Decision Service

Import Java Project

Execution

Export copy book

Deployment options?IBM Operational Decision Manager on z/OS

48

IBM and Client Confidential

z/OS

WebSphere Application Server

for z/OS*

Events ExecutionServer

Rule Execution Server

CICS TS v4.x +

*Limited Use

zRule Execution Server

zRule Execution Server

• Deployment runtime options on z/OS: Deployed on WebSphere Application Server for z/OS Deployed standalone to z/OS for COBOL and IMS Batch Applications Deployed in CICS TS 4.x and above in JVMServer environment

ODM Deployment Options on z/OS

3

2

1

12

3

49


Deployment Option

Rule Execution Server for WAS on z/OS

Web Services, Plain Old Java Object (POJO), Message Driven Beans (MDB), Enterprise Java Beans (EJB).Decisions can also be invoked from COBOL applications using the WebSphere Optimized Local Adapter (WOLA). WOLA is a functional component that provides an efficient cross-memory mechanism for calls both inbound and outbound calls to WAS z/OS

Options for Rules Invocation, Integration Patterns and Benefits

1

Integration Patterns

Unique Cross memory communication, z/OS WLM and a secure infrastructure.

Ease sharing of Rules: Decision services can be invoked from distributed platforms using the patterns shown above

Unique Automated Workload Balancing, High Availability and Scalability with WAS on z/OS topology

Rule execution is offloaded to zAAP reducing mainframe software costs and freeing up CPU cycles.

Rules shared across Logical Partitions in zOS for unparallel high availability requirements (SYSPLEX)

Benefits:

50


Deployment Option

zRule Execution Server (Standalone) Simple COBOL API


2

Integration Pattern

COBOL applications use copybooks as the interface to invoke decisions making development simple.

z/OS permits the copying of message buffers from one virtual address space to another which makes ODM efficient, fast and secure as it is within LPAR.

zRES can be added in an Automatic Restart Manager (ARM) sequence. This will allow zRES to be started automatically in case of a failure.

Rule execution is offloaded to zAAP reducing mainframe software costs, freeing up CPU cycles.

Rules shared across LPARS: With DB2 data sharing, rules can be stored in DB2 and accessed from multiple LPARs in a SYSPLEX environment

Batch/CICS and Rules Engine running on the same LPAR adds to better performance as there are no network hop.

Decision services are deployed and instantly available across z/OS without making any application changes

Benefits:

51


Deployment Option

zRule Execution Server (CICS JVM) Simple COBOL API


3

Integration Pattern

Same benefits as option 2 plus additional

Running ODM inside CICS allows access to the CPSM* Qualities Of Service like workload management, reliability, availability and security within a CICS infrastructure.

Local execution within CICS region.

* CICSPlex System Manager(CPSM ) is a system management tool to manage multiple CICS Intances from a single point.

Benefits:

© 2011 IBM Corporation

IBM Operational Decision Manager for z/OS

Decision Server Options Summary

Full support for all rule authoring constructs

Hot deployment support for new decision versionsIntegration with Decision Center business tooling

Testing and simulation support

Decision Warehousing rule auditing support

Easy sharing of rules with distributed deployments

Local execution support for CICS TS v4.x

Full HA & transactional support


IBM Operational Decision Manager for z/OS

zRule Execution Server Stand-alone

WebSphere Application Server for z/OS

WOLA

CICS

COBOL Application

Rule Execution Server for WAS for z/OS

JVM Server

zRule Execution

Server

IMS

COBOL Application

z/OS Batch

COBOL Application

DS Stub

DS StubDS Stub

zRule Execution

Server

zRule Execution Server Invocation options in v8.0.1

RES WOLAEJB

Address SpaceAddress Space

JVMInvocation Native

Control & Comms

Runtime Rule Repository

File System zFSDB2

RES Mediation

Layer

Rule Server

JVM

Notification

User COBOL Application

DecisionService Stub

Web Container

RES Console

Deploy

zRule Execution Server for z/OS – Stand alone

Address SpaceCICS TS 4.x and above

JVMServer

Invocation

Runtime Rule Repository

File System zFSDB2

RES Mediation

Layer

Rule Server

JVM

Notification

Deploy


DecisionService

Stub TRU

E

Web Container

RES Console

zRule Execution Server for z/OS – CICS TS 4.x and above

Easy integration with existing COBOL applications running in CICS & Batch

Designed for unique needs of the System z customer base

Native zOS Execution in Java

COBOL stubs to glue the application to Rules Execution Native Server

Integrating core functionality from z based products

Fully integrated with all key components of the existing BRMS offering

For enhanced co-location, can implement within an existing CICS 4.x and above region

New Address Space

RES Native

JVM

User Application API Stub

Native

Cobol data structure Data

ConversionCOBOL

Call

JRules J2SE RESComm

Layer

Calling to the zRule Execution Environment for z/OS

Runtime enablement• Write the Decision Service invocation in

COBOL

• COBOL code remains independent of the Business Rules lifecycle on a stable decision service signature

Decision Service Hot Deployment

• New decision version ‘instantly’ available

• From Rule Designer & Decision Center• Versioned service made ready for

execution from COBOL• Let running executions complete

01 HBRA-CONN-AREA.10 HBRA-CONN-EYE PIC X(4) VALUE 'HBRC'.10 HBRA-CONN-LENTH PIC S9(8) COMP.10 HBRA-CONN-VERSION PIC S9(8) COMP VALUE +1.10 HBRA-CONN-RESERVED01 PIC X(8).10 HBRA-CONN-FLAGS PIC S9(8) COMP VALUE +1.10 HBRA-CONN-INSTANCE PIC X(24).10 HBRA-CONN-RETURN-CODES.

15 HBRA-CONN-COMPLETION-CODE PIC S9(8) COMP.15 HBRA-CONN-REASON-CODE PIC S9(8) COMP.

10 HBRA-CONN-RULEAPP-NAME PIC X(256).10 HBRA-RA-PARMS OCCURS 32.

15 HBRA-RA-PARAMETER-NAME PIC X(48).15 HBRA-RA-DATA-ADDRESS USAGE POINTER.15 HBRA-RA-DATA-LENGTH PIC 9(8) BINARY.

10 HBRA-RESPONSE-AREA.15 HBRA-RESPONSE-MESSAGE PIC X(256).

10 HBRA-RESERVED.15 HBRA-RESERVED02 PIC X(128).

* SELLER COPYBOOK - Item Details01 SELLER-Data.

05 SELLER-name PIC X(10).05 SELLER-item-number PIC 9(4).05 SELLER-item-details PIC X(48).05 SELLER-item-count PIC 9(10).

Business Rule Execution

01 HBRA-CONN-AREA.10 HBRA-CONN-EYE PIC X(4) VALUE 'HBRC'.10 HBRA-CONN-LENTH PIC S9(8) COMP.10 HBRA-CONN-VERSION PIC S9(8) COMP VALUE +1.10 HBRA-CONN-RESERVED01 PIC X(8).10 HBRA-CONN-FLAGS PIC S9(8) COMP VALUE +1.10 HBRA-CONN-INSTANCE PIC X(24).10 HBRA-CONN-RETURN-CODES.

15 HBRA-CONN-COMPLETION-CODE PIC S9(8) COMP.15 HBRA-CONN-REASON-CODE PIC S9(8) COMP.

10 HBRA-CONN-RULEAPP-NAME PIC X(256).10 HBRA-RA-PARMS OCCURS 32.

15 HBRA-RA-PARAMETER-NAME PIC X(48).15 HBRA-RA-DATA-ADDRESS USAGE POINTER.15 HBRA-RA-DATA-LENGTH PIC 9(8) BINARY.

10 HBRA-RESPONSE-AREA.15 HBRA-RESPONSE-MESSAGE PIC X(256).

10 HBRA-RESERVED.15 HBRA-RESERVED02 PIC X(128).

* Connect to Execution Regioncall ‘HBRCONN’

using HBRA-CONN-AREA

* Populate Header with parameter data

* Connect to Execution Servercall ‘HBRRULE’

using HBRA-CONN-AREAIF HBRA-CONN-COMPLETION-CODE = HBR-CC-OK THEN

. . .

* Disconnect from Execution Regioncall ‘HBRDISC’

using HBRA-CONN-AREA

WODM

New Programming API


IMS Batch MessageProcessing region

Full capabilities of Decision Server on z/OS now available to IMS batch and online applicationsNatural decision invocation from IMS applications

Use standard zRES API to call from IMS application to– zRES stand alone server – RES deployed to WebSphere Application Server for z/OS via WOLA

Rule execution support for IMS processing regions

59

Decision Server

DEPLOYCOBOL

Application

INVOKEDecisionService Stub

Decision Center

MANAGE

Business Decisions

Decision Warehouse

Testing, simulation, and decision audit support for z/OS

60 © IBM 2012

Run decision tests and simulations from Decision Center in – zRule Execution Server – Stand Alone– Rule Execution Server on WAS for z/OS

Supplied sample for accessing test data from z/OS VSAM fileDecision audit support available through Decision Warehouse capabilities

– Support for Decision Warehouse in all z/OS Rule Execution Server deployment options

Decision ServerCOBOL Application

CICS, Batch and IMS

INVOKEDecisionService Stub

ScenarioService Provider

TEST DA

TA

VSAM

TEST & SIMULATE

Decision Center

AU

DIT

Business Decisions


zRES failover support

Simplified configuration for creating multiple stand alone servers

Connect client to ‘list’ of servers

Client fails over to next server on list in event of server connection failure

61

zRES(Stand Alone)

SSID: RES1

zRES(Stand Alone)

SSID: RES2

X XFailover


CICS, Batch and IMS

DecisionService StubServer List: RES1, RES2

It’s Time For Demo!

A Decision Service to calculate late fee

Merci

Grazie

Gracias

Obrigado Danke

Japanese

French

Russian

German

Italian

Spanish

Brazilian Portuguese

Arabic

Traditional Chinese

Simplified Chinese

Thai

Korean

ibm operational decision manager - websphererus.com€¦ · ibm operational decision manager v8.5...

Documents