Event reception for applications

In addition to sending events, the Tivoli Event Integration Facility enables other applications to receive, that is, listen for, events.

The Event Integration Facility can instantiate one or more event listeners. Each event listener can have one or more channels. This allows information to flow from multiple sources. You can specify multiple channels, and the event listener listens to all of those channels.

The polling mechanism enables the application to retrieve events synchronously, by using the get method of the API. With the non-polling mechanism, the application registers a listener or callback and receives events asynchronously.

Additionally, EIF uses a cache for event reception. If the application has a listener, EIF also registers a listener in the cache. Then it notifies the application and passes the event to the application listener. If the application does not use a listener, the application must request the retrieval of the next event.

The following is an example of a configuration file that enables the application to receive events using sockets:

TransportList=t1

t1Type=SOCKET
t1Channels=t_
t_ServerLocation=myserver.com
t_Port=5151

The following is an example of a configuration file that enables an application created using the C API to receive events using SSL, with FIPS 140-2 mode enabled:

TransportList=t1_
t1_Type=SSL
t1_Channels=c1_
c1_Port=3443

c1_ServerLocation=myserver.com

c1_SSLKeystore=/my/location/gbkeys.kdb
c1_SSLKeystorePW=password
c1_SSLCipherList=SSL_RSA_WITH_3DES_EDE_CBC_SHA

c1_SSLFIPSMode=ON