When using two-way Web service communications using the industry standard SOAP over JMS protocol, you can benefit from configuring a permanent reply queue on a Java API for XML Web Services (JAX-WS) or Java API for XML-based RPC (JAX-RPC) Web services client. The use of a permanent reply queue can improve performance because this reply queue prevents the client from having to create a temporary reply queue each time a Web services request is invoked.
To set the permanent reply queue using any of these options, only client-side configuration is necessary. There is no configuration necessary for the Web service provider.
Use the typical administrative functions of the JMS messaging provider to create the permanent reply queue prior to configuring the reply queue with the Web services client.
jms:jndi:jms/MyRequestQueue&jndiConnectionFactoryName=jms/MyCF&replyToName=jms/MyReplyQueue
((BindingProvider) port).getRequestContext().put (com.ibm.wsspi.webservices.Constants.JMS_REPLY_QUEUE_JNDI_NAME, "jms/MyReplyQueue");
((javax.xml.rpc.Stub) stub)._setProperty(com.ibm.wsspi.webservices.Constants.JMS_REPLY_QUEUE_JNDI_NAME, "jms/MyReplyQueue");
java -Dcom.ibm.websphere.webservices.JMSReplyQueueJndiName=jms/MyReplyQueue
Set a JVM system property using the administrative console for the application server that runs the Web service client application.
To set custom properties, log on to the administrative console, and navigate to the Java virtual machine custom properties panel.
Your Web services client can now receive SOAP overJMS messages from a permanent reply queue.
In this information ...Related tasks
| IBM Redbooks, demos, education, and more(Index) |