Healthcare Interoperability Blog

interfaceware.com
  • Iguana Integration Engine
  • Resource Center
  • Blog
Home Understanding IGUANA’s Message Queue

Understanding IGUANA’s Message Queue

Do you know how IGUANA’s message queue actually works?

When I was taking a look through our support inquiries to find the most asked support questions of March, I made an interesting discovery:

A number of our users don’t understand how IGUANA’s message queue works.

Some of you may have made assumptions about how it works while others may have never thought about it at all. So, for those of you who are interested, I’m going to hopefully clear up some of the misunderstanding.

One queue to rule them all.

That’s right.  In IGUANA, all messages are stored in a single message queue which is used by all IGUANA channels. The destination component of each channel reads its messages from this single queue and processes them.

For each channel, a single source position is defined in the message queue. The source position indicates the location of the last message processed by the channel.

Note: There is an exception to this rule. It applies to channels whose source component is “From Channel” or whose destination component is “To Channel”.

For channels whose source component is “From Channel”, a single source position is defined for each channel specified in the “From Channel” source component.

For channels whose destination component is “To Channel”, no source positions are defined. Instead, source positions are defined by the channels that use these channels as a source.

Let’s take a look at a diagram:

message_queue

We have a simple example here.  There are three channels: named A, B and C, respectively.

(Note: Channel C has a source component of “From Channel”. C1 and C2 are the sources for this channel)

Channel A and B have a single source position. Channel C however, has two source positions: one for the last message processed from source C1 and one for the last message processed from source C2.

Messages that are newer than the source position of their channel are queued for processing.

There you have it! Hopefully, you now understand how IGUANA’s message queue really works and any confusion over the order in which your messages are processed are cleared up.

Where to go from here?

To learn more about using and understanding IGUANA’s queue/log system, your best bet is to visit our Logs and Queues section of our knowledge base.

As always if there’s any topic you’d like to see us blog about, please leave a comment and let us know.

Mar 31, 2015iNTERFACEWARE
  • Email
  • LinkedIn
  • More
  • Facebook
  • Twitter

Related

A Secret Page Inside IGUANATop Support Questions of March 2015
March 31, 2015 News
Enjoying this blog?

Sign up to receive healthcare integration news, just like this, from iNTERFACEWARE Inc.

iNTERFACEWARE needs the contact information you provide to us to contact you about our products and services. You may unsubscribe from these communications at any time. For information on how to unsubscribe, as well as our privacy practices and commitment to protecting your privacy, please review our Privacy Policy.

Resources

Integration Resources & Guides

HL7 Resources

Iguana Case Studies

Iguana Integration Engine

Overview: Integration Engine

Features: Building HL7 Interfaces

Benefits: Why Choose Iguana

Company

About Us

Integration Services

Contact Us

Connect

LinkedIn

Twitter

YouTube

© - iNTERFACEWARE Inc.