Initializing help system before first use

Xpress Insight 5 Release Notes

New in Insight 5.2.1

  • Browser support policy

    Microsoft has announced that Internet Explorer 11 will be officially retired by June 15, 2022. For upcoming releases, Xpress Insight will drop support for IE11. Going forward, Xpress Insight 4 and Xpress Insight 5 will support Chrome, Firefox, and Microsoft Edge.

Maintenance
  • Various security updates.
  • When retrying a failed request, there is no longer a delay before the first retry.
  • The default value of the dmp_max_retries parameter has changed from 8 to 9.

New in Insight 5.2

Back to top
Revised Compute REST API
  • The Compute REST API has been revised to adhere as closely as possible to accepted REST/HTTP industry best practices. The revision includes major changes to the design of the API. Developers intending to integrate with the REST API or update an existing integration should read the Compute Interface REST API chapter of the Insight 5 Compute Interface Guide for foundation concepts and then use the live swagger documentation served from <INSIGHT_URL>/swagger-ui/, or the equivalent online reference docs, to understand the format of individual API requests.
  • The API is versioned using a major.minor versioning scheme.
  • The current version is 2.0.
  • Clients must use content negotiation request headers which allow for the API major version to be specified in the request.
  • The API base has moved from /insightservices to /api.
  • The API uses standard HTTP status codes from RFC-7231 and RFC-4918 to indicate success or failure of a request.
  • Timestamps are in ISO-8601 format in accordance with RFC-3339 and are in Coordinated Universal Time (UTC).
  • The API now uses pagination for collection-type responses.
  • The API supports the OpenTracing standard used for trace context propagation.

New in Insight 5.1.1

Back to top
Maintenance
  • Various security updates.
  • Support for Xpress 8.12.

New in Insight 5.1

Back to top
Job Queue
  • Users can cancel all their own jobs and those with both PROJECT_ALL and SCENARIO_ALL authorities can cancel all jobs in the queue.
  • System enforces a limit on the number of jobs in the queue. The default limit is 1000 jobs. This can be modified in the server's application.properties file with an ultimate limit of 10000 jobs.
Compute jobs
  • When submitting a compute job using the REST API, a priority can optionally be supplied. Jobs are then executed in the queue in priority order. The priority can range from -100 to 100 with 0 being the default
Execution services
  • An execution service can now be marked as requiring authorization. If it requires authorization, only users belonging to authority groups which grant access to the execution service can submit jobs to run on the service.

Worker Mosel environment

Aside from the following exceptions, Mosel no longer inherits the environment of the worker:
  • LANG
  • XPRESSDIR
  • XPAUTH_PATH
  • LD_LIBRARY_PATH

To configure Mosel environment variables, add entries to the worker application.properties file of the form: insight.worker.execution.environment.<VARIABLE_NAME>=<VARIABLE_VALUE>.

Insight 5.0

Back to top
General
Important: Version 5.0 is not yet a replacement for Insight 4 and uploading or migrating custom apps is not supported. Existing users of Insight 4 should upgrade to the latest minor release of 4.x.
  • A deployment is now designated as production or non-production and the non-production lifecycle can have a custom display label e.g. QA, Staging which is shown as a watermark on the banner.
  • Single Sign On support (Service Provider initiated and IDP initiated SAML2). SSO is mandatory for production mode deployments, local account authentication is disabled.
  • REST API is now authenticated using client id/secret credential which can be generated by a logged-in user for their account via the user interface (drop-down menu under account name).
  • Simple installation configuration is available for development and small scale usage which uses a file system based repository.
  • MySQL support for more demanding deployments (database server to user-supplied). PostgreSQL is no longer support on premises.
  • Silent/automated installation option.
Compute Interface
  • Implements an interface for solving LP/MPS/Mosel jobs. REST API for submitted LP/MPS optimization problems and Mosel models as jobs via web services.
  • Integrated with Xpress for remote solving via Optimizer, Mosel and Workbench tools.
  • Progress Events API for receiving job status updates and callback notifications.
  • Drag and drop interface for submitting jobs interactively.
  • Enhanced job queue view with persistent history.
  • LP/MPS jobs can include a basis and/or starting mip solution.
  • LP/MPS job results can include solution, final attribute values, basis, IIS, save file.
  • Jobs can have dependencies on common files that can be pre-uploaded.
  • Support for solver callbacks with the option of querying current attributes and solution, and deciding whether to continue the remote solve or interrupt it.
  • Integration with Credentials Manager (Windows), KeyChain (MacOS) and OpenSSL (Linux) for the secure management of client credentials
  • Jobs can specify a named execution service. An execution service is a logical sub-set of execution resources which can be configured via the Insight administration interface.
  • A clean up service can be scheduled to delete jobs older than a set age. This avoids the service performance being affected by the accrual of a very large number of historic jobs, and is an alternative to the client taking responsibility for deleting the jobs.
Parent Topic Release Notes

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