LibraryLink ToToggle FramesPrintFeedback

Using Configuration

JMS endpoints are configured using Spring configuration. You can configure the server-side and consumer-side transports independently.

The JMS address information is provided using the jms:address element and its child, the jms:JMSNamingProperties element. The jms:address element’s attributes specify the information needed to identify the JMS broker and the destination. The jms:JMSNamingProperties element specifies the Java properties used to connect to the JNDI service.

[Note]Note

Information in the configuration file will override the information in the endpoint's WSDL file.

You configure a JMS endpoint using one of the following configuration elements:

jms:conduit

The jms:conduit element contains the configuration for a consumer endpoint. It has one attribute, name, whose value takes the form {WSDLNamespace}WSDLPortName.jms-conduit.

jms:destination

The jms:destination element contains the configuration for a provider endpoint. It has one attribute, name, whose value takes the form {WSDLNamespace}WSDLPortName.jms-destination.

JMS connection information is specified by adding a jms:address child to the base configuration element. The jms:address element uses the attributes described in Table 6.1 to configure the connection to the JMS broker.


To increase interoperability with JMS and JNDI providers, the jms:address element has a child element, jms:JMSNamingProperties, that allows you to specify the values used to populate the properties used when connecting to the JNDI provider. The jms:JMSNamingProperties element has two attributes: name and value. name specifies the name of the property to set. value attribute specifies the value for the specified property. jms:JMSNamingProperties element can also be used for specification of provider specific properties.

The following is a list of common JNDI properties that can be set:

  1. java.naming.factory.initial

  2. java.naming.provider.url

  3. java.naming.factory.object

  4. java.naming.factory.state

  5. java.naming.factory.url.pkgs

  6. java.naming.dns.url

  7. java.naming.authoritative

  8. java.naming.batchsize

  9. java.naming.referral

  10. java.naming.security.protocol

  11. java.naming.security.authentication

  12. java.naming.security.principal

  13. java.naming.security.credentials

  14. java.naming.language

  15. java.naming.applet

For more details on what information to use in these attributes, check your JNDI provider’s documentation and consult the Java API reference material.

Example 6.1 shows a FUSE Services Framework configuration entry for configuring the addressing information for a JMS consumer endpoint.