Technical Blog Post
Abstract
Asynchronous Processing in Maximo 7.5
Body
Maximo 7.5 has a new way to process set value events called asynchronous processing. The set value events will not be sent to the server immediately, instead, these events will be buffered on the browser until an event occurs that requires a request to the server like 'click save'. The asynchronous processing will reduce end user response times for common user activities which do not require complex business rules by reducing the request number.
For example, insert a new record:
For example, insert a new record:
Requset processing in Maximo 7.2
Asynchronous Requset processing in Maximo 7.5
There are some system properties to control the asynchronous processing function in Maximo:
mxe.webclient.async : Enable(1) or disable(0) asynchronous processing function in Maximo. (default is 1)
mxe.webclient.ClientEventQueue.threshold : The max number (default is 2)of events are buffered in browser, if this value is 1, the queue is disabled and all events are immediately sent.
mxe.webclient.ClientEventQueue.timeout : Timeout (default is 10 sec) when the event buffered in the browser, if nothing else has caused the events queue to be sent, it will be sent when this timer expires.
Remind, the asynchronous processing will only queue events that don’t require any server validation.
For more information on asynchronous processing, reference this previous blog entry which provides additional screenshots and details on this functionality.
Jack Ling
Tivoli Integration Performance
[{"Business Unit":{"code":"BU059","label":"IBM Software w\/o TPS"},"Product":{"code":"SSLKT6","label":"IBM Maximo Asset Management"},"Component":"","Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"","Edition":"","Line of Business":{"code":"LOB59","label":"Sustainability Software"}}]
UID
ibm11134021