Configuring J2EE RunAs Security

You must configure WebSphere J2EE RunAs security before using your security-enabled SIMULIA Execution Engine.

Important: This RunAs security is different from the SIMULIA Execution Engine station Run-As security, which is described in Configuring Station (Run-As) Security. While station Run-As security is not required, J2EE RunAs security must be configured or your SIMULIA Execution Engine will not function properly.

  1. On the WebSphere console, verify that you are viewing the Fiper screen.

    If necessary, follow these steps to access this screen:

    1. On the left side of the console, click Applications.
    2. Click Application Types, then click WebSphere enterprise applications.
    3. In the Name column on the right side of the console, click Fiper.
  2. In the Detail Properties area on the right side of the console, click User RunAs roles.

    The User RunAs roles screen appears.

  3. Click the check box to the left of the fiperuser role.
  4. Type a valid user name and password in the corresponding text boxes near the top of the screen.

    Note: This user must either belong to the fiperuser global security role or be a member of your user authentication registry (such as LDAP) group that is mapped to the fiperuser global security role. For more information on configuring these settings, see Configuring SIMULIA Execution Engine Security.

  5. Click Apply.

    The valid user name appears in the User name column.

  6. Click OK.

    You are returned to the Fiper screen.

  7. Save the configuration.
  8. At the top of the console, click Logout.
  9. Stop and restart the application server as described in Restarting WebSphere with Security Enabled.

    Security has now been enabled for your SIMULIA Execution Engine.

  10. Once you restart WebSphere, verify that the SIMULIA Execution Engine application is running successfully:
    1. Access the WebSphere console.
    2. On the left side of the console, click Applications.
    3. Click Application Types.
    4. Click WebSphere enterprise applications.
    5. In the Application Status column that corresponds to the Fiper application, verify that the symbol appears.