How to use EnsLib.SQL.InboundAdapter in IRIS tables
Hi community.
I was wondering if it was possible to use something like EnsLib.SQL.InboundAdapter with tables in IRIS.
This library monitors when a record has been inserted into a table in an external database, so it requires a DSN to connect to that database.
My goal is to make a call to an external API that takes a long time, it could spend nearly an hour (or more) completing its processes, but I don't want to block the main process.
That's why I was thinking about having the original production store the indicators it needs to process in a table, and from another production, monitor when a record has been inserted and invoke the API (with a fairly high timeout) to process that record.
In short, I want to use IRIS as a queue manager (similar to MSMQ) and have it "listen" for changes to execute a process.
Is it possible to access IRIS tables using an InBoundAdapter?
Any suggestions for achieving the same result? That is, having a queue manager and processing as data enters the queue.
Best regards.
Kurro Lopez
Comments
Hi Kurro
It's a bit of a low tech solution, but you can set up a stored SQL DSN for localhost, then use that to access your tables
I am not sure I quite understand the question, but I just recently wrote EnsLib.SQL.InboundAdapters that will query MS SQL Server and write the data directly to IRIS Cache Tables I built, so in that sense it is possible. But if you have a service that is listening for a connection to query IRIS Tables, then I think you would want to build like an API listener that then queries the tables.