Installing Maximo Asset Management 7.6.1 From Start to Finish
Richard Lesses 2700011KU1 Comments (7) Visits (16009)
Welcome to Maximo Asset Management 7.6.1!
This is the first in a series of blogs on Maximo 7.6.1, released 27 July 2018. Future blog plans include installing to Red Hat Enterprise Linux 7.5 (no Launchpad), Upgrading to Maximo 7.6.1 from Maximo 7.6.0.x, and Installing Maximo with an already configured Active Directory server.
Installing Maximo 7.6.1 and updating from Maximo 7.6 is like installing Maximo 7.6 and updating from Maximo 7.5. It is installed to a new directory.
Maximo Asset Management Feature Packs
Installing Maximo Asset Management 7.6.1, WebSphere Application Server 126.96.36.199 and Db2 Advanced Workgroup Server Edition 188.8.131.52 to a new installation of Microsoft Windows Server 2016
Part 1. Download and Installation
First, download Maximo 7.6.1 from Passport Advantage. (See Maxi
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 the documentation.
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; it is not installed 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 will install WebSphere, Db2 and Maximo 7.6.1 on a single Microsoft Windows 2016 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:
Clicking Next displays a progress bar, the first of many you will see.
Accept the terms, and click Next.
Note: My recommendation is to change the directory to (for example) C:\IBM\IMShared.
The next screen lets us change where Installation Manager installs. I accept the defaults (but see below), and click Next.
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
Here we select languages. This is an English language only server, so I click Next.
This is a good example to show how Installation Manager works. On the left side, you can select items on the left side to modify. Items that must be entered or modified are shown with an asterisk. Or, you can just click Next to go to the next item to be configured. The Install button does not become active until you have filled in all of the required information.
In my case, I accept the defaults for IBM HTTP Server, and enter Db2 password information.
Click Next. The Installation Manager now checks to see that all files are available, and whether there are any blocking processes.
[This is a screenshot from the Installing Maximo 7.6 blog; when I created the screenshots for this series I was distracted and did not get the 7.6.1 version. It looks different because I used Windows Server 2012 for the 7.6 series and Windows Server 2016 for this series.]
Now the Install button is enabled, so click Install.
Part 2. WebSphere Application Server Configuration
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 accept 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 previously: the Prepare WebSphere Application Server for configuration option is now gone.
Exactly what does Create and configure the database mean?
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, you will need to create them, or 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 ear and maximo-x war 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.
On the next screen, enter the passwords for the application server (WebSphere only). Once complete, click Next.
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.)
Installation is now complete!
Updated 27 Aug 2018 - added link to What is supposed to be in the Maximo 7.6.1 installation directory? blog post
Updated 9 Nov 2018 - Expanded Define the Deployment Manager Server Host