Installing an IBM product using the IBM Installation Manager

To install a product such as WebSphere Application Server Liberty Profile we first need to install IBM Installation Manager (IM). WAS 8.5.5 required a minimum of IM version 1.6.2, but below I have chosen to use the latest version of IBM Installation Manager which we can locate via this main IM support landing page, mentioned in the next section

You can get the PDF version here: Command line install for IBM Installation Manager

Installing Installation Manager

Most of the core reference documentation can be located at dedicated support URLs for any given product, or you can refer to the product sections of the IBM Knowledge Centre. IBM has improved and restricted its support documentation presentation. In fact, it is really good now and much easier to navigate around than ever before.

I have recently noticed, that most IBM products now have a dedicated support landing page. An example is the URL below, which is the main support page for IBM Installation Manager.

Also on this page we also find the download for the IBM Packaging Utility, which we will cover later in this guide, where we explain how you can use a web source to acquire the files required for your installation and have then downloaded into a local repository that IM can access.


  • Click on the link Download Document to navigate to the download landing page.

  • Click on the FC link to navigate to Fix Central location

Select the Installer that’s meets your operating system, I have chosen the Linux X86_64 as I am using CentOS 7 as my preferred OS. Now CentOS 7 is not a supported platform, so please refer to the Appendix to add the required dependencies to ensure that IM will install and also run.

  • Select the download and click Continue

You will be presented with a page that will launch the IBM Download Manager which will manage the download.


  • Click Download Now

The IBM Download Manager will launch and the file called will be downloaded.


Copy the zip file to your appropriate installation store on your Linux Server/Desktop


I unpacked the zip file using the CentOS unzip command into a folder called /var/apps/installs/IM1.8.1

But you can use whatever standard that is appropriate to your requirements. Typically organizations have a standard approach to manageable/extendable virtual file-systems

Now that you have the installation kit expanded, you will need to choose the syntax, depending on the security requirements of your Linux OS.

Administrator Non Administrator Group
./installc -log log_file -acceptLicense ./userinstc -log log_file -acceptLicense ./groupinstc -dataLocation application_data_location -log log_file -acceptLicense

Note: The -dataLocation option is required for group mode when you install Installation Manager. The installed instance of Installation Manager uses the stored location each time you start Installation Manager. This stored location was specified by the -dataLocation option during the installation. You do not need to use the -datalocation option to start Installation Manager in group mode.

Use the -installationDirectory directory option to specify a non-default installation directory. For Group mode, specify a directory as described in Group mode roadmaps and silent installations.

An example syntax is displayed below

  • Run the required installc command as root. (We are using a root user in this document).
./installc -log ./logs/im_1.8.1_install_log.xml -acceptLicense

This command installs and logs to a file called /im_1.8.1_install_log.xml in a logs folder within the installation kit directory.


Installed to the /opt/IBM/InstallationManager/eclipse directory.


I often to a quick cat of the logs to ensure not errors are logged. See an example below.

cat logs/im_1.8.1_install_log.xml

Generally a successful installation of IM will create the following example log contents in the log file

[root@localhost IM1.8.1]# cat logs/im_1.8.1_install_log.xml
<?xml version=’1.0′ encoding=’UTF-8′?>



Now since we have used root, we presume that this is allowed by the system admins. Often organizations, will lock down the OS and you will have to either have sudo rights, or use a predefined non admin account/group. For example wasadmin:wasadmin or equivalent.

If you have a Linux desktop ie XSession capability, I would not try and run the IM as a GUI, but there is no need if you have no desktop.

Example of verifying the running of IM as a GUI

We have now completed the installation of IBM Installation Manager, now we can install WAS silently etc.

In the modern world of 2015, I must say I am impressed by IBMs new approach to Knowledge access. Their new Knowledge Centre design is awesome to say the least!, Useful and the search works. Must because Lotus/Domino is not used! It is a wicked new upgrade to accessing information and I am very happy. Everyone knows how hard I am to please when it comes to IBM LOL. I think this is what we have been looking for as Middleware professionals using IBMs products.


Leave a Reply