📄️ Runtime Overrides Config File Settings
Endpoint and Data Element Overrides
📄️ InRule Runtime Config File Settings
Configuration Settings for Common Production Deployment Scenarios
📄️ InRule Logging Config File Settings
Detailed application event information from InRule can be logged to the Windows Application Event Log by configuring the following section in a client config file:
📄️ Rule Application Cache Settings
The first time a Rule Application is requested, it must be compiled so the rules engine can execute the rules. Once a Rule Application is compiled, it is stored in an AppDomain cache for subsequent executions of the application.
📄️ Data Query Cache
The InRule Runtime can cache the results of data queries to reduce latency of querying external data sources that can change infrequently.
📄️ EndPoint Assemblies Folder
.NET assemblies that are referenced from rule applications must be accessible to the rule engine for execution. Referenced assemblies could include static function libraries, bound business objects, and referenced type libraries. InRule will check several locations, in order, to locate any referenced assemblies.
📄️ Execute Query Timeout
Any database query executed using the Execute SQL Query Action has a default timeout of 30 seconds.This timeout can be modified by adding the following to the client configuration file:
📄️ .NET Framework Runtime Config Settings With InRule
The framework runtime settings give you the ability to specify the parameters of the Framework runtime components, such as assembly redirection. Refer to .Net Framework documentation for further information about framework runtime settings, which can be found here.