Configuring a Non-secure Federation Connection

You can configure the Federation feature with a non-secure connection, which provides no Federation security and is not appropriate for use across firewalls or over the Internet. To successfully configure this type of connection, you need to create the necessary partner profiles and user mappings on each SIMULIA Execution Engine in your Federation environment.

Note: To successfully configure the Federation feature with a secure connection, proceed to Configuring a Secure Federation Connection.

For more information on partner profiles, see About Partner Profiles. For more information on user mappings, see About User Mappings.

  1. Access the SIMULIA Execution Engine Command Line Client:

    • Windows: Click the Start button, point to All Programs / SIMULIA Execution Engine x.x, and click Command Line.

    • Linux: Execute the ./fipercmd command from the following directory:

      <see_install_dir>/<os_dir>/code/command/

  2. Log on to the local SIMULIA Execution Engine.

    The Command Line Client is ready when the > prompt appears.

  3. Type the following command:

    partners

    A list of defined partner profiles appears. Initially there will be no existing partner profiles.

  4. Type the following command (on a single line) at the > prompt: 

    addpartner name:your_partner_name connect:http://remoteserver:port 
callback:http://localserver:port

    where

    • your_partner_name is the name of the partner SIMULIA Execution Engine. This name can be any readable string, and it will be displayed to users when federated models are built and executed.

    • remoteserver is the IP address or name of the remote SIMULIA Execution Engine.

    • localserver is the IP address or DNS name of the SIMULIA Execution Engine you are currently logged into as seen by the remote server. This entry represents how the remote SIMULIA Execution Engine addresses the local SIMULIA Execution Engine.

    • port is the listen port of the WebSphere application server and should be the same port number used to test your installation in Testing the Deployment.

    Use caution when typing the connect and callback strings. They must be exactly correct to ensure proper operation. Be sure to leave a single space between both the your_partner_name string and the connect command and the first port string and the callback command.

    A message appears, informing you that the partner has been created.

  5. Specify one or more user mappings. Each defined partner must have at least one user mapping.

    Type the following command on a single line in your command prompt window:

    addusermap name:your_partner_name localid:localid localpw:localpw foreignid:foreignid

    where:

    • your_partner_name is the display name of the partner profile to be modified as specified in Step 4.
    • localid is the ID of the local user account to be used for the mapping.
    • localpw is the password of the local user account.
    • foreignid is the ID of the foreign (remote) user to be mapped to the local user.

    For example,

    addusermap name:MyPartner localid:user1 localpw:user1pwd foreignid:*

    This mapping causes all remote job requests to this partner to execute as local user user1. If no match is made, the map of all remote users (foreignid:*) is used.

  6. If desired, use the partners command in the SIMULIA Execution Engine Command Line client to view the mappings defined for a partner. In addition, you can delete mappings using the deleteusermap command.

    For more information on user mappings, see About User Mappings.

  7. Repeat Steps 4, 5, and 6 for each federated SIMULIA Execution Engine that will be a partner of the current SIMULIA Execution Engine.

  8. Type exit to close the SIMULIA Execution Engine Command Line client.

  9. Repeat Steps 1 through 6 on each SIMULIA Execution Engine in your Federation environment.

    The configuration of the Federation feature with a non-secure connection is complete.