JMS Message Received

The JMS trigger receives messages from 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 trigger, 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 trigger and JMS external action):

Parameters

Note: See also Working with Parameters in Automations Workflows.

Tip: To test that your parameters work as expected, click Validate.

  • Provider Type or Context: The message broker to connect to, or the initial context factory if the broker is not listed.
  • Provider URL: The URL of the directory containing connection details for the JMS provider.
  • Additional Provider Properties: Any additional provider-specific properties, in the form key=value. For example, randomize=false. Specify multiple pairs on separate lines.
  • In most cases, this field is not required. The JMS brokers tested by Safe, including Apache ActiveMQ, IBM Websphere MQ, and Oracle WebLogic JMS, do not require any additional properties to establish a connection.

  • Connection Factory: The name of the connection factory object.
  • Username: An authenticating username.
  • Password: An authenticating password.
  • Destination(s): The name of the destination object(s). These correspond to queues and/or topics. Multiple destinations can be specified, separated with a comma.

Output Keys

See Also

Key Description
message Message content
jms.messageType Message type
source Event type
time Event time

See Also