Send a Java Message System (JMS) Message
The JMS external action receives messages and relays them to Java Message System (JMS)-compliant message brokers, such as IBM WebSphere MQ.
The JMS external action has two output ports. The success port (✔) can send a message if the message broker is notified successfully. The failure port (x) can send a message if the notification fails.
Setting up a JMS Message Broker with FME Server
Before configuring a JMS external action, 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:
Parameters
Expand for details
- 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.
- 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.
- Use Persistent Delivery: If Yes, messages are stored by the JMS broker until the message is delivered to a destination, and can be recovered in the event of a broker restart. If No, messages may be lost in the event of a broker restart during delivery. Persistent delivery is slower than non-persistent delivery, particularly when sending large volumes of messages.
- Notification Content Template: The message body. See below.
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.
Sample Configurations
Expand to view sample configurations
Apache ActiveMQ Sample Configuration
| Java Classpath |
No change required. (Apache ActiveMQ 5.6.0 libraries are bundled with FME Server.) |
| Provider Type or Context | ACTIVEMQ |
| Provider URL | tcp://server:61616 |
| Additional Provider Properties | -- |
| Connection Factory | ConnectionFactory |
| Username |
-- |
| Password |
-- |
| Destination(s) | dynamicQueues/MyQueue |
IBM WebSphere 7 Sample Configuration
| Java Classpath | ... -FMESERVER_CLASSPATH “...;C:/Program Files (x86)/IBM/WebSphere MQ/java/lib/*” ... |
| Provider Type or Context | WEBSPHERE70 |
| Provider URL | file:/C:/jndi/ |
| Additional Provider Properties | -- |
| Connection Factory | cf1 |
| Username | admin |
| Password | admin |
| Destination(s) | q1,t1 |
Oracle Weblogic Sample Configuration
| Provider Type or Context | weblogic.jndi.WLInitialContextFactory |
| Provider URL | t3://bq-w2008:7001 |
| Additional Provider Properties | -- |
| Connection Factory | jms/TestConnectionFactory |
| Username |
-- |
| Password |
-- |
| Destination(s) | jms/TestJMSQueue |
Output Keys
See Also
| Key | Description |
|---|---|
| time | Event time |
| source | Event type |
| error.type | (Failure port only) Error type |
| error.message | (Failure port only) Error message |
See Also