Installing Studio Modeling Platform

This topic describes how to install Studio Modeling Platform.

Before you begin:
  • You must have access privileges to install software on the target computer. Otherwise, you will not be able to start the installation.
    UNIX/Linux
    You must log in as root.
    Windows
    You must log in as a user who belongs to the Administrators group or has the privileges assigned to the Administrators group.
  • You must first install Java (JRE, JDK, SDK).
  • Review the Program Directory, a website that organizes all of the release information for all Dassault Systèmes products for a given release. It contains information about prerequisites, installation, licensing, product enhancements, general issues, open issues, user assistance addenda, and closed issues.
  1. See the DS Installer Guide for instructions on unloading the media and launching the product installation.
  2. Once the Setup program has started, Setup displays the directory where the Studio Modeling Platform software will be installed.

    UNIX/Linux
    The default installation path is empty.
    Windows
    The default is: C:\enovia\VERSION\studio.

    On either platform, Setup does not check for the existence of a previous version. The software must be installed to a new location, and the installation directory may not include any spaces. The installation directory must also be different from the distribution directory.

    To choose a different location, click Browse and navigate to the desired directory or type in the path.

    Click Next.

  3. Choose the components that you want to install from the list of those that are packaged with the media. The DMP media contains only a single product (Studio Modeling Platform), so you can skip this step and go directly to the next panel by clicking Next.

    The MQL command line interface will be installed automatically.

  4. Enter the Java Home path. This is the location of your Java Development Kit (JDK).

    Ensure that the JDK is installed in a fixed directory (such as C:\Java\JDK) which does not include the version number, to guarantee that hot fix installation does not fail later if you update the JDK version.

    Incorrect Java home path selection may abort the installation without a message indicating the reason for the failure. Failing to provide a 64-bit JDK for a 64-bit install will also cause the installation to abort.

    Ensure that the JDK is installed in a fixed directory (such as C:\Java\JDK) which does not include the version number, to guarantee that hot fix installation does not fail later if you update the JDK version.

    To select a directory other than the default, click Browse and navigate to the desired directory, or type in the path.

    Click Next.

  5. Choose a database type. Only those database types that are supported on your particular platform are displayed. Depending on the OS, the available database options could be any of the following:

    • Oracle and MSSQL
    • Oracle only

    If your platform supports multiple types of databases, Oracle is the default.

    UNIX/Linux
    Select the required database type.
    Windows
    To use a database other than Oracle, select Others and then select the required database type (MSSQL).

    Click Next.

  6. If you selected Oracle, Setup asks for the location of the TNS_ADMIN directory, which contains the tnsnames.ora file. This file contains the client-side network configuration parameters required for Oracle. You can copy a tnsnames file from the Oracle server and put it in the location specified here after the installation completes.

    UNIX/Linux
    The Setup program cannot detect the correct Oracle path on UNIX.
    Windows
    The default Oracle path is c:\oracle\product\<version>\NETWORK\ADMIN.

    Incorrect Oracle path selection may abort the installation without a message indicating the reason for the failure.

    To install to a different location than the displayed default, click Browse and navigate to the desired directory or type in the path.

    Click Next.

  7. If you selected Oracle, Setup then asks you to read and accept Oracle's client license agreement. Read the agreement, then click the I have read and accept the license terms radio button.

    Click Next.

    Windows
    The following value is written to the HKEY_LOCAL_MACHINE/Software/Oracle registry key:

    TNS_ADMIN--location of your tnsnames.ora file.

  8. If you selected a database type other than Oracle, Setup displays a set of questions.
  9. Enter the directory of your connection file:

    UNIX/Linux
    The path to the MATRIX-R bootstrap file
    Windows
    The path to the MATRIX-R bootstrap file

    To choose a different location, click Browse and navigate to the desired directory or type in the path.

    Click Next.

  10. The next panel displays the installation summary, including the DMP installation directory, selected products, components to be installed, Java Home path, database type, TNS_ADMIN directory, and finally, the location of your connection file.

    Review the contents and if you want to make any changes, click Back and make the desired corrections.

    When you are satisfied with the information displayed, click Install to start the installation.

    Setup displays the current state of progress of the installation.

  11. Once the installation is complete, Setup informs you that the "DMP - Studio Modeling Native Apps" component has been successfully installed.

    Click End to end the Setup program and dismiss the window.

    Windows
    The Setup program also creates program shortcuts under the "Dassault Systemes Software VERSION" program folder on the Start menu.

Note: The MX_TCL_SHLIB variable sets the TCL path and library file name (without the extension) when a non-default TCL version is used. It defaults to the 8.5.7 directory structure, so you would need to add this setting to use version 8.0 files. For example:
On Windows:
For Live Collaboration Server: MX_TCL_SHLIB=SERVER_INSTALL\win_b64\code\bin\tcl80
For Studio Modeling Platform: MX_TCL_SHLIB=ENOVIA_INSTALL\win_b64\code\bin\tcl80
On UNIX/Linux:
For Live Collaboration Server: MX_TCL_SHLIB=SERVERHOME/PLATFORM/code/bin/tcl80
For Studio Modeling Platform: MX_TCL_SHLIB=ENOVIAHOME/PLATFORM/code/bin/tcl80

Dassault Systèmes validates only the bundled TCL version. Configuration of other versions is allowed, but support is provided only for the bundled version.

When setting MX_TCL_SHLIB, you must also reset the TCL_LIBRARY and TK_LIBRARY settings to reflect the path to the new library versions, including the initialization files.

On Windows:
Make these changes in the .ini files.
On UNIX/Linux:
For Live Collaboration Server: Make these changes in the mxEnv.sh file.
For Studio Modling Platform: Make these changes in the Studio Modeling Platform startup files.

If implementations rely on TCL_LIBRARY or TK_LIBRARY settings to find files under that directory, you need to move those files to the Tcl 8.5.7 directory structure. For example, the Solutions Library depends on these entries being set in the environment to find files under a sub-directory called mxTclDev.

See also Tcl Support.