MUWG Session11 Spring 201

Maximizing Your Maximo Performance

— Darlene Nerden Maximo Systems Analyst

Tuning

Troubleshooting

Tools

Resources

• System architecture setup • Application server configuration • Scheduled tasks (cron tasks) • Reporting • Integration with other systems using the Integration Framework • Network (bandwidth/latency) • Database/SQL/index tuning • Application configurations • Client workstation configuration

Physical / Virtual Server

UI Cluster Database Server Web Application BrowserWeb ServerApplication BrowserWeb ServermaximoApplication Server Database Instance BrowserWeb maximo Browser maximo No. 3 Bottleneck

No. 4 Bottleneck

No. 2 Bottleneck maximo

No. 1 Bottleneck

• Application Server • JVM clustering (UI, cron, MIF, reporting) • Memory – both physical and JVM memory (6144m) • Garbage collection • Thread pool • Current fix packs • Database Server • Disk usage sizing • CPU sizing • Database memory • User I/O • Update Statistics • Reporting Server (replicated database) • Directory/LDAP Server • Integration component • Transaction rates • Clustering • Network • Bandwidth

IBM Watson• IoT / ©Latency 2019 IBM Corporation Tuning – Querying/SQL

• Search Methodologies – Default to “EXACT” • Set most ALN fields to UPPER • Do not use ‘not in’ or ‘!=‘ (this does a full table scan) • Use ‘in’ or ‘not exist’ • Educate users on ad-hoc queries • Check for newly created user queries and optimize • Identify long running reports • Escalations, Conditions • Start Center result sets, KPIs, Doclinks query • List panel ‘order by’ queries • Can remove ‘order by’ in presentation XMLs

• Reporting cluster (BROS) • Reporting database • Identify log running reports from report usage and tune them • Identify poor performing ad hoc reports • Scheduled report cron tasks • Execute in cron cluster • Separate these out of UI servers • Ensure long running scheduled reports are not submitted at the same time

• Separate sequential inbound and sequential outbound queues for integrated system • Limit the number of message driven beans (MDBs) on the continuous queue • Exception handling queues • ‘bad’ data redirect out of continuous queue • XML/HTTP instead of Simple Object Access Protocol (SOAP) web services • Less overhead and better performer under load • File import for XML documents containing multiple records

• 50ms or faster round-trip packet response between client and application server • Low bandwidth or high latency network • Citrix or Terminal Server • Compression techniques • HTTP compression • Web server • Hardware compression • Network appliances – Juniper and Riverbed • Provide compression and caching • Gzip compression • Maximo configuration • Acceleration • Caching • MaxAge – enabled by default on the application server • Configuring asynchronous and client side validation can improve the users experience • Good screen design can reduce traffic

• Best performance is achieved by using the newest supported Operating Systems and the latest hardware • Robust workstations provide better performance • Limit or prevent some workstation activities and processes • Monitor the network for streaming audio and video • Have only one network link active • Monitor for hung processes and applications

• Task focused screen design – create small screens • Limit number of fields on a single screen / develop silo (business unit) based screens with only the fields required for that silo • Off hours WO generation, Reorder, crons, and reporting • Reduce start center data retrieval • Keep the default start center simple to no data fetch portlets • There can be multiple start centers – the first one displayed should be simple to avoid excessive data fetch • Be sure that queries used on the start centers return small numbers of rows and are well tuned • Database connection pooling properties • Lower default properties values • Limit query times (system property)

• Configure client side and asynchronous validation to limit real time interaction with the database server • Limit the number of objects that can be fetched from the database in a single result set (system properties) • Fetch stop limits • Control queries in left hand navigation • Limit the number of queries that display for an application in the side navigation bar under ‘Available Queries’ (system properties)

• Carefully consider business requirements for frequency of cron tasks and escalations • Tune cron tasks and escalations • Adjust start timings to spread the load • Load balance across multiple JVMs

• Analyze and clearly define reported problem • Determine/define what is successful resolution • Focus on technologies that might impact issue • Maximo/Application Server/Database/Web Server logs • SQL logging to collect all SQL statements • Maximo logging marker • JVM memory usage – verbose GC • Database traces and snapshots • Network traces

• Maximo System Properties used as part of logging • mxe.mbocount • mxe.db.logSQLTimeLimit • mxe.db.fetchResultLogLimit • mxe.db.logSQLPlan (Oracle only) • mxe.db.sqlTableScanExclude (Oracle only) • Fetch stop limit • mxe.db.fetchStopLimitEnabled • mxe.db.fetchResultStopLimit • mxe.db.fetchResultStopLimit.OBJECTNAME • mxe.db.fetchStopExclusion

• Enable Connection Pool Watchdog to monitor database connection pool • Close long running database connections • Use database tools to find long running queries and recommended indexes • Test queries through SQL development tools and add required indexes • Network pings and trace routes from client to Maximo server • Monitor CPU and memory usage • Apply the latest patches

• Integrity Checker to find Maximo schema problems that can affect applications as well as performance • LA Test Fix tool • IBM Support Assistant (ISA) • Real world load testing • WebSphere Performance Monitoring Infrastructure (PMI) • Database Utilities • Operating System tools • Bandwidth / Throughput monitoring tools • IBM Thread and Monitor Dump Analyzer for Java • Heap Analyzer • Customization Detection Tools • Maximo Management Interface (MMI)

Application Server IBM WebSphere Tuning (can cause application to hold objects too long if not set correctly) Oracle WebLogic Tuning Using Multiple JVMs to Support Users and Functionality

Network Performance Network caching and compression properties Browser Caching (Helps with Wide Area Network -WAN- performance and high latency)

Reporting BIRT Reporting Performance document link – Maximo 7.6

Database Server Performance SQL Server Index Tuning SQL Server Row Versioning Maximo on SQL Server Performance SQL Server Turning of Page Locking

Database Server Performance Oracle Cursor Sharing DB2 Parameter Tuning Database Connection Leak Resolution How to detect database connection leak How to solve database connection leak

Application Performance Understanding Search Methodologies Start Center Performance Improving Performance Using Small User Interface (UI) Screens Disable Data Validation

Best Practices Maximo 7.6 Performance Best Practices Maximo Wiki Maximo Wiki Performance Page Best Practices for Performance Wiki Page

Troubleshooting Debug properties Understanding the MBOCount Debug Property Understanding the logSQLTimeLimit Property Understanding the fetchResultLogLimit Property Collecting Data/Must Gather – General Information Collecting Data/Must Gather – Performance Logging Logging Appenders Using fetch stop limits to prevent out-of-memory errors Maximo Performance Monitor Configuration

Tools IBM Support Assistant IBM Thread and Monitor Dump Analyzer for Java Heap Analyzer Customization Detection Tool Wait Tool Maximo Management Interface (MMI) Maximo Management Interface (MMI) Maximo Management Interface (MMI) Maximo Management Interface (MMI) HttpWatch WireShark WinPcap

Darlene Nerden Maximo Systems Analyst — dnerden@us.ibm.com ibm.com