Inbound queues for Maximo

This is part of a series on Integration Framework. To read from the beginning, visit
the post IBM Maximo Asset Management Help: Integration Framework

How do I decide which integration queue to use when bringing data into Maximo?

The I-F, by default, provides two inbound JMS queues that are used by Enterprise Services.  The queues vary in behavior based on the ‘consumer’ of the queue.  The consumer is the processing that retrieves the messages from the queue (while the queue provider would be the processing that loads messages into the queue).  For the default inbound queues, the sequential queue (sqin) has a CRON task as the consumer while the continuous queue (cqin) uses Message Driven Beans (MDBs).
Continue reading

IBM Maximo Asset Management Help: Integration Framework

Trying to find help for your Maximo system can sometimes be a little daunting. We will be posting a list of tools, tips and tricks to help make your life a little easier. Our first pass will be addressing the Maximo Integration Framework (MIF).

Integration Framework

The Integration Framework (I-F) which is part of the TPAE platform (which means its features are available to both Maximo and SCCD), provides multiple capabilities to integrate data between Maximo and other (external) applications within and outside of an enterprise. This section of the Wiki will walk through various examples of how the I-F can be enabled for different integration scenarios.  Content will be added to this wiki on a continuous basis.
Continue reading