Editing the Properties File

You may need to verify or edit the webtop.properties file or webdashboard.properties file for proper operation of the application.

The WebTop and WebDashboard read certain installation and SIMULIA Execution Engine connection information from a properties file. In some cases this file may be properly configured during the installation, especially if the WebTop/WebDashboard is running on the same machine as the SIMULIA Execution Engine. However, you should verify that this information is correct regardless of your deployment strategy.

  1. Navigate to the following directory in your SIMULIA Execution Engine installation: 

    <SEE_install_dir>/config/

  2. Open one of the following files, based on the application you are configuring, in the text editor of your choice:

    • webtop.properties

    • webdashboard.properties

  3. Locate one of the following entries in the file, based on the application you are configuring:

    • fiper.webtop.acs.cprfile=

    • fiper.webdashboard.acs.cprfile=

  4. Verify that the path following the = sign points to the .cpr file that will be used to connect to the WebTop/WebDashboard (the .cpr file that matches the SIMULIA Execution Engine that will be used by the WebTop/WebDashboard).

    For example:

    C:\SIMULIA\Isight\2024\config\seehost.cpr

    Important: You need to make sure this connection profile exists on the system running the WebTop/WebDashboard. For more information, see Creating the Connection Profile File. Furthermore, it is recommended that you verify that the connection profile works correctly by connecting to the SIMULIA Execution Engine with any SIMULIA Execution Engine interface (for example, a SIMULIA Execution Engine station or the Dashboard).

  5. In the webtop.properties file only, you must specify a location for the working (temp) directory for the WebTop application. Find the following lines in this file: 

    #Defines temp work directory for WebTop, must be writeable
#fiper.system.temp=c:/temp/webtop

    Remove the # in the fiper.system.temp line to uncomment it, and replace c:/temp/webtop with a path that can serve as a working directory that the WebTop application can write temporary files to. Be sure that the directory/folder that you specify is not subject to automatic cleanup on Linux systems.

    If the SIMULIA Execution Engine and WebTop applications are accessing the same file system, it is recommended that you configure different working (temp) directories for each application.

  6. Isight provides HELP button in the webtop editor page. By default it will open a new Isight documentation page which points to https://help.3ds.com
    Find the following lines in this file: 
    #fiper.help.language=English
fiper.help.url=https://help.3ds.com

    The default value of fiper.help.language is English. The only other supported language is Japanese. If you want, you can change it to Japanese by removing the # in the fiper.help.language line to uncomment it, and replace English by Japanese. Note that, documentation in Japanese language is usually not available at the time of GA release. It becomes available sometime afterward.

    If you want, you can replace https://help.3ds.com by the NodeJS server URL of your served documentation.

    Example: fiper.help.url=http://servername.com:4040

    You can locate the actual NodeJS server port number for the documentation installation in the following file: <documentation_install_dir>\StartDocumentationUsingJavaSearch.txt

  7. Save and close the file.
  8. Restart WebSphere. For more information on stopping and restarting WebSphere, see Restarting the SIMULIA Execution Engine in WebSphere.