-
Place a copy of each SIMULIA Execution Engine's
.arm file on all of the other SIMULIA Execution Engines
in your Federation environment.
In general, this transfer will need to take place outside the scope
of the server-to-server connection (for example, via e-mail, a diskette
transfer, etc.) assuming there is no secure file transfer mechanism in
place.
-
Access one of the SIMULIA Execution Engines
in your Federation environment.
-
Copy the
server.arm file in the SIMULIA Execution Engine's
keys directory, where server is the name
of the system running the SIMULIA Execution Engine.
-
Place a copy of the
server.arm file in
the keys directory on all of the other SIMULIA Execution Engines
in your Federation environment.
-
Repeat Step a and Step c for each SIMULIA Execution Engine
in your Federation environment.
-
Verify that each SIMULIA Execution Engine
now has the following files in the
keys directory, where
server is the name of the system running the SIMULIA Execution Engine
and remote_ server is the name of one of the other SIMULIA Execution Engines
in your Federation environment. The number of files in your directory
will vary based on the number of SIMULIA Execution Engines
you are configuring:
-
server.jks
-
server.arm
-
remote_server1.arm
-
remote_server2.arm
-
Proceed to Importing the Exchanged Public Keys.
|