Built-in ruleset properties

You can use built-in ruleset properties to stock deployment or execution information for a particular ruleset.

The following tables provide the list of built-in ruleset properties. They can be selected and defined in a deployment configuration in Rule Designer, or in a ruleset in the Rule Execution Server console.

Table 1. Built-in ruleset properties
Name Valid values Default value Description
ilog.rules.teamserver.baseline A string from Decision Center   This property contains the Decision Center baseline name if the ruleset is deployed from a classic rule project in the Decision Center Enterprise console.
ilog.rules.teamserver.permalink.project A URL as a string   This property contains the URL to access to the Decision Center project that contains the deployed rules of a classic rule project.
ilog.rules.teamserver.permalink.report A URL as a string   This property contains the URL to access the Decision Center report.
decisioncenter.url A URL   The URL of the Decision Center server from which the deployment was done.
decisioncenter.version A string   The version of the product that was used to generate the ruleset, for example, Decision Center X.X.X.X.
decisionservice.name A string   The name of the decision service that was deployed, for example, loanvalidation-rules-service.
decisionservice.id A string   The ID of the root project of the decision service that was deployed, for example, brm.RuleProject:44:44.
decisionservice.branch.name A string   The name of the deployment snapshot if the user chose to create one, the branch, or the snapshot in the decision service that was deployed, for example, b or d-20150231-158621.
decisionservice.branch.id A string   The ID of the deployment snapshot, branch, or snapshot in the decision service that was deployed, for example, brm.Branch:224:224.
decisionservice.branch.url A URL   A link to a page in the Decision Center Business console that displays the deployed branch or snapshot.
decisionservice.deploymentConfiguration.name A string   The name of the deployment configuration that was deployed, for example, d.
decisionservice.deploymentConfiguration.id A string   The ID of the deployment configuration that was deployed, for example, dsm.Deployment:3:3.
decisionservice.deployer.name A string   The display name of the Decision Center user who did the deployment.
decisionservice.deployer.id A string   The login name of the Decision Center user who did the deployment.
ilog.console.wsdl.endpoint A URL as a string   Use this property to override the default HTDS option for the web service endpoint.
ilog.console.htds.context A URL as a string   Use this property to override the default HTDS option for the location.
New in 8.10.5 ruleset.decisionEngine.maxRunningTime Only positive, non-decimal numbers should be used.   This ruleset property is used to set the amount of time that a ruleset can run. The time is given in seconds. The property works in the decision engine, but it does not work in the classic rule engine.
ruleset.managedxom.uris

A comma-separated list of URIs. For example:

resuri://common-classes.jar/1.0,resuri://LoanValidation.jar

No default value

This ruleset property controls Java™ XOM management. It locates the Java XOM resources for the ruleset.

  • If you do not set this property and the ruleset uses a Java XOM, the Java classes are loaded by the application class loader.
  • If you set this property (as a list of URIs) for a ruleset, the execution unit (XU) creates and stores a dedicated class loader for the execution of the ruleset. Each URI must target a Java Archive .jar file or a .zip archive of classes and resources for Java execution.

Only internal URIs are supported: resuri and reslib protocol
ruleset.maxIdleTime

Three possible values:

  • -1 or undefined: the ruleset is removed from the cache, depending on its usage by the JCA Connection Pool.
  • =>0: the ruleset is removed from the cache after the timeout (in seconds) is reached and no SPI connections reference it any more.
  • 0: the ruleset is never removed from the cache except if the ruleset is redeployed.
 

This property enforces the ruleset pool policy on a ruleset. A ruleset stays in memory until the maximum idle time (in seconds) has reached the specified value set for this property. To avoid ruleset reparsing, you can use the special value of 0 to ensure that the ruleset is never released from memory.

Important: Use the 0 value with caution as it might introduce a significant memory leak if the ruleset is not used any more.
ruleset.trace.enabled true, false   This property enables or disables the rule engine trace mode.
ruleset.xmlDocumentDriverPool.maxSize >=0 1

The 0 value means that an XMLDocumentDriver instance is created for each XMLObject transformation.

Use a strictly positive value to specify the maximum size of the IlrXMLDocumentDriver pool, that is, the maximum number of used and unused IlrXMLDocumentDriver objects per ruleset.
ruleset.xmlDocumentDriverPool.reserveTimeout >=0   This property specifies the number of milliseconds after which the call to reserve an IlrXMLDocumentDriver instance times out.
wsdl.paramtargetnamespace A URL as a string   Use this property to override the default HTDS options for the parameter target namespace.
Note: This parameter can be used for both WSDL and WADL code generation, although wsdl is used as part of the parameter name. You cannot change wsdl to wadl in the parameter name even when this parameter is used for the WADL code generation.
wsdl.targetnamespace A URL as a string   Use this property to override the default HTDS option for the target namespace.