IJ41320: HTTP QUERY FAILS WHEN SYNCHRONOUS MESSAGE TRACKING IS ENABLED - ENTERPRISE SERVICE

APAR status

• Closed as program error.

Error description

• This issue is very similar to the issue in APAR IJ30642.
  In the
  APAR IJ30642 the issue is with an object structure based web
  service. The issue in this APAR is with an enterprise service
  based web service.
  Steps to reproduce:
  1. Set the following
  properties to 1:
  mxe.int.storerestmsg
  mxe.int.storesoapmsg
  mxe.i
  nt.storesynchttppmsg
  mxe.int.trackrestrequests
  mxe.int.tracksoap
  requests
  mxe.int.tracksynchttprequests
  2. Go to Integration ->
  Enterprise Services -> Create a new Enterprise
  Service:
  Operation: Query
  Object Structure: MXASSET
  3. Go To ->
  Integration -> External Systems -> Filter for EXTSYS1 ->
  Enterprise Services tab -> Add the enterprise service created
  at step 2.
  Make sure to enable the enterprise service and the
  external system
  4. Go To -> Integration -> Web Services Library
  -> Create Web Service -> Create Web Service from Enterprise
  Service -> select your web service
  5. Deploy to Product Web
  Service Container -> Deploy Web Service
  6. Open soapUI and
  create a new soap project based on your web service wsdl. In my
  case this is my
  wsdl:
  http://hostname/meaweb/wsdl/EXTSYS1_TESTQUERY.wsdl
  7. Run
  the following query:
  <soapenv:Envelope
  xmlns:soapenv="http://schemas.xmlsoap.org/soap/envelope/"
  xmlns:max="http://www.ibm.com/maximo">;
   <soapenv:Header/>
  
  <soapenv:Body>
   <max:QueryMXASSET>
   <max:MXASSETQuery>
  
  <max:WHERE>assetnum='13150'</max:WHERE>
   </max:MXASSETQuery>
  
  </max:QueryMXASSET>
   </soapenv:Body>
  </soapenv:Envelope>
  
  When
  the properties at step 1 are set to 1 I get an Internal Server
  Error.
  When the properties are set to 0 the query works 200
  OK.
  
  Product version:
  Maximo 7612
  IBM Tpae Integration
  Framework 7.6.1.2-MIF_7612_IFIX.20220404-1408 Build
  20200715-1444 DB Build V7612-11 HFDB Build HF7612-02
  

Local fix

Problem summary

Problem conclusion

• A fix for this APAR will be included in a future release.
  

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