• Overview
  • Documentation
  • Version history

Description

The IBM Operational Decision Manager (ODM) source configuration plug-in supports the following authentication:

  • Basic Authentication using username and password
  • oAuth Authentication

The IBM Operational Decision Manager (ODM) source configuration plug-in includes steps to complete the following tasks:

  • Import a ruleApp from a Classic Rule Project in IBM Decision Center as a component version (Version 3 and prior)
  • Import a Project archive from Decision Services as a component version (Version 4 and later)

The following steps are an overview of the process to follow:

  • Create a component and set the Source Config type to IBM ODM.
  • Provide all details such as the ODM URL, DataSource, and RuleApp name.
  • Import new versions from IBM ODM for this component.

Quick Info

Product icon

Product

HCL DevOps Deploy (HCL Launch)
Plugin type icon

Type

Plug-in
Compatibility icon

Compatibility

HCL Launch version 7.3.2.8 and later, HCL Deploy version 8.0.1.3 and later
created by icon

Created by

HCLSoftware

Published Date

Last Updated

Summary

The IBM Operational Decision Manager source configuration plug-in supports creating component versions from Decision Center RuleApps. It supports two types of authentication Basic Authentication and oAuth Authentication.

Compatibility

Version 10+: IBM Operational Decision Manager 8.9.1 or later

Installation

See Installing plugins in HCL Deploy for installing and removing plugins.

ODM version 8.9.1 introduces a REST API which is used by version 10 of this plug-in. For older ODM versions which do not offer the REST API, several jars from the ODM server must be made available to the plug-in for the plugin steps to run properly. The jars are listed below and can be found in the following location on the ODM server in the directory: ODMSERVERLOCATION/teamserver/lib. The jars must either be copied to the Deploy agents’ lib directory or specified in the Jar Path of the plug-in configuration. The plugin requires the following ODM jars:

  • jrules-engine.jar
  • jrules-language.jar
  • jrules-ruleartifacts.jar
  • jrules-teamserver.jar
  • jrules-dataaccess-rs4j.jar
  • jrules-model-dataaccess.jar
  • jrules-synchronization.jar
  • wbemodel.jar

History

Version Description
15 DVOPS-I-751 - Added capability to fetch artifacts from nested branch.
14 Fixed issue to support both oauth and basic auth.
13 RFE - URBANCODE-I-395 - Implement oAuth .
12 Fixing CVE:CVE-2019-4233.
11 APAR PI89045: add support for setting isFinished flag flag when importing versions.
10 Fixes APAR PI81075 - ODM SOURCE CONFIG PLUG-IN CREATING UNNECESSARY SNAPSHOTS WHEN REDEPLOYING FROM EXISTING SNAPSHOTS Adds support for the REST API introduced in ODM 8.9.1. Removes unneeded Apache HttpComponents jars added in version 8.
9 Fixes APAR PH00399 - Plugin now only shows warning when Manage Properties permission not set.
8 Fixes APAR PI87707, a regression where the user who requested a manual version import was not being tracked. Fixes APAR PI99599, where the plugin requires a newer version of Apache HttpComponents.
7 Fixes APAR PI87636 - Next Version Number not auto-incrementing is now fixed.
6 Fixes APAR PI85260 - Plug-in no longer throws NullPointerException when auto import is set.
5 Removed need to name Rule App Archive. Updated error catching and logging. Fixes APAR PI79804 - Plugin failing to extract non-deployment snapshots.
4 Added the ability to export RuleApps with Deployment Configurations from Decision Services.
3 Eliminated need for supporting jars when importing RuleApps from ODM Classic Rule Projects.
2 Support property file encryption.
1 Initial Release of plugin to import a RuleApp jar from IBM Decision Center as a component version.

Usage

  1. To create a component by importing from Decision Center, complete the following steps. For more information, see Creating components.
  2. On the Components page in HCL DevOps Deploy, click Create New Component.
  3. In the Source Config Type list, select IBM ODM.
  4. Provide all of the necessary information.
  5. Click Save.
  6. Click the Versions tab for the component.
  7. Click Import New Versions.

Settings

  • Importing from Classic Rule Project
  • Importing from Decision Services

Create a Component importing from an Operational Decision Manager Classic Rule Project

The following settings are available when you create a component by using the IBM ODM Source Config plug-in for importing from Classic Rule App Projects (Version 3 and before).

Name Type Description
Data Source String JDBC name of the datasource. (ex. jdbc/ilogDataSource).
Decision Center URL String Hostname and Port number for the IBM Decision Server instance. (ex. http://example.server.com:8080).
Extensions of Files to Convert String A list, separated by commas, of extensions that specify files which must be converted to a new Character set when downloaded.
Jrules Jar Path String Path to the required ODM jrules jars. This path must be specified if the jars were not copied into the plugin lib directory. (ex. lib/odmJars).
Next Version Number Integer Specify the version number for the next version. This value increments automatically after each Version import.
Password String Decision Center password.
Preserve Execute Permissions Boolean When enabled, file execute permissions are saved with files.
RuleApp Name String The name of the ruleApp to be imported.
Username String Decision Center username.
Version Name Pattern String Specify a pattern for each version name.

Import New Version

The following settings are available when you import component versions:

Property Name Type Description
ODM Snapshot String Name of an existing ODM snapshot to pull archive from. This will create a version with this name, overriding the next version numbering scheme.

Create a Component importing from IBM Decision Services

The following settings are available when you create a component by using the IBM ODM Source Config plug-in for importing from Decision Services (Version 4 and later):

Property Name Type Description
Branch Name String The name of the Branch (ex. Spring Release). Pulls from main if left blank.
Data source String JDBC name of the datasource. (ex. jdbc/ilogDataSource).
Decision Center URL String Hostname and Port number for the IBM Decision Server instance. (ex. http://example.server.com:8080)
Deployment configuration String The name of the deployment configuration. (ex. test deployment)
Extensions of Files to Convert String A list, separated by commas, of extensions that specify files which must be converted to a new Character set when downloaded.
Jrules Jar Path String Path to the required ODM jrules jars. This path must be specified if the jars were not copied into the plugin lib directory. (ex. lib/odmJars)
Next Version Number Integer Specify the version number for the next version. This value increments automatically after each Version import.
Password String Decision Center password.
Preserve Execute Permissions Boolean When enabled, file execute permissions are saved with files.
Project Name String The name of the Project. (ex. Loan Validation Service).
RuleApp Archive Name String The name to give the ruleApp archive file. Note that .jar will be automatically appended to the end.
Target Server String The name of the Target Server to deploy to. Leave blank to only extract the archive and skip deployment.
Username String Decision Center username.
Version Name Pattern String Specify a pattern for each version name.

devops-deploy-ibm-odm-source-config-15.1178699.zip

Uploaded: 19-Jun-2025 09:19

Release Notes

  • DVOPS-I-751 - Added capability to fetch artifacts from nested branch. 

launch-odm-source-config-14.1149407.zip

Uploaded: 06-Jan-2023 04:33

Release Notes

  • Fixed issue to support both oauth and basic auth

launch-odm-source-config-13.1143099.zip

Uploaded: 20-Oct-2022 08:23

Release Notes

  • RFE - URBANCODE-I-395 - Implement oAuth

launch-odm-source-config-12.1100650.zip

Uploaded: 17-Mar-2021 13:21

Release Notes

  • Fixing CVE:CVE-2019-4233

Related Plugins