Receiving Profile

Create a profile with an Input Agent of type Message as shown in the screenshot above and make sure it is active. At the latest at a restart of the Integration Server, the profile will fetch all the messages in queue JMSReceiveQueue.

Connection Errors

If your test messages are still on the ActiveMQ Server, the reason could be a connection error. Please check the file ./logsservices/error.log. In the case of an error, you might find a section like the following. You would get an error like this if the Apache ActiveMQ Server was not running at all, for example.

Here is another possible error.

Important note: We will use this error to mention, that with newer versions of ActiveMQ you might have to use the prefix dynamicQueues/ (respectively dynamicTopics/), e.g. dynamicQueues/JMSSendQueue and dynamicQueues/JMSReceiveQueue. Please adjust these names in the configuration file ./etc/message.xml. See 'dynamic contexts' in ActiveMQ for more details. If all the other configurations are correct, the profile should now be able to fetch the messages.

Successful Connection Establishment

If the connection was successful and the messages have been received by the profile, the web interface of the ActiveMQ server will show a view as shown in the screenshot above.

Send Data to a JMS Server

To be able to send Lobster_data messages to a JMS system, the file ./etc/message.xml has to contain a section addMessageMap (which you already have set in the previous chapter). Additionally, the configuration file ./etc/message.xml has to contain the following entries for two additional consumer queues.

Lobster_data messages with context jms and queue name out shall be sent to the JMS queue (or topic) JMSSendQueue. The type (string or byte) of the JMS messages can be set in the configuration file ./conf/dw2jms.properties. The syntax is <context>.<queue>.type=<type>. If the type string is used, you also have to set the encoding with the syntax <context>.<queue>.encoding=<encoding>. Alternatively, you can declare the variables JMS_MSG_TYPE and JMS_MSG_ENCODING and save your values there. If these variables are declared, the settings in the configuration file will be ignored. All declared variables with prefix JMS_ will be set as JMS header properties, however, without the prefix JMS_, i.e. variable JMS_Invoice_No will be set as JMS header property InvoiceNo.

Example

Explanation of the process with reference to context jms and queue out

You create a profile in Lobster_data with a Response Route of type Message, content CSV, and file encoding 8859_1. Then you set the context name to jms and the queue name to out. Note: The profile name will be ignored, but since it is a mandatory field, you have to enter an arbitrary value.

First of all, the Lobster_data message will be received by the subscriber com.ebd.hub.datawizard.plugin.DW2JMS from context jms and queue out and converted to a string JMS message and sent to the Lobster_data context DW2jms and queue DW2out (same values with prefix DW2). This is where the entry addMessageMap comes into play and sends the JMS message to the JMS queue (or topic) JMSSendQueue.

Send a little text file as test message in a new profile ProfileB. Configure the Response Route of that profile as shown in the screenshot above.

The web interface of the ActiveMQ server should now show a view as shown in the screenshot above.

Mass Data Processing

If a large number of messages are to be processed via a queue, the queue can be switched to file processing. There is a patch available that allows an additional option in the queue definition. If you are interested, please contact our support staff.

If this parameter is set to true, the messages are no longer processed via the internal message bus but are output as *.dat in the file system under folder ./jms/in/<queue name>. See the following screenshot.