Oracle® Fusion Middleware
Part 4. Messaging

You can configure a global JMS service under the External Connections node in Policy Studio by right-clicking the JMS Services node, and selecting Add a JMS Service. The details entered in the JMS Service dialog can then be used by the API Gateway to drop messages on to a JMS queue or topic, or to read messages from a JMS queue or topic. For more details, see the following filters:

Alternatively, you can configure a JMS service at the API Gateway instance level, and configure the API Gateway to consume a JMS queue or topic. Right-click the instance under the Listeners node in the Policy Studio, and select JMS Wizard.

Configure the following fields on the JMS Service tab:

Name:

Enter a descriptive name for the JMS provider in the Name field.

Service type:

Select one of the following from the list:

The following settings are displayed when you select a Service Type of Embedded Apache ActiveMQ, Apache ActiveMQ, or Standard JMS:

Provider URL:

Enter the URL of the JMS provider. For example, a URL for a JBoss application server might be jnp://localhost:1099. Defaults to local for Embedded Apache ActiveMQ.

Initial Context Factory:

API Gateway uses a connection factory to create a connection with a JMS provider. A connection factory encapsulates a set of connection configuration parameters that have been defined by the administrator. The following are some example default values:

Connection Factory:

Enter the name of the connection factory to use when connecting to the JMS provider. The name of the connection factory is vendor-specific. For example, the connection factory for the JBoss application server is org.jnp.interfaces:javax.jnp. Defaults to connectionFactory for embedded and external ActiveMQ.

The following settings are displayed when you select a Service Type of IBM MQ:

Host name:

Enter the host name of the JMS provider (for example, localhost).

Port number:

Enter the port number of the JMS provider (for example, 1414).

Queue manager:

Enter the virtual queue manager name by which IBM WebSphere Application Server is known to WebSphere MQ (for example, TEST_BUS).

Channel:

Enter the IBM WebSphere MQ channel name on the WebSphere MQ system (for example, MY_QM.TO.TEST_BUS).

Initial Context Factory:

The API Gateway uses a connection factory to create a connection with a JMS provider. A connection factory encapsulates a set of connection configuration parameters that have been defined by the administrator. Defaults to com.vordel.jms.ibm.mq.InitialContextFactory.

Connection Factory:

Enter the name of the connection factory to use when connecting to the JMS provider. Defaults to connectionFactory.

The following optional settings are common to all service types:

Username:

If a user name is required to connect to this JMS provider, enter it here.

Password:

Enter the password for this user.

Custom Message Properties:

You can add JNDI context settings by clicking Add, and entering name and value properties in the fields.

For the Embedded Apache ActiveMQ service type, you can define Apache ActiveMQ URI parameters using JNDI properties. For example, see the following:

You can configure the following options on the Advanced Settings tab:

When the JMS service has been configured, you can configure the API Gateway to drop messages on to a queue or topic exposed by this service. You can do this when configuring a policy by selecting the service in the Send to JMS or Read from JMS filters. For more details, see the following:

You can also configure JMS sessions for the newly added JMS service at the API Gateway instance level. For more details, see Configure a JMS session.