Optional Environment Settings

This topic describes additional optional environment settings that are available for ENOVIA Live Collaboration Server.

Related Topics
Suppressable Server Commands
Configuring the ENOVIA Live Collaboration Server
Time Zones through ENOVIA Live Collaboration Server
Environment Setting Description
MX_BOS_BLOCKSIZE Sets the size of the data blocks that are transferred between the server and the client. This setting is in bytes and defaults to 65536 (64k). It can be adjusted to a maximum of 131072 (128k).
MX_BOS_EXPAND_LIMIT Can be set to a positive integer value. When set, browsers in Indented and Star modes display that number of connections in each direction at a maximum. The default is to show all connections. The following is added to the environment by default; however, notice it is commented out:
# MX_BOS_EXPAND_LIMIT=500

Refer to the ENOVIA Studio Modeling Platform Programming Guide for use of limits in ENOVIA Studio Customization Toolkit programs.
MX_BOS_FIND_LIMIT Can be set to a positive integer value. When set, find operations load no more than that number of found objects. Users can override this number by using the Limit field in the Find dialog box. The default is to load all objects that meet the search criteria. The following is added to the environment by default; however, notice that it is commented out:
# MX_BOS_FIND_LIMIT=500

Refer to the ENOVIA Studio Modeling Platform Programming Guide for use of limits in ENOVIA Studio Customization Toolkit programs.
MX_MAX_THREAD Can be set in the enovia.ini file for the ENOVIA Live Collaboration Server (previously ematrix.ini) only to indicate the maximum number of threads allowed to run inside the ENOVIA Live Collaboration kernel at one time. The default is 200.
MX_SITE_PREFERENCE Can be set to establish the preferred site for file checkin and checkout in a distributed database that makes use of replicated stores. This adjustment overrides the setting in the Person or Group definition for the site preference. This ensures that all Web clients will use the site preference of the ENOVIA Live Collaboration Server, providing optimum performance.
MX_SUPPRESS_COMMANDS Can be set to a comma-delimited list of symbols that specify MQL commands to be suppressed. This setting limits the possibility of an end user injecting harmful commands into an ENOVIA server using the public MQL command API, which normally allows the execution of any MQL command.
MX_TRANSACTION_TIMEOUT Sets the time interval in seconds after which idle transactions started through the ENOVIA Live Collaboration Server are subject to being cleaned up. A transaction is considered “idle” if the ENOVIA Studio Customization Toolkit call has completed (for example, verbose parameter tracing would show “dispatch complete”), but the session that originated the ENOVIA Studio Customization Toolkit call is still holding the Database connection open. This could happen due to improperly handled transaction boundaries (a “start transaction” without “commit” or “abort”), or if there is a large amount of work being performed by the session, but outside of the ENOVIA Live Collaboration kernel (such as JSP code that is performing operations over a large return set of objects). Note that a JPO is executed in the ENOVIA Live Collaboration kernel, so a session executing a JPO will not be considered “idle” while the JPO is executing.

This does not mean that the transaction abort and cleanup is performed immediately when the time expires, but rather means that the transaction becomes subject to being aborted after that time. The actual transaction abort and cleanup occurs only when a session accesses the same server as follows:

When any session enters the ENOVIA Live Collaboration kernel, one of the first things it does is look for transactions that have been idle for longer than the MX_TRANSACTION_TIMEOUT time. If such an idle transaction is detected, then the transaction will be aborted and the database connection released. So, the cleanup mechanism relies on the fact that other client sessions are trying to access the Live Collaboration kernel, meaning that this variable is only useful in multi-user environments such as the ENOVIA Live Collaboration Server.

If the original session was actually performing a long running operation, when it tries to access the database connection a “transaction not started” error will be thrown.

A suggested setting is 300 (5 minutes). If not set (or set to 0), no transaction timeout is in place. This setting is completely independent of existing session timeout methods available in the xml/http version of the ENOVIA Studio Customization Toolkit.

These settings can be added to the enovia.ini file for both UNIX and Windows:

  • On Windows, this file exists in the SERVER_INSTALL\intel_a\code\bin\ directory, where it is created during installation.
  • On UNIX, typical settings are in the default startup scripts. Optional settings can be set in one of the following ways:
    • UNIX startup shell scripts can be modified to include optional settings as environment variables (startup scripts call mxEnv.sh).

    • The settings can be added to the enovia.ini initialization file. This file exists in the SERVERHOME/PLATFORM/code/bin/ directory, where it is created during installation.

    If a setting is in both the startup shell script and the .ini file, the value in the shell script is used.

Most of the optional variables, date/time format variables, and server diagnostic variables of the enovia.ini file that are used for the ENOVIA Studio Modeling Platform or desktop applications can also be used in the enovia.ini file for the ENOVIA Live Collaboration Server.

The variables that are NOT used by the ENOVIA Live Collaboration Server are:
  • Those that are listed in Dynamically Updated Variables and are updated via Session/Preferences
  • Those that are used for dialog placement and shown in Application Sections
  • Those that used for customizing Help
  • Font and color variables
  • Those that are user specific or have to do with the Graphical User Interface, as listed below:
    • USER and MX_HOME_VAULT—These are user-specific and would not be desirable for all Web clients.
    • FIND_LIMIT—The server uses MX_BOS_FIND_LIMIT instead.
    • MQLWINDOWDISPLAY and MX_BACKGROUND_OPEN—Are used for debugging programs, which shouldn’t be done on the Web.
    • MX_BACKGROUND_OPEN and MX_WIN_MIN_ON_LAUNCH—Have to do with launching applications, which is a completely different mechanism on the Web.
    • MX_EXPAND_ALL—Not used. By default, formats are not expanded to show files checked in when the Formats dialog box is displayed.
    • MX_RESTRICT_EXPAND—The server uses MX_BOS_EXPAND_LIMIT instead.