ODM on Cloud
IBM Operational Decision Manager (ODM) on Cloud is IBM’s software as a service (SaaS) offering that provides decision service development and governance capabilities in the
cloud platform.
IBM ODM on Cloud offers a subset of the capabilities of the full ODM product, but for many organizations these capabilities enable them to start using the technology quickly and is sufficient for their needs. It includes the following functionality:
Rule Designer to build your projects
A Decision Center environment for developing and deploying decisions
Three environments for deployment:
 – Development
 – Test
 – Production
It enables your developers to create the project structures for your decision services, and your business users to create and test rules. In IBM ODM on Cloud, you can use either the decision governance framework or the manual branching capabilities of the product.
This chapter covers the following topics:
10.1 Considerations
From a Governance point of view, there are a few considerations that users should be
aware of:
Only decision services are supported (no support for Classic Rule projects).
Classic Rule Engine is not available, so there is no Decision Validation Service (DVS).
No Java API or Ant scripts are available. Only the Rule Execution Server REST API is available for DevOps deployment operations.
There are other considerations, which can be found in the documentation but which have little (or nothing) to do with Governance as covered in this book.
10.2 IBM ODM components
Developing a project for the cloud involves the following three components:
Rule Designer A rich client tool that you download from the cloud development environment. Rule Designer is the main tool that is used by a rule developer to build the model and technical artifacts that are required for authoring and running a decision service.
Rule Designer includes a local capability for running rules and setting up a solution before it is published to the development environment in the cloud. From Rule Designer, you can deploy to the development environment on the cloud, but not to the test and production environments. Rule Designer is the first tool in the lifecycle of a decision service.
Decision Center A collaborative web tool and repository in the cloud, Decision Center is part of the development environment. It is used in the authoring and governance of decision services by a team that is led by a release manager. Decision Center includes the Business Console for all regular authoring, testing, governance, and deployment activities, and the Enterprise Console for occasional administrative and advanced activities.
Rule Execution Server The runtime component that runs decision services and makes them available as web services to external applications, processes, or services. Each environment has its own isolated instance of Rule Execution Server. During its initial development, a decision service can be deployed from Rule Designer to the Rule Execution Server in the development environment.
However, the decision service cannot be deployed from Rule Designer to the Rule Execution Server in the test environment or in the production environment. Instead, Decision Center provides a governance framework and strong tracing capabilities to control the deployment of decision services in the different environments: First in development, then in test, and finally in production.
10.3 User roles
IBM ODM on Cloud has a slightly simplified set of user roles, shown in Table 10-1 and Table 10-2 on page 138.
Table 10-1 Business roles in IBM ODM on Cloud governance
 
Governance role
Responsibilities
Also known as
Release Manager
Works primarily in the Business Console component:
Orchestrates the lifecycle of a decision service, and is ultimately responsible for the deployment of a decision service release to production.
Follows a staged progression from development to test and production:
 – Creates development branches or releases
 – Defines change and validation activities for rule developers, business users, and integrators
 – Assigns ownership of work, reviews, and approvals
With author rights, the person in this role can create deployment configurations in the Business Console for the development, test, and production environments.
 
Business User
Works primarily in the Business Console component:
Implements and maintains some or all of the business rule artifacts that are in a decision service.
Runs functional tests and simulations in the development environment to validate the changes that are made for a release.
Can deploy a decision service to the test environment to validate changes in a test application. Can also deploy to the development environment.
Can participate in the review or approval process for other business-user or integrator activities.
Business Policy Architect
Rule Analyst
Rule Architect
Business Policy Analyst
Rule Author
Rule Writer
Business Rule Author
Rule Validator
Business Analyst
Integrator
Uses the Business Console component in addition to other development, integration, and test tools:
Builds the applications that call a decision service in the development, test, and production environments.
Can be involved in the validation activities that are defined by the release manager.
Can deploy decision services to the development and test environments.
Can view and use the decision services that are deployed in the production environment.
 
Permission manager
Works primarily in Business Console:
Implements the security policy on decision services.
Creates groups, sets the permissions, adds users to the groups, and sets the groups on decision services.
Can create deployment configurations in the Business Console for the development, test, and production environments.
Can deploy decision services in all environments.
The permission manager can take on all the ODM roles, for example, when the team is small.
 
Table 10-2 Technical Roles in ODM governance
 
Governance role
Responsibilities
Also known as
Cloud Administrator
This role manages users and assigns roles in the IBM ODM on Cloud portal:
There must be at least one administrator in an IBM ODM on Cloud subscription.
Only another administrator can remove an administrator.
Most users do not have a cloud administration role.
 
Rule Developer
This role performs the following functions:
Designs the structure of the implementation to support the design requirements and evolution of the decision services.
Develops technical functionality to support authoring (XOM and utility functions).
Formalizes the business terminology (vocabulary) used in Operational Decision Manager.
Makes the initial version of the business rule artifacts, including textual rules, decision tables, and ruleflows.
Runs the decision service locally or in the cloud development environment until adequate results are achieved.
Publishes the decision service from Rule Designer to Decision Center.
Collaborates with the release manager and business users in authoring and governance activities.
Collaborates with the integrator to integrate the decision service into an application.
Creates deployment configurations in Rule Designer for the execution environments.
 
10.4 Cloud environments
IBM ODM on Cloud provides the following environments on the cloud to support a staged progression from development to production.
Access to these environments is controlled, and depends on the role of the user and the criticality of the environment.
Development environment
Users:
Rule developers (in Rule Designer for ODM on Cloud)
Release managers
Business users
Integrators
Permission managers
Includes:
Decision Center
Development Rule Execution Server
Rule Designer for ODM on Cloud
Used for:
Collaborating on the development and lifecycle of a decision service
Running decision services in development activities
Performing functional tests and simulations that are run from Decision Center
Testing a development application that calls a decision service that is still in development
 
Note: Although the Decision Center instance is in a Development environment, the service level agreement for ODM on Cloud makes it the right location for the purposes of architecture. FixPacks, and so on, are handled by the ODM on Cloud Software as a Service and you do not need a Test instance for Decision Center in this case.
Test environment
Users:
Business users
Integrators
Includes:
Test Rule Execution Server
Used for:
Testing a decision service during or after its development, and within the governance framework that is defined by the release manager:
 – Performance tests
 – System tests
 – Integration tests
 – Other user acceptance tests
Production environment
Users:
Release managers
Includes:
Production Rule Execution Server
Used for:
Running the decision services in Production
10.5 Workflow
Figure 10-1illustrates how the user roles in IBM ODM on Cloud interact with the product components during the lifecycle of a business rules application:
1. Rule development
2. Validation
3. Testing
4. Promotion of the release in the cloud production environment
Figure 10-1 ODM on Cloud Workflow Diagram
10.5.1 Setting up the user roles
The first person to access the IBM ODM on Cloud product is the Cloud Administrator. This person might not use ODM, but must invite the appropriate people and assign them roles.
10.5.2 Collaborating to develop the decision service
The rule developer uses Rule Designer to write and edit rules, deploy the decision service to the development environment, and publish the decision service in Decision Center. This person is competent in Java and understands the company object model and works with the software architects to develop the first version of the decision service. They define the vocabulary and write the business rules that model business logic. The rule developer publishes the initial version of the decision service to Decision Center.
The release manager then creates an additional release with change activities by using the decision governance framework in the Decision Center console. They set up change activities and validation activities in Decision Center. When the team has completed the validation activities, and the rules are ready to test in the development environment, they deploy the completed release to the Rule Execution Server.
The business user views and edits the rules through the Business Console. The work is tracked as a change activity that records the modifications that are made to the rules. The business users can also perform some tests using the testing framework and the Excel spreadsheets.
The permission manager enables security and user access settings in the console to make sure that the business user, and other users who need access to the release and activity branches in the decision service, are assigned to the correct user groups.
10.5.3 Testing and promoting the decision service
The release manager has access to all of the cloud environments so that they can perform testing throughout the development lifecycle of the decision service. For example, when the team is satisfied with the behavior of the decision service in the development environment, they start the next step in the workflow by deploying the most recent decision service release to the test environment.
The integrator tests and validates that the decision service is running as expected by working in the Business Console and in all of the cloud environments. They monitor and evaluate the function of the decision service when it is called from a client application. To run the tests, they add some code to the application so that it calls the new pricing decision service that was developed in IBM ODM on Cloud. The client application runs on an external application server and calls the decision service running in the IBM Cloud test environment.
The release manager evaluates the performance of the decision service in the test environment before deploying it to production. He works with the Integrator to run benchmarks using standard software development validation procedures.
When the development is complete and the Release Manager is satisfied with the benchmark results, they promote the decision service to the Rule Execution Server in the production environment. The release manager is the only user role that has access rights to deploy a decision service to production.
10.6 IBM ODM on Cloud in a hybrid cloud environment
The concept of hybrid cloud designates the connection of one or more clouds to on-premises systems or to other clouds.
A hybrid cloud environment combines technologies that run simultaneously and complement each other on traditional corporate on-premises systems and on the cloud. Hybrid cloud provides flexible allocation of systems while maintaining high levels of security, availability, and performance.
IBM ODM on Cloud supports hybrid cloud environments by allowing deployment to Operational Decision Manager Rule Execution Servers with compatible versions that are hosted outside of the IBM ODM on Cloud environment. For example, deployment can take place on an enterprise on-premises system, in a private cloud, or on IBM Bluemix®.
10.7 Conclusion
The IBM ODM on Cloud provides an environment that organizations can use to quickly get started with the ODM technology. It provides most of the functionalities you would have with an on-premises installation of ODM, and has a built-in Governance Framework that prescribes a workflow for your decision governance. In this chapter, we described some of the main elements that are important to know for ODM on Cloud.
Limitations:
Only decision services are supported (no support for Classic Rule Projects).
Classic Rule Engine is not available, so no Decision Validation Service (DVS).
No Java API or Ant scripts, which might limit some DevOps operations.
ODM on Cloud uses a simplified set of pre-defined roles and includes a new one for Cloud Administration.
The execution environments are preset to:
Development
Test
Production
It is possible to use ODM on Cloud in a hybrid cloud environment.
..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset
52.14.1.136