This entry is part of the Maximo Integration Framework series.
If you have never used the Maximo Integration Framework you have to check the MIF configuration before being able to play with it.
System Properties
All the configuration parameters for MIF can be managed from the System Properties application: GoTo -> System Configuration -> Platform Configuration -> System Properties. -> mxe.int.*
The most important property to check is mxe.int.globaldir. This property specifies the root folder where all the integration configuration files are located. If this value is null, the folders are created under the directory from which the application server is started, or from the current working directory of the application server (e.g. C:\IBM\WebSphere\AppServer\profiles\AppSrv01).
Other important properties that need to be set before using MIF are:
- mxe.int.webappurl: This specifies the integration Web application URL. The syntax is http://[HOST]:[PORT]/meaweb/maximo.
- mxe.int.admintoemail: Email address to which the integration framework sends notification of message processing errors.
JMS Queue Setup
Java Message Service (JMS) is used for routing messages from the processing layers to the external systems.
To verify that the JMS Queues are correctly installed login to the WebSphere Integrated Solutions Console and go to Resources - JMS - Queues. Ensure the following queues are enabled:
- cqin : Continuous Inbound Queue
- sqin : Sequential Inbound Queue
- sqout : Sequential Outbound Queue
CRON Tasks
There are several CRON tasks that must be active.
Go to System Configuration - Platform Configuration - Cron Task Setup and ensure that the following Cron Tasks are enabled:
- JMSQSEQCONSUMERThis cron task pulls records from JMS Queues for processing.
- IFACETABLECONSUMER to regularly poll the interface tables
- FLATFILECONSUMER to use flat files for inbound data import
- XMLFILECONSUMER to use XML file for inbound data import
Continuous JMS Queue Configuration
The continuous JMS queues (CQIN and CQERR) requires some additional steps that requires to rebuild and redeploy the Maximo EAR. However this step can be skipped if you are willing to use only the sequential queues.
Edit maximo/applications/maximo/mboejb/ejbmodule/meta-inf/ejb-jar.xml file and make sure the following four sections are uncommented to look like below:
<!-- MEA MDB -->
<message-driven id="MessageDriven_JMSContQueueProcessor_1">
...
</message-driven>
<!-- MEA MDB for error queue -->
<message-driven id="MessageDriven_JMSContQueueProcessor_2">
...
</message-driven>
<!-- MEA MDB -->
<container-transaction>
...
</container-transaction>
<!-- MEA MDB for error queue -->
<container-transaction>
...
</container-transaction>
Edit maximo/applications/maximo/mboejb/ejbmodule/meta-inf/ibm-ejb-jar-bnd.xmi and make sure the following two sections are uncommented to look like below:
<!-- MEA MDB -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsact">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_1"/>
</ejbBindings>
<!-- MEA MDB for error queue -->
<ejbBindings xmi:type="ejbbnd:MessageDrivenBeanBinding" xmi:id="MessageDrivenBeanBinding_1" activationSpecJndiName="intjmsacterr">
<enterpriseBean xmi:type="ejb:MessageDriven" href="META-INF/ejb-jar.xml#MessageDriven_JMSContQueueProcessor_2"/>
</ejbBindings>
Now rebuild and deploy the maximo.ear.
Labels: integration, intermediate, mif