What customizations were made to my Maximo Asset Management environment?Do you need a quick way to determine what customizations you’ve made to your Maximo Asset Management 7.5 installation? If so, check out the Customization Detection tool. The tool currently works on Maximo Asset Management Version 7.5.0.0 and higher. The tool provides information about customizations for business objects, field classes, and services that were customized (extended/added) for the out-of-the-box system. It does not provide information about UI bean classes or other configuration changes. For information about the tool and to see a sample of the output that it produces, see the Maximo Asset Management wiki article here. You can download the tool via the Integrated Service Management (ISM) Library here.
Sample output
|
Welcome to the Asset Management Blog, where you can read the perspectives from Asset Management experts. This Blog provides technical insights into the Maximo product solutions.Installing WebSphere...
Actualizada
Gusta 0
Comentarios 0
VMMSYNC workings and...
ActualizadaGusta 2
Comentarios 1
How to add a read-wr...
ActualizadaGusta 0
Comentarios 0
Date field calculati...
ActualizadaGusta 0
Comentarios 0
Maximo Asset Managem...
ActualizadaGusta 0
Comentarios 0
How is this tool different from :- <div> </div> select OBJECTNAME, CLASSNAME from MAXOBJECT where CLASSNAME not like 'psdi.%'; <div> </div> select OBJECTNAME, ATTRIBUTENAME, CLASSNAME from MAXATTRIBUTE where CLASSNAME not like 'psdi.%'; <div> </div> select SERVICENAME, DESCRIPTION, CLASSNAME from maximo.MAXSERVICE where CLASSNAME not like 'psdi.%'; <div> </div> <div> </div> -Sanjay
The query you have is very basic and assumes that the user won't use psdi. as the package prefix. There is also a case that is not covered by the query. For example, the customer might use product.xml and could name it so that custom extensions are hidden in the database. Also, while you know the basic query, not everyone does.
Well psdi is reserved for out of the box naming convention and all custom code should not use it. It is the standard practice in Maximo. Most of the consultants are aware of these tables and the class name and hence the basic sql to pull this information. <div> </div> I don't see any specific reason to hide the customization into product.xml. In fact best practice is the customization should be in the form of easy plug and unplug. Why do we require to hide it?
-Customer can call their <product>.xml as customer.xml or zzz_customer.xml or anything they prefer. In case customer calls it custom.xml and has product like Utilities installed (which has tnd.xml) and if both Utilities and Customer extend the same class. The database would reflect Utilities class which wont be shown by your query.
-The tool is designed specially for support team and not all support folks might know the queries.
-The report also shows how heavily customer system is customized.
-The tool also shows you whats the class extension hierarchy and few time there are PMRs reported which class hierarchy is incorrect due to some miss-steps. This report can be used to see the actually hierarchy versus whats on customers system.
Ok this makes sense. But I never came across this. Thank you. Appreciated.
Anyone know where to find a good example on how to properly create the customer.xml? <div> </div> We don't have any utilities installed, I just want a way to avoid the extended classes being removed after updatedb. <div> </div> thanks for any help.
You might want to check out this article on the Maximo Asset Management wiki: https://www.ibm.com/developerworks/community/wikis/home?lang=en#!/wiki/IBM%20Maximo%20Asset%20Management/page/Customizations%20with%20other%20add%20on%20products