Access the system that will host the application (not the system that is hosting the SIMULIA Execution Engine).
Verify that you have installed the SIMULIA Execution Engine.
Verify that you have created a WebLogic domain on the system that will host the web application as described in Creating WebLogic Domains for Remote Managed Servers.
Navigate to the following directory:
<see_install_dir>/<os_dir>/code/bin/
Start the editcpr.exe file (editcpr file on Linux). This file allows
you to create a connection profile for connecting the WebTop or WebDashboard to
a SIMULIA Execution Engine.
Create the new connection profile using the Profile Editor dialog box:
-
Type a name for the profile in the Profile name text box. Typically the name
of the computer hosting the SIMULIA Execution Engine application is used.
-
Select Weblogic Server 12 from the Server type list.
-
Type the name of the computer running the SIMULIA Execution Engine in the
Server name text box.
-
Specify the Listen Port number for the managed server that is running the
SIMULIA Execution Engine deployment.
-
Select Save from the File menu to save the connection profile. The Save
Connection Profile dialog box appears.
-
Specify a file name, and click Save. This file name will be used in a later step.
-
Close the Profile Editor dialog box.
Navigate to the following directory:
<see_install_dir>/2017/config/
Open the .properties file that corresponds to the application you are
configuring in the text editor of your choice.
Locate the following entry in the file, where <application> is either webtop
or webdashboard:
fiper.<application>.acs.cprfile=
Update the path following the = sign to point to the .cpr file that will be used to
connect to the WebTop or WebDashboard. The path needs to point to the file
created in step 6. For example:
c:/simulia/Isight/2017/config/seecomputer.cpr
Verify that the following two settings are commented out (have the # sign at the
beginning of the setting) as shown below:
#fiper.<application>.acs.server=
#fiper.<application>.acs.port=
Locate the fiper.system.esihome= entry.
Verify that the entry is correctly pointing to the operating system of your SIMULIA Execution Engine installation directory, including the operating system directory name, and make sure that the line is uncommented. For example:
c:/simulia/Isight/2017/win_b64
Save and close the file.
If necessary, repeat step 7 through step 14 if you are installing both web-based
applications on the same host. Otherwise, repeat step 1 through step 14 on another
remote host.
Stop and restart the managed servers. For more information, see Stopping the SIMULIA Execution Engine Server.