Apama event correlator configuration
The adapter configuration file requires an <apama> element, which configures how the IAF connects to the Apama event correlator(s).
The following elements can be nested (in this order):
<sinks> - This element lists the Apama correlators that the IAF needs to connect with in order to inject EPL event-type definitions and events. Each correlator is defined through a
<sink> element:
<sink> - This defines the event correlator that the IAF must send events to. Two attributes are defined,
host and
port.
host defines the name or address of the host machine where the correlator is running, whereas
port specifies the port it can be contacted on.
Note: It is possible to specify multiple sinks. However, although all the sinks specified will be injected with any EPL event-type definitions as defined in the <event> elements, by default, only the first sink will receive the events generated by the Semantic Mapper. If you want to change the default behavior so that the Semantic Mapper sends events to components defined by subsequent <sink> elements, add the sendEvents="true" attribute to those <sink> elements.
<sources> - This element lists the Apama components from which the IAF can receive events, usually event correlators. Each component is defined with a
<source> element:
<source> - This defines the Apama component that the IAF needs to register with as an event consumer, so that it gets sent any alerts generated. Four attributes are defined:
host,
port,
channels, and
disconnectable. The
host attribute defines the name or address of the host machine where the component is running, and
port specifies the port it can be contacted on. The
channels attribute specifies the list of channels the IAF wants to register on. This string must either be empty – in which case all events generated will be sent to the IAF – or else a comma-separated list of channel names. Do not include any spaces alongside the commas. The
disconnectable attribute specifies whether or not the IAF can be disconnected if it is slow. If set to
yes or
true (case insensitive), the IAF can be disconnected. Any other setting specifies it cannot be disconnected.
It is possible to define the IAF as having only sinks, or only sources, or both, or neither. If the IAF has been started with no sinks or sources, you can use the engine_connect tool to connect it to a correlator (or another IAF).
For complete information on
engine_connect, see
Event correlator pipelining in
Deploying and Managing Apama Applications.
An example <apama> element is shown below:
<adapter-config>
...
<apama>
<sinks>
<sink host="localhost" port="15903"/>
</sinks>
<sources>
<source host="localhost" port="15903" channels="MY_ADAPTER"/>
</sources>
</apama>
</adapter-config/>
Copyright © 2013
Software AG, Darmstadt, Germany and/or Software AG USA Inc., Reston, VA, USA, and/or Terracotta Inc., San Francisco, CA, USA, and/or Software AG (Canada) Inc., Cambridge, Ontario, Canada, and/or, Software AG (UK) Ltd., Derby, United Kingdom, and/or Software A.G. (Israel) Ltd., Or-Yehuda, Israel and/or their licensors.