Using Enable JMS/AMQP for a SOAP API

This policy is used to expose a SOAP API over JMS/AMQP. A SOAP API can be exposed as HTTP/HTTPS or JMS/AMQP as the policies Enable HTTP/HTTPS and Enable JMS/AMQP are mutually exclusive.

If you are using JMS with Message Broker native protocol support ensure that following actions are performed before using the Enable JMS/AMQP policy:

Create an alias to a JNDI Provider. For a detailed procedure, see Creating a JNDI Provider Alias.

Configure API Gateway to use a JMS connection alias to establish an active connection between API Gateway and the JMS provider. For a detailed procedure, see Creating a JMS Connection Alias.

Create a WS (Web Service) JMS Provider endpoint alias and configure the Alias, Description, Type (Provider), Transport Type (JMS) fields and JMS Transport Properties. For a detailed procedure, see Creating an Endpoint Alias for a Provider Web Service Descriptor.

Configure a WS (Web Service) endpoint trigger. For detailed procedures, see .

If you are using JMS with AMQP protocol support, ensure the following before using the Enable JMS/AMQP policy:

You have configured API Gateway for JMS with AMQP. For details, see Configuring API Gateway for JMS with AMQP Protocol

The table lists the properties that you can specify for this policy:

Parameter	Description
JMS Provider Endpoint Alias	Specifies the name of the JMS provider endpoint alias. The provider endpoint alias specifies the trigger which listens to the source queue or topic for the input message.
SOAP Version	Specifies the SOAP version of the requests which the API Gateway accepts from the client. Select one of the following: SOAP 1.1. This is selected by default. API Gateway accepts requests that are in the SOAP 1.1 format. SOAP 1.2. API Gateway accepts requests that are in the SOAP 1.2 format.