© 2009 IBM Corporation IBM Maximo Understanding IBM Maximo Architecture - Configuration and...

© 2009 IBM Corporation

IBM Maximo

Understanding IBM Maximo Architecture - Configuration and Performance

2 of 50

IBM Maximo

Maximo Architecture | Premium Support Presentation © 2009 IBM Corporation

Overview

J2EE/Java Application Architecture The TPAE Architecture Maximo Reliance Pyramid Network

– LAN / WAN

– Resolving Issues

Hardware– Minimum Requirements

– Common Problems

– Soft and Hard Partitioning

Services– J2EE Services

– Database Services

– Report Services

Maximo– Fine Tuning

Questions

3 of 50

IBM Maximo


Considerations for this presentation

Because of the approach of this presentation, some technologies will be covered from different perspectives (Example Network tuning and Maximo tuning for the network)

Every environment is different and exact tuning solutions require and analysis of a specific environment


IBM Maximo

J2EE Application Architecture

Java 2 Platform Enterprise Edition Application Architecture

5 of 50

IBM Maximo


Quick overview of Java Technologies

Java code is written in a text style editor in semi English terms.

Source text files (.java) are compiled using a java compiler (javac) to become class files (.class)

Class files are really a collection of tokens that execute in a Java Virtual Machine (JVM)

JVMs are written for each computer environment (OS, Processor).

Since it is the JVM that is running on the computer equipment, Java code does not have to be recompiled for different computers. The same code runs in different JVMs

6 of 50

IBM Maximo


Quick overview of Application Servers

Java code can execute in a JVM without the use of an Application Server

Application Servers were designed to simplify JVM management and provide additional functionality

Application Servers provide deployment, logging, memory management and other services

Additional functionality provided by most Application Servers includes JDBC pooling, JMS Queues, and Load Balancing

7 of 50

IBM Maximo


Technology Relationships of Java Programs

The Application Server starts => The JVM starts

=> The Java code starts

So Maximo relies on the JVM to run which relies on the Application Server to run which relies on the Operating System to run

Application Server (IBM WebSphere or Oracle WebLogic)Manages the JVMs

Java Virtual Machine (IBM, Sun, and others)Executes the Java Code

Java Code (Maximo and others)Contains the application logic

8 of 50

IBM Maximo


External Technology Relationships

Java code can have reliance on external technologies in addition to the Java relationships. In Maximo’s case, it relies on external database technologies and may rely on external report technologies.

Maximo does not use Application Server JDBC pooling

Application Server (IBM WebSphere or Oracle WebLogic)Manages the JVMs

Java Virtual MachineExecutes the Java Code

Java CodeContains the application logic

External DB Technologies (DB2, Oracle, SS)Manages the data from the application

External Report Technologies (Actuate)Manages the reporting for the application

9 of 50

IBM Maximo


Resolving J2EE configuration issues

Each layer of technology relies on the layer it resides in

J2EE Layers can be reviewed separate from external technologies

External technologies such as database and report can be reviewed separate from J2EE

Both J2EE and external technologies may have common reliance such as network


IBM Maximo

The TPAE Architecture

Tivoli Process Automation Engine (TPAE) Architecture

11 of 50

IBM Maximo


What is TPAE?

The Tivoli Process Automation Engine provides basic services to applications that are built on it’s architecture

Functionality such as database connectivity, email listeners, cron tasks, workflow, security and much more is built into TPAE and provided to applications

Applications that use TPAE have a single point of troubleshooting for core issues


IBM Maximo

The IBM Maximo Reliance Pyramid

Tips for finding performance bottlenecks

13 of 50

IBM Maximo


The Maximo Reliance Pyramid

14 of 50

IBM Maximo


Reliance on other technologies complicates

To simplify troubleshooting, start with the least reliant technology and build towards the most reliant

Using the bottom up approach to the reliance pyramid, troubleshooting starts with network and progresses upward.

– Maximo

– Services

– Hardware

– Network

The Approach Used For Troubleshooting

15 of 50

IBM Maximo


Networks – The Ground Rules

Maximo uses about 32 kbps in bandwidth per concurrent user

Maximo performs best in 50 ms or less latency

– It takes thousands of packets to display a single User Interface (UI) screen

– 1000 * 50 ms = 50,000 ms or 50 seconds

16 of 50

IBM Maximo


Networks – Bandwidth

Bandwidth is the amount of data that can be transmitted simultaneously

Using a 56 kbps connection to transmit 512 kbps of data will…. fill up your “tubes”

Maximo uses approximately 32 kbps per user. Multiply 32 * number of concurrent users to determine required available bandwidth

17 of 50

IBM Maximo


Networks – Latency

Latency is the amount of time in milliseconds that it takes for a packet to reach its destination and a receipt to be sent back to the sender

When too much data is sent through a connection, it is put in a queue and transmitted as bandwidth becomes available

Queued data takes longer to transmit because of the wait time and results in higher latency

Since latency is a key factor in Maximo performance, proper bandwidth must be allocated in order to ensure maximum performance

18 of 50

IBM Maximo


Maximo On The NetworkMaximo

Application

Server

Database

Server

Report

Server

19 of 50

IBM Maximo


Networks – Wide Area Networks (WAN)

Cloud

20 of 50

IBM Maximo


Networks – Quick Answers

Two simple commands to help determine performance

ping tracert

Senator Ted Stevens explains network communication best

21 of 50

IBM Maximo


Networks – Objects vs. Packets

Two objects can be related to packets:– Object 1 = 51 bytes and can be placed in 1 packet

– Object 2 = 2,330 bytes and can be placed in 2 packets

How does this translate into performance?– It takes 100 copies of object 1 to make up 1 copy of

object 2

– Object 1 takes 98 more packets to transfer and cover the same area as object 2

– At 50 ms latency, object 1 will fill the area in 5 seconds while object 2 will only take 1/10 of a second

22 of 50

IBM Maximo


Networks – Maximo vs. Web Pages

Images and objects (Application Designer)– Web Pages use larger images for static content

– Maximo breaks images into smaller objects

Validation (Ajax type technology)– Web pages typically validate at submit time

– Maximo validates and secures at field level during input

User Interface and Data Manipulation (ad hoc search)– Web pages typically focus on a specific job

– Maximo provides a high level of customization capability and user flexibility to access and manipulate large quantities of data

23 of 50

IBM Maximo


Networks – Optimization Technologies

Citrix / Terminal Server (Client Emulation)

Junniper, Expand, & similar – (Single Device Acceleration / Caching, HTTP Header Compression)

Riverbed & similar – (Multi-device Acceleration / Caching, Compression, HTTP Headers)

24 of 50

IBM Maximo


The Maximo Reliance Pyramid - Networks

You are here

When network tuning is complete, the next step is Hardware

25 of 50

IBM Maximo


Hardware is measurable & relatively easy to define

Maximo requires a minimum of 900 MHz processors, enough memory to support the Java JVM, and network connectivity (a NIC card)

If these minimums are not met, Maximo may still run but is not supportable

Check documentation for specific release requirements

Hardware

26 of 50

IBM Maximo


Hardware - Operating System Relationships

Hardware is the physical equipment (processor, memory, storage devices, monitors) that software runs on

Operating systems manage the hardware and how it is used by software programs

All calls and uses of hardware are processed by the operating system

If the operating system runs poorly then the software running in it will run poorly

27 of 50

IBM Maximo


Hardware – Common Windows OS Problems Mapped drives requiring network access for logs &

attached documents

When building/deploying EAR files, remote source files may cause the build/deploy process to perform poorly

Operating System swap space and memory management

Disk space / quotas

Configuration of the Network Interface Card (NIC)

Antivirus software on the server set too aggressively

Windows defaults to a more open security architecture than Unix but can be locked down

28 of 50

IBM Maximo


The #1 OS problem experienced in Unix is privileges!

Unix defaults to a more secure security architecture than Windows does but privileges can be granted. If access to required files is denied, Maximo may not run properly

Mounted drives requiring network access for logs and attached documents

Operating System temp space and memory management

Unix Configuring X-Windows, XVFB, and the display variable on the server

Disk space / quotas for logs & attached documents

Unix controls upper limits on all types of connections such as DB connections, open files, logins etc… These can prevent proper function. (set “ulimit” for open files and memory)

Hardware – Common Unix OS Problems

29 of 50

IBM Maximo


Physical servers can be divided into physical partitions. Example: 4 processors, 4 GB memory, can be 4 separate hard partitions acting as 4 separate computers, each one independent (IBM LPAR, Sun Domain, etc)

Physical partitioning usually applies to large Unix based systems

Soft partitions such as VM Ware and Microsoft VM are more PC oriented. VM Ware is not supported for production environments until release 7.1.1.4

Hardware – Partitioning

30 of 50

IBM Maximo


The Maximo Reliance Pyramid - Hardware

You are here

When hardware tuning is complete, the next step is Services

31 of 50

IBM Maximo


Maximo is a software product written in Java that pulls together many types of technology to empower users

If a service is not performing well, that functionality of Maximo will not perform well

Tuning services is heavily reliant on recommendations from the manufacturer of that product

Services include J2EE, JVM, Database, Reporting and others that Maximo relies on

Services – How they affect Maximo

32 of 50

IBM Maximo


Services – How they affect Maximo

If database queries run slowly then Maximo performance will degrade due to waiting for database response

If the J2EE server (IBM WebSphere or BEA WebLogic) does not perform well, Maximo running inside the J2EE server cannot perform well

If the JRE / JVM that the J2EE server uses does not perform well, Maximo cannot perform well

If the report server does not perform well, reports may be slow and other areas of Maximo may be affected

33 of 50

IBM Maximo


Services – Database - How they affect Maximo DB2 has a cost driven optimizer , executing the RUNSTATS

utility will update the catalog and improve performance

Maximo does not use bind variables. Oracle will perform better if cursor_sharing is set to similar or force

In Oracle, more SGA is better, Oracle for Windows may have memory limitations

SQL Server uses memory page level locking by default. High concurrent user counts can cause database locks as a result. SQL Server will perform better if row level locking is enabled

Any database platform will perform better if indexing has been tuned for your particular use

34 of 50

IBM Maximo


Services – J2EE Services - How they affect Maximo

If the J2EE server (IBM WebSphere or BEA WebLogic) or the JVM supporting Maximo does not perform well, Maximo cannot perform well

WebSphere should have cache settings and TCP/IP settings tuned to perform well

WebLogic should have threads tuned to perform well

HTTP servers and JVMs be deployed in sufficient numbers to support incoming requests and should be load balanced

Documents 1261874 & 1261853

WebSphere Tuning - http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21261874&loc=en_USWebLogic Tuning - http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21261853&loc=en_US

35 of 50

IBM Maximo


The Maximo Reliance Pyramid - Services

You are here

When service tuning is complete, the next step is Maximo

36 of 50

IBM Maximo


Maximo Tuning – Common Performance Problems

Network Issues described earlier

Too many users on too few JVMs

Minimal training for end users causing improper use

Configuration choices at implementation time

Memory leaks

Databases not properly tuned

Log Overkill

37 of 50

IBM Maximo


Maximo Tuning – Network Properties

Maximo 6.1 built in compression – (Software Compression / Gzip)

Maximo 6.1 built in caching – (Software Caching / max-age)

Document numbers 1262009 & 1292557

http://www-1.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21262009&loc=en_UShttp://www-1.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21292557&loc=en_US

38 of 50

IBM Maximo


Maximo Tuning – Concurrent Users Maximo should be clustered and load balanced to

maintain less than 50 concurrent users per instance

50 users is a guideline not a hard number. 50 users logged in and not doing anything is not the same as 50 users run in a Load Runner script hammering the system

Performance testing scripts should include wait times, different users, and different tasks to ensure a more real world experience

Be prepared to add more instances if performance is not as targeted. Document 1329219

http://www-01.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21329219&loc=en_US

39 of 50

IBM Maximo


Maximo Tuning – Minimal Training

Maximo is very flexible and often has more than one way to accomplish a task

Untrained users often choose an approach that may be less than optimal

Common tasks should be reviewed by knowledgeable staff to fine tune processes

Maximo searching is very powerful but if misused, can impact performance for all users

40 of 50

IBM Maximo


Maximo Tuning – Configuration Choices Search functionality defaults to the most flexible

searching method but burdens the database server. Search methodologies include:• Wildcard (default)

• Exact

• Text

• None

User loads, type of work and user training may dictate changing the default search methodology

A common implementation approach is to create catch all screens for users. More smaller screens can improve performance over larger crowded screens

41 of 50

IBM Maximo


All programs have bugs

Some memory leaks may be related to invalid program data (example parent/child locations set as the same value causing a loop)

Some bugs may be related to custom coding

Memory and MBO’s will continue to grow and not release if there is a memory leak – Documents 1291250 & 1326774

• 07 Apr 2008 11:14:22:622 [INFO] WORKORDER: mbosets (272), mbos (306)







Maximo Tuning – Memory Leaks

http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21291250&loc=en_US

http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21326774&loc=en_US

42 of 50

IBM Maximo


Maximo Tuning – Databases

Maximo is shipped for generic use. A specific implementation requires specific index and database tuning

Tuning the database will involve a good understanding of the database environment as well as the ways Maximo is used in a given environment

If Maximo is more focused on purchasing, tuning work order tables and indexes will probably not help

Use Maximo logging properties to identify problems

Document 1291250http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21291250

43 of 50

IBM Maximo


Maximo Tuning – Database (SQL Server 2005) SQL Server 2005 tuning parameters

• mxe.db.disableservercursor=Y

• mxe.db.resultsettype=TYPE_FAST_FORWARD

• mxe.db.fetchsizeuse=Y

• mxe.db.fetchsize=40

• mxe.db.optionuse = Y

• mxe.db.optionnum=1000

• mxe.db.sqlserverPrefetchRows=200

Note: For Maximo releases > 6.1 & SQL Server 2000, these values are different

Documents 1268567, 1296072, 1313428

http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21268567http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21296072http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21313428

44 of 50

IBM Maximo


Maximo Tuning – < 6.2 Database (SQL Server 2000) Use SQL Server tuning parameters to manage cursor

usage


• mxe.db.resultsettype=TYPE_SCROLL_INSENSITIVE


Note: For Maximo releases > 6.1 & SQL Server 2000, these values are different

Documents 1268567,1295983, 1313428


45 of 50

IBM Maximo


Maximo Tuning – > 6.1 Database (SQL Server 2000) Use SQL Server tuning parameters to manage cursor

usage


• mxe.db.resultsettype=TYPE_SCROLL_INSENSITIVE


• mxe.db.fetchsize=40

• mxe.db.rowcount=15000

• mxe.db.optionuse=N

Note: For Maximo releases < 6.2 & SQL Server 2000, these values are different

Documents 1268567,1295983, 1313428


46 of 50

IBM Maximo


Maximo Tuning – Oracle

Use Oracle logging properties to identify problems

Ensure that Oracle has enough SGA

Ensure that Oracle is set to: Cursor_Sharing=similar

Ensure that Oracle is upgraded to 9.2.0.8 or later

Ensure that Oracle is set to Cost Based optimization

http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21262180http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21262959

47 of 50

IBM Maximo


Maximo Tuning – Logging

Setting verbosity 9 or debug mode makes finding a problem in a log like a needle in a haystack

Setting verbosity 9 or debug mode causes performance problems, impacts disk space and may cause the log to roll before the issue can be captured

Minimizing logging can impact problem resolution times. Typical logging should be set at verbosity 3 and per document 1291250 for general runtime.

Use common sense when logging for a suspect issue

Debug Logging - http://www-1.ibm.com/support/docview.wss?rs=3214&uid=swg21291250&loc=en_US

48 of 50

IBM Maximo


Maximo – Tuning and Troubleshooting

Use the Maximo debug parameters to ensure that SQL is performing well

– mxe.db.logSQLTimeLimit (5.2 P02A and above)

– mxe.db.logSQLPlan (6.0 P01 and above - Oracle)

– mxe.db.sqlTableScanExclude (6.0 P01 and above - Oracle)

Use the debug parameters to ensure that memory is performing well

– mbocount (5.2 P05 and above - different implementations)

– mxe.db.fetchResultLogLimit (5.2 P02A and above)

Document numbers 1291250 & 1326774

http://www-01.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21291250&loc=en_UShttp://www-01.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&uid=swg21326774&loc=en_US

49 of 50

IBM Maximo


This link is the key to finding good information on Maximo

WebSphere Tuning - 1261874Gzip / max-age – 1262009Oracle performance - 1262959 & 1262180max-age - 1292557SQL Server - 1268567SQL Server 2000 - 1295983 &

1313428SQL Server 2005 - 1296072Debug logging - 1291250

Type the document reference number into the search criteria

Important Information to Take Awayhttp://www-1.ibm.com/software/sysmgmt/products/support/IBMMaximoAssetManagement.html

Or go to http://www.ibm.com and enter the following in the search field (include the quotes)

"IBM Maximo Asset Management Support"

50 of 50

IBM Maximo


Questions

© 2009 IBM Corporation IBM Maximo Understanding IBM Maximo Architecture - Configuration and...

Documents

Transcript of © 2009 IBM Corporation IBM Maximo Understanding IBM Maximo Architecture - Configuration and...