Check the following configuration details:
-
In your connection profile verify that you did not specify the fully
qualified domain name of the system running the SIMULIA Execution Engine.
Use the non-FQDN hostname. For more information on this setting, see
Creating the Connection Profile File.
-
In the <SEE_install_dir>/config/acs.properties file, check the following:
-
Verify that you have not set the SIMULIA Execution Engine
name property (fiper.acs.name
). The SIMULIA Execution Engine
name must be the non-FQDN hostname.
-
Verify that the fiper.acs.isWindowsService
property
is set correctly. This property informs the SIMULIA Execution Engine
if the application server is running as a service.
-
The user running your application server must be able to submit LSF
jobs successfully to all hosts. To perform this action, the user must
exist, the user name and password must be the same on all computers,
and the user’s password must be made known to LSF using the lspasswd
command.
-
Before starting your application server, the user account specified
in the previous item must already be set up for the LSF cluster. On Windows
systems user accounts are typically configured at the time LSF is installed.
-
The lspasswd
command applies to installations involving
Windows only. The lspasswd
command must be run on a
Windows system, even in a mixed cluster. The lspasswd
command is not required if there are no Windows systems. This command
is an LSF utility program that each user must run once to store a Windows
password in the LSF system. This step is required to run LSF work on
a Windows LSF node.