IV80180: INCORRECT FATAL ERROR MESSAGE LOGGED IN SYSTEMERR.LOG EVERY TIME MAXIMO SENDS WEB SERVICE TRANSACTION TO EXTERNAL SYSTEM

APAR status

• Closed as program error.

Error description

• This is happening in both cases when MEP
  parameter on End Point is set to  sendreceive  or
   sendrobust , but it is not happening when MEP parameter
  is set to  fireandforget . Message processing is not
  affected, but error log file is overloaded with error messages
  and it is of concern to our operations administrators when
  system logs FATAL ERROR continuously.
  STEPS TO REPLICATE:
  Step 1:
  Go to Integration > Object Structure application
  a) Create new object to be used for Published Integration
  Channel.
  Name: Test_MXWO
  Descritpion: Test
  Object: Workorder
  b) Save
  Step 2:
  Go to Integration > Publish Chanel application
  a) Create Publish Chanel for the object.
  Name: TEST_MXWO
  Description: Test
  b) In the Processing Rules for Sub-Record WORKORDER section
  click on New Row
  Rule: SKIPWO
  Sequence: 1
  Action: SKIP
  Enabled: Checked
  d) Select Action > Enable Event Listener
  Click ok
  e) Save
  Step 3:
  Go to Integration > End Points application
  a) Create new end point
  EndPoint: TEST_ENDPOINT
  Description: Test
  Handler: WEBSERVICE
  b) In the properties section
  ENDPOINTURL: set to a local machine where mockup soapui service
  is running.
  SOAPACTION: urn:processDocument
  SERVICENAME: Test
  MEP: sendrobust
  c) Save
  Step 4:
  Go to Integration > External Systems application
  a) Create new external system
  System: Test
  Description: Test
  End Point: Select endpoint created in step 3a
  Enabled: Checked
  Outbound Sequential Queue: jms/maximo/int/queues/sqout
  b) On the publish channel tab, click on New row and add the
  publish chanel created in step 1a.
  Enabled: Checked
  End Point: Select endpoint created in step 3a
  c) Save
  Step 5:
  Go to Integration > Web Services Library application
  a)In order to prepare test WSDL you need to create new Web
  Service for the same Integration Object.
  Select Action > Create Web Service > Create Web Service From
  Object Structure
  Select object structure created in step 1a
  Click create button
  b) Then click Generate Schema, WSDL and View XML
  c) Files are generated and saved on the server under
  C:\GLOBAL\wsdl
  Step 6:
  Open a browser and type in the URL for the WSDL file generated
  in step 5b.
  Open http://localhost:9080/meaweb/wsdl/TEST_MXWO.wsdl and
  download WSDL document
  Step 7:
  a) Open the WSDL file saved in step 6.
  b) Find the <operation name="SyncTEST_MXWO"> and replace with
  <operation name="PublishTEST_MXWO"> to get WSDL for Publish
  Channel
  c) Save the file
  Step 8:
  Open SoapUI application
  Create a test service in SoapUI application
  a) File > Open
  b) Select newly modified WSDL xml file with PublishMXWO
  operation in 7a
  c) Click on SOAP11 binding and select  Generate SOAP Mock
  Service
  d) Select only PublishMXWO operation
  change Path to the same URL as you specified for MAXIMO End
  Point Url   ENDPOINTURL parameter in step 3b
  Step 9:
  New Test service is create and you can start it
  a) Press the Play button to start
  b) On the left menu expand SOAP11 binding > PublishTest_MXWO
  c) Click on Request 1
  d) Change URL at the top and test it.
  You should get SOAP response with envelope, header,
  body and PublishMXWO
  e) Stop mock-up service and open response document
  f) Remove PublishMXWO tag from the response body and leave
  response body part blank. This will result in empty response
  document
  g) Start mock-up service, open Request part again and test it
  that response is different now. SOAP Response body is empty.
  Step 10:
  Go to MAXIMO and approve one Work Order to generate
  document to be published via MXWO publish channel into end point
  a)  In the SOAPUI application, you can see that mock-up service
  has received documents successfully
  Step 11:
  Open SystemErr.log from WebSphere log folder. You will
  see the following error message logged:
  FATAL ERROR:  '[ERR 0290] The StreamSource object passed to
  ''{0}'' has no contents.'
  This is the error and although it does not prevent
  messages from being transferred but incorrectly logs these
  messages.
  

Local fix

• n/a
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * All users using web service handler for invoking external    *
  * web services                                                 *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * Error logged when invoking web services with a null response *
  * - ie response with soap envelope but no soap body.           *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * apply this fix.                                              *
  ****************************************************************
  

Problem conclusion

• Error logged when invoking web services with a null response -
  ie response with soap envelope but no soap body.
  

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

  INTEGRATION

• Fixed component ID

  5724R46I1

Applicable component levels

• R750 PSY

     UP