The executable for the iaf tool is located in the bin directory of the Apama installation.

To start the adapter, run the following command:

where config.xml is the name of a configuration file using the format described in The IAF configuration file. A configuration file must be provided unless the -h or -V options are used.

When you run this command with the –h option, the usage message for this command is shown.

Unless the –e or --events options are used, the above will generate and start a custom adapter, load and initialize the plug-ins defined in the configuration file, connect to Apama, and start processing incoming messages.

When the –e or --events options are used, the iaf tool generates event definitions that can be saved to a file and injected during your application's startup sequences as specified by Software AG Designer, the Enterprise Management and Monitoring console (EMM), or Apama command line tools. If either of these options is used, the IAF will load the IAF configuration file, process it, generate the event definitions and print them out onto stdout (standard output) and promptly exit. A valid configuration file must be supplied with either of these options. The output definitions are grouped by package, with interleaved comments between each set. If all the event types in the configuration are in the same package, the output will be valid EPL code that can be injected directly into the correlator. Otherwise, it will have to be split into separate files for each package. The IAF can be configured to automatically inject event definitions into a connected correlator, but this is not the default behavior. The event definitions generated by the -e or --events options are exactly what the IAF would inject into the correlator, if configured to do so.

For more information about the service configuration file, see Using the Apama component extended configuration file.

If the --logfile and --loglevel options are provided, any logging settings set in the IAF configuration file (<logging> and <plugin-logging>) will be ignored.

If the IAF cannot write to the log file specified either with the --logfile option or in the adapter's configuration file, the IAF will fail to start.

The iaf tool takes the following options: