Changing Your SIMULIA Execution Engine Passwords

Passwords for various accounts are stored inside the SIMULIA Execution Engine or SIMULIA Execution Engine station configurations in the locations described below.

Some or all of the passwords must be updated if the password for one of the SIMULIA Execution Engine utility user accounts is changed.

  • WebSphere LDAP security has the password for the “Bind Distinguished Name”. If this password changes (based on your network’s LDAP settings), you must change the password on the Security page of the WebSphere console before changing the password on the account, and then restart WebSphere after the account’s password is updated. If you change the password on the account before changing the password in WebSphere, you will not be able to log on to the WebSphere console. For more information, contact your local WebSphere administrator.

    Symptom: If the LDAP password in WebSphere is wrong and WebSphere security is enabled, you will not be able to access the WebSphere console. Instead, you will receive a message stating that your password is incorrect. You may be able to log into an Isight interface (such as the Design Gateway) and connect to the SIMULIA Execution Engine, but the user you specified will be listed as UNAUTHENTICATED and none of the SIMULIA Execution Engine features will work correctly.

  • The password of the SIMULIA Execution Engine Database owner is kept in a WebSphere J2C Authentication Alias usually named SEEOracleAuth (or fiperOracleAuth). This password must be for the user ID that is passed to the createtables script when creating the database. If the password for this user is changed, the SIMULIA Execution Engine will lose access to the database. Changing the password for this user will not affect access to the WebSphere console.

    To update this password, follow these steps:

    1. Access the WebSphere console as described in Starting WebSphere and Determining Server Port Numbers.
    2. Click Security on the left side of the console.
    3. Click Secure administration, applications, and infrastructure.
    4. Expand the Java Authentication and Authorization Service option in the Authentication area on the right side of the console.
    5. Click the J2C authentication data link.
    6. Click the link in the Alias column that corresponds to the Authentication Alias that you must update.
    7. Alter the password in the corresponding text box.
    8. Click OK.
    9. Click the Save link to save your configuration changes.
    10. Click Resources on the left side of the console.
    11. Expand the JDBC option.
    12. Click the Data sources link.
    13. Click the check box in the Select column that corresponds to the two SIMULIA Execution Engine data sources (Fiper NonXA Data Source and Fiper XA Data Source).
    14. Click Test connection.

    Two messages appear, telling you that the test connection was successful.

    Symptom: If this password is wrong, the SIMULIA Execution Engine loses connection to the database. You can log on to the SIMULIA Execution Engine, but almost all operations will fail.

  • The password for the SIMULIA Execution Engine administrative user (usually fiperacs or seeadmin) is stored in WebSphere in two places:

    1. J2C authentication alias SEEOracleAuth (or fiperOracleAuth). Refer to the previous entry for details on how to alter this password information.

    2. SIMULIA Execution Engine Application Run-As Role User. To fix this setting, alter the password information as described in Configuring J2EE RunAs Security.

      Note: You will have to restart the SIMULIA Execution Engine Application for this change to take effect, and you may have to restart WebSphere.

      Symptom: If the password for the SIMULIA Execution Engine administrative user is wrong in either the WebSphere J2C Authentication Alias or the WebSphere J2EE RunAs security, jobs fail to complete. The WebSphere SystemOut.log file shows errors indicating that the user is UNAUTHENTICATED even though all users are logged in. There may also be errors indicating that user ‘seeadmin’ is not known.

  • The password for an account used to log a station running as a service in to the SIMULIA Execution Engine is stored in the station service configuration.

    On Linux, this password is stored in the FiperStation file, which is located in the /etc/init.d directory. This file is a copy of the station.service file, which is located in the <SEE_install_directory>/<operating_system>/code/command directory.

    On Windows, the password is stored in the Wrapper.conf file, which is located in the <SEE_install_directory>\<operating_system>\code\command directory.

    To fix the password on all operating systems:

    1. Change the password of the account.

    2. Uninstall the station as a service on the system.

    3. Reinstall the station as a service, supplying the new password.

    Symptom: If this password is wrong, the station service will not start. You can view error messages in the station.log file (located in the station temporary directory, which was specified during the station installation and is listed in the station.properties file at the top level of the SIMULIA Execution Engine installation directory).

    Note: If a station running as a service on Windows is set up to run as a user other than the default LOCAL SYSTEM, you must update the Service configuration after changing the password. To change the password, access the Services control panel, open the Properties dialog box for the station service, click the Log On tab, and update the logon information. For more information on accessing these settings, see Installing a SIMULIA Execution Engine Station as a Service or contact your local system administrator. This procedure must be performed in addition to uninstalling and re-installing the service as described above, since the logon user for a service is set after the service is created.