Configure an ActiveMQ Subscriber

An ActiveMQ subscriber receives messages from a configured publisher and forwards the message to a configured Apache ActiveMQ endpoint for processing by an external system. An alternative 'standard' subscriber type is also available. See Configure a Subscriber.

This activity assumes that message queues have been manually created in the ActiveMQ application, or (if the ActiveMQ version and configuration allow) will be created automatically when messages are written to the queue.

Note: Recommended practice for all adaptors: Copy IntegrationHub.dll and IntegrationHub.Interfaces.API.dll from the IMS Integration Hub installation folder to the folder with the adaptor DLL before configuring the subscriber. (Configuring the adaptor path of the subscriber without having these DLLs in the same folder causes an error that can only be resolved by deleting and recreating the subscriber.)

Recommended practice for adaptors used with MineMarket:

  1. Place the adaptor DLL in the MineMarket installation folder.
  2. Copy IntegrationHub.dll and IntegrationHub.Interfaces.API.dll from the IMS Integration Hub installation folder to the MineMarket installation folder before configuring the subscriber.
  3. In the following configuration, set Load Adaptor In Own Application Domain to True.

Activity Steps

  1. On the toolbar, click New ActiveMQ Subscriber.

    A subscriber is added to the Integration » Subscribers node in the Configuration Explorer.

  2. Double-click the ActiveMQ subscriber node.

    The ActiveMQ Subscriber screen displays the connection details for the subscriber.

  3. Complete the following fields.
    • Name
    • Retry Count—Number of times IMS Integration Hub should try to push a message to the subscriber before stopping. Default: 1.
    • Retry Timeout—The amount of time that IMS Integration Hub waits after a failed attempt to push a message to a subscriber before retrying. Default: 30 seconds.
    • B2MML Message Type—Not applicable for ActiveMQ subscribers. For more about B2MML subscribers, see IMS Integration Hub B2MML Configuration.
    • Error Endpoint—The name of the ActiveMQ endpoint configured to receive error messages. Errors that occur on the subscriber during message processing are sent to the ActiveMQ endpoint when the subscriber enters the 'given up' state based on the configuration of the subscriber. Example: tcp://localhost:61616|ErrorQueue.

      Important: The endpoint name must include a pipe symbol (|) as a separator between the host connection string and queue name.

    • Log Successful Runs—Whether to log each attempt to send a message to a subscriber.
  4. Complete the following details.
    • Broker URI—The connection string for the ActiveMQ server. Default: tcp://localhost:61616.
    • Queue Name—The ActiveMQ message queue to which the message is written.

      Important: Message queue names are case-sensitive. The Queue Name entered here must exactly match the name of the queue in the ActiveMQ application.

  5. If required, enter the Username and Password. User authentication is required only if a user with read/write permissions is configured in ActiveMQ.
  6. Click Test.
  7. If the connection is not successful, determine the correct settings or contact your network administrator or Datamine representative.
  8. If the connection is successful:
    1. Click OK.
    2. Click Save.
    3. Click Close.