The WebSphere Migration Tools – The Hidden Gem

Well then, it comes as no surprise that one of my first posts will be on a WebSphere related topic. I meant to write about this earlier but had no time over the last few months, but a recent project required me to work with a client on a WebSphere migration and go over the tools and their usefulness with them – so I decided to go back and briefly talk about the WebSphere Migration Tools and how they can me useful not only for migrations …


Where to get them:

The tools are made up of three parts, all of them are available at the IBM WebSphere/Liberty Developer site:

Just go to the [DOWNLOADS] area and do a search on [MIGRATION] and you can download them all.

Just be aware of one thing - if you install Eclipse (needed for all tools except the Binary command line tool) you can also just download them from IBM's Marketplace/Update site inside of Eclipse and install it directly - here is the URL for that site:
Just make sure you also install a Java J2EE environment inside of Eclipse as the tools require that to run correctly ....

The Tool Set

Basically there are four tools:

WebSphere Application Server Migration Toolkit

You need Eclipse to run this – it will analyze applications in the context of different migration scenarios (source system and target system) . This is the list of scenarios it can help you with: This tool will help you do most of what you need to do ….

  • Cloud Migration Tool
  • WebSphere Version to Version Application Migration Tool
  • Apache Tomcat to WebSphere Application Migration Tool
  • JBoss to WebSphere Application Migration Tool
  • Oracle to WebSphere Application Migration Tool
  • WebLogic to WebSphere Application Migration Tool
  • Apache Tomcat to Liberty Configuration Migration Tool
  • WebSphere Configuration Migration Tool: JBoss
  • WebSphere Configuration Migration Tool: WebLogic
  • WebSphere Configuration Migration Tool: WebSphere to Liberty
WebSphere Configuration Migration Tool for IBM Cloud

This will also require Eclipse – the main difference is that it only uses the cloud as a target system – I have tested itonce or twice and it creates a great clone of your current system in IBM’s cloud infrastructure. You need to have an active cloud/Bluemix account to be able to use this.

WebSphere Configuration Migration Tool

This is my go-to tool to see if I can “just upgrade” a server/servers as is or if I will have problems …. the tool gives you a wsadmin command to run on the originating server (if it is WebSphere) that give you an output file – that you then import and the rest is “magic”.

Migration Toolkit for Application Binaries

A command line tool that will quickly analyze existing applications – it will tell you quickly if an existing app will run on a newer (or different) platform and/or what problems might exist.

Note: I often use this tool to analyse apps when trouble-shooting them on WebSphere – it’s not just useful for a migration/upgrade! I have often used this tool to figure out what Java jars are in an application and if there are any old opensource (and possibly incompatible) versions inside. Try this with the [-inventory] switch and then hand the report to the developer ….


Other Resource:

This is a great presentation on the tools and how they work. It is a bit long, but it will give you most of the details you need to get a start with these tools and learn how to use them. They are quite straight forward and not hard to use, it is the results they give you that cause the prolonged episodes of head scratching ….

Sametime 9 – Cumulative Hotfix for Sametime Proxy 9.0.0 install woes

Installing a new environment for a client and ran into an issue trying to install the Cumulative Hotfix for Sametime Proxy 9.0.0 ontop.  The documentation is wrong, the location of the registry.xml is incorrect in the document, but let’s not dwell on that one.

I set up the package and ran the Installation Manager and the install was always failing, the package tried to update things in incorrect profile locations and failed with the error it could not find the wimconfig.xml … strange.

I ran the issue past a few friends and compatriots and Declan Lynch had some suggestions: he had run into problems installing HF for Sametime if the WebSphere server running the actual ST process (in this case STProxy) was set to auto-start using the Java Monitoring settings.

So – I disabled the auto-start settings, synced the nodes and restarted the STPRoxy server …. and the update went through without a hitch. I will be disabling this for all servers during updates/upgrades from here on – I noticed the process stops and starts the nodes and the auto-start of the servers probably made the install scripts go haywire.

Good luck, everybody!

Connections 4.0: Tails from the Upgrade Part 2 – Oracle

This is an interesting one for all of you out there that utilize Oracle as your database server.

Character Set:

The approved character set for Connections is AL32UTF8. You  might have a look at your database and discover that you are running some other character set but that you are seeing no issues – at least in Connections 3.x


In comes Cognos . . .

Cognos will NOT install (fails to connect to the dB without errors) if your Oracle character set is anything other than AL32UTF8. The reason is that it expects a certain date format that it will not find in another character set.

Funny enough Connections would probably work – both the update wizard and the subsequent install but you will not get Cognos to work – sorry. You will need to create a new Connections database in the correct character set, export the data from the old one and import it into the new dB and THEN run the upgrade wizard – or alternatively run the individual SQL statements (allot of DB Admins prefer that – this way they can change temp folder settings etc.).

Depending on your V 3.x database size that can be quite an undertaking, fro what I hear from Oracle dB admins (I am definitely NOT in that league) the export and re-import into a new database is the way to go.



More to come soon . . . .

Connections 4.0: Tails from the Upgrade Part 1

As a few early risers might have already read on some blogs and press releases, IBM has released Connections 4.0 to the general public this morning – here woudl be Ed Brill’s blog as one of the many announcements.

I have been working for a client I shall call TWSSU (=”They Who Shall Stay Unnamed”) and been part of a large Connections implementation since last year.  As part of this environment we have been working on a V4 upgrade for quite some time, to the point where we started developing new look-and-feel designs and customizations on every code drop of the Beta cycle (that is a tale onto itself) and received the Connections V4 code early along with some “interesting” draft documentation for V4 … I know it’s unfair and mean, but sometimes it is fun to be me!

I have been under and NDA until today (general availability – finally!) so I have not been able to talk about any of the interesting items that are likely to pop up during a migration.

To that end I will start this tale  in small doses and hand out some of the more interesting tidbits in several blog posts, starting with the basics right here:

OS Requirements

Ditch any old Windows 2003 servers you still have, they are no longer supported. If  you were planning to re-use some of your existing infrastructure and they are windows 2003 … sorry. You can still run TDI and probably DB2 on them but anything with WebSphere on it will require Windows 2008 or AIX/UNIX/Linux. time to buy that next license pack from Redmond if you want Linux, otherwise Red Hat/CentOS is your best bet.

The detailed system requirements are here – be patient with the new design for the document for right now … it is still work in (design) progress and – as I find it personally – rather confusing. From what I hear IBM looked at it and is workgin on it. Hey – it is still better than some of the documentation that I have come up with over the years … 🙂

WAS Version: – SDK/JAVA

This was a painful experience for me – and partially self inflicted. Well, I had the excuse that the documentation was not yet ready. when IBM says that you have to install WAS FP 21(and a few more fixes separately) they don’t just mean WAS FP, IHS and Plugin FP- they also want you to install the SDK part of the fix pack. For most of us this is not something we are used to as most applications bring their own SDK or at least update it during the install process.

Connections has been significantly re-architected (more on that later) and contains a feature called “Comon” that is in charge of serving up all the static content, along with jsp’s, scripts/code and all the fun stuff that the features share among themselves. This feature will not initialize correctly – UNLESS – you have the SDK installed since it is only certified to run with a minimum Java version of WAS The install works and throws no errors, all the other features will start but common will not initialize (the errors in the systemOut.log are confusing and I needed serious IBM help to find the root cause – THANKS DAVID!)

Configuration XML files – There are ALLOT of them

There are about 19 features running on a full blown Connections environment now so there are naturally more configuration files. Also, the configuration of some items was moved to separate xml files (I like that – more later) so you can’t just port over all your old files, and in many cases not even the settings since they have changed.

I suggest to run a dif between your existing config files and the new ones, I use Beyond Compare for that (my favorite tool!). That will show you quite clearly what settings are different, what new settings exist and what the default settings are. Not all of the settings are documented in detail in the WIKI so  … be careful and start slow.

Cognos … The uncharted land

This is a new one for us. I have never touched Cognos before and without the help of my main man Vijay F. (full name shall remain secret to protect the innocent …) I am not sure if we would have gotten through the experience unscathed.

We found a few problems in the install that have already made it into the documentation so you have the benefit of our sweat and Vijay’s expertise. Just make sure you install Cognos first and have the right client version of the DB system you use installed.  AND – having more expertise in SQL than I do helps – it seriously helps. More on this at a later stage.


Stay tuned for more . . .

This is the end of part 1, more will follow next week: database upgrade/migrationss and new iFixes for V4 that get released along with the new version … yippie! We will have fun!!

BES Express for Domino in November – Announcement

This one comes courtesy of Volker Weber. I read one of his tweets about this and searched the web and came up with zilch – I contacted him and it seems it was announced interactively by RIM at an IBM function in Stuttgart that he (I assume) attended.

Exciting news indeed!! Lets see what November brings. I am sure that there will be some official pres release by RIM soon – I can’t wait to ditch my current Small Business BES that is eternally stuck at 4.1.4 and upgrade/migrate to the Express version.