Working with JMS

Liz Sanderson
Liz Sanderson
  • Updated

As of FME Server 2021+, this functionality can be completed using FME Server Streams. For more information, please see FME and Stream Processing.


FME Server brings real-time spatial data transformation to enterprise environments using the Java Message Service (JMS). JMS is an industry standard for communicating between distributed systems. Software vendors and products that support JMS include:

  • Oracle (Advanced Queuing, Weblogic)
  • IBM (WebSphere)
  • Microsoft (BizTalk)
  • Informatica (PowerExchange)
  • Adeptia (ESB Studio)
  • Apache (ActiveMQ)
  • Redhat (JBoss)
  • SAP
  • Cisco
  • and many more

FME Server provides two options for working with JMS based on the rate of incoming/outgoing messages:

  • Notification Service - flexible
  • Message Streaming - high capacity


Notification Service

The Notification Service offers the most flexible configuration due to it's loosely coupled publish and subscribe pattern. Messages can be sent to topics and multiple clients can receive and process those messages. Subscriptions and Publications can be created in the FME Server Web Interface, where you select the JMS protocol and provide the connection details.

Get started with JMS and the Notification service.


Message Streaming

The Message Streaming capability allows for message rates higher than 1 per second up to 1000s per second by locking an FME Engine onto a JMS stream. The FME Engine continuously runs a workspace, which contains one or both of the JMS transformers:

  • JMSSender
  • JMSReceiver

High Capacity Message Streaming

Was this article helpful?



Please sign in to leave a comment.