The RabbitMQ is an event receiver to receive messages from RabbitMQ Broker that match a specified configuration. You can configure it with XML, JSON, and Text input mapping types.
Creating a RabbitMQ event receiver
For instructions to create a RabbitMQ event receiver, see Configuring receiver properties.
A RabbitMQ event receiver can be configured in the Management Console as shown below. To open the following page,click Main => Manage => Receiver to open the Available Receivers page and then click Add Event Receiver.
The properties configured above are described in the table below.
Configuration file property
|The host name of the server.|
|Host Port||The port of the server.|
|A valid user name for the broker connection.|
A valid password for the broker connection.
The name of the queue. A queue is a buffer that stores messages.
The name of the exchange. The exchange provides the logic to handle messages received by the RabbitMQ event receiver.
|Enable Queue Durable||This specifies whether the queue should remain declared even if the broker restarts.|
Enable Queue Exclusive
This specifies whether the queue should be exclusive to one connection or whether it should be consumable by other connections.
Enable Queue Auto Delete
This specifies whether the queue should be kept even if it is not being consumed anymore.
Enable Queue Auto Ack
This specifies whether an acknowledgement should be sent back for the messages received.
Queue Routing Key
The routing key is referred to by the exchange in order to determine how messages should be routed to queues. The routing key is similar to the address for a message.
This specifies the identifier for the consumer. The consumer tag is local to a channel. Therefore, two or more clients can use the same consumer tag. If consumer tag is specified, the server generates a unique tag.
The type of the exchange.
Enable Exchange Durable
This specifies whether the exchange should remain declared even if the broker restarts.
Enable Exchange Auto Delete
This specifies whether the queue should be kept even if it is not used anymore.
|The number of times the CEP receiver should retry connecting to the RabbitMQ broker.|
The number of milliseconds within which the CEP receiver should retry connecting to the RabbitMQ broker.
The virtual host used. The virtual host provides a way to segregate applications using the same RabbitMQ instance.
The number of milliseconds after which an inactive connection is considered dead. The connection is removed after the specified amount of time. This ensures that the resources are not wasted on inactive connections.
This specifies whether an encrypted communication channel should be established or not.
SSL Keystore Location
The location of the
SSL Keystore Type
The type of the keystore.
SSL Keystore Password
The password of the keystore.
SSL Truststore Location
The location of the truststore. A truststore contains certificates from other parties that you expect to communicate with, or from certificate authorities that you trust to identify other parties.
SSL Truststore Type
The type of the truststore.
SSL Truststore Password
The password of truststore.
Connection SSL Version
The version of the SSL.
After entering the above receiver properties, click Advanced and do the following.
- Select the event stream to which you want to map the incoming events.
- Select the message format in which the events should be received.
- Define custom output mappings based on the message format you selected. For more information, see Output Mapping Types.
You can also configure the properties mentioned above based on the transport type within the
<from> element of the event receiver configuration in the
<CEP_HOME>/repository/deployment/server/eventreceivers directory as shown below.