How to import existing WebSphere Installation in IBM Installation Manager – WID7 installation woes

The process of IBM WebSphere Integration Developer V7.0‘s installation uses IBM Installation Manager and is a 3-step process. First, you install the main product – WID7 – and then move on to installing WebSphere Application Server and the WebSphere test environment. It ensures that not only can you develop an integration solution, but also can you run it atop a fully-functional WebSphere Process Server (or WebSphere Enterprise Service Bus) local instance.

Once you finish the first step – Install IBM WebSphere Integration Developer V7.0 – you’re given a window with a summary.

It’s as good as it says. You can develop your integration modules, but you can’t test them with your local instance of a WPS server. It has to be installed in the next step.

I’ve recently been installing WID7 on MS Windows 7 and guess I did a wrong choice where the installation packages were in a host system whereas the installation was performed within a virtual image. It turned out that the path to the binaries was not quite right and the installer blew up with the following error.

I made every step to avoid such problems having been told that Win7 is a brand new operating system supported by WID7, but forgot about the path name of the mounted directory (!)

I begun a search in Google looking for a solution and how to eventually import the package into the IBM Installation Manager repository, so I can go on with the installation and found a hint in Installing WSRR interactively over an existing installation of WebSphere Application Server Network Deployment:

Note: By default, the Import button is enabled only in versions of Installation Manager that are provided with WebSphere Application Server, or WebSphere Application Server based products. If the Import button is not enabled in your version of Installation Manager, complete the following steps to enable it:

C:\ProgramData\IBM\Installation Manager\.settings\

That was it! After the change the Import button displayed itself in the main panel of the IBM Installation Manager. That was really awesome. I really like such hidden gems – they can easily make you a hero when a team is in trouble and they call you for help. Now, they won’t have to unless they haven’t been following the blog.

With the import button, I could begin the importing process, but it quickly turned out be not enough. Doh! What’s wrong?!

My happiness begun to fade gradually as was the patience.

I can’t really remember where I found the information and the repo URL, but it was as simple as adding a URL into the Preferences > Repositories in the IBM Installation Manager.

With the change, the import was again a simple process.

…and finally The import is complete message.

I could continue the main installation.

Alas, more issues emerged just a few clicks later. The available installation packages were incompatible to be installed together.

I remember I tried almost every possible combination and eventually ended up with a mere installation of the base version of the products.

I was almost done with the task when I hit an issue with a virtual image that…crashed without being able to recover itself afterwards. I’ll have to install WID7 on Win7 again, but this time I’ll be more experienced. I wish you not to experience it as it’s certainly not worth your time – the product should’ve been installed with one click. It’s not yet, but I hope it will one day.

The bottom line is to not install a product in a directory with a space in its path and, as importantly as the former, have the installation packages locally. You’ve been warned.

Be Sociable, Share!
This entry was posted in WebSphere.

3 Responses to How to import existing WebSphere Installation in IBM Installation Manager – WID7 installation woes

  1. Unbeliveable, but it’s not working although somewhat similar procedure is described at infocenter of IBM.

    Do you have clue why I don’t see “import” button …

    • It could be that the version of IM is different and they changed how/when Import shows up. Time flies by very quickly and what worked yesterday may no longer work when tried out with the latest versions.

      If you could provide more information on your environment, most notably the version of IM, it’d be useful.

  2. Daniel S. Haischt says:

    That’s the canonical way how to configure an IM that is not WAS capable to expose the WAS import capability:

Leave a Reply

%d bloggers like this: