IJ47483: <!CDATA' TAGS ON INBOUND MESSAGES VIA WEB SERVICE ARE GETTING STRIPPED OUT OF THE MESSAGE.

APAR status

• Closed as program error.

Error description

• While sending messages into Maximo via an inbound web service,
  in order to pass in special characters, '<!CDATA[]>' tags are
  added, as recommended in IBM documentation. However, when the
  (original) message is written and viewed in the message tracking
   application. It seems to drop the CDATA tag and corrupts the
  message value if the processing fails the first time. Then it
  cannot be directly reprocessed without manually adding the CDATA
   tags back in.
  
  e.g.
  <tns:NWLCLASSIFICATIONID><![CDATA[WNM-M<6]]></tns:NWLCLASSIFICAT
  IONID>
  ends up in message tracking as:
      <tns:NWLCLASSIFICATIONID>WNM-M&lt6</tns:NWLCLASSIFICATIONID>
  
  This issue appears to be only for messages posted via web
  service. When messages are posted via external system end points
  it retains the CDATA tags in message tracking.
  
  STEPS TO REPRODUCE:
  1. Create an Input xml with CDATA[] tag as example below
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:max="http://www.ibm.com/maximo">
     <soapenv:Header/>
     <soapenv:Body>
       <max:SyncMXASSET >
           <max:MXASSETSet>
              <max:ASSET>
                 <max:ASSETNUM>KDTEST017</max:ASSETNUM>
                 <max:SITEID>BEDFORD</max:SITEID>
                 <max:DESCRIPTION_LONGDESCRIPTION><![CDATA[WNM-M<6
  "]]>" </max:DESCRIPTION_LONGDESCRIPTION>
              </max:ASSET>
           </max:MXASSETSet>
        </max:SyncMXASSET>
     </soapenv:Body>
  </soapenv:Envelope>
  
  2. Process this xml through webservices.
  <?xml version="1.0" encoding="UTF-8"?>
  <max:SyncMXASSET xmlns:max="http://www.ibm.com/maximo">
    <max:MXASSETSet>
      <max:ASSET>
        <max:ASSETNUM>KDTEST017</max:ASSETNUM>
        <max:SITEID>BEDFORD</max:SITEID>
        <max:DESCRIPTION_LONGDESCRIPTION>WNM-M<6
  ""</max:DESCRIPTION_LONGDESCRIPTION>
      </max:ASSET>
    </max:MXASSETSet>
  </max:SyncMXASSET>
  
  3. After successful processing the message in message tracking
  application removes CDATA tag from processed XML.
  
  4.Change the SITEID to REDFORD as site REDFORD does not exist
  and try to process the below xml
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:max="http://www.ibm.com/maximo">
     <soapenv:Header/>
     <soapenv:Body>
       <max:SyncMXASSET >
           <max:MXASSETSet>
              <max:ASSET>
                 <max:ASSETNUM>KDTEST017</max:ASSETNUM>
                 <max:SITEID>REDFORD</max:SITEID>
                 <max:DESCRIPTION_LONGDESCRIPTION><![CDATA[WNM-M<6
  "]]>" </max:DESCRIPTION_LONGDESCRIPTION>
              </max:ASSET>
           </max:MXASSETSet>
        </max:SyncMXASSET>
     </soapenv:Body>
  </soapenv:Envelope>
  
  5.Process the xml through webservices.
  
  6. After processing the message in message tracking application
  CDATA tag is removed from XML.But the transaction failed as
  there is no siteid as REDFORD.
  
  7. Go to Message Tracking application and check the message
  where status is ERROR
  
  8. Click on the pen icon(Integration message) next to ERROR
  message.
  
  ACTUAL RESULT:
  CDATA tag is removed from the integration message.
  
  EXPECTED RESULT:
  CDATA tag should not be removed from the integration message
  while the transaction fails
  
  REPORTED IN VERSION:
  Tivoli's process automation engine 7.6.1.2
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * MAXIMO                                                       *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * <!CDATA' TAGS ON INBOUND MESSAGES VIA WEB SERVICE ARE        *
  * GETTING STRIPPED OUT OF THE MESSAGE.                         *
  ****************************************************************
  

Problem conclusion

• The fix for this APAR is contained in the following maintenance
  package: release\fix pack for Release 8.x 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:

Modules/Macros

• MAXIMO
  

Fix information

• Fixed component name

  MAXIMO ASST MGM

• Fixed component ID

  5724R46AM

Applicable component levels