Software Configuration

Before you begin, ensure that you have the correct version of Xpress for the version of Xpress Insight that you are installing. Xpress Insight 5 uses Xpress v 8.10.

Xpress Insight 5 can be installed in one of two configurations:

1. Development mode or Production mode. Development mode allows local accounts and should only be used while evaluating Xpress Insight or for development. IdP (Identity Provider) integration using the SAML 2.0 standard is available in development mode and FICO recommends using Okta.
2. Production mode should be used for operational installations. It utilizes SAML 2.0 identity verification and disables local accounts. All user administration functions are handled by your IdP system.

Xpress Insight 5 stores the operational data that it generates using either the native file system associated with your installed operating system, or a customer installation of MySQL v 8 or above.

Note MySQL v 8 integration is not available in the BETA release of Xpress Insight 5.

File system storage is sufficient for use during development, but production deployments should use a database.

Components and concepts include:

• Execution Worker: Execution workers are the machines that ultimately run scenarios. Each execution worker can run on a separate machine, and you can configure as many as are required subject to licensing arrangements.
• Execution Services: These are used by Xpress Insight to execute scenarios when mapped to execution workers. An execution service represents a logical partition of its associated worker's processing capabilities
• Execution Service Mappings: Provide links between the defined execution services and their associated execution workers
• Execution Modes: A mechanism that enables scenario developers to specify their likely processing needs and are usually expressed as model annotations.

Key data artifact:

• Model: The optimization model itself, defining a set of input entities to receive scenario data and a set of result entities that are populated with the optimization solution. A solution is a set of values representing the decisions identified by the optimization process, together with other data synthesized from these values. It contains a set of constraints that place restrictions on what can be valid solutions.

© 2001-2020 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.