JMS Transport Mechanism • The JMS transport mechanism is based on the SOAP over JMS specification. • Two JMS queues are used per communication channel (one for requests and another for responses) to simulate synchronous communication. • Each individual request is synchronous. The system places the message on the request queue and waits for a reply to arrive on the response queue. • TextMessage or BytesMessage JMS message classes can be used. In both cases message must be a valid MultiSpeak message. • Requests and responses are connected through JMSCorrelationID JMS header. • In the request message, the JMS header JMSReplyTo must contain the queue where response message should be sent. • SOAP protocol versions 1.1 and 1.2 are supported. • There is no support for accessing a WSDL over JMS. The following table describes how JMS message properties, specific to SOAP over JMS, are being used: JMS Message Property Value SOAPJMS_bindingVersion "1.0" SOAPJMS_targetServer "SCADA_Server" or "OA_Server" depending on the target system SOAPJMS_soapAction SOAP action SOAPJMS_contentType "text/xml; charset="utf-8"" SOAPJMS_isFault "true" for SOAP fault messages