All Apps and Add-ons

HL7 Messages From a Queue

Path Finder

Hello. We're planning to use HL7 Add-On. The HL7 messages will be posted to a messaging queue. We're currently using JMS Modular Input on a Heavy Forwarder which connects to some queues and ingesting XML messages and forwarding them to indexers. We'd like to do the same for ingesting HL7 messages. We have Splunk Enterprise v6.4.4; JMS Mod Input v1.5. Questions:

  1. Will HL7 add-on work with the jms queue inputs.conf on the JMS Forwarder with the sourcetype = hl7_v2? Here's a example stanza would look like in inputs.conf; sourcetype in the 2nd line from the bottom:

    browse_mode = stats
    browse_queue_only = 0
    durable = 0
    host =
    index = hl7events
    index_message_header = 0
    index_message_properties = 0
    init_mode = jndi
    jms_connection_factory_name = SplunkConnectionFactory
    jndi_initialcontext_factory = com.sun.jndi.fscontext.RefFSContextFactory
    jndi_provider_url = file:/opt/splunk/provider
    sourcetype = hl7_v2
    strip_newlines = 1

  2. Where do we install the HL7 Add-on, on the Indexer, Search Head, Heavy Forwarder (co-exist with JMS Mod Input)?

Thanks for your help!

0 Karma

Splunk Employee
Splunk Employee

You can add this as a new input on your existing system where you have the JMS modular input.

You are correct, all you need to do is change the sourcetype name and the provider information to point to the HL7 queue.

Most the parsing is done on the HF you are running the modular input on. However, if you are doing any index time operations, you should also have the operations there for the new sourcetype. Any extractions at search time would need to be on your Search Head.

0 Karma
State of Splunk Careers

Access the Splunk Careers Report to see real data that shows how Splunk mastery increases your value and job satisfaction.

Find out what your skills are worth!