The connector can expose collaborations as SOAP/JMS web services as well as enable collaborations to invoke SOAP/JMS web services. The requirements for using SOAP/JMS with the web services connector are as follows:
For SOAP/JMS, the connector uses JNDI to look up the connection factory using the JNDI context. During initialization, the connector reads the JNDI connector-specific property to connect to JNDI. If you do not configure a JNDI property, you will be unable to use SOAP/JMS. You can specify the following JNDI connector-specific properties:
Refer to your JNDI documentation for guidance in specifying these properties. To use SOAP/JMS with the connector, the following JNDI connector-specific properties are required:
If you set LookupQueuesUsingJNDI to true, make sure all the queues used by the connector can be looked up using JNDI.
To expose collaborations as SOAP/JMS web services, you must use the SOAP/JMS protocol listener. Using the SOAP/JMS protocol listener requires that you specify JNDI connector properties.
Your JMS provider configuration should reflect the requirements of the
SOAP/JMS protocol listener. Make sure all the queues required by the
SOAP/JMS protocol listener are defined by your JMS service provider. Be
sure to check your JMS provider documentation-- the task of defining
queues varies by provider. You must define six queues for the SOAP/JMS
protocol listener. You must set the queue names in SOAP/JMS listener
configuration properties and, if you have set
JNDI " LookupQueuesUsingJNDI to true, you also must specify
the JNDI names of the queues in the SOAP/JMS listener configuration
properties.
You should specify the queues names as the values of the following SOAP/JMS Listener configuration properties:
InputQueue and InProgressQueue are required properties. Make sure that you have correctly configured these queues.
ArchiveQueue, UnsubscribedQueue and ErrorQueue are optional properties. These queues are used to archive web service requests. If you plan to use any of these properties, make sure you have configured the corresponding JMS queues correctly. When defining these queues with your JMS provider, you should carefully specify the capacity of these queues.
To enable collaborations to invoke SOAP/JMS web services, you use the SOAP/JMS protocol handler. The SOAP/JMS protocol handler requires that you specify JNDI connector properties. Work with your web service provider to determine the JMS and JNDI requirements.
To invoke SOAP/JMS web services, the connector requires that the value of the Destination attribute in the SOAP/JMS Protocol Config MO be set to the input queue o f the target web service. If you have set JNDI " LookupQueuesUsingJNDI to true, you must specify the JNDI name of the input queue.
If you are invoking request-reply web services, you must work with your web service provider to determine the requirements for the ReplyTo queue. Make sure that the ReplyTo queue is defined. Also make sure that you have specified the name of the ReplyTo queue in the ReplyToQueue configuration property of the SOAP/JMS protocol handler. If JNDI " LookupQueuesUsingJNDI is set to true, the value of the ReplyToQueue configuration property should give the JNDI name of this queue.
It is important to note that, unlike protocol listeners, protocol handlers are not pluggable to the web services connector. As a result, the connector uses the same ReplyTo queue for all the request-reply web services that the connector invokes.