Configure the connector
Mule provides a JMS connector and a WebLogic JMS connector, both can be used here:
<jms:connector name="JMS" username="weblogic" password="welcome1" validateConnections="true" jndiInitialFactory="weblogic.jndi.WLInitialContextFactory" jndiProviderUrl="t3://localhost:7001" connectionFactoryJndiName="myfactory" doc:name="JMS"/>
or
<jms:weblogic-connector name="Web_logic_JMS" username="weblogic" password="welcome1" validateConnections="true" jndiInitialFactory="weblogic.jndi.WLInitialContextFactory" jndiProviderUrl="t3://localhost:7001" connectionFactoryJndiName="myfactory" doc:name="Web logic JMS"/>
Configure the endpoint
When configuring the JMS endpoint, we need to be careful on the name to use, because there are 2 ways to specify the name:
1) use JNDI name
To use JNDI name, we need to add a Spring property to the connector:
<jms:connector name="JMS" username="weblogic" password="welcome1" validateConnections="true" jndiInitialFactory="weblogic.jndi.WLInitialContextFactory" jndiProviderUrl="t3://localhost:7001" connectionFactoryJndiName="myfactory" doc:name="JMS">
<spring:property name="jndiDestinations" value="true"/>
</jms:connector>
or:
<jms:weblogic-connector name="Web_logic_JMS" username="weblogic" password="welcome1" validateConnections="true" jndiInitialFactory="weblogic.jndi.WLInitialContextFactory" jndiProviderUrl="t3://localhost:7001" connectionFactoryJndiName="myfactory" doc:name="Web logic JMS">
<spring:property name="jndiDestinations" value="true"/>
</jms:weblogic-connector>
Then we can just use the JNDI name in endpoint:
<jms:inbound-endpoint queue="jms.TestQueue" connector-ref="Web_logic_JMS" doc:name="JMS"/>
Note: using '.' or '/' does NOT make a difference here. The following works too:
<jms:inbound-endpoint queue="jms/TestQueue" connector-ref="Web_logic_JMS" doc:name="JMS"/>
2) use complete WebLogic JMS name
By default, if nothing set, it's using name, and the format is: JMS_Server_Name/JMS_ModuleName!JMS_Queue_Name, so in this case, it's:
<jms:inbound-endpoint queue="JMSServer/SystemModule-0!Queue-0" connector-ref="Web_logic_JMS" doc:name="JMS"/>
001118896

We use three kinds of cookies on our websites: required, functional, and advertising. You can choose whether functional and advertising cookies apply. Click on the different cookie categories to find out more about each category and to change the default settings.
Privacy Statement
Required cookies are necessary for basic website functionality. Some examples include: session cookies needed to transmit the website, authentication cookies, and security cookies.
Functional cookies enhance functions, performance, and services on the website. Some examples include: cookies used to analyze site traffic, cookies used for market research, and cookies used to display advertising that is not directed to a particular individual.
Advertising cookies track activity across websites in order to understand a viewer’s interests, and direct them specific marketing. Some examples include: cookies used for remarketing, or interest-based advertising.