It can happen you misplace your password for the WebSphere Administrative Console where you have your Maximo deployed.
There are various ways to retrieve such a password and if your account is locked, how to unlock the account.
The 2 main ways to disable and again enable the security are as follows:
A) By way of manual edit of the security.xml file -->
1. Create a copy of the security.xml file, in the event you need to do any roll backs.
2. Disable the security from the security.xml file (change... [More]
I've been doing a lot of work with our latest Mobile software, Maximo Anywhere. If you haven't heard of Maximo Anywhere or your looking for more information on Maximo Anywhere you can head on over to it's product page .
When working with Maximo Anywhere, I decided I wanted to secure my transactions using LDAP and SSL (I will document LDAP in another post) and recently a blog was published by a colleague of mine on using the key tool with Java, that blog can be found here . Now we all know how... [More]
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 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]
This post will cover some of the same ground as a series I published last year . Those postings went into depth on setting up a new WebSphere Application server, database server, and setting up application server security with LDAP, but didn't go into much depth about doing the WebSphere application server "migration". using the term migration is misleading--I am recreating the Maximo application server on a new server.
I decided recently that I need to re-image the Windows server that hosts four of... [More]
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]
So you've configured or are configuring Maximo to authenticate with a directory server. You've set the base entries to determine which Organizational Unit's you will be bringing into your repository and you realize; you don't want all the users in each of the OU's to have the option to authenticate (in all authenticated mapping), you don't want to configure base entries for many different OU's bringing in users you don't need to exist in the repository, you may just want users from a specific group be brought in... [More]
This is a true story (film rights reserved) but some names, events and facts may have been changed (due mainly to my typing and proofreading skills)
A tale of a hero - IBM Support Assistant ( ISA ) Team Server 5 and his sidekick (that would be me)
and of a villain - RC=13
It all started one wet and miserable morning in a small dark room in a place not so very far away. Disaster had struck as my server had just run out of memory. What could I do. Where could I turn. I had heard tales of a... [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]
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]
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]
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]
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]