Require JMS

If you have a native API that requires clients to communicate with the server using the Java Message Service (JMS) protocol, you can use the Require JMS protocol action.

This action allows you to bridge protocols between the client and the native API. For example, suppose you have a native API that is exposed over JMS and a client that submits SOAP requests over HTTP. In this situation, you can configure the API’s Require JMS Protocol action to accept SOAP requests over JMS and configure its JMS Routing Rule action to route the request to the web service using JMS.

When this action is configured for a proxy API, you can intentionally expose an API over a JMS protocol. For example, if you have a native API that is exposed over HTTP, you might expose the API over JMS simply to gain the asynchronous-messaging and guaranteed-delivery benefits that one gains by using JMS as the message transport.

Create an alias to a JNDI Provider (in the Integration Server Administrator, go to Settings > Web Services).

To establish an active connection between Integration Server and the JMS provider, you must configure Integration Server to use a JMS connection alias (in the Integration Server Administrator, go to Settings > Messaging > JMS Settings).

Create a WS (Web Service) endpoint alias for provider Web Service Descriptor (WSD) that uses a JMS binder. In the Integration Server Administrator, navigate to Settings > Web Services and complete the Alias Name, Description, Descriptor Type, and Transport Type fields.

Configure a WS (Web Service) endpoint trigger (in the Integration Server Administrator, go to Settings > Messaging > JMS Trigger Management).

Create a WS (Web Service) endpoint alias for consumer Web Service Descriptor (WSD) that has a JMS binder. In the Integration Server Administrator, navigate to Settings > Web Services and complete the Alias Name, Description, Descriptor Type, and Transport Type fields.

Additionally, in the API's Message Flow, ensure that you delete the predefined Require HTTP / HTTPS Protocol action from the Receive stage. This is because, these actions are mutually exclusive.

JMS Provider Alias	(String). Specify the name of Integration Servers, JMS provider alias. The alias should include the JNDI destination name and the JMS connection factory.
SOAP Version	(String). Specify the SOAP version of the requests which the Mediator accepts from the client.
	Value	Description
	SOAP 1.1	(Default). Mediator accept srequests that are in the SOAP 1.1 format.
	SOAP 1.2	Mediator accepts requests that are in the SOAP 1.2 format.