Setting Server Properties for Java DRM Customization

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=<Java-drm-name>
```
For example:
```
fiper.system.drm.4=MyJavaLSF
```
Do not use the predefined values "fiper" or "Lsf"—these are reserved names for the preset built-in systems.

Make sure that <Java-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=MyJavaLSF
#fiper.system.drm.3=Lsf
#fiper.system.drm.4=LoadLvler
```
Define the following new property to specify the executable command for the 3DOrchestrate transient station, which must be used on all DRM compute nodes.
fiper.system.<Java-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.MyJavaLSF.transStationCommand=/opt/ds/v6r2017x/3DOrchestrate/lin_a64/code/command/SMAExeTranstation
```
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 you should simply 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.

You must add this property in the SMAExeServer.properties file; it is not pre-populated in the template version of the file that is installed.