Configuration for custom functions and formatters is done via the Oracle Determinations Engine configuration file. This is a properties file, which can be created using a text editor such as notepad.
In order for the engine to use this file, it must be located in the same directory as the rulebase to which it applies and have the name <rulebase>-config.properties.
A rulebase properties configuration that configures both a custom function and a custom formatter will look something like:
custom-function.java.library-path = TestCustomFunction.jar
custom-function.java.class = oracle.testrulebase.TestCustomFunctionformatter.java.library-path = basic-formatter.jar
formatter.java.class = oracle.test.TestFormatter
All property names follow the pattern <object>.<platform>.<setting> where:
object
Specifies which object this configuration property is for. The valid values are:
- custom-function – specifies that the property configures the active custom function.
- formatter – specifies that the property configures the active custom formatter.
platform
Specifies which platform this configuration this custom component is written for. The valid values are:
- java – specifies that the property is to be used with the Oracle Determinations Engine for Java.
- dotnet – specifies that the property is to be used with the Oracle Determinations Engine for .NET.
setting
Specifies which setting this configuration property is for. The valid values are:
- library-path – Specified the location of the library which implements the custom component and its dependencies. The library path can either be absolute or relative to the location of the configuration file. Multiple libraries can be specified as a ‘;’ list and will be loaded in the order in which they are specified.
- class – The class (including the package or namespace) which implements either the CustomFunctionHandler interface for custom functions, or the Formatter interface for custom formatters.