Continuing from Using the WebSphere 9 Migration Tool with Maximo 7.6, part 1 . Post-Migration Tasks For the following post, the original (WAS 8.5.5) installation is at C:\IBM\WebSphere. The new (WAS 9.0.0) installation is at C:\Program Files\WebSphere. At this point in the migration, the profiles are: WebSphere 8.5.5.11: Deployment manager (dmgr): C:\IBM\WebSphere\AppServer\profiles\ctgDmgr01 and nodeagent: C:\IBM\WebSphere\AppServer\profiles\ctgAppSrv01 (nodeagent, MXServer, webserver1). WebSphere 9.0.0.6: Deployment manager (dmgr): C:\Program... [More]

The instructions for enabling security created by my colleague included in the blog entry link below describe the steps necessary to enable application server security including modifications to web.xml files for the associated war modules, updates to system properties, rebuild/redeployment of the maximo.ear, enabling global security within the WebSphere Administrative Console, and restarting the application servers. ... [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. Steps: 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 servers > server1 > Java... [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 . Now, the missing blog post: Installing WebSphere... [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 called WASServiceCmd.exe.)... [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 upgrade... [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 chance to back up your profiles in the Migration... [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 7.5.0.5 from WebSphere 7.0.0.29 to WebSphere 8.5.5.0. Prerequisites for using Migration Tool: 1. WebSphere Application Server Network Deployment 8.5.5.0 2. A Maximo Asset Management instance currently running on WAS 7.0 2a. MAM Fix Pack 7.5.0.5 or later installed Configuration Migration Tool - what is it? It is one of several WebSphere wizards that use a graphical interface that generate and... [More]

We are getting lots of new clients and deploying an ear file seems to be one of the areas new clients are usure of. I've prepared the following to walk clients through the deployment stage step by step with screenshots to be able to effectively and efficiently deploy an ear file. Login to the Websphere console, expand Applications, click Websphere enterprise applications and then click the Install button. ﻿ Click Browse and drill down to locate the maximo.ear file which is located at... [More]

Now that you've installed WebSphere 8.5.5, how do you get Maximo 7.5.0.6 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 able to transfer most of your... [More]