The Monitor action allows an administrator to view current state of the Informer processing queues and their processors, as well as performance information if available. When an action occurs within Maximo that may impact a record on a device the action information is put into a queue to be processed in the background. This ensures that the Maximo UI is never impacted by the evaluation of records destined for mobile devices. To ensure that Informer remains scalable, the queue is designed for high volume parallel processing across multiple threads and multiple nodes within a cluster. Being able to view the state of the various threads across the nodes in the cluster is key to understanding the system health and performance.
Note that when the Maximo system is in Admin Mode queue processing is suspended.
There are three categories of Queue Processor: Notification, Catalog, and Push.
The Notification Queue dialog displays:
The Total records in the queue will include:
User Refreshes are evaluations of the query or workflow process that defines the records to be sent to the user. This evaluation determines whether records have come into or gone out of scope of the query or the user's workflow inbox. These will add and/or remove user notifications, as displayed on the User Tab for each user.
If an error is encountered during processing, in most cases the error is logged to the Maximo log and the record is automatically retried. When an unexpected error occurs, the error is logged to the Maximo log and the record is retried according to the system property informer.queue.maxerror (or 5 times if this property is not set). If this retry count is exceeded, the refresh queue entry is marked in error, and will not be further evaluated until it is reset by an administrator.
The Queue Processors table then provides information about each Host running one or more processing threads, the node name of the JVM, the name of the thread, its current stated, WAITING, ADMIN MODE, or ACTIVE and the time stamp when the data was last updated. In the screen shot below there are two threads running on a single host running a single JVM node.
The Refresh button can be clicked to refresh the data on the screen with newly collected information from the server if it is available.
The Refresh button can be clicked to refresh the data on the screen with newly collected information from the server if it is available.
The Reset Error button allows an administrator to force all records in Error status to reset. This is useful if the cause of the error has been resolved, and allows the records to be processed by the queue processors.
The Catalog Queue dialog displays:
The Total records in the queue will include:
Historical performance information presented on this tab is generated by the "InformerStats" CronTask, if enabled.