IBM Support

Data validation not reflected immediately in Maximo

Technical Blog Post


Abstract

Data validation not reflected immediately in Maximo

Body

Have you asked yourself whether there is any property in Maximo 7.6 to control the refresh the data on the screen after a launch point executed?

 

Some people asked the same question, so, it's not just you.

 

Sometimes you experience the scenario where after a launch point automation script executed, the screen does not refresh the data immediately in the Maximo UI fields.

 

It is about 10 second delay that it takes to correct the data in the fields involved.

 

One thing that we could recommend you to check is a system property called  mxe.webclient.asyncrendertimelimit  , which controls the max seconds between responses sent to client while framework is processing multiple async requests.

 

As this considers update processes that are not fully synchronized with Maximo, we would recommend for performance purposes that you set it to a low value, such as 1 or 2, instead of zero.  (in order to avoid the refresh process at every single second, overloading the server data processing)

 

If you set it to zero, there should be no impact since you don't have any network connectivity issues in your Maximo system.

 

But this would depend on the specific Maximo environment that you are using, it is not a global recommendation that must be applied to all environments and all customers business. For example, if you are running many different processes at the same time in Maximo with many concurrent users on the system, you may want not to overload the maximo server with a request at each 0 seconds...  this is why in Maximo, the default is 15. 

 

As this considers update processes that are not fully synchronized with Maximo, we would recommend for performance purposes that you set it to a low value, such as 1 or 2, instead of zero.  (in order to avoid the refresh process at every single second, overloading the server data processing)

Here are some documents on how to make a field Always Sychonous and that solved similar issues for other cases 
 
Disable Data Validation 
http://www-01.ibm.com/support/docview.wss?uid=swg21516856 
  
Asynchronous Data Validation Troubleshooting Overview 
http://www-01.ibm.com/support/docview.wss?uid=swg21595657 
 
Enabling the asynchronous data validation functionality in IBM Maximo Enterprise Asset Management 7.5 
https://www.ibm.com/developerworks/community/blogs/a9ba1efe-b731-4317-9724-a181d6155e3a/entry/enabling_the_asynchronous_data_validation_functionality_in_ibm_maximo_enterprise_asset_management_7_58?lang=en 
 
Also we found that setting mxe.webclient.ClientDataValidation to 0 solved many validation delay issues. 

 

If you ever face this kind of behavior, feel free to try the following on a Test environment where you are able to replicate this issue.

 

Go to System Properties app, then make you have the following property set to a value of 0.

The properties in question are:
mxe.webclient.ClientDataValidation = 0
mxe.webclient.ClientEventQueue.timeout = 1
mxe.webclient.ClientEventQueue.threshold = 1
mxe.webclient.async = 1
mxe.webclient.asyncerrortooltipwaitbeforeopen = 2
mxe.webclient.asyncrendertimelimit = 1

If you do NOT have this property, please click on New Row and manually add it.
After that, restart you maximo application server completely and all its JVMs

 

But again, this is configured by each customer depending on which kind of processes are concurrent at a specific Maximo environment.

 

The only available documentation on the mxe.webclient.asyncrendertimelimit property is the System Administration guide.

 

See ya

[{"Business Unit":{"code":"BU005","label":"IoT"}, "Product":{"code":"SSLKT6","label":"Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":""}]

UID

ibm11112685