Skip to content

IBM Operational Decision Manager (ODM) Source Config - Settings

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).

NameTypeDescription
Data SourceStringJDBC name of the datasource. (ex. jdbc/ilogDataSource)
Decision Center URLStringHostname and Port number for the IBM Decision Server instance. (ex. http://example.server.com:8080)
Extensions of Files to ConvertStringA list, separated by commas, of extensions that specify files which must be converted to a new Character set when downloaded.
Jrules Jar PathStringPath 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 NumberIntegerSpecify the version number for the next version. This value increments automatically after each Version import.
PasswordStringDecision Center password.
Preserve Execute PermissionsBooleanWhen enabled, file execute permissions are saved with files.
RuleApp NameStringThe name of the ruleApp to be imported.
UsernameStringDecision Center username.
Version Name PatternStringSpecify a pattern for each version name.For example, the ibm-ucd pattern produces versions such as ibm-ucd-1, ibm-ucd-2, and so on, based on the Next Version Number.

Import New Version

The following settings are available when you import component versions.

NameTypeDescription
ODM SnapshotStringName 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)

NameTypeDescription
Branch NameStringThe name of the Branch (ex. Spring Release). Pulls from main if left blank.
Data SourceStringJDBC name of the datasource. (ex. jdbc/ilogDataSource)
Decision Center URLStringHostname and Port number for the IBM Decision Server instance. (ex. http://example.server.com:8080)
Deployment ConfigurationStringThe name of the deployment configuration. (ex. test deployment)
Extensions of Files to ConvertStringA list, separated by commas, of extensions that specify files which must be converted to a new Character set when downloaded.
Jrules Jar PathStringPath 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 NumberIntegerSpecify the version number for the next version. This value increments automatically after each Version import.
PasswordStringDecision Center password.
Preserve Execute PermissionsBooleanWhen enabled, file execute permissions are saved with files.
Project NameStringThe name of the Project. (ex. Loan Validation Service)
RuleApp Archive NameStringThe name to give the ruleApp archive file. Note that .jar will be automatically appended to the end.
Target ServerStringThe name of the Target Server to deploy to. Leave blank to only extract the archive and skip deployment.
UsernameStringDecision Center username.
Version Name PatternStringSpecify a pattern for each version name.For example, the ibm-ucd pattern produces versions such as ibm-ucd-1, ibm-ucd-2, and so on, based on the Next Version Number.

Import New Version

The following settings are available when you import component versions.

NameTypeDescription
ODM SnapshotStringName of an existing ODM snapshot to pull archive from. This will create a version with this name, overriding the next version numbering scheme.