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]
QUICK OVERVIEW ......... If you know how it works and just want to look at logging, look below for 'Basic Debugging'
VMMSYNC is a crontask provided within Maximo products. As with all crontasks it can be set to run at regular intervals.
The crontask makes contact with a component of WebSphere called VMM (Virtual Member Manager) via API calls.
The calls will be actioned against a federated repository and will request information on users, groups and group assignments from within the federated... [More]
This is a cross post from Ser vice Man agem ent 360 sit e .
Would you like to configure your Maximo Anywhere solution to show additional fields?
In this blog " How to add a read-write Maximo field to IBM Maximo Anywhere ", I cover the steps to implement this configuration, which include:
Determining the Maximo field you want to add
Updating the app.xml UI section to show/update the field in the Work Details... [More]
Daytime and Date field calculation issue when using Daylight Savings in MAXIMO
When using daylight savings option in MAXIMO, bug occurs in date and date time calculation where 1 hour is added or deducted from the date, and this can result in completely different date when 1 hour is deducted from 00:00, so it becomes 23:00 on the previous date. This bug affects all applications in MAXIMO including the Invoices and Scheduler, where it can create numerous issues, since dates will not be aligned and transactions can get... [More]
It's July? Really? Nooooooo!!! What happened to January, February, March, April, May and June?
If your year is speeding by,, you may have missed some of the incredible new features and information on Maximo Asset Management. To make sure you are up to date -- check out the latest information below
Interested in exploring alternate ways to deploy Maximo? Maximo is now available in a SaaS (Software as a Service) offering! This hosted solution... [More]
On June 27, 2014, IBM Software released the 184.108.40.206 fix pack for Maximo Asset Management, Maximo Asset Management Essentials, and Tivoli Asset Management for IT.
Information for Fix Pack 220.127.116.11 can be found here: http://www.ibm.com/support/docview.wss?uid=swg24037898
Additionally, you can find the list of corrected APARs for this fix pack here: http://www-01.ibm.com/support/docview.wss?uid=swg21676540
What's new in 18.104.22.168?
Here's a few highlights:
New Platform Support:... [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]
In LDAPSYNC, if a large chunk of data takes a long time to process and the processing time exceeds the Active Directory’s idle connection timeout setting ( MaxConnIdleTime ), it can cause the Active Directory to close the connection which leads to synchronization failure.
LDAPSYNC fails with errors like these:
BMXAA6752E - Group synchronization could not be performed because of error connection closed. The error count was 148. See the associated message. Correct the... [More]
You've downloaded and installed WebSphere 8.5.5, the IHS and the Plugin. You have everything up and running, Maximo deployed and want to use the web server to access Maximo or load balance to multiple JVM's, so why isn't it working? Why are you receiving "Page Not Found" errors? In most cases it's likely a key step was missed that is automated with the Middleware\Maximo install when using WebSphere 7, that step is the Plugin Configuration.
During the install of WebSphere 8.5.5, you may of only installed the... [More]
This is a cross post fr o m S e r vi c e M a n ag e m en t 36 0 s i t e .
Would you like to know how to do the initial setup of Maximo Anywhere in your environment?
In this blog post, " How to configure queryBases in Maximo Anywhere" , I provide an overview of the initial configurations available for setting up your Maximo Anywhere solution and also provide a sample for adding a queryBase to Maximo Anywhere apps.
I am interested in understanding the specific setup and configurations... [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]
On May 30, 2014 IBM Software released the Interim Fix 009 (IF009) for Maximo Asset Management 22.214.171.124.
Information for Interim Fix 009 (IF009) can be found here: http://bit.ly/1kMkWWL
See the readme file for more information.
Remember to review considerations and prerequisites before applying this interim fix.
IBM Support strongly recommends keeping Maximo Asset Management implementations up to date with the latest available maintenance.
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 126.96.36.199 from WebSphere 188.8.131.52 to WebSphere 184.108.40.206.
Prerequisites for using Migration Tool:
1. WebSphere Application Server Network Deployment 220.127.116.11
2. A Maximo Asset Management instance currently running on WAS 7.0
2a. MAM Fix Pack 18.104.22.168 or later installed
Configuration Migration Tool - what is it? It is one of several WebSphere wizards that use a graphical... [More]
This is a cross post fro m Se r vic e Ma n age m ent 360 si t e .
Would you like to know the extensibility capabilities of Maximo Anywhere and how you can turbocharge your Maximo Anywhere solution so that it includes the configurations and customizations required for your specific environment?
In this blog post, " How can you turbocharge your Maximo Anywhere application?" , I introduce the Maximo Anywhere platform, and explain its configuration and customization capabilities and how... [More]