Interested in knowing if we can pick off messages of a given xml format, and process them, so that a queue is per business functionality, or whether this is only meant as a pipeline and you get the next message regardless of what it is?
We also would like to see functionality like this. Our current workaround gets all messages (FIFO by default) and routes them afterwards.
What do you mean with "pick off messages of a given xml format"?
I mean, in queue parlance, peek a message of a given format. Since the queue isn't for a particular format, I wondered if it would be possible to peek the messages - i.e. read the messages without removing them from a queue. Then we could look at the message format, and use them.
I know it's also possible to have a queue per message format, which it probably the preference way to go, but I would still like to see a Peek function.
I might take a look in the ideas section them, and vote up or suggest it, as it would be core in the underlying queue functionality that boomi uses...
Ah, I was talking about something like a filter on a Queue GET/LISTEN based on a Profile. This way, we wouldn't have to route based on Profile after getting all messages, or create multiple queues per Profile and route messages before sending them to the queue. I think I misunderstood because as far as I understand, peek analyzes messages one by one and places messages back in the queue when they don't meet requirements. In my scenario, I don't want to do anything with the messages that don't meet requirements in the first place.Regardless, any extra functionality for the Atom Queue would be great!
Hi Amber Jessen,
Yes, a filter would be ideal, which is more of a publisher / subscriber setup - so the subscriber registers an interest in a particular topic.
I guess in this instance as a subscriber you'd have to consume the message and the first part would be to use business rules, or a decision shape to find if you are interested in the functionality.
As I understand it, the Atom Queue is a lightweight version of Apache ActiveMQ 5, so whilst I understand that we want to make things simpler for people, this would surely be a core requirement, and currently it is being suppressed to keep it 'lightweight'.
Here is how it would be done if it wasn't being hidden: Apache Active MQ Selectors
Aha...message peeking. It's a long time ago I used that. I always called it the "sneek preview" Not an option on Boomi I'm afraid. We use the process route shape (content based routing) to route events dynamically to separate queues. Works fine.
Not currently. Existing ideas related to this discussion:
Retrieving data ...