Discovering the value of IBM
Operational Decision Manager on
Cloud
Trial Guide
An IBM Proof of Technology
Catalog Number
© Copyright IBM Corporation, 2016
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Contents
LAB 1
RULES TECHNICAL TRACK .................................................................................................................... 14
1.1
DESIGNING A DECISION SERVICE AND THE VOCABULARY IN RULE DESIGNER ..................................... 14
1.2
CREATE A DECISION SERVICE ...................................................................................................... 19
1.3
DEFINING THE DECISION SERVICE OPERATION AND ENTRY POINT ..................................................... 31
1.4
ORGANIZING AND ORCHESTRATING RULES ..................................................................................... 36
1.5
AUTHORING BUSINESS RULES ....................................................................................................... 42
1.6
DEPLOYING AND EXECUTING RULES ON RULE EXECUTION SERVER .................................................. 49
1.7
USING THE W EB APP TO TEST DEPLOYED THE RULES...................................................................... 60
1.8
PUBLISH THE RULES TO DECISION CENTER .................................................................................... 61
1.9
SUMMARY .................................................................................................................................. 63
LAB 2
RULES BUSINESS TRACK ...................................................................................................................... 64
2.1
MANAGE THE BUSINESS RULES WITH THE DECISION CENTER BUSINESS CONSOLE ............................. 65
2.2
CHANGING THE RULES AND ANALYZE THE IMPACT ........................................................................... 84
2.3
VALIDATING THE RULES AND DEPLOYING THEM ............................................................................... 89
2.4
SUMMARY .................................................................................................................................. 98
APPENDIX A.
NOTICES ................................................................................................................................................... 99
APPENDIX B.
TRADEMARKS AND COPYRIGHTS ...................................................................................................... 101
Contents
Page 3
IBM Software
THIS PAGE INTENTIONALLY LEFT BLANK
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Overview – Business agility
Business agility depends on responsive, intelligent decision automation. Operational Decision Manager
helps manage decisions separately from business applications, and with more flexibility and
responsiveness to the changing needs of the business.
The ability to deal with change in operational systems is directly related to the decisions that they are
able to make. Every transaction, order, customer interaction, or process depends on decisions, which are
in turn dependent on particular internal or external requirements and contexts. Therefore, every change
affects decisions, many of which are handled automatically within business systems.
Extracting decisions from your application code
Business policies are statements that are used to make decisions. These decisions can determine
pricing for insurance or loan underwriting, eligibility approval for social or health services, or product
recommendations for online purchases. Business policies are typically found inside application code, in
the form of if-then statements. However, they can also be stored elsewhere for documentation purposes,
such as in procedural manuals and other documents.
A business policy can be expressed as several business rules. The following example might be a familiar
type of business policy:
Customers who spend a lot of money in a single transaction need an upgrade.
The process of capturing rules happens in two steps. The first step consists in formalizing the vocabulary
that is required to express the policy as a conceptual object model. The second step consists in
representing the logic of the business policy as if-then statements.
After the vocabulary is created, the business policy can be implemented with the following business rule:
if
the customer's category is Gold
and the value of the customer’s shopping cart is more than $1500
then
change the customer's category to Platinum
When a business policy also has an IT policy or security policy that is embedded in it, you can combine
business rule management with capabilities to handle the business policy aspects. For example, the
following business policies can be handled as rules:

Page 5
customers who spend a lot of money should be routed to a preferential service
ODM on Cloud PoT
IBM Software

customers who spend a lot of money require additional security on their transactions
In the form of business rules, the business logic can be packaged and called from the application code
as a decision service. Therefore, changes to the business policy do not require changes to the
application or process code.
Managing decisions
When decision management is separate from application code, business experts can define and manage
the business logic. Decision management reduces the amount of time and effort that is required to
update the business logic in production systems, and increases the ability of an organization to respond
to changes in the business environment.
Operational Decision Manager provides an environment for designing, developing, and deploying
business applications that are based on decision services. The IT cycle consists of developing and
maintaining this infrastructure. After the infrastructure is set up, distributed business teams can start
collaborating through a web-based environment to create and maintain the decision logic.
Decision Server provides the runtime and development components to automate the response of highly
variable decisions that are based on the specific context of a process, transaction, or interaction.
Putting decision management in the hands of business users
With Decision Center, business users can manage decisions that are directly based on organizational
knowledge, with limited dependence on the IT department. Business users have a varying degree of
dependence, which can range from a limited review to complete control over the specification, creation,
testing, and deployment of the business logic. Business and IT functions can work in collaboration. The
entire organization can align in the implementation of automated decisions. The maintenance lifecycle
accelerates based on new external and internal requirements.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
The lifecycles of decision service development and management can evolve in parallel. Decisions can
evolve as required by the business context, without putting an extra load on the development of the
business rule application. Each time the business rule application evolves, the decision management
environment synchronizes with the development environment.
With this separation, decisions and application architecture can be managed asynchronously. For
example, application developers can develop a new application version in response to changing
application infrastructure and core business requirements. At the same time, policy managers can work
on new decisions that are delivered in response to an evolving market, changing regulatory environment,
or new patterns of events.
Operational Decision Manager components for decision management
The following figure shows the components that Operational Decision Manager provides for rule
application development, rule management and authoring, and the execution environment.
Page 7
ODM on Cloud PoT
IBM Software
In addition to working on different timelines, developers and business users also expect to work with
different tools, reflecting their different skill sets and views of the application.
For example, developers are accustomed to the Java™ world. They use source-code management
systems to work simultaneously on separate copies of a project without interfering with each other.
Business users do not concern themselves with the details of application development, but are interested
in testing and managing decisions. Therefore, they need tools that can help them author, organize, and
search for rules in the context of the overall policy.
With developers and business users that work in their own environments at their own pace, the work of
these two groups must be synchronized and merged.
Finally, both developers and business users require access to a rule execution environment to deploy
rules to enable testing, validation, and rollout to production of new and changed business logic.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Introduction
This section describes the scenario that you work through during this lab.
The Miniloan business application
The Lab scenario is based on a web-based online loan application. Its objective is to modify the
application to support the new business process shown later. On receipt of the loan request, the
borrowers’ credit score would be checked and the interest rate identified.
The next stage in the process is to make a decision about whether the loan should be accepted or not.
This decision uses business rules to determine the loan risk based on the relative debt to income ratio
and the borrowers’ credit score. If the loan is not approved, the borrower is informed that the loan is
rejected together with the reasons.
The Miniloan information model
The information available to make the decision is shown here.
Page 9
ODM on Cloud PoT
IBM Software
The Borrower represents the person that is applying for the loan. They are identified by a name and have
a yearly income, which is used to assess their debt to income ratio. To make a good decision about the
risk of the loan, the borrower’s credit score is also required. This information would usually be provided
from an outside source, but for this exercise, the information is provided with the lab as input.
The Loan represents the loan characteristics and is divided up into three sections.



The amount and the duration (or repayment period in months) are provided by the borrower
The yearly interest is provided by the application at submission time
The loan status is defined and returned by the rules
Introducing the lab environment
IBM ODM on Cloud is a complete web solution for developing and deploying business rule software for
your applications. Capture your policies in business rules through a collaborative environment that
supports developers, analysts, and business users. IBM ODM on Cloud includes a comprehensive
component for creating business rules, and a development platform that is specifically designed for
business users. This section introduces the components that you use in the lab and the steps you take.
IBM Operational Decision Manager modules
IBM Operational Decision Manager comprises a set of modules that operate in different environments,
but also work together to provide a comprehensive decision management platform.

Rule Designer: An Eclipse-based development environment where you can develop and integrate
decision services.

Rule Execution Server: Rule Execution Server provides a reliable and scalable execution
environment for your business rule application. The process for executing a business rule application
involves such tasks as creating and deploying a RuleApp and developing a client application.

Decision Center: A scalable rule management server and repository with a collaborative web
environment for authoring, managing, validating, simulating, and deploying business rules. Decision
Center provides project governance, including role-based security, history maintenance, and custom
metadata. Decision Center provides enhanced collaboration between teams through multi-user
access for business users and synchronization between IT and business user environments.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Two categories of users are involved in developing and maintaining a decision management solution:

IT users
Architects, developers, and administrators develop and maintain the rule application.
Developers work with Rule Designer in Eclipse for design, Java development, and rule project
development.

Business users
Business users work with Decision Center to write and maintain business rules, both during
application development and after the application is deployed to production.
Business users can perform end-user testing and simulation in Decision Center. Business
analysts can simulate business outcomes, run updated rules against historical data, simulate
expected changes in data profiles against existing rules, and analyze aggregate outcomes.
Overview of lab tasks
The lab offers an introduction to both Decision Server and Decision Center. You first take the role of a
Page 11
ODM on Cloud PoT
IBM Software
business user to manage the business rules that are developed in Decision Server in a web-based
environment. Next, you take the role of an IT user to discover how the business rule application was
built.
The lab is divided into two parts:

Technical track (uses Decision Server)

Business Track (uses Decision Center)
Each track is divided into steps that incrementally build the solution to the scenario described in the next
section.
Activate IBM ODM on Cloud account
To activate your ODM on Cloud account:
__1.
Request IBM Operational Decision Manager on Cloud trial from here.
__2.
When you receive the invitation email, follow the link and instructions to activate your account.
__3.
Follow the activation process to enter your login details.
The ODM on Cloud portal opens to the Applications tab.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
THIS PAGE INTENTIONALLY LEFT BLANK
Page 13
ODM on Cloud PoT
IBM Software
Lab 1
Rules Technical Track
In this lab, you create a rule project for the Miniloan application to store the business rules that manage
loan requests from borrowers. The rules validate the loan, compute the debt-to-income, and determine
the eligibility of the loan.
You assume the role of a rule developer by using Rule Designer, an Eclipse-based development
environment to develop your rule application. In this detailed lab, you create a rule project, a business
object model, and the necessary business rules. Finally, you deploy the rule application to Rule
Execution Server and publish the project to Decision Center.
1.1
Designing a Decision Service and the vocabulary in Rule Designer
In this task, you use Rule Designer to create a rule vocabulary that enables business users to write rules
using terms that are meaningful to them. This vocabulary is created directly from the object model of the
existing Miniloan application.
Business users need to write and edit rules using familiar terms. As the rule project developer, you must
create a rule project and business rule vocabulary for them. The process of creating this business rule
vocabulary is called “verbalization”. You create a Business Object Model (BOM) based on an Execution
Object Model (XOM). The classes and members of the BOM map to the terms and phrases familiar to
the business user, as follows:
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Step 1: Launch Rule Designer and import Execution Object Model (XOM)
Step 2: Create a Decision Service
Step 3: Review predefined Execution Object Model (XOM)
Step 4: Create the Business Object Model (BOM)
Step 5: Add a business method to the Loan Class
Step 6: Define the variables used by the rules
1.1.1
Install Rule Designer
Developers use Rule Designer for authoring and managing business rule applications. Since Rule
Designer is based on Eclipse technology, developers can quickly familiarize themselves with the platform
and use this integration to develop their Java projects, in addition to rule projects.
You use Rule Designer for most of the technical activities in this lab.
To download Rule Designer:
__1.
Sign in to IBM ODM on Cloud portal at this URL:
https://<vhostname>.bpm.ibmcloud.com
__2.
On the Applications tab, in the Rule Designer panel, click Download. Make sure that your
browser is configured to allow downloads.
__3.
Download ruledesignerforcloud.zip to your computer, and extract its contents to a
convenient directory, for example: C:\ODMoC\tools.
Page 15
ODM on Cloud PoT
IBM Software
__4.
Open the folder where you downloaded the files and extract the
ruledesignerforcloud.zip file and open the resulting directory to find the
eclipse\eclipse.exe file.
__5.
Download ODMoC.zip (additional project files) from this URL:
http://ibm.biz/ODMfiles
__6.
Save and extract ODMoC.zip file to a temporary folder, such as C:\ODMoC\files. The
following files in the folder:
1.1.2
Launch Rule Designer
__1.
Double-click the C:\ODMoC\tools\eclipse\eclipse.exe file to start Rule Designer.
__2.
In the Workspace Launcher, use the given location or browse to another location for the
workspace, and click OK.
__3.
In the wizard that opens, replace <myodmcloud> with the host name for your IBM ODM on
Cloud portal. The URL is:
https://<vhostname>.bpm.ibmcloud.com/
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__4.
Click Connect and provide your IBM ODM on Cloud credentials when prompted.
The wizard configures the connections to your Decision Center and Rule Execution Server
instances on the cloud.
The message beside “User name” changes from “Not yet authenticated” to your user name.
__5.
Click Finish.
__6.
Close the Welcome page in Rule Designer.
1.1.3
Import Miniloan XOM Java project into the workspace
__1.
Import the Miniloan xom to Rule Designer.
Page 17
__a.
On the File menu, click Import.
__b.
In the Import wizard, expand General, select Existing Projects into Workspace and
click Next.
__c.
In the Select root directory field, click Browse, and browse to the folder where you
downloaded Miniloan xom (inside ODMoc.zip), and click OK.
__d.
Make sure that Miniloan xom and Copy projects into workspace are checked.
__e.
Click Finish.
ODM on Cloud PoT
IBM Software
__2.
The Miniloan xom Java project is imported into the workspace.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.2
Create a Decision Service
In Rule Designer, you manage development at the rule level. As you add rules to decision services, you
make the decision services more complex. You can use rule project hierarchies to spread the rules
among different projects. You can also use decision operations in decision services to define multiple
rulesets that share rules in the hierarchies. You can package each decision operation and its ruleflow,
along with its unique rules, in a project that does a specific task.
When you create a decision service, you create a main rule project that serves as the root of the rule
project hierarchy. For a simple decision service, you can use a single main rule project. However, you
usually organize the decision service into a hierarchy.
The following diagram shows a main rule project that contains two sets of business rules:
To avoid having to manage numerous business rules in a few projects, spread the rules among several
rule projects. You can then set up the projects to refer to one another. You can also use a Rule Project
with a BOM to hold the business object model (BOM) that is used by all the projects, and start the build
process incrementally, instead of building all the projects at the same time.
The following diagram shows a modular organization that distributes the rulesets in the previous diagram
among two rule projects that are linked to by the main rule project:
Page 19
ODM on Cloud PoT
IBM Software
In this lab, for the sake of simplicity, you create one Decision Service with only one main rule project.
To create the Decision Service with a main rule project:
__1.
In the Decision Service Map, click Create main rule project.
__2.
In the list of Decision Service Rule Projects templates, select Main Rule Project and click Next.
__3.
In the Project name field, type: Miniloan Rules <your userid>
Where <your userid> is the user name part of your email address or your initials, which you
append to the project name so that the name is unique.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Note:
You can append your initials or user name to distinguish your decision
service from other Miniloan Rules decision services that are published
to your cloud instance.
__4.
Click Finish.
The Miniloan Rules project opens in the Rule Explorer.
The Rule Explorer view shows all of the rule projects that exist in the current workspace. By
default the rule project contains empty folders. During the lab you use the rules and bom
folders to store the business rules and business object model (BOM), respectively.
The Decision Service Map guides you through the different steps of setting up a rule project,
creating rules, and deploying them to the runtime server. This tool is great for users who are new
to Rule Designer.
Page 21
ODM on Cloud PoT
IBM Software
Note:
When using the Decision Service Map, make sure that the
Decision Service or rule project is selected in the Rule
Explorer view.
1.2.1
Define the Execution Object Model (XOM) from Java classes
Now that you have an empty rule project, you can use the Decision Service Map to guide you through
the steps of building the rule application.
The first thing your rule project needs is the data model that is provided by the Miniloan xom Java
classes. In ODM, this is referred to as the Execution Object Model (XOM), the underlying technical object
model used during the execution of the rules.
__1.
Make sure that your main rule project is selected, and in the Setup a Decision Service part of
the Decision Service Map, click Import XOM.
Note:
If the Decision Service Map is not active or if you cannot click Import
XOM, click the Miniloan Rules project in the Rule Explorer to select it.
__2.
In the Import XOM dialog, select Java execution object model and click OK.
__3.
Select the Miniloan xom Java project and click OK.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.2.2
Create the Business Object Model (BOM)
Before you create and edit rules you need to define a Business Object Model (BOM). You can create a
BOM from scratch or create it automatically by parsing your execution object model (XOM).
Here, you use Rule Designer to automatically parse the types and elements in the XOM and create the
BOM from their properties. You can then write rules from the vocabulary terms contained in the BOM.
To create a BOM from the XOM:
__1.
In the Decision Service Map, click Create BOM.
__2.
On the BOM Entry page enter the BOM details.
Page 23
__a.
Make sure that Create a BOM entry from a XOM is selected.
__b.
Leave the other fields at their default values and click Next.
ODM on Cloud PoT
IBM Software
__3.
In the Choose a XOM entry field, click Browse XOM.
__4.
Select platform:/Miniloan xom and click OK.
__5.
Under Select classes click the checkbox next to the miniloan package to select all of the
classes in the package.
__6.
Expand the miniloan package to see the two main classes Borrower and Loan, plus the
Loan$StatusType, which is a Java enumeration, and click Next.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__7.
In the BOM Verbalization page, clear Setters and click Finish.
You clear Setters because you do not want to generate verbalizations for input parameters. For
example, from a business perspective, in our scenario it does not make sense to have a “set the
name of the borrower to …” because the name of the borrower should not be changed by the
rules.
In the Rule Explorer, the bom folder under the Miniloan Rules project now contains the
model BOM entry.
Page 25
ODM on Cloud PoT
IBM Software
__8.
Double-click bom > model to open the BOM Editor.
__9.
Expand the miniloan package. You now have in your BOM two classes equivalent to those in
the XOM, that is, one for the Borrower and one for the Loan.
1.2.3
Add a business method to the Loan class
When creating a BOM vocabulary, the default parameters and operations that are generated
automatically from the XOM are sometimes unsuitable for business users. You can modify the
generated vocabulary, as well as create new business methods and members to leverage additional
features for the business user.
You want to provide the business users with a single phrase that allows them to reject and add a
message to the messages list. You don’t want to change the Java object model for this purpose, so in
this step, you create a new business method in the BOM to set the status of a loan and to add a
message to the list.
To add a method to the Loan BOM class:
__1.
In the BOM editor view, double click Loan or highlight Loan and click Edit.
The Loan class opens in the BOM editor.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__2.
Page 27
In the Members section, click New.
ODM on Cloud PoT
IBM Software
__3.
Create the loanDecision method.
__a.
In the Type panel at the top, select Method.
__b.
In the Name field, enter: loanDecision
__c.
In the Type field, enter: void
__d.
Click Add to create an argument.
__e.
In the Name field, enter: status
__f.
In the Type field, click Browse and type status to find StatusType, and then click
OK.
__g.
Click OK.
__h.
Click Add to create the second argument.
__i.
In the Name field, enter: message
__j.
In the Type field, click Browse and type string to find String, and then click OK.
__k.
Click OK.
The member should look like this.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__l.
Click Finish.
This new method now appears in the list of Members of the Loan class. As this method is
virtual, an implementation is required.
__4.
In the Members list, double-click loanDecision (StatusType, String).
__5.
In the Member Verbalization pane, click Create a default verbalization.
__6.
Replace the content of the Template field with the following phrase to define the verbalization to
be used in rules:
Page 29
ODM on Cloud PoT
IBM Software
loan decision: {0, <status>} {this} with the reason {1, <message>}
__7.
Scroll down to the BOM to XOM Mapping panel, and expand the editor.
__8.
Type the following implementation for this method in Advanced Rule Language (ARL):
this.status = status;
this.approved = ! (status == miniloan.Loan.StatusType.Rejected);
this.messages.add(message);
Note:
The BOM to XOM mapping mechanism can translate BOM-based rule artifacts into
XOM-based rule artifacts at run time.
The Advanced Rule Language (ARL) was designed for the decision engine. It
contains a set of keywords, and has its own syntax.
__9.
From the File menu, select Save All (or press Ctrl+Shift+S) to save your work.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.3
Defining the Decision Service operation and entry point


1.3.1
Step 1: Define the Decision Service operation
Step 2: Define the service interface with ruleset parameters
Define the service interface with variables and ruleset parameters
You use decision operations to define rulesets within a decision service. A ruleset combines business
rules into an executable container.
Decision operations define the contents of the ruleset, and the connection between the ruleset and the
calling application. Decision operations also include information about how the rule engine processes the
ruleset. You can also define a ruleflow that is used when the operation is called by an application.
Ruleset scope and contents
When you create a decision operation, both the rules of the project that contains the operation and all the
rules from any referenced rule projects are included by default.
Operation signature and ruleset parameters
Calling applications interact with a ruleset by using input and output parameters that are defined in the
operation signature.
Ruleset parameters can have three directions:

IN: The parameter value is provided as input to the ruleset on execution.

OUT: The parameter value is set by the execution of the ruleset and provided as output from the
ruleset at execution completion.

IN_OUT: The parameter value is provided as input to the ruleset on execution and its value can
be modified by the ruleset and provided as output at execution completion.
You base ruleset parameters on ruleset variables that are available in the rule projects that are part of
the scope of the decision operation. Only ruleset variables that are defined at the top-level package are
eligible to be used as ruleset parameters.
Page 31
ODM on Cloud PoT
IBM Software
1.3.2
Define the Decision Service operation
To create the decision operation
__1.
In the Decision Service Map, click Add decision operation.
__2.
In the Name field of the New Decision Operation wizard, enter: Miniloan Decision
Operation
__3.
Click Next.
There is only one rule project in the workspace and it’s selected by default.
__4.
Click Next and then click Finish.
You now define the parameters for the operation. This defines the interface of the service.
__5.
In the Decision Service Map, click Go to operation map.
__6.
In the Select an operation page, select Miniloan Decision Operation.dop and click OK.
__7.
In the Design signature part of the Operation Map, click Add variable set.
__8.
In the Name field, type variables and click Finish.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__9.
Click Add.
__10.
Create a new variable.
Page 33
__a.
In the Name field, overwrite the name by typing: borrower
__b.
Click in the Type field, click the Ellipsis (…) and type borrower to select
miniloan.Borrwer and click OK.
ODM on Cloud PoT
IBM Software
__c.
__11.
In the Verbalization field, type: the borrower
Add another variable for the Loan with these values:

Name: loan

Type: miniloan.Loan

Verbalization: the loan
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
The Verbalization is the term that is used when writing rules against the loan and the borrower
variables.
__12.
Press Ctrl+S to save your work.
__13.
In the Design signature part of the Operation Map, click Bind Variables.
__14.
In the Eligible variables section, expand variables.
__15.
Drag and drop the borrower variable to the Input parameters section.
__16.
Drag and drop the loan variable to the Input - Output parameters section.
Page 35
ODM on Cloud PoT
IBM Software
__16.
Switch to the Overview tab of the Decision Operation editor, and in the Ruleset Name section,
change the ruleset name to: <your userid>_operation
Where <your userid> is the user name part of your email address or your initials, which you
append to the operation name so that the name is unique.
__17.
Save your work (Ctrl+S).
1.4
Organizing and orchestrating rules
In this task, you use Rule Designer to orchestrate rule execution with a ruleflow.
To specify the order in which rules are executed, you must create a ruleflow. A ruleflow is a way to
organize the sequence in which rules are processed by the rule engine.




Step 1: Create rule packages
Step 2: Create the ruleflow
Step 3: Design the ruleflow
Step 4: Define the ruleflow conditions
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.4.1
Create the rule packages
The Miniloan Rules application first validates the input request data for the loan and the borrower. If the
data is valid, the rules assess whether the borrower is eligible for the loan.
When defining the flow of execution, you organize your rules into packages that contain related rules. In
this case, you have two packages of rules related to validation and eligibility. A package can contain one
or more rules, and each rule package is treated as a task in the ruleflow.
To create rule packages:
__1.
In the Orchestrate part of the Operation Map for the Miniloan Decision Operation, click Add
rule package.
__2.
In the New Rule Package wizard, name the package: 1 – validation and click Finish.
The new 1 - validation rule package appears in the Rule Explorer. This package is to
contain rules that perform a set of basic checks. For example, you write a rule to verify that loan
requests are within valid limits (such as the loan amount being less than $1,000,000).
__3.
Page 37
Create another package with the name: 2 - eligibility
ODM on Cloud PoT
IBM Software
This package is to contain a decision table that determines whether the borrower is eligible for
the loan according to the yearly repayment and the score.
Your rule project now contains two packages for storing your rules:
1.4.2

1 – validation

2 – eligibility
Create the ruleflow
To define the high-level flow of execution for the business rules, you need to create a ruleflow. A ruleflow
is also the entry point of a Decision Service operation. In this activity, you organize the business logic so
that, after validating the loan criteria, the applicant’s eligibility is determined.
To create a ruleflow:
__1.
In the Orchestrate part of the Operation Map for the Miniloan Decision Operation, click Add
ruleflow.
__2.
In the New Ruleflow wizard, verify that the Source folder is set to /Miniloan Rules
<your_userid>/rules and that the Package field is empty.
Note:
You append your initials or user name as <your_userid> to give
your decision service a unique name. This distinguishes your decision
service from other Miniloan Rules decision services that might be
published to the same cloud instance.
__3.
In the Name field, type: miniloan
The ruleflow name and structure should look like this:
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__4.
Click Finish.
The Ruleflow Editor opens so that you can visually construct the flow of tasks.
1.4.3
Design the ruleflow
__1.
Click Create a start node
and then click in the ruleflow editor to add the start node to the
ruleflow diagram. Do not drag the start node.
__2.
Click Create an end node
and add it to the diagram.
You now have a start point and an end point for your ruleflow diagram.
__3.
Drag the 1 – validation rule package from the Rule Explorer view on the left and drop it
into the ruleflow editor.
The 1 – validation rule package becomes a rule task in the ruleflow. By dropping this
package in the ruleflow, any rule that you create in the package is executed at this point in the
ruleflow, unless you specify otherwise.
__4.
Drag the 2 – eligibility package from the Rule Explorer and drop it below the validation
package. Do not worry about the format of the diagram.
__5.
Create transitions between the diagram elements.
__a.
Page 39
Click Create a transition
.
ODM on Cloud PoT
IBM Software
__b.
Click the start node and click the 1 – validation package.
__c.
Click the 1 – validation and click the 2 – eligibility package.
__d.
Click the 2 – eligibility package and click the end node.
__e.
Click the 1 – validation and click the end node.
__f.
Click Create a transition
again to deselect the transition arrow.
Note:
The end node has two inbound transition links.
__6.
Click the Layout All Nodes
icon to rearrange the ruleflow diagram.
__7.
Save your work by pressing Ctrl+S.
Ignore the errors on the transitions, which indicate missing conditions. You fix these errors in the
next step.
1.4.4
Define ruleflow conditions
You can define conditions on transitions in the ruleflow. In the miniloan ruleflow, you set a transition
condition so that rules in 2 – eligibility package run only when data is validated. To do so, the
status of the loan is set to Accepted by default. If no rule triggers in the 1 - validation task, then
the status remains Accepted and the 2 – eligibility is evaluated. Otherwise, the flow reaches
the end point directly.
Add conditions to the ruleflow:
__1.
The miniloan ruleflow should still be open from the last exercise; if not, open it now.
__2.
Set the loan to Approved
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__a.
Double-click the
start node of the ruleflow.
The Properties view opens in the lower-right part of Rule Designer.
__b.
In the Initial Action page, select IRL and type:
loan.approved = true;
Note:
The ILOG Rule Language (IRL) contains a set of keywords, and has its
own syntax to structure each part of the rule.
__3.
Define the condition on the transition from 1 – validation to 2 – eligibility.
__a.
Double-click the transition from 1 – validation to 2 – eligibility.
__b.
The Properties view should appear at the bottom of Rule Designer. If not, click the
Properties view as follows:
__c.
In the Label field of the Condition page, type: data validated
__d.
Select Use BAL for transition condition to write the condition by using the Business
Action Language (BAL), and in the text area, type:
'the loan' is approved
You can also press the Space bar to use Content Assist, which prompts you with
vocabulary.
Notice that the transition from 1 – validation to the end node is automatically set to
else.
Page 41
ODM on Cloud PoT
IBM Software
__e.
Save your work.
Your ruleflow should now look like this:
__4.
Close the ruleflow editor.
You have now defined the flow of execution.
1.5
Authoring business rules
In this task, you use Rule Designer to author the business rules in an if-then layout using the vocabulary
that you created.
When developing a rule project, the developer writes the initial rules, designs rule templates, and
organize the folders that are used to manage the rules. Later, the business user writes and edits these
rules in a web environment, though a developer might be asked to write more complex rules.
For this lab, you create the first business rules and import other rules that are prepared for you.

Step 1: Create a business rule

Step 2: Import remaining rules
1.5.1
Create an if-then action rule
The first business rule that you write rejects the loan if the requested loan amount is greater than
$1,000,000. You use the Content Assist completion mechanisms in the Intellirule Editor to help you
create the rule.
To create a business rule:
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__1.
In the Author part of the Operation Map, click Add action rule.
__2.
Make sure that the Source folder is set to /Miniloan Rules <your_userid>/rules.
__3.
In the Package field of the New Action Rule dialog, click Browse and double-click 1 –
validation.
__4.
In the Name field, type maximum amount and click Finish.
The Intellirule Editor opens and allows you to enter the rule logic by using the Content Assist
completion.
__5.
Create the conditional if logic.
__a.
In the Intellirule Editor, type if and then press the Spacebar. The Content Assist box
opens.
__b.
You can either select terms and phrases from the menu to build the following expression
or type directly:
the amount of 'the loan' is more than 1,000,000
__c.
__6.
Page 43
Press Enter for a new line.
Create the action then clauses.
ODM on Cloud PoT
IBM Software
__a.
Type then (and space) and press Ctrl+Shift+Space to activate the Tree Completer.
__b.
Double-click loan decision: <status> <a loan> with the reason <message>.
__c.
Click the placeholders (<…>) to complete the action statement to match the following
statement:
loan decision: Rejected 'the loan' with the reason "The loan cannot
exceed 1,000,000" ;
Important!
You must include a semi-colon (;) at the end of the line.
__7.
Press Ctrl+Shift+F to format the rule. Your rule should now be:
You have created your first if-then action rule.
__8.
Save your work and close the Intellirule Editor.
1.5.2
Create two other rules in the 1 – validation folder
__1.
Create debt to income rule in the 1 – validation package with the following text:
definitions
set ‘maximum yearly repayment’ to 0.30 * the yearly income of ‘the
borrower’ ;
if
the yearly repayment of ‘the loan’ is more than ‘maximum yearly
repayment’
then
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
loan decision: Rejected ‘the loan’ with the reason "Debt to income
ratio is too high." ;
Note:
The definitions part introduces local variables that you can use in the
rest of the rule.
This rule rejects the loan if the yearly repayment of the loan exceeds 30% of the yearly revenue
of the borrower.
Create another rule in the 1 – validation package, named minimum credit score,
with the following text:
__2.
if
the credit score of ‘the borrower’ is less than 200
then
loan decision: Rejected ‘the loan’ with the reason “Credit score is too
low.” ;
The 1 – validation package should look like this:
Page 45
ODM on Cloud PoT
IBM Software
1.5.3
Import the remaining rules
The Miniloan Rules project requires an additional decision table to take the final decision when the loan
has not been rejected by the validation rules.
So that you do not have to create the decision table of the 2 – eligibility rule package, you
import it from the solution workspace.
To import the remaining rules:
__1.
Import the remaining rules.
__a.
Click File > Import.
__b.
In the Import wizard expand General > File System, and click Next.
__a.
In the From directory field, click Browse and select the folder where you
downloaded/extracted ODMoc.zip, and click OK.
__c.
Select the decision.dta file in the section on the right.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__d.
In the Into folder field, click Browse and select Miniloan Rules <your userid> > rules
>2 – eligibility and click OK.
__2.
Click Finish.
__3.
When your rules are properly loaded, the rule structure should look something like this (in the
“Miniloan Rules <your_userid>” folder).
1.5.4
View the imported rule artifact
Next, you review the decision table that was imported in the previous step.
__1.
In the Rule Explorer, expand the 2 – eligibility folder and double-click decision to open
and review the decision table:
You use decision tables to represent rules that share conditions and actions. Each row in a
decision table represents a rule. By placing your cursor over the number of a row, you can view
the test of the corresponding rules as hover help.
__2.
In the rules folder, double-click miniloan to open the ruleflow.
__3.
In the Ruleflow Editor, double-click the 1 – validation task.
__4.
In the Properties view, click the Rule Selection tab and expand the 1 – validation task.
Page 47
ODM on Cloud PoT
IBM Software
By default, all the rules participate when the task is executed by the rule engine.
__5.
In the Ruleflow Editor, double-click the 2 – eligibility task and open the Rule Selection
tab.
The imported decision table is automatically included in the 2 – eligibility task of the
ruleflow.
__6.
Close the Ruleflow Editor.
__7.
Make sure that the Decision Operation uses the miniloan ruleflow.
__a.
In Rule Explorer, expand the deployment folder and double-click Miniloan Decision
Operation.
__b.
In the Ruleflow section, select Use main ruleflow and click <choose a ruleflow>.
__c.
Expand the Miniloan Rules > rules folder, select miniloan and click OK.
__8.
Save your work.
__9.
In the Operation Map, click return to decision service map.
You have now completed the rules and are ready to test them.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.6
Deploying and executing rules on Rule Execution Server
The decision operation defines the ruleset that is deployed. It also defines the input and output
parameters that are used to exchange information between the ruleset and the client application.
In this task, you deploy your ruleset to Rule Execution Server with a deployment configuration. You also
retrieve the generated web service that is associated with the ruleset and, finally, you validate the
business logic that you implemented and validated in previous tasks is now in Rule Execution Server.

Step 1: Deploy the rules from Rule Designer

Step 2: View the deployed RuleApp in Rule Execution Server

Step 3: Retrieve the Hosted Transparent Decision Service

Step 4: Testing the HTDS with the REST API
1.6.1
Deploy the rules from Rule Designer
You create deployment configurations for the decision service and use them to deploy RuleApps.
In this task, you create deployment configuration for the decision service. Then, you use the
configuration to deploy a RuleApp that contains the rulesets that are defined by the decision operations.
The deployment configuration contains all the information that is required for a deployment:

The RuleApp name, version, and properties

Which decision operations to include in the deployment

The ruleset properties and behavior

The version policy

The target server

The type of deployment, either production or nonproduction. This choice has the following effects:
o It filters the choice of target servers according to their type, identified when you create a
server location.
o As part of governance in the Decision Center Business console, only deployment
configurations set to nonproduction are available if a release or change activity is not
complete.
A deployment configuration is an artifact that can be published and synchronized with Decision
Center.
To create a deployment configuration and deploy the RuleApp:
__1.
Click the Miniloan Rules project in the Rule Explorer tree view on the left.
__2.
In the Decision Service Map (the name of the view is Rule Project Map), click Create
Deployment Configuration.
Page 49
ODM on Cloud PoT
IBM Software
__3.
Make sure that the Deployment folder field uses this path:
/Miniloan Rules <your userid>/deployment
__4.
In the Name field, enter Miniloan Deployment and click Finish.
__5.
In the Decision Operation section on the right, click Include decision operation.
__6.
In the Configured Decision Operation section, click the plus sign.
__7.
Choose Select existing decision operation, select the Miniloan Decision Operation, and
click Finish.
__8.
Save your work and return to the Overview tab (at the bottom of the view).
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
You now need to define the server to which you want to deploy the rules.
__9.
In the Target Servers section on the right, click Define target servers.
__10.
Click the plus sign
and in the Target Server window, choose Select existing nonproduction
Rule Execution Server connections, choose Development Environment, and click Finish.
__11.
Save your work and go back to the Overview tab.
__12.
To deploy the rules, click Proceed to ruleapp deployment in the Deployment section at the
lower right of the Overview tab.
__13.
Review the Deployment Summary and click Next.
Page 51
ODM on Cloud PoT
IBM Software
__14.
Click Connect and enter Credentials. Click Next.
__15.
Review the version of the RuleApp and Ruleset. Click Finish.
A deployment report is generated with the details of what was deployed.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.6.2
View the deployed RuleApp in Rule Execution Server
You can now verify that the Miniloan_Decision_Operation ruleset is deployed properly to Rule
Execution Server, which is an execution environment for rules that manages a pool of rule engines.
Rule Execution Server handles the runtime, management, performance, and security associated with the
execution of your rules. From your application, you can access Rule Execution Server by using Web
Services.
To view the deployed RuleApp:
__1.
Sign in to IBM ODM on Cloud portal at this URL:
https:// <vhostname>.bpm.ibmcloud.com
__2.
Page 53
On the Applications tab, in the Rule Execution Server console pane, click Launch.
ODM on Cloud PoT
IBM Software
__3.
Click the Explorer tab (or alternatively, click the Explorer link from the RES home page).
__4.
Expand RuleApps and Miniloan_Deployment in the Navigator.
__5.
Click the <your userid>_operation and review the ruleset information.
You see that the ruleset was successfully deployed to Rule Execution Server.
Do not close this view, as you need it open for the next steps.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.6.3
Retrieve the Hosted Transparent Decision Service
In this activity, you are going to retrieve the Hosted Transparent Decision Service (HTDS). A transparent
decision service is technically either a strongly typed Web Service (WSDL) or a REST API that provides
an interface to access a deployed rule set. The Decision Service component can pass one or more input
parameters to the rule engine and access the return values. The transparent decision service support
includes traceability from decision services to rules, runtime monitoring, and version management.
The HTDS is available in two forms: SOAP and REST. First, you look at the REST API to call the rules,
then you retrieve the SOAP HTDS.
__1.
In the Ruleset View for your latest ruleset, click Retrieve HTDS Description File on the toolbar.
You should still be on the Ruleset View page from the previous step. If not, click the latest
version of the /Miniloan_deployment/odmuser1_operation/ ruleset, as you did earlier.
__2.
For the Service protocol type, make sure that SOAP is selected, and choose Latest ruleset
version and Latest RuleApp version.
__3.
Click View.
The Web Service WSDL opens in a separate browser tab.
Page 55
ODM on Cloud PoT
IBM Software
__4.
Return to the Rule Execution Server console tab in your browser and again click Retrieve HTDS
Description File.
__5.
This time, for the Service protocol type, select REST, choose Latest ruleset version and
Latest RuleApp version, and click View.
The REST API WADL file opens in a separate browser tab.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.6.4
__1.
Page 57
Test the Hosted Transparent Decision Service (REST API)
Go back the Rule Execution Server Console tab in your browser and again click Retrieve
HTDS Description File.
ODM on Cloud PoT
IBM Software
__2.
Click Test. A new page opens with an interface that allows you to test the REST API
generated for the ruleset. You can now test the REST API by:


__3.
Changing the request payload type (XML or JSON)
Providing some values for the input loan and borrower. Default values are generated
but you might want to put some more relevant values for the attributes.
Change the values for the loan and borrower’s attributes. For example, you can copy the
values that are provided here and paste them in the Execution Request field.
{
"borrower": {
"name": "Joe",
"creditScore": 600,
"yearlyIncome": 80000
},
"loan": {
"amount": 500000,
"duration": 240,
"yearlyInterestRate": 0.05
},
"__DecisionID__": "12345"
}
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__4.
Click Execute Request to test the rules with the REST API.
The result is returned in the Server Response view.
You have successfully deployed and tested a rule-based decision service.
Page 59
ODM on Cloud PoT
IBM Software
1.7
__1.
Using the Web App to test deployed the rules
Open the Miniloan Web Application at the URL that was provided to you for this session. For
example:
http://miniloan-cloud.mybluemix.net
__2.
Make sure that the following parameters are set correctly:

Server Hostname: <vhostname>.bpm.ibmcloud.com
Where <vhostname> is the host name for your cloud instance.
__3.

Ruleset path: /Miniloan_Deployment/<your userid>_operation

User ID: <your username>

User Password: <your password>

Select environment: Development
Click Validate Loan.
The loan is rejected with same reason as the testing in previous step.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.8
Publish the rules to Decision Center
In this task, you make the rule project that you developed in Rule Designer available to business users in
Decision Center.
Decision Center is a web-based environment that allows business users to view, create, edit, and
simulate rules. From Rule Designer, you publish your rule project to Decision Center, and then
periodically synchronize the work of the business users from Rule Designer. Furthermore, any changes
that are made to the rules in Decision Center can be synchronized with the Rule Designer workspace.
1.8.1
Publish the rules to Decision Center
To make your rule project available to business users, you need to connect to Decision Center from Rule
Designer and publish Miniloan Rules.
To publish the rule project to Decision Center:
__1.
Go back to Rule Designer.
__2.
Right-click 2 - eligibility > Decision and click Refactor > Update UUIDs.
Note:
The decision table was imported from file system. It might have the UUID
(Universal Unique Identifier) conflicted with existing one in the Decision Center.
__3.
In the Updating resource UUIDs window, click OK.
__4.
In Rule Designer, right-click the Miniloan Rules <your userid> project and click
Decision Center > Connect.
Page 61
ODM on Cloud PoT
IBM Software
__5.
Leave the Data source field empty and click Connect.
__6.
Enter you credentials and click Connect again.
__7.
Click Finish. You get the following message.
__8.
Click OK.
__9.
Click No when prompted to switch perspectives.
An empty Synchronize view opens, indicating that the projects in Rule Designer and Decision
Center are synchronized. Therefore, your rules are now published to Decision Center. You can
now manage the rules in Decision Center as done during the Lab 1 Rules Business Track.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
1.9
Summary
In this lab, you assumed the role as an IT analyst and performed the following tasks:

Create a rule project in Rule Designer

Import an existing execution object model (XOM), from which you created and modified a
business object model (BOM)

Create if-then business rules, a ruleflow, and import a decision table

Test the rules against some scenarios

Deploy a project to Rule Execution Server to test the rules in a runtime environment

Publish a project to Decision Center
Page 63
ODM on Cloud PoT
IBM Software
Lab 2
Rules Business Track
In this lab, you act as a business user, by using the Decision Center Business console to write,
modify, test, simulate and deploy the business rules, and to work collaboratively with the other rules
editors.
You use the Business console to quickly access the rules that you need to modify. You edit some rules
and add comments and posts that are useful for the other business users. Then, you test the new
version of the rules to validate that the new version of the rules behaves as expected. You also
experience the power and ease of use of the new simulation capability of Decision Center. Finally, you
learn how to deploy rule applications from Decision Center to Rule Execution Server.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
2.1
Manage the business rules with the Decision Center Business Console
Business users create and edit business rules in Decision Center. Their work is saved in the central rule
repository, which manages rule versions, rule history, and multi-user access.
Decision Center Business console is the browser-based tool used for creating and managing business
rule assets in a collaborative way. The robust capabilities that are offered through this interface are one
of the features that distinguish Operational Decision Manager from other decision-based platforms.
In this exercise, you see each component of the Decision Center environment.




Step 1: Sign in to the Decision Center Business Console
Step 2: Review and understand the rules
Step 3: Test the rules
Step 4: Simulate the rules
Later in the lab, you go into more depth of how to use some of these capabilities.
Note:
This lab is focused on the business user experience. It starts with a
rule project that has the basic building blocks already defined and
deployed in Decision Center.
2.1.1
Sign in to Decision Center Business console
To sign in to Decision Center Business console:
1.
Sign in to IBM ODM on Cloud portal at this URL:
https://<vhostname>.bpm.ibmcloud.com
Where <vhostname> is the host name for your cloud instance.
2.
Page 65
Click Launch in Decision Center Business console pane.
ODM on Cloud PoT
IBM Software
2.1.2
Reviewing the business rules
__3.
Click LIBRARY to review the Decision Services.
__4.
Click Miniloan Rules (your user name) and click main in Branches tab.
You can see all the rules of the Miniloan Rules Decision Service.
Next, you need to change some of the rules of the Miniloan Rules decision service because
the bank decided to be less restrictive on the loan acceptance criteria.
__5.
The following shows Decision Service view. Make sure that the Decision Artifacts tab is open
to see the list of artifacts in the Miniloan Rules project.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Next, you review the contents of the Miniloan Rules project.
__6.
Review the decision operation.
__a.
Click Miniloan Rules > Operations and click Miniloan Decision Operation.
__b.
Notice the name of the ruleset in this decision operation in the Overview section.
Page 67
ODM on Cloud PoT
IBM Software
A decision operation defines one ruleset and its input and output parameters. A ruleset
combines business rules into an executable container that is deployed.
__c.
In the Inputs and Outputs section, notice the names of the variables defined for this
operation.
The variables are bound to ruleset parameters, which are used to exchange data
between a ruleset and the client application. In Miniloan Decision Operation, the
borrower and the loan variables are bound to the ruleset parameters.
__7.
Review the ruleset variables.
Click variables to view the ruleset variables.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
A ruleset variable defines a value of a specified type and verbalization. Ruleset variables can be
used in all the business rules you add to a rule project, and as input and output parameters in
decision operations.
__8.
Review the ruleflow.
__a.
Click miniloan to view the ruleflow.
This sequence flow in which rules for rule execution within the ruleset is orchestrated by
a ruleflow in the ODM terminology. In the Business console, you can view the ruleflow
but you cannot edit it.
The rules are organized in these functional packages:

Page 69
1 – validation
ODM on Cloud PoT
IBM Software

2 – eligibility
These packages are executed sequentially. The loan is Approved by default before the
rules execute. Then, the ‘1 – validation’ rules are evaluated. If the status of the loan
is still Approved, then the ‘2 – eligibility’ rules are evaluated according to above
flow.
Note:
During the Technical track, you see how to create and edit
a ruleflow.
__b.
Click the 1 – validation ruleflow task (light blue box) to view the contents of that
task.
__c.
Click the 1 – validation folder in the task.
The folder view opens and you can click the rules in that folder to open them and review
the rule statements.
__d.
Use the “back” arrow to return to the ruleflow view.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
In some of the rules, you see a phrase like this one:
loan decision: Rejected 'the loan' with the reason "<some
explanation>";
This construct was requested by the business users and it is equivalent to:
reject 'the loan';
add "some explanations" to the messages of 'the loan' ;
It makes the writing of the rules easier for the business users. In the Technical track, you see
how such a specific phrase can be added to the business vocabulary.
__9.
Review the decision table in the 2 – eligibility rule package, which contains the business
logic about whether a loan is risky, average, or low.
What borrower and loan request information would generate the following loan
decision statuses?



Risky loan
Average risk loan
Low risk loan
For example, if Joe has a credit score of 400 and requests a loan amount of $200,000,
the Miniloan web application generates a result of: Risky loan.
This is a result of the yearly repayment calculation as “0.3 * 80000 (yearly income) =
$24000” by the “debt to income” rule in the validation folder.
Can you find the correct row in the decision table that matches this condition?
Write down the inputs for the other decision statuses and try them in the Miniloan web
application.
Note:
You can make some tests with the Miniloan Web App.
2.1.3
Test the rules
As a business user, you want to test the rules make sure that the business output as expected.
Page 71
ODM on Cloud PoT
IBM Software
__1.
Click the Tests tab.
The first step is to view the test suite file, which is a file that contains various scenarios to test
along, with their expected output.
__2.
Click plus to add a new test.
__3.
Change the Name to: Miniloan Test
__4.
In the File to use field, click Choose and select the miniloan-test.xlsx file from the folder
you saved/extracted ODMoC.zip on the Windows Desktop.
__5.
Click miniloan-test.xlsx in the File to use field.
__6.
When prompted to save the file, click OK.
__7.
Review the scenarios.
Note: You can use the latest version of Microsoft Excel or Excel Viewer to view the scenario
files.
__a.
Review the values in the Scenarios sheet:
Scenario ID
description
Scenario 1
Low risk
the
borrower
the loan
credit score name yearly income
amount
800 Joe
80000
250000
duration
yearly interest rate
240
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
0.05
IBM Software
Scenario 2
Average risk
650 Joe
80000
250000
240
0.05
Scenario 3
Debt too high
500 Joe
80000
500000
240
0.05
__b.
Review the values in the Expected Results sheet.
Scenario ID
the messages of the loan contains
the status of the loan equals
Scenario 1
Low risk loan
Accepted
Scenario 2
Referred
Scenario 3
Rejected
__8.
In the Report section, select the execution details as shown below:
__9.
Click Save and Run
.
Decision Center switches to the Reports view. Testing might take a few seconds to complete as
performs the following actions:

Deploys the current version of the rules to a remote Rule Execution Server (RES)

Reads each scenario from the Excel spreadsheet, transforms into Java objects, and sends
to the RES for execution against the deployed rules
Compares the output of the execution to the Expected Results that are defined in the Excel
spreadsheet
Generates an execution report


After the test is done, you see a check icon displayed in the Status column.
Page 73
ODM on Cloud PoT
IBM Software
__10.
Click the generated report name (Report – 20XX…) to view the execution results.
__11.
Check that the success rate is 100%.
__12.
Review the details of Scenario 1 by clicking the triangle twistie to expand the view. You may click
Details… to see more information.
__13.
In Scenario 3, expand the Execution Details to see which were rules triggered by the scenario
(High debt to income ratio).
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Why did this rule trigger for this scenario?
__14.
Click Close.
2.1.4
Run a simulation
By using simulations, you can evaluate how changes to rules or data affect the results of your business
rule applications.
You can use either fictitious data or real data from your organization. When you run a simulation, it
shows the results in a user-formatted report.
You assemble a simulation by bringing together key performance indicators (KPIs), a set of rules and
data. You define the KPIs by using metrics that take values from the business rules. The KPIs serve as
measurements of the results from running the rules.
You configure a simulation to show its results in a report. You format the report to make the results of the
simulation easy to understand. The resulting report helps you determine any changes for the rules or the
data.
You can change all these aspects of a simulation in the Business console, and run the simulation again
to assess your changes. You can also compare reports side by side in the console. Through this iterative
process, you can refine the way that your rules work to make sure that you get the right results from your
business rule applications.
__1.
Click main within the breadcrumbs at the top to return to the Decision Service view.
__2.
Click the Simulations tab and make sure that you are on the Metrics page.
Page 75
ODM on Cloud PoT
IBM Software
__3.
Define the metrics.
a. Click the
to create a new metric.
b.
In the Name field, type: processed scenarios
c.
In the Type list, choose Boolean.
d.
For the Metric Expression field, you can press CTRL+SPACE to list the possible options or
you can simply type: the status of 'the loan' is not null
This metric allows you to count the simulation scenarios that are successfully processed.
e.
Click Save
.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
f.
Leave the comment empty and click Create New Version.
g.
Create another metric with these values:

Name: loan status

Type: Domain

Metric expression: the status of ‘the loan’
This metric allows you to store the status value of the loan.
h.
Click Save
i.
Click Create New Version.
__4.
.
Define the KPIs.
a.
Switch to the KPIs section.
b.
Click
Page 77
to create a new KPI.
ODM on Cloud PoT
IBM Software
c.
In the Name field, type: status distribution
d.
In the KPI expression field, type: number of 'processed scenarios' grouped by
'loan status'
OCCASIONAL PROBLEM: Sometimes ‘processed scenarios’ will not show without restarting
the server…
__5.
e.
Click Save
.
f.
Click Create New Version.
Define the data.
a.
Switch to the Data section.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
b.
Click
to create a new data file for the simulation.
c.
In the Name field, type: simulation data
d.
Click Browse, go to the directory you saved/extracted ODMoC.zip, and select the
simulation.xlsx file.
e.
Click Create.
Note:
Here, the data source is an Excel spreadsheet. Decision
Center also allows connection to a database and use of
existing data as input for the simulation.
You now need to define how we want to display the simulation execution results.
__6.
Define the format for the report.
a.
Page 79
Switch to the Report Formats section.
ODM on Cloud PoT
IBM Software
b.
Click
to create a report format for the simulation.
c.
In the Name field, type: Miniloan Simulation Report
d.
Click Add section.
e.
Click New Section and change the section name to: Loan Status
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
f.
Drag the status distribution KPI from the right panel to the Loan Status section. Or click
Actions > Add KPI > status distribution > Center
g.
Hover the mouse pointer over the status distribution KPI and click the gear icon:
h.
Change the KPI Display Configuration as follows:
i.
Page 81

Select Pie for the Display Type.

Select Percentage for the Data Label.

Select green for A, orange for B and red for C by clicking the colored square box
next to these labels.
Click OK.
ODM on Cloud PoT
IBM Software
__7.
j.
Click Save
.
k.
Click Create New Version.
Define and run the simulation.
a.
Switch to the Simulations page.
b.
Click
c.
In the Name field, type: Miniloan Decision Operation Simulation
to create a new simulation.
A Simulation Configuration puts together all the information required to run a simulation:
d.

A Rule Execution Server

A report format (by default, the one you created is selected)

Input data (by default, the data file you created is selected)
Click Save and Run
.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
e.
Click Create New Version.
f.
Click OK.
__8.
Wait for the check symbol to appear in the Status column and then click the simulation report
name.
The simulation report opens.
__9.
Page 83
Click Close.
ODM on Cloud PoT
IBM Software
What other KPI can you think of?
2.2
Changing the rules and analyze the impact
2.2.1
Modify an action rule
In your business user role, you are asked to change the allowable debt-to-income ratio from 30% to 40%
for people who earn less than $50,000.
Your starting point in Decision Center is to find all the rules in your project that use the yearly income on
which the debt-to-income ratio is based.
__1.
Click the Decision Artifacts tab.
__2.
In the search field, type yearly income and press Enter.
Notice the filter options on the left that help you quickly find the rule you're looking for even if the
project contains hundreds or thousands of rules.
By looking at rule previews, you see that the debt to income rule needs to be changed to
implement the policy change.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__3.
Click the debt to income rule to review to rule.
__4.
Click Edit. The editing panel is launched to edit the content of the rule.
The rule editor can be used in two modes, both of them are active at the same time:

Point and click
The editor automatically displays a list of possible choices for the next part of rule you're
writing. At any time, press Ctrl+Space to display the list.

Free text
You can directly type in the part of rule you want to write.
Use one mode or both modes to modify the rule.
__a.
In the definitions part of the rule, change the value 0.30 to 0.40.
__b.
Add the following condition above the then keyword:
and the yearly income of 'the borrower' is less than 50000
__5.
Press Ctrl+Shift+F to format the rule.
__6.
Click Save and add this comment:
Increased the debt-to-income from 30% to 40% for salary below 50,000
Page 85
ODM on Cloud PoT
IBM Software
__7.
Click Create New Version. The new rule details are displayed.
2.2.2
Modify a decision table
The next task is to make your lending criteria less restrictive.
__8.
Click main and make sure you are in the Decision Artifacts tab.
__9.
Click the 2 – eligibility folder and click decision to open the decision table.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__10.
Click the edit icon in the upper-right corner.
__11.
When prompted to choose the type of row order, click OK to use Automatic.
The decision table editor opens to edit the content of the decision table and its properties.
__12.
In row 7, double-click the cell that contains "200 650" in the Corporate score column.
__13.
Replace 650 with 550 and press Enter.
__14.
Click the "Optimize row order"
icon.
Notice the warning on the column header. This indicates that there is an error.
__15.
Hover the mouse over the column name to see the error message that states that Rows have
gap(s).
__16.
To solve the gap, double-click the cell that contains ”650 750” in the Corporate score column
in row 8, replace 650 with 550, and then press Enter. The error disappears.
Page 87
ODM on Cloud PoT
IBM Software
__17.
Click elsewhere on the table and then hover the mouse pointer over a row number to view the
rule associated with that row.
__18.
Click Save and add a comment to the version that you created.
A relevant comment could be:
Changed the score threshold from 650 to 550 for Rejected loan when the
yearly repayment is more than 30000.
__19.
Click Create new version.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
2.2.3
Review a decision table timeline and compare two versions
__1.
Click the
__2.
Select the two more recent versions and click Compare.
Compare icon.
The version comparison view is displayed. Hover the mouse pointer over one of the changes
listed at the top of the view and note that the change is highlighted in the table:
__3.
Click main in the breadcrumb to return to the Decision Service view.
2.3
Validating the rules and deploying them
In the previous task, you modified a rule and a decision table. In this task, you run the tests and the
simulation again to check that the modified rules behave as expected.



Step 1: Run the simulation
Step 2: Deploy the rules
Step 3: Check that the rules correctly execute
2.3.1
Run the Simulation
__1.
Click the Simulations tab and make sure that you’re on the Simulations page.
Page 89
ODM on Cloud PoT
IBM Software
__2.
Hover the mouse pointer over the simulation row and click the Run icon.
__3.
Click OK.
Once the processing is over, open the simulation report by clicking on its name. Make sure to
open the latest simulation report.
The simulation report opens.
__4.
Click the Compare icon and select the previous simulation report that you generated earlier.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__5.
Click Compare.
A side-by-side comparison of the simulation reports opens.
Explain the differences. Why are there less Rejected customers?
What other KPI would help you better understand this situation?
2.3.2
Deploy the rules to Development Environment
__1.
Click the Deployments tab and make sure that you are on the Configurations page.
Page 91
ODM on Cloud PoT
IBM Software
__2.
Hover the mouse pointer over the Miniloan Deployment configuration name and click the
Deploy icon.
__3.
Make sure that only Development Environment is selected in the Servers section.
You can see that the version of the deployed RuleApp (1.0 in this case) and Ruleset (1.1 in this
case) are created.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__4.
Click Deploy.
__5.
In the Deployment status window, click OK.
A check symbol should appear when the deployment is completed.
2.3.3
Test the deployed the rules
__6.
Switch to the Miniloan Web Application in a browser at the URL that was provided to you for
this session. For example:
http://miniloan-cloud.mybluemix.net
__7.
Page 93
Set the following values, making sure the version number is set to 1.1 and the environment is set
to Development.
ODM on Cloud PoT
IBM Software

Server Hostname: <vhostname>.bpm.ibmcloud.com
Where <vhostname> is the host name for your cloud instance.
__8.

Ruleset Path: /Miniloan_Deployment/1.0/your user name_operation/1.1

User ID: <your username>

User Password: <your password>

Select environment: Development
Click Validate Loan.
The result is now different. The loan is Approved.
Why is the result different?
2.3.4
Deploy the rules to Test Environment and/or Production Environment
Since the result is the same as expected, you want to promote the new modification to Test
Environment and/or Production Environment.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__1.
Back in the Business console, click the Deployments tab and make sure that you are on the
Configurations page.
__2.
Hover the mouse pointer over the Miniloan Deployment configuration name and click the
Edit icon
__3.
Go to Targets tab, check Production and Test Environment, Save and Create New Version.
__4.
Hover the mouse pointer over the Miniloan Deployment configuration name and click the
Deploy icon.
__5.
Make sure that Test Environment and Production Environment are checked under Servers.
Page 95
ODM on Cloud PoT
IBM Software
__6.
Click Deploy.
__7.
In the Deployment status window, click OK.
A check symbol should appear when the deployment is completed.
2.3.5
Test the deployed the rules
__1.
Switch to the Miniloan Web Application in a browser at the URL that was provided to you for
this session. For example:
http://miniloan-cloud.mybluemix.net
__2.
Set the following values, making sure the environment is set to Test or Production.

Server Hostname: <vhostname>.bpm.ibmcloud.com
Where <vhostname> is the host name for your cloud instance.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
__3.

Ruleset Path: /Miniloan_Deployment/your user name_operation

User ID: <your username>

User Password: <your password>

Select environment: Test or Production
Click Validate Loan.
The result is same as the development environment. The loan is Approved.
Page 97
ODM on Cloud PoT
IBM Software
2.4
Summary
In this lab, you used Decision Center to perform the following business analyst tasks:

Review and run a test suite

Review and run a simulation

Change the rules and analyzed the impact with the test suite and the simulation report

Deploy the new version of the rules

Promote the rules to Production Environment
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Appendix A. Notices
This information was developed for products and services offered in the U.S.A.
IBM may not offer the products, services, or features discussed in this document in other countries.
Consult your local IBM representative for information on the products and services currently available in
your area. Any reference to an IBM product, program, or service is not intended to state or imply that
only that IBM product, program, or service may be used. Any functionally equivalent product, program, or
service that does not infringe any IBM intellectual property right may be used instead. However, it is the
user's responsibility to evaluate and verify the operation of any non-IBM product, program, or service.
IBM may have patents or pending patent applications covering subject matter described in this
document. The furnishing of this document does not grant you any license to these patents. You can
send license inquiries, in writing, to:
IBM Director of Licensing
IBM Corporation
North Castle Drive
Armonk, NY 10504-1785
U.S.A.
For license inquiries regarding double-byte (DBCS) information, contact the IBM Intellectual Property
Department in your country or send inquiries, in writing, to:
IBM World Trade Asia Corporation
Licensing
2-31 Roppongi 3-chome, Minato-ku
Tokyo 106-0032, Japan
The following paragraph does not apply to the United Kingdom or any other country where such
provisions are inconsistent with local law: INTERNATIONAL BUSINESS MACHINES
CORPORATION PROVIDES THIS PUBLICATION "AS IS" WITHOUT WARRANTY OF ANY KIND,
EITHER EXPRESS OR IMPLIED, INCLUDING, BUT NOT LIMITED TO, THE IMPLIED WARRANTIES
OF NON-INFRINGEMENT, MERCHANTABILITY OR FITNESS FOR A PARTICULAR PURPOSE. Some
states do not allow disclaimer of express or implied warranties in certain transactions, therefore, this
statement may not apply to you.
This information could include technical inaccuracies or typographical errors. Changes are periodically
made to the information herein; these changes will be incorporated in new editions of the publication.
IBM may make improvements and/or changes in the product(s) and/or the program(s) described in this
publication at any time without notice.
Any references in this information to non-IBM Web sites are provided for convenience only and do not in
any manner serve as an endorsement of those Web sites. The materials at those Web sites are not part
of the materials for this IBM product and use of those Web sites is at your own risk.
IBM may use or distribute any of the information you supply in any way it believes appropriate without
incurring any obligation to you.
Any performance data contained herein was determined in a controlled environment. Therefore, the
results obtained in other operating environments may vary significantly. Some measurements may have
Page 99
ODM on Cloud PoT
IBM Software
been made on development-level systems and there is no guarantee that these measurements will be
the same on generally available systems. Furthermore, some measurements may have been estimated
through extrapolation. Actual results may vary. Users of this document should verify the applicable data
for their specific environment.
Information concerning non-IBM products was obtained from the suppliers of those products, their
published announcements or other publicly available sources. IBM has not tested those products and
cannot confirm the accuracy of performance, compatibility or any other claims related to non-IBM
products. Questions on the capabilities of non-IBM products should be addressed to the suppliers of
those products.
All statements regarding IBM's future direction and intent are subject to change or withdrawal without
notice, and represent goals and objectives only.
This information contains examples of data and reports used in daily business operations. To illustrate
them as completely as possible, the examples include the names of individuals, companies, brands, and
products. All of these names are fictitious and any similarity to the names and addresses used by an
actual business enterprise is entirely coincidental. All references to fictitious companies or individuals are
used for illustration purposes only.
COPYRIGHT LICENSE:
This information contains sample application programs in source language, which illustrate programming
techniques on various operating platforms. You may copy, modify, and distribute these sample programs
in any form without payment to IBM, for the purposes of developing, using, marketing or distributing
application programs conforming to the application programming interface for the operating platform for
which the sample programs are written. These examples have not been thoroughly tested under all
conditions. IBM, therefore, cannot guarantee or imply reliability, serviceability, or function of these
programs.
© Copyright IBM Corporation, 2017
US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corp.
IBM Software
Appendix B. Trademarks and copyrights
The following terms are trademarks of International Business Machines Corporation in the United States,
other countries, or both:
IBM
AIX
CICS
ClearCase
ClearQuest
Cloudscape
Cube Views
DB2
developerWorks
DRDA
IMS
IMS/ESA
Informix
Lotus
Lotus Workflow
MQSeries
OmniFind
ILOG
Rational
Redbooks
Red Brick
RequisitePro
System i
System z
Tivoli
WebSphere
Workplace
System p
Adobe, Acrobat, Portable Document Format (PDF), and PostScript are either registered trademarks or
trademarks of Adobe Systems Incorporated in the United States, other countries, or both.
Cell Broadband Engine is a trademark of Sony Computer Entertainment, Inc. in the United States, other
countries, or both and is used under license therefrom.
Java and all Java-based trademarks and logos are trademarks of Sun Microsystems, Inc. in the United
States, other countries, or both. See Java Guidelines
Microsoft, Windows, Windows NT, and the Windows logo are registered trademarks of Microsoft
Corporation in the United States, other countries, or both.
Intel, Intel logo, Intel Inside, Intel Inside logo, Intel Centrino, Intel Centrino logo, 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.
UNIX is a registered trademark of The Open Group in the United States and other countries.
Linux is a registered trademark of Linus Torvalds in the United States, other countries, or both.
ITIL is a registered trademark and a registered community trademark of the Office of Government
Commerce, and is registered in the U.S. Patent and Trademark Office.
IT Infrastructure Library is a registered trademark of the Central Computer and Telecommunications
Agency which is now part of the Office of Government Commerce.
Other company, product and service names may be trademarks or service marks of others.
Page 101
ODM on Cloud PoT
NOTES
NOTES
© Copyright IBM Corporation 2016.
The information contained in these materials is provided for
informational purposes only, and is provided AS IS without warranty
of any kind, express or implied. IBM shall not be responsible for any
damages arising out of the use of, or otherwise related to, these
materials. Nothing contained in these materials 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 these materials to IBM products,
programs, or services do not imply that they will be available in all
countries in which IBM operates. This information is based on
current IBM product plans and strategy, which are subject to change
by IBM without notice. Product release dates and/or capabilities
referenced in these materials 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.
IBM, the IBM logo and ibm.com are trademarks or registered
trademarks of International Business Machines Corporation in the
United States, other countries, or both. If these and other IBM
trademarked terms are marked on their first occurrence in this
information with a trademark symbol (® or ™), these symbols
indicate U.S. registered or common law trademarks owned by IBM at
the time this information was published. Such trademarks may also be
registered or common law trademarks in other countries. A current
list of IBM trademarks is available on the Web at “Copyright and
trademark information” at ibm.com/legal/copytrade.shtml
Other company, product and service names may be trademarks or
service marks of others.
Download PDF
Similar pages