The following diagram depicts quad-channel JMS synchronous invocations of the WSO2 Enterprise Integrator (WSO2 EI).
The following example code shows configuration of WSO2 EI for quad-channel JMS synchronous invocations.
Code Block | ||||
---|---|---|---|---|
| ||||
<proxy name="QuadJMS" transports="jms" xmlns="http://ws.apache.org/ns/synapse">
<target>
<inSequence>
<property action="set" name="transport.jms.ContentTypeProperty" value="Content-Type" scope="axis2"/>
<log level="full" xmlns="http://ws.apache.org/ns/synapse"/>
<send>
<endpoint>
<address uri="jms:/BEReq?transport.jms.ConnectionFactoryJNDIName=QueueConnectionFactory&java.naming.factory.initial=org.apache.activemq.jndi.ActiveMQInitialContextFactory&java.naming.provider.url=tcp://localhost:61616&transport.jms.DestinationType=queue&transport.jms.ReplyDestination=BERes"/>
</endpoint>
</send>
</inSequence>
<outSequence>
<send/>
</outSequence>
</target>
<parameter name="transport.jms.ContentType">
<rules>
<jmsProperty>contentType</jmsProperty>
<default>text/xml</default>
</rules>
</parameter>
<parameter name="transport.jms.Destination">ClientReq</parameter>
</proxy> |
...