IBM Maximo consultant, geek, agile evangelist
This entry is part of the Java MBO performance optimization golden rules series. Sometimes you have to perform some complex logic or you have to join several tables to retrieve a piece of data. In other cases there is a piece of code where performance is critical. In such cases it may be hard to […]
This entry is part of the Java MBO performance optimization golden rules series. A not well tuned SQL query is often the biggest contributor to elapsed time taken by Maximo Business Objects (MBO) logic. A general example of this is the use of IN or NOT IN in SQL where clauses. Avoid IN or NOT IN […]
This entry is part of the Java MBO performance optimization golden rules series. It is important to know the difference between close(), cleanup(), and clear() methods and use them to free up resources as soon as possible. close(): Close the cursor, release the database resources (result set), SQL statement, and connection key. Does not release […]
This entry is part of the Java MBO performance optimization golden rules series. The MboSet.setQbe() method is designed to be used to build filters from the user interface. Using the MboSet.setQbe() method will automatically add jolly characters in text searches preventing the database server to be able to use indexes.For example let’s look at the […]
This entry is part of the Java MBO performance optimization golden rules series. This tip regards the correct handling of transactions in TPAE. The important concept to understand is that MBOs obtained via relationship are included in the same transaction as the parent MBO set. When any MboSet in the transaction is saved, all MboSets […]
This entry is part of the Java MBO performance optimization golden rules series. The initValue() method is the first method executed after the MBO constructor. It is typically used to initialize attributes on new records and to set default values.The init() method is called after initValue(). It is typically used to set current attribute as […]
This entry is part of the Java MBO performance optimization golden rules series. If an MboSet is used for traversing forward only and not to be saved make it discardable by setting the DISCARDABLE flag.The following snippet shows how to do it. MboSetRemote mboSet = getMboSet(“ASSET”);mboSet.setFlag(MboConstants.DISCARDABLE, true);MboRemote mbo=null;for(int i=0; (mbo=mboSet.getMbo(i))!=null; i++){ …} Using a discardable […]
This entry is part of the Java MBO performance optimization golden rules series. I think this is one of the most common errors when developing Java MBO code.The MboSet.count() method issues a “SELECT COUNT(*) from …” SQL query to retrieve the number of records in the database table.This can be a big problem especially when […]
This entry is part of the Maximo Java Development series. In this post I have collected the most important Maximo Business Objects (MBO) development performance tips and suggestions that I have learned during my job as a Maximo Consultant.These suggestions are partly distilled from the IBM Maximo wiki page trying to organize and simplify the […]
Here is a useful IBM Technote that explains how to capture all SQL statements issued from Maximo/TPAE when using DB2 database. I think it may be useful to analyze users queries and performance bottlenecks.