IJ22706: ENTERPRISE SERVICE SKIP RULE NOT WORKING ERROR: ORG.JDOM.DOCUMENT INCOMPATIBLE WITH ORG.JDOM.ELEMENT

APAR status

• Closed as program error.

Error description

• Problem Description:
  There is an issue with a skip rule within
  the Maximo Enterprise Service. This worked fine until the
  upgrade to IBM Control Desk 7.6.1.
  STEPS TO
  REPRODUCE:
  Create an Object Structure, Enterprise service,
  External System and Webservice.
  Object structure: MC_INCIDENT
  (With the Incident and Worklog object, use relationship
  MODIFYWORKLOG)
  Enterprise service: MC_UPDATE_NEW
  (Use
  Continuous Queue, Operation = Update)
  External system:
  Maincontractors
  Webservice: MC_UPDATE_NEW
  (Turn off 'Bypass
  Queue')
  Create a new relationship in the Database
  Configuration application:
  Worklog to
  Worklog:
  AAS_DUPLICATEWORKLOG
  createdate=:createdate and
  recordkey=:recordkey and class = :class
  Create in the
  Enterprise Service a skip rule:
  Condition on the Object
  Set:
  Action = Skip
  Object = WORKLOG
  Relation=
  AAS_DUPLICATEWORKLOG
  Send a xml message with a Soap tool, for
  example SoapUI.
  Test Demo xml
  message(Test_Demo.xml):
  <UpdateMC_INCIDENT
  xmlns="http://www.ibm.com/maximo"
  xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance">
  <MC_INCIDENTSet>
   <SR>
   <CLASS>SR</CLASS>
   <DESCRIPTION>This is
  a test incident</DESCRIPTION>
  <DESCRIPTION_LONGDESCRIPTION>This is a test
  incident</DESCRIPTION_LONGDESCRIPTION>
  <REPORTDATE>2020-01-31T12:45:04+01:00</REPORTDATE>
  <REPORTEDBY>Wilson</REPORTEDBY>
   <STATUS>QUEUED</STATUS>
  <STATUSDATE>2020-01-31T15:15:55+01:00</STATUSDATE>
  <TICKETID>157745</TICKETID>
   <WORKLOG>
  <CREATEBY>MXINTADM</CREATEBY>
  <CREATEDATE>2020-01-30T11:39:58+01:00</CREATEDATE>
  <DESCRIPTION>This is a short description</DESCRIPTION>
  <DESCRIPTION_LONGDESCRIPTION/>
   <LOGTYPE>UPDATE</LOGTYPE>
  <MODIFYBY>MXINTADM</MODIFYBY>
   </WORKLOG>
   </SR>
  </MC_INCIDENTSet>
  </UpdateMC_INCIDENT>
  The first time it will
  create a worklog entry, however, on the second time, you are
  unable to edit the incident record.
  RESULTS:
  You will get
  the following error message in the systemout.log
  [1/31/20
  15:02:48:516 CET] 000065fa SystemOut O 31 Jan 2020 15:02:48:516
  [ERROR] [MAXIMO] [] Processing failed for MC_UPDATE_INCIDENT.
  The object structure is 1. The primary object is INCIDENT. The
  key is INCIDENT~157745.org.jdom.Document incompatible with
  org.jdom.Element
  [1/31/20 15:02:48:533 CET] 000065fa SystemOut
  O 31 Jan 2020 15:02:48:532 [ERROR] [MAXIMO] [] BMXAA4214E - An
  unknown error has occurred. Please contact your system
  administrator for assistance. Gather the logs from the <HOME>
  directory and determine where and why the error is
  thrown.
  org.jdom.Document incompatible with
  org.jdom.Element
  psdi.util.MXSystemException: BMXAA4214E - An
  unknown error has occurred. Please contact your system
  administrator for assistance. Gather the logs from the <HOME>
  directory and determine where and why the error is
  thrown.
  org.jdom.Document incompatible with org.jdom.Element
  at
  psdi.iface.mic.EntMicService.processDataIn(EntMicService.java:14
  35)
  EXPECTED RESULTS:
  Successful Skip rule
  transaction.
  REPORTED IN VERSION:
  IBM Maximo Asset Management 7.6.1.0
  

Local fix

• Add WORKLOGID attribute in the payload and restrict this column
  in Object Structure.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * ENTERPRISE SERVICE SKIP RULE NOT WORKING ERROR:              *
  * ORG.JDOM.DOCUMENT INCOMPATIBLE WITH ORG.JDOM.ELEMENT         *
  ****************************************************************
  

Problem conclusion

• Example: The fix for this APAR is contained in the following
  maintenance package: release\fix pack for Release 7.6.1.3
  Product
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels