FME Transformers: 2026.1
AzureServiceBusConnector
Connects to Azure Service Bus to send and receive messages.
Typical Uses
-
Sending and receiving messages from a queue or topic
How does it work?
The AzureServiceBusConnector uses your account credentials to connect to Azure Service Bus and perform various tasks:
| Action | Task |
|---|---|
|
Count Messages |
Count available messages in a queue or subscription. |
|
Receive from Queue |
Receive messages from a queue. |
|
Receive from Subscription |
Receive messages from a subscription. |
|
Send to Queue |
Send messages to a queue. |
|
Send to Topic |
Send messages to a topic. |
Optional Input Port
This transformer has two modes, depending on whether a connector is attached to the Input port or not:
- Input-driven: When input features are connected, the transformer runs once for each feature it receives in the Input port.
- Run Once: When no input features are connected, the transformer runs one time.
When the Input port is in use, the Initiator output port is also enabled.
Heartbeat
When Action is Receive from Queue or Receive from Subscription and the connection is still alive (Receive Mode is Stream or a batch is not yet complete), heartbeat features are output at a specified interval after a period of non-activity.
Heartbeat features have two attributes:
- _heartbeat_id: Integer starting at 0. This is a unique identifier for each heartbeat feature output from this port.
- _heartbeat_counter: Integer starting at 0 that resets whenever the connector receives a new message and a new period of inactivity begins. This counter represents the number of consecutive heartbeat features.
Usage Notes
- See Azure Service Bus Messaging documentation for further information about the service.
Configuration
Input Ports
This transformer accepts any feature.
Output Ports
Features with added attributes, as specified in parameters and according to Action:
|
Action |
Output - Input-Driven |
Output - Run Once |
|---|---|---|
|
Count Messages |
Input feature with a message count. |
One new feature with a message count. |
|
Receive from Queue |
Multiple features, one for each message received, with details about the message. |
Multiple features, one for each message received, with details about the message. |
|
Receive from Subscription |
Multiple features, one for each message received, with details about the message. |
Multiple features, one for each message received, with details about the message. |
|
Send to Queue |
Input feature with details about the sent message. |
New feature with details about the sent message. |
|
Send to Topic |
Input feature with details about the sent message. |
New feature with details about the sent message. |
When Action is Receive, heartbeat features are output through this port.
When the optional Input port is used, input features are output here unmodified, in addition to any other output locations (Output or <Rejected>).
Features that cause the operation to fail are output through this port. An fme_rejection_code attribute describing the category of the error will be added, along with a more descriptive fme_rejection_message which contains more specific details as to the reason for the failure.
If an Input feature already has a value for fme_rejection_code, this value will be removed.
Rejected Feature Handling: can be set to either terminate the translation or continue running when it encounters a rejected feature. This setting is available both as a default FME option and as a workspace parameter.
Parameters
|
Credential Source |
Select the type of credentials to use:
|
||
|
Account |
When Credential Source is Web Connection, select or create a Web Connection connecting to a Azure Service Bus Web Service. |
||
|
Namespace |
When Credential Source is Default Azure Credential, provide the Service Bus Namespace containing Queues or Topics. The value is typically a hostname under servicebus.windows.net. |
||
|
Embedded Credentials |
When Credential Source is Embedded:
|
|
Action |
Select an operation to perform. Choices include:
|
|
Event Hubs |
Specify the event hub to connect to. |
Count Messages Options
|
Resource |
Select the resource type to count available messages on:
|
|
Resource |
When Resource is Subscription, provide the message topic. |
|
Resource |
When Resource is Subscription, provide the subscription name. |
|
Resource |
When Resource is Queue , provide the queue name. |
Output Attributes
|
Attributes to Add |
Select any available attributes to be included on the output features:
|
Receive Options
|
Queue |
Specify the queue to receive from. |
|
Delete on Receive |
Select a message deletion option:
|
|
Receive Mode |
Select a message receiving method:
|
|
Batch Size |
When Receive Mode is Batch, specify the number of messages to read per batch. |
Heartbeat
|
Interval |
Specify the duration of a period of inactivity before a heartbeat feature is emitted, in Time Units. Default is 1. |
|
Time Unit |
Select the Interval unit:
|
Output Attributes
|
Attributes to Add |
Select any available attributes to be included on the output features:
|
Receive Options
|
Topic |
Specify the topic to receive from. |
|
Subscription |
Specify the subscription to receive from. |
|
Delete on Receive |
Select a message deletion option:
|
|
Receive Mode |
Select a message receiving method:
|
|
Batch Size |
When Receive Mode is Batch, specify the number of messages to read per batch. |
Heartbeat
|
Interval |
Specify the duration of a period of inactivity before a heartbeat feature is emitted, in Time Units. Default is 1. |
|
Time Unit |
Select the Interval unit:
|
Output Attributes
|
Attributes to Add |
Select any available attributes to be included on the output features:
|
Send Options
|
Queue |
Specify the queue to send messages to. |
|
Create Queue |
If the specified Queue does not exist, select an action:
|
|
Payload |
Provide the message content. This is often JSON, but can be any string, binary, integer or floating-point value. |
|
Message Properties |
(Optional) Set any additional properties. Any key value can be used, however, the following keys are mapped to their respective message attributes:
|
Output Attributes
|
Attributes to Add |
Select any available attributes to be included on the output features:
|
Send Options
|
Topic |
Specify the topic to send messages to. |
|
Create Topic |
If the specified Topic does not exist, select an action:
|
|
Payload |
Provide the message content. This is often JSON, but can be any string, binary, integer or floating-point value. |
|
Message Properties |
(Optional) Set any additional properties. Any key value can be used, however, the following keys are mapped to their respective message attributes:
|
Output Attributes
|
Attributes to Add |
Select any available attributes to be included on the output features:
|
Editing Transformer Parameters
Transformer parameters can be set by directly entering values, using expressions, or referencing other elements in the workspace such as attribute values or user parameters. Various editors and context menus are available to assist. To see what is available, click
beside the applicable parameter.
Defining Values
There are several ways to define a value for use in a Transformer. The simplest is to simply type in a value or string, which can include functions of various types such as attribute references, math and string functions, and workspace parameters.
Using the Text Editor
The Text Editor provides a convenient way to construct text strings (including regular expressions) from various data sources, such as attributes, parameters, and constants, where the result is used directly inside a parameter.
Using the Arithmetic Editor
The Arithmetic Editor provides a convenient way to construct math expressions from various data sources, such as attributes, parameters, and feature functions, where the result is used directly inside a parameter.
Conditional Values
Set values depending on one or more test conditions that either pass or fail.
Parameter Condition Definition Dialog
Content
Expressions and strings can include a number of functions, characters, parameters, and more.
When setting values - whether entered directly in a parameter or constructed using one of the editors - strings and expressions containing String, Math, Date/Time or FME Feature Functions will have those functions evaluated. Therefore, the names of these functions (in the form @<function_name>) should not be used as literal string values.
| These functions manipulate and format strings. | |
|
Special Characters |
A set of control characters is available in the Text Editor. |
| Math functions are available in both editors. | |
| Date/Time Functions | Date and time functions are available in the Text Editor. |
| These operators are available in the Arithmetic Editor. | |
| These return primarily feature-specific values. | |
| FME and workspace-specific parameters may be used. | |
| Creating and Modifying User Parameters | Create your own editable parameters. |
Table Tools
Transformers with table-style parameters have additional tools for populating and manipulating values.
|
Row Reordering
|
Enabled once you have clicked on a row item. Choices include:
|
|
Cut, Copy, and Paste
|
Enabled once you have clicked on a row item. Choices include:
Cut, copy, and paste may be used within a transformer, or between transformers. |
|
Filter
|
Start typing a string, and the matrix will only display rows matching those characters. Searches all columns. This only affects the display of attributes within the transformer - it does not alter which attributes are output. |
|
Import
|
Import populates the table with a set of new attributes read from a dataset. Specific application varies between transformers. |
|
Reset/Refresh
|
Generally resets the table to its initial state, and may provide additional options to remove invalid entries. Behavior varies between transformers. |
Note: Not all tools are available in all transformers.
For more information, see Transformer Parameter Menu Options.
Reference
|
Processing Behavior |
|
|
Feature Holding |
No |
| Dependencies | Microsoft Azure Account with the Service Bus Service |
| Aliases | |
| History | Released FME 2019.2 |
FME Online Resources
The FME Community and Support Center Knowledge Base have a wealth of information, including active forums with 35,000+ members and thousands of articles.
Search for all results about the AzureServiceBusConnector on the FME Community.
Examples may contain information licensed under the Open Government Licence – Vancouver, Open Government Licence - British Columbia, and/or Open Government Licence – Canada.