Property | Description |
---|---|
Name | Required. The event source name that appears in the Process Designer. The name must be unique for the connection. You can change this property after you create the connection. The name cannot exceed 128 characters, contain spaces, or contain the following special characters: ~ ` ! $ % ^ & * ( ) - + = { [ } ] | \ : ; " ' < , > . ? / |
Description | Optional. A description for the RabbitMQ event source that appears in the Process Designer. The description cannot exceed 4,000 characters. |
Enabled | Select Yes to make the event source available immediately after it is published. Select No to disable the event source until you are ready to use it. Default is Yes. |
Event Source Property | Description |
---|---|
Enable Load Balancing | Required. Determines whether the connection must be deployed on all the Secure Agents in a group or on the selected Secure Agent for load balancing. You must enable this option only if the Process Server uses a Secure Agent Cluster configuration. Default is No. Note: After you publish a connection and run a process, if you toggle the load balancing option, you might see duplicate messages. To avoid this issue, Informatica recommends that you create a new connection if you want to change the load balancing option. |
Exchange Name | Optional. The exchange name where the produced messages are sent to. If left blank, the default exchange is used. |
Routing Key | Optional. The routing key to route the message to a queue. |
Queue | Required. The name of the RabbitMQ queue from where the messages can be consumed. |
Payload Format | Required. Specifies the type of message payload format you expect on the destination. Select one of the following options:
Default is TEXT. |
Object List Field Name | Optional. If the payload format is JSON, the queue accepts a JSON message that might contain an array of objects. If it does, enter the value here to be used as the field name of the object list in the RabbitMQ message body. |
Enable Dead Letter Routing | Optional. Select Yes to route faulty messages to a target dead letter queue. Note: If you have configured dead letter routing for the RabbitMQ broker, you must ensure that the Enable Dead Letter Routing field is disabled. Default is No. |
Dead Letter Exchange | Name of the dead letter exchange. If left blank, the default exchange is used. |
Dead Letter Routing Key | Routing key for the dead letter exchange to route the message to a dead letter queue. |
Other Attributes | Optional. If you need to set RabbitMQ advanced attributes for the event source, you can supply them here. Contact Informatica Global Customer Support for assistance. |
Enable Automatic Message Acknowledgement | Optional. Select Yes if you want messages to be automatically acknowledged. Note: If you have configured dead letter routing for the RabbitMQ broker, you must ensure that the Enable Automatic Message Acknowledgement field is disabled. Otherwise, messages will not be routed to the dead letter queue. Default is No. |
Prefetch Count | Optional. The maximum number of unacknowledged messages delivered on a RabbitMQ channel. Specify 0 to deliver unlimited unacknowledged messages. Default is 100. |