I recently updated a Windows XP-based vmware image that was running
WAS v6.1 to use WAS v7, and migrated the applications it was running as
well, and this is how it went. Pretty smoothly actually. I think,
because I followed the advice captured in this article: A
quick guide for migrating to WebSphere Application Server V7
the applications were just simple JMS services, nothing fancy.
Part 1: Migrating WAS from V6.1 to V7
Part 2: Changing the port
- Decided to leave WAS v6.1 intact while I installed WAS v7,
because they can coexist peacefully on the same machine, and to migrate
configuration info, you need to keep the old version of WAS on there.
- Looked at the configuration on WAS v6.1, taking note of the
names of the server, node, cell, and the applications and their
- In retrospect, I would have also made note of the port numbers
being used, in case they were different from the defaults (see Part 2
- I did not make a backup, because if this didn't work, I was
just going to roll back the vmware image and start over.
- Installed WAS v7, but did not configure a profile, because I wanted to try
migrating the old one. Installed it in a different target directory
from the old installation.
- Ran the Migration Wizard, selected the source profile from
v6.1, and checked the option to also migrate and install the
applications. I also chose to install the apps in the default directory
of the target installation, and use the port values assigned to the
target profile. In retrospect, it probably would have made my life
easier if I had chosen to use the port values assigned to the previous
- The migration of the profile succeeded, but the migration of
the apps did not. The errors looked like it could not access or copy
the files from point A to B. I ended up just installing the
applications myself later because everything else seemed fine.
you install WAS again on a machine that has already seen a WAS
installation, chances are that the port values assigned to the second
installation will all be incremented by 1 from the default value. For
example, 9060 will become 9061. You can change the port values as
necessary to avoid conflicts. However, I ran into some issues with
this. Here's how that went down:
WAS v6.1 completely, I changed the ports for WAS v7 back to the
default values by using the administrative console (which, I know now
is probably not the best way to do it), stopped and restarted the
server, and got the following error when I tried to launch the console
"SRVE0255E: A WebGroup/Virtual
Host to handle /ibm/console has not been defined. SRVE0255E: A
WebGroup/Virtual Host to handle :9060 has not been defined. IBM
WebSphere Application Server"
Ok, so the port number got
changed in some places but not others. Somewhere, it thinks that the
port is still 9061. I looked up the error on the IBM Support Portal page
and quickly found a solution.
The quick and easy fix for
this was to just manually edit the virtualhosts.xml
file for the profile in question, located by default here -
I did a search for "9061" and sure enough found it in there.
Changed it to 9060, saved, stopped and restarted the server. All
better, right? I forgot about the applications, running on the default
host, which uses 9080. I got a similar error when trying to access
them, so I went back into virtualhosts.xml
and looked for 9081, changed it to 9080.
- There are other tools/better methods for changing the port numbers
than just using the admin console, which I didn't try this time, but
definitely will next time. Check developerWorks or the Info Center.
- The IBM Support Portal search field is your friend. Chances are,
someone else has seen that error before. Just type the error code or
description in, and the solution is probably there.
feel free to question or comment