Collecting Data for Maximo Integration Framework

Resolving The Problem

This technote describes what information you need to gather to begin troubleshooting a Maximo 7 Integration Framework issue.

Collect the following files and information:

1. Maximo.log file reproducing the problem with the following logging properties enabled:

log4j.logger.maximo.integration=DEBUG
log4j.logger.maximo.sql=INFO
log4j.logger.maximo.crontask=DEBUG

2. If using a custom integration object, output containing the object definition information from the following queries:

select * from maxintobject where intobjectname='your custom integration object'
select * from maxintobjdetail where intobjectname='your custom integration object'
select * from maxintobjcols where intobjectname='your custom integration object' order by objectname,name

3. Application server log:

For WebSphere, the log is systemOut.log and is located in the server directory IBM\WebSphere\AppServer\Profiles\customprofilename\logs\servername.
For WebLogic, the output goes to a console or if you define an appender, MAXIMOSERVER.log will be created in the BEA\userprojects\domains\MAXIMOSERVER\servers\AdminServer\logs

4. Output containing all the integration properties from the following query:

select propname,servername,serverhost,propvalue,changeby,changedate from maxpropvalue where propname like 'mxe.int%' order by serverhost,servername,propname

5. Copy of the xml file from the error folder under the globaldir\ERROR\jms.maximo.intqueues.queuename.

The name of the xml file is ExternalSystem_InterfaceName_uniquenumber.xml

6. If using flat files or interface tables:

- screenshot of the object structure indicating that 'Support Flat Structure' check box is marked.

- screenshot of the flat file End Point.

- screenshot of the FLATFILECONSUMER crontask setup.

7. Screenshot of the configuration of the JMSQSEQCONSUMER crontask for two instances SEQQIN and SEQQOUT.

8. If using continuous queues, the Message Driven Beans are not enabled by default. To enable MDBs, two files located in the <root>\applications\maximo\mboejb\ejbmodule\META-INF directory must be edited.

ejb-jar.xml

ibm-ejb-jar-bnd.xmi (WebSphere) or weblogic-ejb-jar.xml (WebLogic)

9. If all the configuration appears to be correct but nothing is processed:

- screenshot of the Select Action - Admin Mode from the Database Configuration application.

- screenshot of the Publish Channel or Enterprise Service that indicates the status of the Event Listener.

- screenshot of the External System, Publish Channel or Enterprise Service indicating that they have been enabled.