Expand the Messaging option (under Services) on the left side of the console.
Click JMS Servers.
The Summary of JMS Servers screen appears.
Click the FiperJMSServer link in the Name column on the right side of the console.
The Settings for FiperJMSServer screen appears.
Click the Targets tab.
Select the managed server that will host the SIMULIA Execution Engine from the Target list.
Click Save.
Click JMS Modules (under Services/Messaging) on the left side of the console.
The JMS Modules screen appears.
Click the Fiper-SystemModule link in the Name column on the right side of the console.
The Settings for Fiper-SystemModule screen appears.
Click the Targets tab.
A list of servers appears.
Click the check box that corresponds to the managed server that will host the SIMULIA Execution Engine.
Clear (uncheck) the AdminServer check box. Only the managed server that will host the SIMULIA Execution Engine should be selected.
Click Save.
Expand the JDBC option (under Services on the left side of the console).
Click Data Sources.
The Summary of JDBC Data Sources screen appears.
Click the Fiper nonXA Data Source link in the Name column on the right side of the console.
The Settings for Fiper nonXA Data Source screen appears.
Click the Targets tab.
A list of servers appears.
Click the check box that corresponds to the managed server that will host the SIMULIA Execution Engine.
Clear (uncheck) the AdminServer text box. Only the managed server that will host the SIMULIA Execution Engine should be selected.
Click Save.
Click Data Sources on the left side of the console (under JDBC).
Repeat step 15 through step 19 for the Fiper XA Data Source entry.
Click Activate Changes in the upper left corner of the console.
Proceed to one of the following sections, based on your deployment: