...
- WSO2 MB should be installed and set up. See Setting up WSO2 Message Broker.
WSO2 ESB should installed and set up. See Setting up WSO2 ESB. Specific entries that are required to be added to the
<ESB_HOME>/repository/conf/jndi.propertiesfile for this use case are as follows.
Item Value Queue queue.SMSStore=SMSStoreQueue queue.SMSReceiveNotificationStore=SMSReceiveNotificationStoreConnection Factory connectionfactory.QueueConnectionFactory = amqp://admin:admin@clientID/carbon?brokerlist='tcp://localhost:5673'
Configuring the JMS publisher
...
The endpoint of this proxy service uses the following properties to map the proxy service with WSO2 MB.
| Property | Value for this use case | Description |
|---|---|---|
address uri | jms:/SMSStore | The destination in which the request received by the proxy service is stored. |
java.naming.factory.initial | org.wso2.andes.jndi.PropertiesFileInitialContextFactory | This property specifies the initial context factory to use. The value specified here should be the same as that specified in |
| java.naming.provider.url | repository/conf/jndi.properties | The location of the JNDI service provider. |
transport.jms.DestinationType | queue | The destination type of the JMS message that will be generated by the proxy service. |
| transport.jms.ReplyDestination | SMSReceiveNotificationStore | The destination in which the response generated by the back-end service is stored. |
Since this is a two-way invocation, the OUT_ONLY property is not set in the In sequence.
...
Execute the following command from the the <ESB_HOME>/sample/axis2Client directory to invoke the SMSSenderProxy proxy service you defined as the JMS publisher.
...