Chapter 10.12.4. Loading and looping of MBOs in memory

Page 207

Chapter 10. Other configuration options 207 Before implementing any application change, ensure you have a change management procedure and release management protocol in place. Also ensure that change requests are approved by senior management and that they match your business processes. Change requests are best released in phases in the deployment: for example, first the development environment, then training, then acceptance, and only then to the production environment. Use tools such as the Migration Manager to maintain identical deployment platforms. Review updates and new patch releases in development environments before attempting to implement these changes in acceptance and production environments. If you are experiencing technical issues with the IBM Asset Management application, copy the IBM Maximo Asset Management database and restore it in a test environment. From there, enable debugging by using the Logging application. Avoid running the Logging application in the production environment; logging may hinder the performance of the application server. Monitor for processes and applications that are not responding. They use memory and can affect the performance of the client workstation. A workstation can have unresponsive processes or applications that the user might not be aware of. Use system tools, such as the Windows ® Task Manager, to check for and stop processes and applications. Use one active network link only. If a user has both an active wireless network link and an active LAN link, system performance issues can result. Limit users to one active network link. 10.12.4 Loading and looping of MBOs in memory MBO stands for Maximo Business Object. All objects in Maximo ( Tivoli Process Automation Engine) are represented as MBOs. These objects have their definitions ( including parent- child relationships) in the meta data of the Tivoli Process Automation Engine database. You can learn whether an application or an MBOset is loading a large number of objects ( MBOs, for example) into the MBOset and, in turn, into memory. Enable the following property in the maximo. properties file to display MBO creation: mxe. db. fetchResultLogLimit= 200 Note: To tune the IBM Maximo Asset Management V7.1 for better performance, review the SQL statements periodically in the QUERY and KPIMAIN tables.

..................Content has been hidden....................

You can't read the all page of ebook, please click here login for view all page.
Reset