Option | Description |
-V | --version | Displays version information for the iaf executable. |
-h | --help | Displays usage information. |
-p port | --port port | Specifies the port on which the IAF should listen for commands. The default is 16903. |
-f file | --logfile file | Specifies the name of the file to which to write log information. The default is stderr. See also
Text internationalization in the logs. |
-l level | --loglevel level | Sets the level of information that is sent to the log file. Available levels are TRACE, DEBUG, INFO, WARN, ERROR, FATAL, CRIT and OFF. The default is INFO. |
-t | --truncate | Specifies that if the log file already exists, the IAF should empty it first. The default is to append to the log file. |
-N name | --name name | Sets a user-defined name for the component. This name is used to identify the component in the log messages. |
-e | --events | Dumps event definitions to stdout and then exits. |
--logQueueSizePeriod p | Sends information to the log every p seconds. See also
IAF log file status messages. |
--pidfile file | Specifies the name of the file that contains the process identifier. This file is created at process startup and can be used, for example, to externally monitor or terminate the process. The IAF will remove that file after a clean shutdown. It is recommended that the file name includes the port number to distinguish different IAFs (for example, iaf-16903.pid). The IAF takes an exclusive lock on the pidfile while it is running. This means that if you have another IAF or correlator running using the same pidfile, the second process will fail to start up. You should not run multiple components from the same configuration using the same pidfile. In other cases, existing pidfiles will be overwritten, even if they contain a process identifier of a running process. |
-Xconfig file | --configFile file | Reserved for usage under guidance by Apama support. See also
Using the Apama component extended configuration file. |