The web blog strives to be a comprehensive guide to SCCD, TADDM, SERVICE NOW and MAXIMO tools. This is a personal site maintained solely by me. I intend to update it regularly.For live updates please follow us on.

What are beans in IBM Maximo?

Beans in Maximo

There are 2 types of Beans in IBM Maximo, App Bean and Data Bean.
App Bean
The App Bean manage application functionality, such as WOTRACK or ASSET. This class is defined in the bean class attribute of the presentation tag in the application’s XML.

If you export the WOTRACK application XML and go to the bottom of the file you can see a group of actions (action tag) defining actions and their corresponding method in the App Bean bean class.

For instance if you’d like to add a button on WOTRACK to approve a work order besides of creating the SIG OPTION and TOOLBAR records for that operation you’d also have to develop custom Java code for it, this would be done in the App Bean.

Data Bean
Data Beans can manage both dialog boxes and tables. The Data Bean class associated is defined in the bean class attribute of both the dialog and table tags in the application’s XML.

For instance, on dialog boxes you can use a Data Bean to control what to do when the OK button is pressed (submit() method).

On tables you can do things such as custom the way to load the MboSet on that table (getMboSet() method).

You have to have in mind that the flow control of the dialog’s execution is quite complex. For instance, if you don’t provide a submit() method on your dialog’s bean class, Maximo will try executing other methods and will end up executing the execute() (I think this is the method) method of the MBOSet associated with your dialog (defined with the mbo name attribute of the dialog tag).