Gathering information for support

Use the MustGather Tool in the IBM® Maximo® Real Estate and Facilities Administrator Console to gather information on your application server, web server, database, and Maximo Real Estate and Facilities implementation.

Review the application stack

Draft comment: michael.bowler@ibm.com
This topic is overloaded with references to other Perf Mgt pages. I'm considering replacing all these with one reference to the top-level perf Mgt topic and let readers navigate from there??
Review each tier of the stack as a potential source of the performance bottleneck:
  • Maximo Real Estate and Facilities
  • Software services
  • Operating systems
  • Hardware servers
  • Network architecture
For more information, see the infrastructure pyramid in Planning for optimized performance. Identify the segments of the pyramid where you isolated the performance issue. Also see Gathering troubleshooting data.

System architecture

Do you have a basic, typical, or advanced system configuration? Review the relevant sections in Tuning system architecture and hardware.

Application server

Record the following application server parameters:

  • All application server initial and maximum JVM heap sizes.
  • Any additional JVM arguments that are added.
  • JDBC minimum and maximum connection pool values.

If you are using IBM DB2®, confirm that the REOPT(ONCE) bind option and isolation level are set at the application-server level. For more information, see Tuning the IBM DB2 server.

Web server and load balancing

Confirm the following details:
  • If you are using IBM HTTP Server, confirm that you followed the tuning recommendations.
  • Confirm if HTTP compression is used.
  • If you are using a load balancer, confirm that you reviewed the load balancing recommendations.

Database server

Confirm the following details:
  • If you are using Oracle, confirm the values for CURSOR_SHARING, NLS_LENGTH_SEMANTICS, PGA, and any other settings. For more information, see Oracle database.
  • If you are using IBM DB2, confirm the values of all registry, database manager, and configuration settings. For more information, see Tuning the IBM DB2 server.
  • If you are using IBM DB2, confirm the use of automatic buffer pool size and auto extends. For more information, see Tuning the IBM DB2 server.
  • Use standard database tools to check which database monitoring is enabled. Also check which database indexes were added or customized based on the best practices.
  • Specify the table spaces that are used and whether you added a third table space for binary large objects (BLOBs).
  • Check that statistics are updated regularly.
  • Did you perform any reorganization of tables or indexes? For more information, see 5 Database Server Tuning and Maintenance.
  • Does the database use multibyte character sets (MBCS)?
  • Is there an archiving strategy in place and how frequently is archiving performed?

Network

Confirm the following details:
  • Confirm if hardware compression is used.
  • List the results of a network speed throughput test on a sample client machine that exhibits slow performance. For more information, see Tuning the Network.

Maximo Real Estate and Facilities

Confirm or provide the following details:
  • Provide a list of values for every property. For more information, see System properties.
  • Provide a list of every running agent on each Maximo Real Estate and Facilities server that is indicated in your system architecture.
  • Confirm the thread count values of all multithreaded agents. For more information, see System properties.
  • Confirm all Workflow Agent settings and properties such as WFAgentMaxThreads and WF_AGENT_MAX_ACTIVE_PER_USER. For more information, see System properties.
  • Confirm that the Platform Maintenance Scheduler is running. Note the activities that it runs and the value of the CLEAN_HOUR property.
  • If the performance issue is determined to be at the Maximo Real Estate and Facilities tier, run and analyze performance logging. Determine the primary Maximo Real Estate and Facilities components that are running slowly and why. If the slow-running components are customized, identify these customizations in the logs.
Evaluate the performance of optimized components based on the following items:
  • Confirm that any slow-running reports that are identified in the performance logging are optimized. For more information, see Query and report performance. If the report is still slow, include information from the database about the query execution plan for any SQL running during the report execution. For example, an AWR report or execution plan XML file.
  • Confirm that fields and extended formulas that are identified in the performance logging are optimized or are required for the business process. For more information, see Query and report performance.
  • Confirm that custom BIRT reports use the appropriate filtering to limit the result set.
  • Confirm that workflows that are identified in the performance logging are optimized and trigger an extended formula in areas, such as Query Task versus Retrieve Records Task, only when needed. For more information, see Workflow performance. Also, did you run the Workflow Analysis Utility, and what are the results?
  • Detail any integrations that run during slow performance periods. Identify which APIs are used, what they do, and when they run. Confirm that you followed the tuning recommendations. For more information, see Integration framework.