Scribe Insight version 7.5.2 has been released and is available for download. Version 7.5.2 is primarily a maintenance release that addresses a number of defects. You can read about the release in the release notes. The Insight 7.5.2 installer includes the most recent version of all Insight adapters, including an update to the Web Services adapter.
In addition to correcting defects, we also added support for message queue priority to the core product. This feature is one of the most requested features as voted on in OpenMind. Let's consider a couple of use cases where setting the message queue priority can help your integration design.
First, there is the scenario where you want to put a priority on processing certain types of data. Let's say you were integrating general ledger information and sales orders and that you consider sales order processing the priority. There is a daily process that churns through all of the changes to the general ledger that are processed in batch. While the general ledger transactions are being processed a new sales order comes in and has to wait its turn for its message to be processed. If you can set a higher priority on sales order messages, you can ensure that sales order messages get processed soon after they are submitted to the message queue, jumping to the front of the line.
Second, there is the scenario with referential integrity and retrying failed messages. A general pattern used in Scribe Insight integrations is to set a message to be reprocessed if it has an error. Let's say you are processing contact and account data and the contact message is processed first. The target system will not allow a contact to be inserted unless there is an account record to attach it to. The contact message will fail and go into the retry queue and will be processed again until it times out or until the account message is processed. This situation can cause churn in the message queues and a drain on server resources. If you configure a higher priority on the account messages, then they will be processed before the contact messages, reducing the chances of the referential-integrity-failed-row-retry-message loop.
Note: With Insight 7.5.2, the message priority feature applies only to the query publisher and the XML adapter. We plan to implement message priority in other adapters that have publishers when we update them in the future.

This is great stuff :-)
Thanks Scribe for the new priority of messages I'm looking forward to use this feature
Posted by: Anders Jeppesen | 08/21/2012 at 04:14 PM