IBM proprietary JMS endpoint URL syntax (deprecated)

A Java™ Message Service (JMS) endpoint URL is used to access Java API for XML Web Services (JAX-WS) or Java API for XML-based RPC (JAX-RPC) Web services with the JMS transport. This proprietary URL specifies the Java Message Service (JMS) destination and connection factory, as well as the port component name for the Web service request. This endpoint URL is similar to the HTTP endpoint URL, which specifies the host and port as well as the context root and port component name.

Deprecated feature: In earlier versions of the application server, an IBM® proprietary SOAP over JMS protocol was supported for Java API for XML-based RPC (JAX-RPC) applications. In WebSphere® Application Server 7.0, this proprietary SOAP over JMS protocol is now deprecated in favor of an emerging industry standard SOAP over JMS protocol. You can use the IBM proprietary SOAP over JMS protocol with your Java API for XML Web Services (JAX-WS) or JAX-RPC Web services; however, take advantage of the emerging standard SOAP over JMS protocol. If your client application invokes enterprise beans-based Web services that are supported by an earlier version of the WebSphere Application Server, you must continue to use the IBM proprietary SOAP over JMS protocol to access those Web services. depfeat
Supported configurations: A JMS endpoint URL has the following general form:
jms:/[queue|topic]?<property>=<value>&<property>=<value>&...
The URL consists of the jms: transport type, followed by either /queue or /topic to indicate the JMS destination type, followed by the query string containing a list of property and value pairs that are used to specify the JMS endpoint information.sptcfg

The properties supported in the URL string are described in the following tables:

Table 1. Destination-related properties (required). Use these properties to specify destination-related properties for a JMS endpoint URL.
Property name Description
destination Specifies the Java Naming and Directory Interface (JNDI) name of the destination queue or topic.
connectionFactory Specifies the JNDI name of the connection factory.
targetService Specifies the name of the port component to which the request is dispatched.
Table 2. JNDI-related properties (optional). Use these properties to specify JNDI-related properties for a JMS endpoint URL.
Property name Description
initialContextFactory Specifies the name of the initial context factory to use which is mapped to the java.naming.factory.initial property.
jndiProviderURL Specifies the JNDI provider URL, which is mapped to the java.naming.provider.url property.
Table 3. JMS-related properties (optional). Use these properties to specify JMS-related properties for a JMS endpoint URL.
Property name Description
deliveryMode Indicates whether the request message is persistent or not. The valid values are 1 for nonpersistent and 2 for persistent. The default value is 1.
timeToLive Specifies, in milliseconds, the lifetime of the JMS request message. The default value of 0 indicates an infinite lifetime. However, when you are using Web Services, this property is bounded by the value that is specified for the synchTimeout property. The setting for the synchTimeout property determines how long a client waits for a response from the server. This bounding prevents the JMS message from remaining active after the client has stopped waiting for a response from the server.
priority Specifies the JMS priority associated with the request message. Valid values are between 0 to 9. The default value is 4. A value of 0 is the lowest priority and a value of 9 is the highest priority.
replyToDestination Specifies the JNDI name of a queue to be used to receive reply messages. Using this optional property enables the client to use a permanent queue, rather than a temporary queue, for receiving replies.

If you set values for the deliveryMode, timeToLive, and priority properties on the JMS request, these values are propagated from the JMS request message to the corresponding JMS reply message.

The required properties, destination, connectionFactory, and targetService must be contained in the JMS endpoint URL string. The rest of the properties are optional.

You can set any of the properties on the client Stub object. The various properties can be specified by including them as part of the endpoint URL or you can set these properties programmatically by the client on the Stub object. Properties specified on the client Stub object take precedence over properties that are specified as part of a JMS endpoint URL string.




Related tasks
Using SOAP over JMS to transport Web services
Configuring a permanent replyTo queue for JAX-RPC Web services using SOAP over JMS (deprecated)
Invoking one-way JAX-RPC Web service requests transactionally using the JMS transport (deprecated)
Related information
IBM proprietary SOAP over JMS protocol (deprecated)
Reference topic    

Terms of Use | Feedback

Last updated: Oct 20, 2010 11:50:58 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=compass&product=was-base-iseries&topic=rwbs_jmsurl
File name: rwbs_jmsurl.html