IBM BJ0NJML - Service And Asset Management, Integration Manual

Page: 140 / 330

Common Causes of Errors
126
Integration Guide
Because the error is a major exception, the integration framework cannot retry the
XML file. To correct the error you must remove the incorrect data from the source
XML file. You then must delete the error record by changing its message status to
DELETE. After you remove the invalid data from the source XML file, you can
reprocess the message.
The integration framework provides a view queue utility to help you identify the
application data content that caused the error. The utility creates a view queue file
and places the file in the view folder under the integration global directory. The
view queue file is identified with the same file name as the error XML file, and its
data content includes the message that was initially received in the inbound
queue.
For example, if a view queue utility error occurs after you export person data
through the MXPERUSERInterface publish channel, the system generates a
MX_MXPERUSERInterface file. The file contains the following original outbound
message content.
<?xml version="1.0" encoding="UTF-8" ?>
<PublishMXPERUSER creationDateTime="2007-12-04T13:21:03-05:00"
transLanguage="EN" baseLanguage="EN"
messageID="11967924643281249" maximoVersion="7 1 082 V7100-001"
event="0" xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
xmlns="http://www.ibm.com/maximo">
<MXPERUSERSet>
<PERSON>
<ACCEPTINGWFMAIL>0</ACCEPTINGWFMAIL>
<ADDRESSLINE1>760 Unity Blvd.</ADDRESSLINE1>
<ADDRESSLINE2 />
<ADDRESSLINE3 />
<BILLTOADDRESS />
<BIRTHDATE xsi:nil="true" />
<CITY>Framingham</CITY>
<COUNTRY>USA</COUNTRY>
<COUNTY>xxx</COUNTY>
<DELEGATE />
<DELEGATEFROMDATE xsi:nil="true" />
<DELEGATETODATE xsi:nil="true" />
<MAXUSER>
<DATABASEUSERID />
<DEFSITE>BEDFORD</DEFSITE>
<DEFSTOREROOM />
<EMAILPSWD>0</EMAILPSWD>
<FAILEDLOGINS>0</FAILEDLOGINS>
<FORCEEXPIRATION>0</FORCEEXPIRATION>
<INACTIVESITES>0</INACTIVESITES>
<LOGINID>jennyb</LOGINID>
<MAXUSERID>37</MAXUSERID>
</MAXUSER>
</PERSON>
</MXPERUSERSet>
</PublishMXPERUSER>d
The incorrect county on line 11 caused the major exception. The integration
framework does not process the message until you correct the incorrect data.