Skip to content

Better Error Messaging from Maximo Web Service Response

You are ready to test drive your perfect web service that you just spent the last few minutes constructing in Maximo.  A final comparison is performed on your test message to ensure that the structure of the XML is aligned with your object structure.  You are satisfied with the message and it is placed in SOAPUI or your favorite XML test engine.  The message is sent and the response you receive is:

Internal Error

In this example I am trying to add my labor code using an organization identifier that does not exist in my Maximo system.  The response in no way helps me understand the problem however.

Internal Error?  How “internal” should I look?  Could the message possibly be vaguer?  With a sigh it’s off to the logs in order to find more information.  All the while hoping that the message hasn’t rolled off into a backup log.

Thankfully there is a way to configure WebSphere 8.5.X and newer to display the Maximo error code in the response message.

Log in to the WebSphere Administration Console and navigate to WebSphere Application Servers.  Click on your application server.

On the right side under Server Infrastructure expand Java and Process Management and select Process Definition.

 

Select Java Virtual Machine.

Select Custom Properties.

 

Click New and enter the following information.

Name: webservices.unify.faults

Value: false

Click Apply or Ok.  Save and restart the WebSphere Application Server.  Note that all you have to do is navigate to WebSphere application servers and restart the server from there.  You do not have to restart all WebSphere services or the Cell or Node.

After the application server has restarted retry your message in SOAPUI.  You should see a Maximo error code along with a more helpful message.

Considerations

The property is set to true by default in order to restrict the information that is sent as part of the error code.  Consequently, this is a property that should most likely not be available in a production setting or in an environment with sensitive data that is exposed as a web service.  However, in a development environment this setting can speed up the creation and testing of web services.

This information can also be found in the IBM Upgrade Guide Maximo Products V7.5 to V7.6.

Share This

Related Posts

ibm maximo a3jgroup
Inserting into Long Description
To start off with, long descriptions are essential for multiple different reasons.  They are often used...
integration-trobleshooting-IBM-Maximo-A3J-Group-Consulting-e1636065766665
Preventing fields from Editing Once Record is in Workflow
Preventing fields from Editing Once Record is in Workflow I like this problem because it involves a few...
how_to_enable_the_print_button_in_ibm_maximo
How to Enable Print Functionality in IBM Maximo
How to enable the print button in Maximo.   By default, Maximo only allows the MAXADMIN group to have...

1 Responses

1 Comment

  1. How would you achieve the same result in a different J2EE App Server like Weblogic?
    There seems to be no equivalent to webservices.unify.faults
    Thank you.


Add a Comment