Installing Maximo Asset Management 7.6 (Windows) from Start to Finish (2017 edition)
Richard Lesses 2700011KU1 Comments (9) Visits (38341)
Welcome to Maximo 7.6! This is a compilation and update of a series of posts I made just after Maximo 7.6 came out at the end of 2014. It is updated through December 2017.
Let's start stepping through the installation, screen by screen.
Part 1. Download and Installation
Double-click on launchpad64.exe, which will lead to 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:
Let's stop here, with an explanation of what using Installation Manager gives you. A few years ago, I blogged about gett
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.
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. It works directly to download WebSphere updates. For Maximo updates, you still download the Feature Packs and Interim Fixes and add them to the IM repository.
Clicking Next brings a progress bar, just to let you know it's working.
I accept the terms, and click Next.
Note: My recommendation is to change the directory to (for example) C:\IBM\IMShared.
Note: My recommendation is to change the directory location so there are no spaces in the file path, for example, C:\IBM\SQLLIB, C:\I
On this page we fill in configuration information for DB2 and WebSphere. This is a good example of the way Installation Manager works. On the left side, it lets you select items on the left side to modify. Those that must be modified are shown with an asterisk. Or, you can just click Next to go to the next item to be configured. The Install button won't become active until you've filled in all of the required information.
I enter the DB2 password information, and accept the defaults for WebSphere's web server.
I click Next. The Install Manager checks to see that all files are available, and whether there are any blocking processes.
Now the Install button is enabled, so click Install.
(After you have installed Maximo Feature Pack 18.104.22.168, the Config Tool screen has more options.)
Part 2. WebSphere Application Server Configuration
These two parts of the configuration - Middleware product installation and configuration - used to be handled by the Middleware Installer (MWI) tool in Maximo 7.5. In Maximo 7.6, they are separate. This separation lets you skip WebSphere configuration. This is very important if you need to configure WebSphere manually, or have already configured WebSphere and don't need the Config Tool to do it for you.
However, in this case you are installing it for the first time and do need the Config Tool to do the configuring. A future blog post will show one way of installing Maximo to a server with an existing WebSphere installation. [Not by cloning, which is unsupported, but see my b
Here we will prepare the WebSphere instance for use with Maximo. That includes setting up application servers, creating profiles, configuring IBM HTTP Server, and setting the administrative security mode. Since the Config Tool is a direct descendant of the Reconfiguration tool, you can automate configuration for deployment into a clustered environment.
From this screen, you can also configure a new deployment and access the Maximo documentation. There is also a WebSphere cleanup option. Configuring a new deployment will be the subject of a future blog entry or two.
DB2 configuration will be done in a later step, when you configure a new deployment.
For my installation, I am accepting all defaults.
Most fields and controls will have flyover help. In addition, there are (?) icons that indicate item help and section help, depending on where they are placed. Clicking the help text will open contextual assistance without leaving the panel. For page level context help, you can click on the Click for More Information links, which will give you access to additional pages for more help. It is available by pressing F1, going through the Help menu, or clicking the Help button at the bottom.
This screen also gives you the option to configure the system for clusters.
Part 3. New Deployment Configuration
When you have finished WebSphere configuration and deployment, it reloads the Configuration screen. It looks different than before - the Prepare WebSphere Application Server for configuration option is now gone.
Exactly what does Create and configure the database mean?
Ticking this checkbox will have the Config Tool create the database, necessary users and schema first. You will have to enter the user name and password of a user with administrative rights to the server you put into the Host name field. If your site's security roles separate Maximo installation from database administration, need to create them, you will need to have someone else create them before running this configuration step. Instructions for the database administrator to do so are in the inst
Exactly what does Define the Deployment Manager Server Host mean?
The default value, Complete Configuration of WebSphere for your product, will have the Config Tool create the JMS queues and maximo_host Virtual Host, and tune MXServer. Tuning will set the starting and maximum memory values, set the thread pools and generic JVM arguments foll
Checking off Deploy the product into a clustered environment. will deploy Maximo to if the cluster(s) had previously been created, either through the Configuration tool (during Prepare WebSphere Application Server), or done manually. The default value is to complete configuration. That will build and deploy the maximo and maximoiehs ear files.*
If you want to do this manually, you can select WebSphere is already configured, and, if you wish, Bypass WebSphere Validation. Select these options is necessary if you have an existing WebSphere installation or are installing a second Maximo instance to the existing WebSphere installation.
On this screen, you can also define a default password for all users. This is a good option when you're setting up a demo or preview Maximo.
Since I am going the default everything route, I fill in the password for the Administrator account on the Windows server to which I am installing Maximo, and use a default password for everything, and click Finish.
Installation is now complete!
Appendix: Some Handy Links for Maximo 7.6
Maximo Asset Management feature Packs (updated 19 Jan 2018)
Questions and Answers
1. I discovered that not all WAS zip packages one downloads from Passport Advantage are the same. This blog assumes use of the WAS middleware media packaged for Maximo Installation.
This blog does assume WebSphere was installed using our packages. But, still WAS is WAS. The changes the installer and configuration tools do are all by the book. To get an idea of what to do if you are configuring manually, see http
2. Is it be considered a better (or best) practice to download and install Feature/Fix Pack updates to main Maximo software and middleware components, prior to moving to Part II of the blog (TPAE Config Tool)? At the very least, it would avoid the extra steps of rebu
Generally, yes. In some special cases, where a large number of Industry Solutions and Add-Ons are installed, it may be necessary to install them stepwise rather than all at once.
3. The DB2 Fix Pack 9 update installed without using IBM Installation Manager (IM). After completing the update, Installation Manager still reports DB2 is at 10.5.0.4. Is this is a known issue? Or is there some other method I missed on how IM installed DB2 packages should be updated?
This is a known issue because DB2 does not use IBM Installation Manager (IM) natively. We created a package for the initial installation of DB2 10.5 FP4 that uses command-line installation of DB2 to install and license DB2 10.5 FP4, and then configures DB2 for use with Maximo.
4. Can I use Java 8 with Maximo 7.6?
Yes, but only with WebSphere 9. WebSphere 8.5.5 with Java 8 is is not compatible Maximo 7.6. Since we now (Maximo 7.6 IFR2) includes WebSphere 9, you can install and migrate WAS 8.5.5 profiles to it. For a first time WAS install for Maximo, see the link above. The future post referenced above, on using Configuration Tool with an already-installed WebSphere environment, may work with WebSphere 9, but doing so is not supported by IBM.
If you like this blog post, I'm sure you'll like Maxi
Updated 19 Jan 2018 - Added Q&A Section
Updated 9 Nov 2018 - Expanded Define the Deployment Manager Server Host