Configuring SOAP Over JMS Protocol
Mediator supports "SOAP over JMS" protocols (or "SOAP-JMS" for short) for sending messages between Web services. You can:
Create SOAP-JMS provider Web service endpoint aliases and SOAP-JMS triggers.If a virtual service's "Entry Protocol Step" is set to JMS, a
provider Web service endpoint alias is used to construct the endpoint reference, the JMS bindings, or both when consumers request the Web service. These endpoint aliases can be used by
Mediator or JMS provider Web service descriptors to facilitate SOAP-JMS messaging. For more information, see
Creating SOAP-JMS Web Service Endpoint Aliases.
You must also create a SOAP-JMS trigger to receive and send SOAP-JMS messages.
Create SOAP-JMS consumer Web service endpoint aliases. If a virtual service's "Routing Protocol" is set to JMS, a
consumer Web service endpoint alias is used at run-time to generate a request and invoke an operation of the Web service. These endpoint aliases can be used by
Mediator or JMS consumer Web service descriptors to facilitate SOAP-JMS messaging. For more information, see
Creating a SOAP-JMS Consumer Web Service Endpoint Alias.
Because the behavior and configuration of SOAP-JMS protocols is similar to those of other JMS protocols in Integration Server, you must be familiar with its JMS configuration procedures. For more information about configuring JMS protocols in Integration Server, see webMethods Integration Server Administrator’s Guide.
