Updating the SIMULIA Execution Engine Properties File

You need to update two settings in each SIMULIA Execution Engine’s properties file. These settings, which represent the new security credentials defined earlier, are then used by the SIMULIA Execution Engine after WebSphere is stopped and restarted.

  1. On the local system, navigate to the following directory in your SIMULIA Execution Engine installation: 

    <see_install_dir>/config/

  2. In the text editor of your choice, open the acs.properties file.

  3. Locate the following two entries in the file and edit them as shown below, where local_see is the name of the local SIMULIA Execution Engine and <password> is the password for the .jks file you created in Importing the Exchanged Public Keys:

    fiper.ssl.keystore.file=c:/keys/local_see.jks

    fiper.ssl.keystore.password=<password>

    Important: Be sure to specify your system name and password information, and use forward slashes in file names.

    The first line names the JKS key database file, and the second is the plain-text password used when the key file was created.

  4. Save and close the file.

  5. Repeat Steps 1 through 4 on each SIMULIA Execution Engine in your Federation environment. Be sure to use each individual SIMULIA Execution Engine’s .jks file and password when editing the acs.properties file.

  6. Stop and restart the WebSphere servers for all of the SIMULIA Execution Engines that have been updated.

    For more information on performing this step, refer to the SIMULIA Execution Engine Installation and Configuration Guide - WebSphere.

    Tip: If you encounter an error when attempting to restart the WebSphere Application Server, check to see if IIS Admin Services are running. Stop IIS Admin Services, and start the server again. For more information on performing this task, contact your local WebSphere administrator.

  7. Proceed to Testing the Federation Connection.