Comments (7)
  • Add a Comment
  • Edit
  • More Actions v
  • Quarantine this Entry

1 maximo_TND commented Permalink

How is this tool different from :- <div>&nbsp;</div> select OBJECTNAME, CLASSNAME from MAXOBJECT where CLASSNAME not like 'psdi.%'; <div>&nbsp;</div> select OBJECTNAME, ATTRIBUTENAME, CLASSNAME from MAXATTRIBUTE where CLASSNAME not like 'psdi.%'; <div>&nbsp;</div> select SERVICENAME, DESCRIPTION, CLASSNAME from maximo.MAXSERVICE where CLASSNAME not like 'psdi.%'; <div>&nbsp;</div> <div>&nbsp;</div> -Sanjay

2 charglen commented Permalink

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.

3 maximo_TND commented Permalink

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>&nbsp;</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?

4 SmarterInfrastructureGuy commented Permalink

-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.

5 maximo_TND commented Permalink

Ok this makes sense. But I never came across this. Thank you. Appreciated.

6 CanuckDuck commented Permalink

Anyone know where to find a good example on how to properly create the customer.xml? <div>&nbsp;</div> We don't have any utilities installed, I just want a way to avoid the extended classes being removed after updatedb. <div>&nbsp;</div> thanks for any help.

7 charglen commented Permalink

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