Station Administration Properties Reference

The directory in which the 3DOrchestrate Station writes temporary files and log files during job execution.

If you want to change this setting from the default location, be sure to select a directory that has the following characteristics:

• Is not a temporary file system. This disk space must never be reclaimed automatically. This rules out any directories that are cleared during a restart or during an automatic disk space cleanup.
• Preferably on a local disk on the station computer. If there is insufficient local storage space, a NAS device can be used; however, this is not recommended.

This property determines whether to save the station LSF log file when an error occurs, if you are using the LSF distributed resource management (DRM) mode. This property can be set to true or false (the default).

If this property is set to true, the station LSF log information is saved in the following file in the temporary directory when an error occurs:

{fiper.station.tempdir}/station_{LSF-job-ID}.log

Enable or disable the run-as security feature on this station. By default, the station follows the run-as configuration of the 3DOrchestrate Distribution Server to which it is connected (as determined by the fiper.security.runas.enabled property in the SMAExeServer.properties file). You can use this property to force the station to run with run-as security disabled even if the 3DOrchestrate Distribution Server has run-as enabled.

This property can have the following values:

• Disabled – Turns off the run-as feature for the station. It is valid only if the run-as feature is active on the 3DOrchestrate Distribution Server.

• Enabled – Turns on the run-as feature for the station. It is valid only if the run-as feature is active on the 3DOrchestrate Distribution Server.

This setting defines how the 3DSpace MCS accesses the path defined in the Staging Directory (fiper.station.fcs.stagingdir) property. If the MCS can access the fiper.station.fcs.stagingdir path directly, there is no need for this setting. Otherwise, define the exact path for how the MCS will access the fiper.station.fcs.stagingdir path. For example:

fiper.station.fcs.stagingdir=\\file-server\path\vm8-29sim\home\STAGING
fiper.station.fcs.serverstagingdir=/path/vm8-29sim/home/STAGING

This property is set to true by default. This causes the station to cache files that have been downloaded from the 3DSpace FCS (File Collaboration Server). If the same file is requested later, the station will use the copy from its local cache if the file has not changed. This saves time by avoiding repetitive downloads from the FCS. The caching operation works with or without run-as security.

If you encounter problems with downloaded files, set this property to false to disable the caching.

Set to true to suppress the usual file locking of the station's temporary directory (fiper.station.tempdir). This is required when the station's temporary directory is on an NFS file system on Linux and you see the following error when trying to start the station: "Unable to verify station temp directory lock file."

Message Passing Interface (MPI) software libraries are required for the station to execute any co-simulation jobs. The MPI libraries are automatically installed along with the Abaqus solvers from the SIMULIA_ComputeServices media. If this station does not have the mpirun command in the default system path, however, you must use this property to specify the full path to the executable. On Linux, for example, this might be

fiper.station.mpirunPath=/opt/abaqus/External/mpi/hpmpi-2.3/bin/mpirun

Set this property to the absolute path and file name of your SMAVariantParameterMatch.txt file for the Results Analytics app. If this property is not set, the file is read from the following directory in the station software installation:

<station_install_dir>/3DOrchestrate/<os>/reffiles/SMAResIntServant/SMAVariantParameterMatch.txt

The SMAVariantParameterMatch.txt file contains regular expression rules. Parameters extracted from the variants in Results Analytics are matched against the rules in this file and the filtered parameters are then used. If the file is empty or not found, all the extracted parameters are used.

Set this property to specify TCP/IP ports to be used for the file monitoring station service and Results Analytics app (servant). You can specify the exposed ports in two ways:

• A port number range such as 56000-57000.
• A range of ports with a string identifier to map identifier to port in the reverse proxy configuration. For example: 8080-8085:red. Here the reverse proxy should map ID's red0-red5 to ports 8080-8085.

You can include wildcards (*) in the exposed IP address as well. For example, you can specify that the exposed IP address is of the pattern 172.30.*.* to avoid having to set an exact IP address.