Using the data pipeline with ActiveMQ is not a typical configuration and may require significant customization. If you are interested in using this feature, please contact LabKey to inquire about support options.

This topic covers configuring LabKey Server to use the Enterprise Pipeline with ActiveMQ. This configuration allows work to be distributed to remote servers, separate from the LabKey Server web server.


In order to install the LabKey Enterprise Pipeline, you will first need to install and configure the following prerequisite software:

Enable Communication with the ActiveMQ JMS Queue

You will need to add the following settings to the file. Before adding this section, check to see if it is already present but commented out, and if so simply uncomment it by removing the leading #s:

context.resources.jms.ConnectionFactory.description=JMS Connection Factory
# Update to the appropriate hostname and port

You will need to change all of these 'default' settings to the values appropriate for your installation.

Set the Enterprise Pipeline Configuration Directory

By default, the system looks for the pipeline configuration files in the following directory: <LABKEY_HOME>/config.

To specify a different location, set it in the file.

Provide Configuration Files

The config location set above must contain the configuration XML files your pipeline requires. This will depend on your use case. Contact us for assistance and more information about support options.

As one example, you might need both:

  • pipelineConfig.xml and
  • another tool-based file, such as ms2Config.xml in a previous example.

Restart LabKey Server

In order for the LabKey Server to use the new Enterprise Pipeline configuration settings provided in the specified config location, the server will need to be restarted. Confirm that the server started up with no errors:

  • Log on to your LabKey Server using a Site Admin account.
  • Select (Admin) > Site > Admin Console.
  • Under Diagnostics, click View all site errors.
  • Check to see that no errors have occurred after the restart.

Related Topics

Was this content helpful?

Log in or register an account to provide feedback

expand allcollapse all