It has been brought to Maximo L2 Support's attention that 2 manual steps for issue numbers APAR #: IV65124 & APAR #: IV68129 are incorrect. the 2 sections are listed below. The bold sections are the incorrect steps which are then followed by the correct steps. The issue is that it states to ADD the section when it should state REPLACE.
If you have not down loaded the fix as of today you might have the incorrect read me file. We have reported the issue to Fix Central who has since... [More]
Recently, I got questions about why PM generated Child Work Orders from routes do not have PM (Preventive Maintenance) information populated. This is actually working by design. Only the work order the PM created references the PM on it. The children are created by the route stops, not the PM record. Hence, the child work orders would not contain have any PM information.
However, Maximo can be configured to have the PM information populated on child work orders by creating crossover domains and escalations.
Below are... [More]
I was recently working an issue where a reverse proxy was configured with Maximo using IBM Edge. After the proxy was configured all users logging into Maximo via the proxy were being automatically redirected to the sign-out page (exit.jsp). I ran several tests, including logging in with the same users via the IHS and the Web Container port directly. The users could log in fine this way, so the problem appeared by be directly related to the proxy.
Maximo has a table called LOGINBLOCK , this table contains IP addresses that... [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]
Earlier this year, I blogged on installing IBM Installation Manager, without getting into too much detail, actually. I recently followed that up with a step-through migrating profiles from WebSphere 7.0 to WebSphere 8.5.5. I seem to have forgotten an important step, huh? Yep, that's right. This week's blog post will be all about How to Get Your Blog Posts In Order.
First, the link to the Installation Manager install blog post
Second, the link to the first Migrating profiles blog post... [More]
Finishing up from the last blog post , it's time to create Windows services. Otherwise you will always have to have a session logged into the Windows server to start the three Maximo-related services (Dmgr, nodeagent, MXServer).
You can follow the instructions in the installation guides found here to create Windows services manually using WASService.exe, or you can use the nifty WASServiceHelper interactive command-line interface tool now included with WebSphere 8. (With WAS 6 and 7, it was a downloadable product... [More]
Just a quick plug before we head off into the land of screen shots.
I attended a demo that showed off new user interface features coming in the next version of Maximo. Of great interest was the new interface, or skin. It's much cleaner than before, with larger type and just the right amount of white space. They've also hidden some elements that don't need always to be seen. (If you're worried about the new look causing problems for users used to the old look and feel, don't worry - everything is turned off when you... [More]
Continuing from my last blog posting , the next step is to migrate your profiles.
Today's entry is pretty much going to be a step-by-step how to migrate the existing Deployment Manager profile, using out-of-the-box (OOB) Maximo 7.5. Your own environment is more complex than out-of-the-box Maximo, so this will be easy. Let's start!
1. First, shut down IBM HTTP and IBM WAS 7.0 services, and change their startup Type to manual. Then, restart the server.
Even though you'll be given a... [More]
Continuing from my last blog post , I'm assuming you have installed WebSphere 8.5.5. I'm going to do a simple migration: out-of-the-box Maximo 188.8.131.52 from WebSphere 184.108.40.206 to WebSphere 220.127.116.11.
Prerequisites for using Migration Tool:
1. WebSphere Application Server Network Deployment 18.104.22.168
2. A Maximo Asset Management instance currently running on WAS 7.0
2a. MAM Fix Pack 22.214.171.124 or later installed
Configuration Migration Tool - what is it? It is one of several WebSphere wizards that use a graphical... [More]
Now that you've installed WebSphere 8.5.5, how do you get Maximo 126.96.36.199 to run on it?
There are two ways to do it.
The hard way is to set up everything manually. This requires that you know what needs to be set up. More importantly, it requires that you need to know where to go to find out what needs to be set up.
While WebSphere 8.5.5 is a big leap forward for WebSphere, a lot of that's under the hood. You don't see it. To the Maximo administrator, the interface will look very familiar. You will be... [More]
The current Migration Group, CLASSIFICATIONDATA, does not migrate the Attributes and Measure Units.
This can result in missing descriptions on Attributes and Measure Units which can be confusing for the end user.
The solution is to add two new Migration Objects for these two objects so that they can be migrated and then to create
a new Migration Group containing the exisitng DMCLASSIFICATION Migration Object and the two new created
Migration Objects for Attributes and Measure Units.
Creating the two new Migration Objects
I'd like to start my first blog entry by introducing myself. My name is Mario Travers and I'm one of the team leads for the Maximo EAM Support group. I've been working with Maximo now for over 8 years (might actually be longer than that but my memory isn't what it once was) in various roles within in support for IBM and, previous to my old companies' acquisition by IBM, at MRO Software. Throughout my time here I've been lucky enough to be involved with many great projects within the support team... [More]
Maximo 7.5 has a new way to process set value events called asynchronous processing. The set value events will not be sent to the server immediately, instead, these events will be buffered on the browser until an event occurs that requires a request to the server like 'click save'. The asynchronous processing will reduce end user response times for common user activities which do not require complex business rules by reducing the request number. For example, insert a new record: Requset processing in Maximo 7.2 Asynchronous Requset... [More]
Your in the midst of importing a ton of records into Maximo via the new Application Import feature or simply previewing them via the Import Preview feature in the External Systems application when the browser gui throws up an 'Internal Server Error'. The generic explanation for this error:
The Web server (running the Web Site) encountered an
unexpected condition that prevented it from fulfilling
the request by the client (e.g. your Web browser) for access to the requested URL.