The Java Messaging Service (JMS) Producer step allows Pentaho Data Integration to send text messages to Apache ActiveMQ JMS server. Additionally, you can send text messages to any JNDI-enabled JMS server if you've embedded PDI to run in a J2EE container.
You could use the JMS Producer step to define a transformation that for every update of a warehouse, posts to a JMS queue that could launch another job that flushes an application cache.
You must be familiar with JMS messaging to use this step. Additionally, you must have a message broker like Apache ActiveMQ available before you configure this step. If you are using the Java Naming and Directory Interface (JNDI) to connect to JMS, you must have the appropriate connection information.
Note: Place JMS Library jars for the ConnectionFactory and other supporting classes in the .../data-integration/plugins/pdi-jms-plugin/lib directory.
License Information: Enterprise Edition only
JMS Producer Options
Optionally, you can change the name of this step to fit your needs.
Enable ActiveMQ Connection you are using the message broker.
Enter the appropriate broker URL.
Enter the ActiveMQ user name
Enter the ActiveMQ password
Enable JNDI Connection if you are using the Java Naming and Directory Interface (JNDI) to connect to JMS
The URL for the JNDI connection
Select Topic or Queue from the drop down list to specify whether you want to use a Topic or Queue delivery model.
Specify the queue or topic name.
If the header properties file is specified, then the name/value pairs are submitted with the message text as JMS string properties.
Is field a filename?
Enable if the message is based on a field name. In this instance, the contents of the file, (not the field name), are sent.
If applicable, select the name of the field from the list.