Adding the Certification Signer to the Trust Store of the SIMULIA Execution Engine Server

Once the public key files have been exchanged and imported and the digital certificates are being used by each SIMULIA Execution Engine in your Federation environment, you need to add the SSL signer of the digital certificates to the trust store of each SIMULIA Execution Engine.

  1. Open the WebSphere Administrative console on the local SIMULIA Execution Engine as described in Deploying (Installing) the Feature. This process is also described in detail in the SIMULIA Execution Engine Installation and Configuration Guide - WebSphere.
  2. Under Security on the left side of the console, click SSL certificate and key management.

    The SSL certificate and key management screen appears.

  3. In the Related Items area on the right side of the console, click Key stores and certificates.
  4. In the list on the right side of the console, click NodeDefaultTrustStore.

    The NodeDefaultTrustStore screen appears.

  5. In the Additional Properties area on the right side of the console, click Signer certificates.

    A list of signer certificates appears.

  6. Click Add.
  7. Type the following information in the corresponding text boxes, where server is the name of one of the remote SIMULIA Execution Engines:

    • Alias: serverB2B

    • File name: \keys\server.arm

    This file was created in Exchanging the Extracted Certificates.

  8. Click OK.

    The SSL signer of the digital certificates has now been added to the trust store of the partner’s server.

  9. Repeat Steps 6 through 8 for each of the SIMULIA Execution Engines in your Federation environment.
  10. At the top of the interface, click Save to save the updated WebSphere configuration.
  11. Repeat Steps 1 through 10 for each of the SIMULIA Execution Engines in your Federation environment.
  12. Proceed to Adding Partner Profiles and User Mappings.