Initializing help system before first use

Mosel Execution

Users can submit a compute job in several ways:
  • The Optimizer Console, Optimizer libraries, Mosel, and Xpress Workbench can be configured to transparently out-source optimization processing to a remote Insight Server.
  • Solver jobs can be submitted via the Compute Interface app's user interface.
  • Solver and Mosel jobs can be sent as requests to the web services REST API.
Computational effort for these jobs is offloaded; Insight submits the model to be optimized by Xpress installed on one or more execution workers.

Worker application.properties file

The worker application.properties file is configured with the default options for Mosel. 
# -----------------------------------------------------------------------------
# FICO® Xpress Insight Execution Worker configuration file
# -----------------------------------------------------------------------------
…
#------------------------------------------------------------------------------
# Mosel configuration
#------------------------------------------------------------------------------
#insight.worker.execution.environment.MOSEL_RESTR=NoExecWDOnly
#insight.worker.execution.environment.MOSJVM_ALLOW=*
#insight.worker.execution.environment.MOSEL_RWPATH=
#insight.worker.execution.environment.MOSEL_EXECPATH=
#insight.worker.execution.environment.MOSEL_SSL=${XPRESSDIR}/ssl
#insight.worker.execution.environment.MOSEL_ROPATH=${XPRESSDIR}/dso/mmsvg.tgz
#insight.worker.execution.environment.XPRESSDIR=${XPRESSDIR}
#insight.worker.execution.environment.XPAUTH_PATH=${XPAUTH_PATH}
When submitting the model, Xpress Insight 5 will only pass to Xpress those environment variables defined in the worker application.properties file to be used during execution. Some values required by Xpress at a system level are taken directly from the environment variables. These include:
  • XPRESSDIR
  • LANG
  • LD_LIBRARY_PATH
  • XPAUTH_PATH
These can also be configured in the application.properties file if the environment variables have been set incorrectly. The property and value pairings are completely configurable. For example, you can add any property name to the application.properties file and assign a value. 
insight.worker.execution.environment.some_property_name=some_value
Note Changes made to this file will not be applied until the worker has been restarted.

Overriding Mosel Environment Variables

Environment variables can be defined in a Mosel model using the following format, where ENVNAME is the environment variable name and val is the value to pass to Xpress: 
insight.worker.execution.environment.ENVNAME=val
System variables can be updated using an absolute path to the file on the local drive: 
insight.worker.execution.environment.XPRESSDIR=C:/newXpressDir
The configured environment variable can be passed from the worker through to Xpress using the following format: 
insight.worker.execution.environment.ENVVARNAME=${ENVVARNAME}
It is possible to configure a custom variable by declaring it using the following format: 
insight.worker.execution.environment.CUSTVARNAME=customVariable

Setting Mosel Restricted Mode (MOSEL_RESTR)

The value assigned to the parameter MOSEL_RESTR determines the actions an executing model is allowed to perform, such as file I/O and shell commands. The default settings has no restrictions.

Computational effort for jobs offloaded to one or more execution workers which apply the configured setting for MOSEL_RESTR from the environment. If it is not set then it will default it to the value NoExecWDOnly.

In addition, any of the following security related environment variables that are not explicitly set in the environment default to an empty string.
  • MOSJVM_ALLOW: *
  • MOSEL_RWPATH:
  • MOSEL_EXECPATH
  • MOSEL_SSL: XPRESSDIR/ssl
  • MOSEL_ROPATH: XPRESSDIR/do/mmsvg.tgz

For more on the Mosel restricted mode, see Use in Mosel Restricted Mode.

Parent Topic Insight 5 Installation Guide