You are here: Reference Manual > FME Server Web Services > Notification Service > Subscribers > JMS Subscriber

JMS Subscriber

The JMS Subscriber receives notifications from topics and relays them to Java Message System (JMS)-compliant message brokers, such as IBM WebSphere MQ.

Setting up a JMS Message Broker with FME Server

Before configuring a JMS subscriber, you must set up a JMS broker to work with FME Server. The steps depend on the broker you use, and are explained in the following section (applicable to both the JMS Subscriber and JMS Publisher):

Creating a JMS Subscriber for FME Server

  1. In the FME Server Web User Interface, select Notifications > Subscriptions, and click New.
  2. Provide a name for the Subscription.
  3. Specify JMS for the protocol.
  4. Specify the Topics you want to subscribe to using the drop-down selector. To create a topic and use it right away, click +.

  5. Specify the JMS-specific fields for the subscriber
  6. Click OK.

Notification Content Template

The notification content template uses the following keywords in the incoming notification:

{

"location": "<location>"

"subscriber_content": "custom_message"

}

If the "subscriber_content" keyword is present, it overrides the Notification Content Template.

For example, consider the following Notification Content Template:

Hello, {Location}

If the incoming notification contains the following:

{

"location": "world"

}

The JMS subscriber sends the following message:

"Hello, world"

If the incoming notification contains the following:

{

"location": "world"

"subscriber_content": "My custom message"

}

The JMS subscriber sends the following message:

"My custom message"

See Also