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 June 2017.
Let's start stepping through the installation, screen by screen.
Part 1. Download and Installation
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, 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:
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 126.96.36.199. 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 188.8.131.52 adds JDK 1.8 support, which is downloaded separately.
Let's stop here, with an explanation of what using Installation Manager gives you. A few years 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.
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.
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.
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:\IBM\WebSphere\AppServer, C:\IBM\HTTPServer, and so on.
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 184.108.40.206, 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 blog post on Cloning Maximo 7.6
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.
On this screen, you can see that most functions are handled using a wizard interface. You have several options: you can go step-by-step through each of the configuration screens, filling in or changing information and clicking the next button. You can also navigate on the left side between different screens. You will see field indicators (validation) that let you find and correct problems more quickly. Error and progress messages are written to the console area on the bottom of the screen.
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.
This screen is for configuring the application server profiles. The application servers are both the web application server (default name is MXServer) and the web server (default name is webserver1). You also configure WAS admin server security here, providing a username (defaults to wasdmin) and password for access into the WebSphere administrative console. Click Next.
For Windows installations, here you indicate whether the services should be run as Windows services, and which account is used to run the services. I'm using the defaults, and click Next.
This screen allows you to configure Administrative security. If you have previously set up an IBM Tivoli Directory Server or Microsoft Active Directory server, you configure the connection and directory hierarchy here. If you already have users and groups ready to bring into Maximo, you enter the hostname, bind credentials, and the base entry, user suffix, group suffix and organization container suffix here. (You will set up the VMMSync or LDAPSync cron task later in Maximo itself.) A future web post will cover installing with an already configured Active Directory server.
On this screen, you can validate the changes (by unchecking the two bottom check boxes) before applying any of them. This is a great feature. I cannot stress just how neat it is.
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.
Click on Configure a New Deployment. It brings up the following screen.
From the Database type dropdown, you can select DB2, Oracle database or Microsoft SQL Server, and provide it with the host name.
Exactly what does Create and configure the database mean?
Glad you asked. It means it will 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 installation documentation, found here.
For Define the Deployment Manager Server Host, I can select Deploy the product into a clustered environment. This would work if I had created the cluster(s) previously, either through the Configuration tool (during Prepare WebSphere Application Server) or had done so 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. Using these options will be covered in the same blog post I promised above on installing Maximo to a server with an 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.
Once the Config Tool has validated the database parameters, it will bring you to this screen. Here, you set your database, application server and security and base and additional language options (and whether you want to populate the database with demo data) and click Next.
The next two screens are for configuring the database. The options will be different for each database (DB2, Oracle database, or Microsoft SQL Server).
Here you configure WebSphere application server security. If you are using JEE application security, indicate so here, and configure the directory server as well. I am going with native Maximo authentication. Click Next. (As promised above, a future web post will cover installing with an already configured Active Directory server.)
In these two following screens you indicate your base language and additional languages you want to install. With English-only, I click Next and Next.
Once completed you will see this screen, Apply Deployment Operations. Again, one of the great things about the Configuration Tool is that you can validate everything before you commit it. So, I unchecked everything and just left the Validate the configuration properties selected, and clicked Finish.
So it is validating away...
Once Validation is complete, since the deployment operation did not complete, you get the option to continue the configuration.
I click Yes, and select every configuration option.
For my configuration, I will be creating the Maximo database, populating it with demo data, build the Maximo and Maximo Help ear files, start the Maximo application server (MXServer), then deploy the maximo.ear and maximoiehs.ear and start the MAXIMO and MAXIMOIEHS applications. All of these tasks will take awhile.
Note the information messages as the scroll in the console underneath.
And it's complete!
Once you click OK, you're brought back to the Configuration Tool screen. Now that it has installed a working Maximo, notice that it has changed again.
Installation is now complete!
Appendix: Some Handy Links for Maximo 7.6
Maximo Asset Management feature Packs
That's all for today.
If you like this blog post, I'm sure you'll like Maximo and LDAP - Configuration from Start to Finish and Clustering with Maximo and WebSphere 8.5.5.