Using the FIPER_JVMPARMS Variable

The variable options are similar to command line options. However, they are set in the FIPER_JVMPARMS environment variable. The variable options can be useful if you always log in using the same connection profile, user name, and password.

For more information on setting environment variables on your system, contact your local system administrator.

Note: Some of these options have matching command line arguments. All of these options can be used (as they appear below) on the command line in conjunction with the gateway command or the rt_gateway command. For more information on command line arguments, see Setting Gateway Options on the Command Line.

Important: Be sure to leave a space between the argument that you add and the last one currently listed in the environment variable definition.


Option	Action
`-Dfiper.gateway.modelToLoad=MODEL.zmf`	Allows you to define a model that will be loaded with the gateway.
`-Dfiper.logging.maxSizeKB=99`	Specifies the maximum size of log files (in kilobytes) created by the gateway. Once the maximum size of the file is reached, the original log file is saved and a new file is created.
`-Dfiper.logging.numBackups=2`	Determines the number of backup (old) log files to keep. A new log file is created when its maximum size is reached. This size can be specified using the `-Dfiper.logging.maxSizeKB` option previously described. By default, one backup log and one active log are created.
`-Dfiper.logon.profile=PROFILE`	Allows you to specify the connection profile.
`-Dfiper.logon.prop.user=USER`	Allows you to specify the user name.
`-Dfiper.logon.prop.pw=PASSWORD`	Allows you to specify the password.
`-Dfiper.logon.prompt=yes\|no`	Allows you to specify whether or not the Logon dialog box appears when the gateway is started.
`-Dfiper.gateway.executeModel=`	Allows you to specify where the Runtime Gateway will execute the loaded model (i.e., `local` and `remote)`.
`-Dfiper.gateway.quitAfterExecution=true`	Closes the Runtime Gateway automatically following execution.

You can also customize the directory that will be used for all temporary files using the FIPER_TEMP environment variable.