No OOB Maximo components

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

Integrating Maximo data when there are no ‘out of the box’ integration components

Maximo provides a number of integration components (object structures, channels & services) for a wide variety of business object data, such as Work Orders, Purchase Orders and Assets.  However Maximo has over 1000 objects so there will be cases where the data you want to integrate with does not have the corresponding integration components pre-built.  In this case you need to leverage the applications provided in Maximo to create the necessary components.

Note: the description below covers the configuration steps in some of the I-F applications.  This content does not cover every possible configuration that can be done, just those relevant to the example being discussed.
Continue reading

Customize with Rules and Controls

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 to customize your integrtion message processing

If you need to customize your integration message processing but don’t want to implement Java code, one option is to use Integration Controls and Processing Rules to provide customizations that will let you filter messages and set values to fields in your integration message.

To provide customizations, you can define integration controls and then leverage those controls in Processing Rules on your Publish Channels and/or Enterprise Services. Doing this, provides a configurable approach to customizing that will allow you to easily alter your integration processing as your integration requirements change.  First, you need to create integration controls and then build processing rules that exploit those controls. Continue reading

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