WSO2 MB Message Store
- Former user (Deleted)
WSO2 Enterprise Integrator (WSO2 EI) is shipped with a separate message broker profile (WSO2 MB). You can easily set up this WSO2 MB profile as the message store for the ESB. Explained below are the parameters you need to configure for a WSO2 MB Message Store. Also, find details of other configurations that are relevant to the WSO2 MB Message Store.
See the following topics for details:
WSO2 MB Message Store parameters
Use this link for instructions on how to create a message store artifact for the ESB. Be sure to set the message store type as WSO2 MB Message Store, and configure the parameters as explained below.
Listed below are the required parameters for configuring the WSO2 MB Message Store.
Parameter Name | Description |
|---|---|
| Message Store Name | Give a unique name for the JMS message store. |
| Message Store Type | Select WSO2 MB Message Store from the list of options. |
| Initial Context Factory | This specifies the JNDI initial context factory class (java.naming.factory.initial). This class implements the implement the java.naming.spi.InitialContextFactory interface. The value is set to org.wso2.andes.jndi.PropertiesFileInitialContextFactory, by default. |
| Queue Connection Factory | This is the connection factory URlfor connecting to WSO2 MB. By default, the value is set to Important! Be sure to change the port to 5675. |
| JNDI Queue Name | The name of the queue in the broker that will store messages. |
| JMS API Specification Version | The JMS API version to be used. Possible values are 1.1 or 1.0. The value is set to 1.1, by default. |
If you need to ensure guaranteed delivery of your messages, specify values for the following parameters:
Parameter Name | Description |
|---|---|
| Enable Producer Guaranteed Delivery | This flag specifies whether guaranteed delivery is enabled on the producer side. The value is set to False, by default. |
| Failover Message Store | The message store to which the store mediator should send messages when the original message store fails. |
Other configurations
When you use the Message Broker profile as the message broker and configure a Message Processor with max.delivery.attempts, if the Message Broker profile does not get an acknowledgment from the Integration profile, it re-sends the message that results in duplicate messages being delivered. To avoid this, add the following line in the <EI_HOME>/bin/integrator.sh file:
-DAndesAckWaitTimeOut=3600000 \
Related topics
- See the tutorial on Storing and Forwarding Messages.
- Read more about this use case: Store and Forward Using JMS Message Stores.