Configuring a permanent replyTo queue for JAX-RPC Web services using SOAP over JMS

When using two-way Web service communications using SOAP over JMS, it can be beneficial to configure a permanent replyTo queue on a JAX-RPC Web services client to prevent the client from having to create a temporary reply queue each time a Web service request is made.

About this task

A permanent replyTo queue is configured on the Web service client in one of the following ways:
  • Specify the optional replyToDestination property in the JMS endpoint URL.
  • Set the replyTo queue programmatically on the client JAX-RPC Stub or Call object. Setting the replyTo queue as a Stub or a Call property affects all requests that are invoked using that Stub or Call object.
  • Set the replyTo queue as a JVM System property. Setting the replyTo queue as a JVM System property affects all of your SOAP over JMS clients running in the particular JVM. If there are multiple clients in the same application that need to use a different replyTO queue, then the best option is to set the property programmatically.
Note: To set the permanent replyTo queue using any of these options, only client-side configuration is necessary. There is no configuration necessary on the Web service provider side.

Procedure

Results

Your Web services client can now receive SOAP/JMS messages to a permanent replyTo queue.



In this information ...


Related information

IBM Redbooks, demos, education, and more

(Index)

Use IBM Suggests to retrieve related content from ibm.com and beyond, identified for your convenience.

This feature requires Internet access.

Task topic Task topic    

Terms and conditions for information centers | Feedback

Last updatedLast updated: Aug 30, 2013 4:53:43 PM CDT
http://www14.software.ibm.com/webapp/wsbroker/redirect?version=pix&product=was-base-dist&topic=twbs_jmspermreplyto
File name: twbs_jmspermreplyto.html