Fuse ESB Enterprise - Using the Web Services Bindings and Transports

Provider configuration

Overview

The provider specific configuration allows you to specify two types of properties:

JMS messaging qualities of service
JMS runtime behaviors

Configuration elements

Provider endpoint configuration is specified using the jms:destination element. It has two children:

jms:runtimePolicy—configures the JMS qualities of service
jms:serverConfig—configures the runtime behavior

Quality of service configuration

The jms:runtimePolicy element specifies the qualities of service for the provider endpoint. Table 21 describes the attributes used to configure the qualities of service.

Table 21. Provider Endpoint Configuration

Attribute	Description
`useMessageIDAsCorrealationID`	Specifies whether the JMS broker will use the message ID to correlate messages. The default is `false`.
`durableSubscriberName`	Specifies the name used to register a durable subscription.
`messageSelector`	Specifies the string value of a message selector to use. For more information on the syntax used to specify message selectors, see the JMS 1.1 specification.
`transactional`	Specifies whether the local JMS broker will create transactions around message processing. The default is `false`.[a]
^[a]Currently,setting the `transactional` attribute to `true` is not supported by the runtime.

Runtime configuration

You configure provider runtime behavior using the jms:serverConfig element. It has two attributes that are used to specify the configurable runtime properties of a provider endpoint:

messageTimeToLive: The messageTimeToLive attribute specifies the amount of time, in milliseconds, that a response can remain unread before the JMS broker is allowed to delete it. The default is 0 which specifies that the message can live forever.
durableSubscriptionClientId: The durableSubscriptionClientId attribute specifies the client identifier the endpoint uses to create and access durable subscriptions.

Example

Example 67 shows a Fuse Services Framework configuration entry for configuring a provider endpoint.

Example 67. Configuration for a Provider Endpoint

<beans xmlns="http://www.springframework.org/schema/beans"
       xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
       xmlns:ct="http://cxf.apache.org/configuration/types"
       xmlns:jms="http://cxf.apache.org/transports/jms"
       xsi:schemaLocation="http://www.springframework.org/schema/beans
                             http://www.springframework.org/schema/beans/spring-beans.xsd
                           http://cxf.apache.org/jaxws
                             http://cxf.apache.org/schemas/jaxws.xsd
                           http://cxf.apache.org/transports/jms
                             http://cxf.apache.org/schemas/configuration/jms.xsd">
   ...
  <jms:destination name="{http://cxf.apache.org/jms_endpt}HelloWorldJMSPort.jms-destination">
    ...
    <jms:runtimePolicy messageSelector="cxf_message_selector"
                       useMessageIDAsCorrelationID="true"
                       transactional="true"
                       durableSubscriberName="cxf_subscriber" />
  <jms:serverConfig messageTimeToLive="500"
                    durableSubscriptionClientId="jms-test-id" />
  </jms:destination>
  ...
</beans>

Comments powered by Disqus