Setting Server Properties for DRM Scripts

Register the new DRM system in the SMAExeServer.properties file by creating a new numbered line in this set of properties:
```
#fiper.system.drm.1=fiper
#fiper.system.drm.2=Lsf
#fiper.system.drm.3=LoadLvler
```
For example, add this new property:
```
fiper.system.drm.4=<drm-name>
```
For example:
```
fiper.system.drm.4=CustomLSF
```
Do not use the predefined names "fiper", "Lsf", or "Cloud"—these are reserved names.

Make sure that <drm-name> does not exceed 10 characters.

Uncomment the lines you want to activate and use. You can renumber the DRM systems, for example:
```
fiper.system.drm.1=fiper
fiper.system.drm.2=CustomLSF
#fiper.system.drm.3=Lsf
#fiper.system.drm.4=LoadLvler
```
Define the following new properties with values to specify your custom scripts for the DRM features. Add these properties in the SMAExeServer.properties file; 3DEXPERIENCE does not prepopulate them in the template version of the file that it installs.
1. Specify your wrapper script for the submit command. This script submits the job to the DRM system.
  
  fiper.system.<drm-name>.submitCommandScriptPath=</path/filename>
  
  Example:
```
fiper.system.CustomLSF.submitCommandScriptPath=/opt/scripts/bsub.pl
```
2. Specify your wrapper script for the kill command. This script kills the specified jobs in the DRM system.
  
  fiper.system.<drm-name>.killCommandScriptPath=</path/filename>
  
  Example:
```
fiper.system.CustomLSF.killCommandScriptPath=/opt/scripts/bkill.pl
```
3. Specify your wrapper script for the status command. This script queries the DRM system to obtain status for the specified jobs.
  
  fiper.system.<drm-name>.statusCommandScriptPath=</path/filename>
  
  Example:
```
fiper.system.CustomLSF.statusCommandScriptPath=/opt/scripts/bjobs.pl
```
4. Specify the executable command for the 3DOrchestrate transient station, which must be used on all DRM compute nodes.
  
  fiper.system.<drm-name>.transStationCommand=</<path>/SMAExeTranstation>
  
  The default path to the transient station command in the software installation is:
```
<station_install_dir>/<platform>/code/command/SMAExeTranstation
```
  Example:
```
fiper.system.CustomLSF.transStationCommand=/opt/ds/v6r2017x/3DOrchestrate/lin_a64/code/command/SMAExeTranstation
```
  The SMAExeTranstation command must be accessible by every DRM compute node, either from a local 3DOrchestrate Station installation or a shared file system installation. Depending on the type of simulation processes they are executing, the DRM compute nodes may also need the SIMULIA_ComputeServices media installed (for the Abaqus physics solvers).
  
  Note: You do not have to use an absolute path to the SMAExeTranstation executable command. If you have both Windows and Linux compute nodes, for example, you cannot use an absolute path that works on both platforms. In this case, set the property to the command to be launched (SMAExeTranstation) and ensure that the PATH environment variable is set to find it on every compute node.
5. Choose whether to write all wrapper script log information to the 3DOrchestrate Distribution Server log file (catalina.out).
  
  fiper.system.<drm-name>.debugLog= true | false
  
  The default is false.
  
  Example:
```
fiper.system.CustomLSF.debugLog=true
```
6. Specify execution time for the kill command. If you specify a timeout, 3DEXPERIENCE kills the process if it does not end after the given number of seconds. The default value is 60 seconds. Specifying zero allows the process to run indefinitely.
  
  fiper.system.<drm-name>.killCommandWaitTime=60
7. Specify execution time for the submit command. If you specify a timeout, 3DEXPERIENCE kills the process if it does not end after the given number of seconds. The default value is 60 seconds. Specifying zero allows the process to run indefinitely.
  
  fiper.system.<drm-name>.submitCommandWaitTime=60
8. Specify execution time for the status command. If you specify a timeout, 3DEXPERIENCE kills the process if it does not end after the given number of seconds. The default value is 60 seconds. Specifying zero allows the process to run indefinitely.
  
  fiper.system.<drm-name>.statusCommandWaitTime=60