TIBCO EMS Integration
The following example demonstrates how to configure Mule to use the TIBCO Enterprise Message Server (EMS) with authentication in place.
<?xml version="1.0" encoding="UTF-8"?>
<mule xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns:spring="http://www.springframework.org/schema/beans"
xmlns="http://www.mulesoft.org/schema/mule/core"
xmlns:jms="http://www.mulesoft.org/schema/mule/jms"
xsi:schemaLocation="
http://www.springframework.org/schema/beans http://www.springframework.org/schema/beans/spring-beans-current.xsd
http://www.mulesoft.org/schema/mule/core http://www.mulesoft.org/schema/mule/core/3.4/mule.xsd
http://www.mulesoft.org/schema/mule/jms http://www.mulesoft.org/schema/mule/jms/3.4/mule-jms.xsd">
<jms:connector name="jmsConnector"
jndiProviderUrl="tibjmsnaming://host:port"
connectionFactoryJndiName="QueueConnectionFactory"
username="username"
password="password"
jndiDestinations="true"
forceJndiDestinations="true"
jndiInitialFactory="com.tibco.tibjms.naming.TibjmsInitialContextFactory"
specification="1.1">
<spring:property name="jndiProviderProperties">
<spring:map>
<spring:entry key="java.naming.security.principal" value="jndiUsername"/>
<spring:entry key="java.naming.security.credentials" value="jndiPassword"/>
</spring:map>
</spring:property>
</jms:connector>
...Note that when you use tibjmsnaming as the protocol in your jndiProviderUrl, you can also specify TCP or SSL with the JNDI property com.tibco.tibjms.naming.security_protocol.
For XA transactions, you must create an XA Connection Factory from the TIBCO administration-tool (tibemsadmin) as follows:
> create factory XAQueueConnectionFactory xaqueue url=tcp://7222