This blog post (and the parts after it) have been updated and combined into Installing Maximo Asset Management 7.6 (Windows) from Start to Finish (2017 edition).
I've been working with the new Maximo 7.6 installer for a while now. Compared to the installer used with Maximo 7.1 and 7.5, it is a big improvement.
First, you have many fewer screens to go through. At most, you'll see 11 screens, instead of more than 25. Each screen provides field validation for your entries.
Second, before you install anything, you can review, validate and modify all of the entries, rather than waiting until everything has been entered and pressing that next button.
Third, there is additional contextual information, flyover help, embedded help on panels, and additional page level help.
Finally, you will see important messages and errors while it is going through its steps. You can fix errors on the fly and resume most installation operations.
The new installer separates the WebSphere installation into two parts, installation and preparation. This gives you a good break point between laying down the application files and configuring the product.
Let's start stepping through the installation, screen by screen.
First, download the product from Passport Advantage. (See Maximo Asset Management 7.6 and Maximo Asset Management Multitenancy 7.6, too.) Make sure you extract each download into the same directory. When finished, it should look something like this
Double-click on launchpad64.exe. Here's the Welcome screen.
Looking at the left side, select Installation Planning.
Here you can access the installation documentation directly from the IBM web site. You will need this to install the middleware and Maximo properly. I strongly recommend that you download it.
The prerequisite verification tool is a command line interface (CLI) tool that helps you ensure that you have the proper OS versions and resources available on your target server. (The product installer performs some of these tests as well.)
Select Install Product.
This screen is where you select whether you will install WebSphere and DB2 and Maximo, and from where you launch the installer. Depending on how you choose to install the product, you can download and run the installer from as many as three machines: one each for the WebSphere server, DB2 server, and administrative workstation. You can combine one or more of these installations to a single server; make sure you have the resources available on a server before installing DB2 and WebSphere to the same server.
From this screen, you can also install a second instance of these products. (I will not be covering that option at this time; we haven't installed it for the first time yet!)
Click on Optional components.
From here, you can install the IBM Data Studio, which is used to manage DB2.
Going back to the Install Product screen, I'm going to install WebSphere, DB2 and Maximo 7.6 on a single Windows 2012 server, so I make sure all three items are selected, and click Install IBM Maximo Asset Management components.
This shows all of the packages that will be installed. There are four products it is installing:
1. IBM Installation Manager 1.8.0. This will be "running in the background" to install WebSphere and Maximo. DB2 uses its own installer, which we repackaged into an IM installation.
2. Maximo 7.6, in two parts (Maximo and Tivoli's process automation engine configuration tool)
3. DB2 10.5.0.4
4. WebSphere 184.108.40.206. The install includes IBM HTTP Server and web server plug-in, the customization toolbox and IBM WebSphere Java SDK. Note that Maximo 7.6 requires JDK 1.7. Maximo Feature Pack 220.127.116.11 adds JDK 1.8 support, which is downloaded separately.
Let's stop here, with an explanation of what using Installation Manager gives you. A while ago, I blogged about getting excited about installation. This what I wrote then (edited and updated):
IBM Installation Manager (IM) is an Continuous Engineering product that installs and maintains software packages.
It replaces the variety of installers we used to install products that employ custom-built installers (WebSphere’s installer and updater), third-party installers (InstallAnywhere), OS-dependent installers (batch files and shell scripts) and IBM Autonomic Deployment Engine (Deployment Engine, Middleware Installer, Base Services Installer and Process Solution Installer)
Like DE, IM writes to a local repository to track product installations, versions and configurations.
For installation administrators, here's the neat part:
IBM Installation Manager is integrated with Passport Advantage and IBM Fix Central to speed downloading installation packages and Fix Packs and Feature Packs. It connects directly to those sites when you want to install new packages or update current installations. While it works directly with WebSphere updates, in the case of Maximo updates, you will still download the Feature Packs and Interim Fixes and add them to the IM repository.
Also, Installation Manager is supported externally and internally. It is sold as a standalone product for enterprises to roll out software and need to be able to package, customize, and track installations in a local data repository. Support for Installation Manager, as with WebSphere and DB2, is available both directly and through Maximo support.
Next time: Clicking Install and after.
Updated 20 Jun 2016 RWL