Normally my blog entries are lengthy and contain full tutorials regarding configuration, however tonight I have a just a quick post regarding a new property in Maximo 7.6. If you have read my past blog on Isolating Functionality in a cluster for Maximo 7.5 you know about the property mxe.crontask.donotrun . This property defines which cron tasks\escalations will run on specific JVM's. Some of you may also have run in to problems using this as an instance level property due to field size not being... [More]
The performance was spectacular. The consumption of six chocolate and potato chip cookies was done in record time. Spurred on by their performance enablers of smell, warmth and my driving hunger, rapid morsel feasting was inevitable
In Maximo 76, numerous new report performance features are available and many existing features have been enhanced. These performance features target delivering report content quickly to meet the dynamic business needs of your users.
The new Maximo 76 Report Performance... [More]
It's been a bit since my last entry in this series, so I thought I'd take some time this morning to finish off this tutorial on configuring a basic horizontal cluster. If you haven't read my previous posts, you can jump over to Part 1: WebSphere Configuration and Part 2: JMS Configuration .
In this final portion of the three part series, we will go over the following topics.
Creating the Virtual Host
Assigning Names to JVM's
Building and Deploying ear files
Previously I had posted a blog on creating a horizontal cluster across multiple nodes in WebSphere 8.5.5. If you haven't read that posting, please head on over Clustering with Maximo and WebSphere 8.5.5 - Part 1 - Configuration and take a look. Today we will be continuing forward with JMS configuration. I was going to do this series in 2 parts, but I will separate this out in 3 parts due to the length of the topic.
In the original blog posting we configured the following.
I'm back again, changing things up a bit this week from the usual LDAP blog. Today we are going to talk about clustering and go into a detail step by step guide to configuring WebSphere 8.5.5 in a horizontal cluster. Unlike a vertical cluster which is built up on the same server, a horizontal cluster spans multiple servers/nodes to allow for another layer of fail over.
Clustering is appropriate for implementations with a large user load, as you add more users you may need to add additional JVM's to either the existing nodes... [More]
Out of Memory condition could occur when deploying ear file in Websphere console or when running Maximo 7.5
Additional configuration from Websphere is needed to avoid getting error: java.lang.OutOfMemoryError: Java heap space in the log.
Open the WebSphere Application Server administration site by typing http://hostname:port/ibm/console .
The port is the number of the HTTP administrative port, which is 9060 by default. Type an ID (any ID without a password) and log in to it.
Select Servers > Application... [More]
Once in a while I'll get questions about performance problems. Specific scenarios can be resolved by applying Interim Fixes or adding indexes. Those critical and urgent problems often happen throughout the entire system.
Here is a collection of performance related recordings and technotes that might help:
SCCD 7.5.1 Performance Education Session
Correcting Slow User Queries
So you and your team are ready to make the leap on to the next release of Maximo or SCCD but, there is that looming concern about what is going to happen when you flip the "ON" switch on your go-live date. Will it work? Will performance be acceptable? or will you have to find a safe house to hide from the angry mob of users that can not use the system? You are not alone. Those are the type of questions that keep every Project Manager and System Implementer up at night.
Through collaboration with some of our... [More]
"Before you can race, you must qualify". As a fan of Motorsports (Formula 1 in particular) I hear this phrase on many weekends throughout the season. The phrase basically means that to have the highest chance of being successful in an endeavor you must prepare adequately. In this article I shall take this same idea and show you how to apply it to a successful Maximo installation.
If "qualifying" is preparing for a race then careful planning of your IBM Maximo Administrative Workstation is along the same lines. Many... [More]
I need to set limits when faced with these. Knows as Fluffernutters, smooth, decadent peanut butter and sticky marshmallow topping on plain white bread form the ultimate comfort sandwich. With a cold glass of milk, the number I can toss down is crazy high.
You may also need to stop your users from over-indulging by setting records limits when they create Ad Hoc or QBR (Query Based Reports.) The creation process of ad hoc reporting is where users select the fields, application query,... [More]
When following the current Best Practices for Performance white paper, one of the Generic JVM arguments that is recommended is to set the -Xdisableexplicitgc parameter. Setting this parameter turns a System.gc() call into a no-op.
This parameter works well for the vast majority of our clients. However, there have been a few cases where JVM memory is fairly tight due to the specific workloads that the end users are generating. In some cases, requests for object memory grow faster than the Java virtual machines decides to... [More]
If you're looking for ways to optimize system performance, consider enabling data compression on the IBM HTTP server. You can use the Apache mod_deflate module to improve response time in
environments that have low bandwidth and high latency. The Apache
mod_deflate module compresses output from your server before the data is
sent to the client over the network.
Setting the compression level is to 3 provides minimal CPU usage and
a decent benefit from the compression. You can also set the compression
level to 6, which provides... [More]
Do you collect coins? In a gargantuan container that once held a supersize collection of cheese puffs? My mammoth 24 x 8 inch plastic container was so packed full of coins, it broke thru its bottom when I recently tried relocating it... Maybe relocating wasn’t the best plan for the coins….which is just one of the many collections I’ve shared with you this year. Others included post cards , National Park Stamps , photos , and BiLog entries! Yes! BiLogs are a collection of Maximo Business Intelligence Blogs detailing reporting... [More]
The other day, we encountered a problem during one of our performance tests. We observed from the database side that there is a steady increase of connections over time. Of course, we immediately suspected there is a newly introduced connection leak somewhere and started the hunt. The very first thing we did was to turn on the dbconnection logger to info level. We confirmed from the maximo logs that these connections indeed are recorded in the maximo connection pool as used connections and not released. The stacktrace did confirm that there... [More]
In a large scaled Maximo environment, some of us would use IBM DB2 pureScale database. As the more nodes you have, the more contentions there are on every kind of resources. Normally, Maximo is using Sequence object inside database to avoid the locking issues that are associated with other more heavier approaches In a standard database, Maximo usually cache some sequence values in memory to improve response time. While in a DB2 pureScale environment, if both CACHE and ORDER are specified, the specification of ORDER overrides the specification... [More]