Initializing help system before first use

Configuring the Execution Environment

The application.properties file for the Insight worker controls the environment that the scenario model is executed in. The execution environment does not inherit the environment of the server that the worker is installed on. Only the variables that are mandatory for the Xpress runtime software are propagated through to the execution environment:
  • XPRESSDIR
  • LANG
  • LD_LIBRARY_PATH
  • XPAUTH_PATH
  • XPRESS_INSIGHT_LIB

Additional variables can be defined in the application.properties file of the worker, and the above variables can be redefined if necessary.

Note: Changes made to this file will not be applied until the worker has been restarted.
Important: This is a java properties file which uses the backslash character to indicate an escape sequence. Paths stored in this file that use this character must be edited to ensure this is ignored. For example, C:\ProgramData\FICO\XpressInsight becomes C:\\ProgramData\\FICO\\XpressInsight

Default execution environment

Environment variables can be defined using the following format, where ENVNAME is the environment variable name and val is the value to pass to the executing scenario:

insight.worker.execution.environment.ENVNAME=val

The existing value of a variable in the global environment of the system that the worker is running on, can be referenced using the format below:

insight.worker.execution.environment.ENVVARNAME=${ENVVARNAME}
The value of a variable defined earlier in the file can be referenced with the fully qualified variable name e.g.
insight.worker.execution.environment.ENVVARNAME2=${ insight.worker.execution.environment.ENVVARNAME}
These environment variables will be applied to scenario executions from all apps.

App-specific execution environment

Environment variables can be defined using the following format, where CUSTOM_ENVIRONMENT_1 is a namespace for the set of environment variables defined (ENVNAME, ENVNAME1 in the examples below):

Insight.worker.execution.custom-environment.CUSTOM_ENVIRONMENT_1.ENVNAME=val
insight.worker.execution.custom-environment.CUSTOM_ENVIRONMENT_1.ENVNAME1=val

The Execution Environment Mappings page in the ADMIN view allows this namespace to be mapped to one or more apps.

Note: The app-specific environment overlays the default environment. Any variables defined in the app-specific namespace will overwrite variables of the same name in the shared environment.

© 2001-2024 Fair Isaac Corporation. All rights reserved. This documentation is the property of Fair Isaac Corporation (“FICO”). Receipt or possession of this documentation does not convey rights to disclose, reproduce, make derivative works, use, or allow others to use it except solely for internal evaluation purposes to determine whether to purchase a license to the software described in this documentation, or as otherwise set forth in a written software license agreement between you and FICO (or a FICO affiliate). Use of this documentation and the software described in it must conform strictly to the foregoing permitted uses, and no other use is permitted.