The IBM Websphere MQ Consumer step allows Pentaho Data Integration to receive text messages from any IBM Websphere MQ Server. This step is has been tested against the 7.x version of IBM Websphere MQ Server.
You could use IBM Websphere MQ Consumer step to define a long running transformation that updates a data warehouse every time a MQ message is received.
You must be familiar with IBM Websphere MQ messaging to use this step. Additionally, you must have a running IBM Websphere MQ Server available before you configure this step. If you are using the Java Naming and Directory Interface (JNDI) to connect to IBM Websphere MQ Server, you must have the appropriate connection information.
IBM licensing prevents Pentaho from distributing the necessary IBM Websphere MQ Java libraries directly with the plugin software. You will need to locate and install these libraries before you use these steps. See the Installation section of Processing Message Queues with IBM Websphere MQ for further details.
License Information: Enterprise Edition only
Optionally, you can change the name of this step to fit your needs.
Enable MQ Connection if you are using an MQ connection string to connect to your IBM Websphere MQ Server.
Enter the appropriate connection URL. The syntax of the URL should follow:
Enter the IBM Websphere MQ Server authorized user name.
Enter the IBM Websphere MQ Server password.
Enable JNDI Connection if you are using the Java Naming and Directory Interface (JNDI) to connect to the IBM Websphere MQ Server.
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.Topic uses a publish/subscribe delivery model meaning that a one message can be delivered to multiple consumers. Messages are delivered to the topic destination, and ultimately to all active consumers who are subscribers of the topic. Also, any number of producers can send messages to a topic destination; each message can be delivered to any number of subscribers. If there are no registered consumers, the topic destination does not hold messages unless it has durable subscription for inactive consumers. A durable subscription represents a consumer registered with the topic destination that can be inactive at the time the messages are sent to the topic.
Specify the queue or topic name.
Specify the time to wait for incoming messages in milliseconds.Note: A timeout setting of zero never expires.
Specify the field name that contains the contents of the message.