The following is intended to describe how to configure Oracle Web Determinations, describing the functions of each of the configuration properties, as well as common configuration patterns. The configuration file is typically located in the following directory:
WEB-INF\classes\configuration\config.properties
If you make any changes to the config.properties file, be sure to restart your application server, because the configuration is cached.
Note: UTF-8 encoding should always be used.
Classpath-based loading (Java only)The following is an example of the config.properties file, configuring the Oracle Policy Automation Web Determinations component to load everything from the classpath.
It is assumed that the resources are placed into folders called configuration, images, properties, resources, rulebases and templates under the WEB-INF/classes folder in the web application's deployment folder.
Note: This would work for both an exploded and unexploded WAR deployment.
#########################################
# Deployment Properties
# Screen template to use for the question screen
screen.template =question_screen.vm
# Debug or Release
release.context =DEBUG
# The locale to default to if we're displaying a screen that is not attached to a specific locale.
default.locale =en-US#########################################
# Rulebase Loading Properties# Load rulebases as resource streams, as opposed to loading them
# from the file system.
load.rulebase.as.resource =true# If rulebases are to be loaded as resource streams, this
# property specified whether or not the Java classpath
# is to be used to load the resources.
load.rulebase.from.classpath =truerulebase.path =rulebases
cache.loaded.rulebases =false#########################################
# Resourcing Properties
load.messages.as.resource =true
messages.path =configuration
cache.messages =falseload.images.as.resource =true
images.path =images
cache.images =falseload.resource.as.resource =true
resources.path =resourcesload.properties.as.resource =true
properties.path =properties
cache.properties =falseload.templates.as.resource =true
templates.path =templates
cache.templates =false#########################################
# Plugins Properties
plugin.libraries=
File System-based loading (Java and .NET)The following is an example of the config.properties file, configuring the Oracle Policy Automation Web Determinations component to load everything from the file system.
It is assumed that you are running the Java version of the application and that the resources are placed into folders called configuration, images, properties, resources, rulebases and templates under the WEB-INF/classes folder in the web application's deployment folder.
Notes:
- The following example will not work under Java for application servers that do not explode the WAR (for example, WebLogic) - the only option in such casesis to use classpath-based resource loading.
- Under .NET, the paths to the resources must be changed to the relative paths under the application's directory (for example, 'bin/rulebases', 'bin/configuration' and so on).
- The cache.loaded.rulebases=false property, combined with the fact that we are loading the rulebases from the file system, will cause a directory watcher to be invoked on the rulebases directory. This allows rulebases to be dynamically loaded, removed and updated as the contents of the rulebases directory changes.
#########################################
# Deployment Properties
# Screen template to use for the question screen
screen.template =question_screen.vm
# Debug or Release
release.context =DEBUG
# The locale to default to if we're displaying a screen that is not attached to a specific locale.
default.locale =en-US#########################################
# Rulebase Loading Properties# Load rulebases as resource streams, as opposed to loading them
# from the file system.
load.rulebase.as.resource =false# If rulebases are to be loaded as resource streams, this
# property specified whether or not the Java classpath
# is to be used to load the resources.
load.rulebase.from.classpath =falserulebase.path =/WEB-INF/classes/rulebases
cache.loaded.rulebases =false#########################################
# Resourcing Properties
load.messages.as.resource =false
messages.path =WEB-INF/classes/configuration
cache.messages =falseload.images.as.resource =false
images.path =WEB-INF/classes/images
cache.images =falseload.resource.as.resource =false
resources.path =WEB-INF/classes/resourcesload.properties.as.resource =false
properties.path =WEB-INF/classes/properties
cache.properties =falseload.templates.as.resource =false
templates.path =WEB-INF/classes/templates
cache.templates =false#########################################
# Plugins Properties
plugin.libraries=
Before you commence any configuration of Web Determinations, it is important to note that an application will not function properly if the date, time, or date/time value, as formatted according to the output format, cannot be understood according to the input format.
On Java, this means that the configured output format must match one of the configured input formats, and if one of the input formats might possibly be ambiguous the version matching the output format must come first.
On .NET, this means that the output format must be a legal and unambiguous format according to Microsoft's .NET runtime library. (We don't configure input formats on .NET.)
If you do not do this, dates will not be correctly understood and could result in a fatal error.