1 / 17

Maximo 7.1 AVP Constellation Energy Group

Richard Goyette – Advisory Software Engineer 19 August 2010. Maximo 7.1 AVP Constellation Energy Group. IBM Presentation Template Full Version. Agenda. Introduction Maximo and Linux considerations Maximo and VMware considerations Performance considerations Review / Q&A.

almag
Télécharger la présentation

Maximo 7.1 AVP Constellation Energy Group

An Image/Link below is provided (as is) to download presentation Download Policy: Content on the Website is provided to you AS IS for your information and personal use and may not be sold / licensed / shared on other websites without getting consent from its author. Content is provided to you AS IS for your information and personal use only. Download presentation by click this link. While downloading, if for some reason you are not able to download a presentation, the publisher may have deleted the file from their server. During download, if you can't get a presentation, the file might be deleted by the publisher.

E N D

Presentation Transcript

  1. Richard Goyette – Advisory Software Engineer 19 August 2010 Maximo 7.1 AVPConstellation Energy Group

  2. IBM Presentation Template Full Version Agenda • Introduction • Maximo and Linux considerations • Maximo and VMware considerations • Performance considerations • Review / Q&A

  3. IBM Presentation Template Full Version Supported Linux Distributions • For Maximo 7.1.x.x based products the following Linux distributions are supported: • Testing and certification is done using the current release level for each version

  4. IBM Presentation Template Full Version Red Hat Enterprise Linux • This was the first Linux distribution to be supported by Maximo • Back in the 6.2.x timeframe • Priority 1 platform for IBM Development and Support • Red Hat Enterprise Linux 4 and 5 based environments are tested with each build of Maximo 7.1 Fix Packs • Maximo supports 32 bit, 64 bit, and z based implementations • Intel processor based 32 and 64 bit are the most popular

  5. IBM Presentation Template Full Version SuSE Linux Enterprise Server • Became a supported distribution with Maximo 7.1 • Priority 1 platform for IBM Development and Support • SLES 10 and 11 based environments are tested with each build of Maximo 7.1 Fix Packs • Maximo supports 32 bit, 64 bit, and z based implementations • Intel processor based 32 and 64 bit are the most popular

  6. IBM Presentation Template Full Version Comparison between RHEL and SLES • No discernible performance difference between the two distributions on the same hardware • SLES comes with a unified administration tool (YAST) • No similar tool comes with Red Hat which can make some administrative tasks more difficult to accomplish • Red Hat ships with an earlier kernel version (2.6.18) as compared to SLES (2.6.27) • Not necessarily a good or bad thing either way • Broader support for Red Hat due to it’s time in the marketplace compared to SLES

  7. IBM Presentation Template Full Version Maximo on Linux: Installation Considerations • Personal experience is that Linux on System X is the quickest Maximo environment that we provide for Test/Development/Documentation • Both deployment and runtime operations are noticeably faster than an equivalent system running Windows 2003 • Only post-install consideration that is critically important is to check for resolution of LOCALHOST to make sure it resolves to the true IP and not the loopback adapter • This will allow full RMI functionality for items such as BIRT reports • Stay up to date on all OS patches • They will appear to come out daily but luckily no reboot is required for 99% of them

  8. IBM Presentation Template Full Version Maximo and VMware • Maximo supports both the VMware Server and ESX(i) hypervisors for Maximo 7.1 based products • Dramatic performance differences between these two hypervisors however so use them accordingly • VMware Server • Great for prototype & development environments but too slow for production • Dependent on OS availability and performance • VMware ESX(i) • Very easy to install, very fast, acts as the base OS layer on top of the hardware • Used as IBM production hypervisor worldwide

  9. IBM Presentation Template Full Version VMware Server Considerations • OS based hypervisor that requires Linux or Windows as a base layer • Hardware resources consumed by the base OS are not available to VMware Server therefore you lose performance / capacity • If the OS reboots for any reason (updates, configuration change, etc) then the VM’s go down as well • VM’s not properly shut down can be corrupted as part of the base OS reboot – not good! • Use this for early stage development & prototyping

  10. IBM Presentation Template Full Version VMware ESX(i) Considerations • Bare metal hypervisor that interfaces directly with the hardware • All hardware resources in the system are available to ESX(i) • No dependency on any other OS so it’s fast and reliable • Must install as the only base OS on a system so you can’t “share” a server with it • Use once you move beyond single user development/test/prototype

  11. Maximo and VMware Performance • All VM’s are basically large compressed files • Disk i/o performance is critical to VM performance • Maximo itself can be disk intensive at the AppServer level (classes, jsp files, html pages, etc) • If you want a fast Maximo VM, use a fast disk subsystem (SAN, JBOD, etc). • Avoid using a VM to host the database due to the disk performance considerations if possible

  12. General Maximo Performance Considerations • Stay up to date! • Maximo, AppServer fix levels, JDK level, Database, etc. • Many performance issues arise when customers are down level on dependent products • Analyze application performance before going live • Have a good performance test plan to stress test your application and environment • Build a good foundation early on and reap it’s benefits throughout the application’s life cycle • A lot easier to do it right early than change it later • Determine max concurrent users and design your environment appropriately

  13. Hardware Considerations • Maximo application performance is dependent on 3 primary considerations • Application Server performance • Maximo is a collection of many small files (Java classes, XML/HTML/JSP files, etc) • Disk I/O performance at the AppServer level is critical to Maximo performance • RAID / SAN recommended for the Application Server where the cache directory is located • Database Server performance • Faster that data can be served up for Maximo, the faster it is presented to the end user • Follow vendor published database performance recommendations • Separate log data from application data, etc. • Disk I/O performance is also critical at the database server level • RAID / SAN recommended again • Network performance • Keep the AppServer and the Database Server on the same subnet if at all possible • Gigabit networking is a must between AppServer and Database Server • Utilize a hardware load balancing solution to front end requests to your back end Maximo hosts

  14. JVM tuning considerations • Testing has shown that multiple VM’s perform better than a single huge JVM • Maximo documentation recommends min/max JVM memory settings of 512M/1024M • This should get you to the standard answer of 50 users per JVM • Maximo “PVT” Performance group uses a JVM memory setting of 2560M/2560M • Obviously a 64-bit system is required to get above the 2048M limit • Create multiple JVM’s in a Cluster to increase application performance and capabilities • Adds redundancy if one JVM goes down • Hardware load balancing introduces even more application performance • More JVMs = more performance • Lots of web resources on garbage collection, application tuning, etc. • Try, test, analyze before you implement any changes into a production environment!

  15. Scalability and Maximo: The Easy Way • Because Maximo is a compartmentalized application you can separate out components and distribute these components across multiple physical servers • Advisable to separate UI, MEA, and CRON components across multiple servers to balance load and increase application performance • Lots of documentation on performing this step: Maximo “SAG”, web links, etc • Utilize multiple JVM’s to increase the number of concurrent users in your application • Performance (load and stress) test your application throughout the prototype phase so it is ready to deploy when you are!

  16. Useful Web Resources • http://www-01.ibm.com/support/docview.wss?uid=swg21329219 • Guide talking about number of users per JVM • http://www-01.ibm.com/support/docview.wss?rs=3214&context=SSLKT6&q1=7014419&uid=swg27014419&loc=en_US&cs=utf-8&lang=en • Platform compatibility matrix • http://www-01.ibm.com/support/docview.wss?uid=swg21440192 • Maximo v7 “Best Practices” guide for Performance • http://publib.boulder.ibm.com/infocenter/tivihelp/v3r1/topic/com.ibm.tamit.doc_7.1/pdf/mam71_sys_admin_guide.pdf • Maximo 7 SAG (System Administrator’s Guide) • http://www-01.ibm.com/support/docview.wss?uid=swg21327735 • Updates to the SAG • http://maximotimes.com/ • Third party (VAR) website dedicated to Maximo. Lots of active topics and daily blog posts. Very useful site!

  17. Questions?

More Related