About this task
Deprecated feature: In WebSphere
® Application Server 7.0,
the IBM proprietary
SOAP over JMS protocol is now deprecated in favor of the emerging industry
standard 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, you are encouraged
to take advantage of the SOAP over JMS protocol standard. This task describes
configuring a permanent replyTo queue when using the IBM proprietary SOAP over JMS transport.
To learn more about the SOAP over JMS standard, see the using SOAP over JMS
to transport Web services documentation.
depfeat
A permanent replyTo queue
is configured on the Web services 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 Java virtual machine (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.