Mapping AdapterConnectionClosed and AdapterConnectionOpened events
As described in
Asynchronously notifying IAFStatusManager of connection changes, the semantic mapper contains implicit rules to map
NormalisedEvent objects that contain special fields to
AdapterConnectionClosed and
AdapterConnectionOpened events. This means you do not need to add mapping rules to your adapter’s configuration file. These implicit rules are:
<event name="AdapterConnectionClosed"
package="com.apama.adapters"
direction="downstream"
breakDownstream="false">
<id-rules>
<downstream>
<id fields="codecName,
transportName,
connectionName,
connectionGeneration"
test="exists"/>
<id fields="AdapterConnectionClosedEvent"
test="exists"/>
</downstream>
</id-rules>
<mapping-rules>
<map apama="codecName"
transport="codecName"
type="string" default=""/>
<map apama="transportName"
transport="transportName"
type="string" default=""/>
<map apama="connectionName"
transport="connectionName"
type="string" default=""/>
<map apama="connectionGeneration"
transport="connectionGeneration"
type="string" default=""/>
</mapping-rules>
</event>
<event name="AdapterConnectionOpened"
package="com.apama.adapters"
direction="downstream"
breakDownstream="false">
<id-rules>
<downstream>
<id fields="codecName,
transportName,
connectionName,
connectionGeneration"
test="exists"/>
<id fields="AdapterConnectionOpenEvent"
test="exists"/>
</downstream>
</id-rules>
<mapping-rules>
<map apama="codecName"
transport="codecName"
type="string" default=""/>
<map apama="transportName"
transport="transportName"
type="string" default=""/>
<map apama="connectionName"
transport="connectionName"
type="string" default=""/>
<map apama="connectionGeneration"
transport="connectionGeneration"
type="string" default=""/>
</mapping-rules>
</event>