Technical Blog Post
Complete the steps in this blog post to install a new Maximo 7.6.1 instance.
Welcome to Maximo Asset Management 7.6.1!
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.
- Product information and publications: Maximo Asset Management software requirements
- What's New in Maximo Asset Management 7.6.1
- What to download for Maximo Asset Management 7.6.1
- What is supposed to be in the Maximo 7.6.1 installation directory?
- Maximo 7.6.x Designer 431 Report Development Guide (BIRT Reporting) - updated for Maximo 7.6.1
- Maximo Upgrade Resources
- Maximo Upgrade Requirements Matrix includes Industry Solution and add-on versions compatible with Maximo 7.6.1
- Updates for Maximo Asset Management 7.6.1 feature packs has a complete list of updates for all Maximo Asset Management 7.6.1 feature packs
- Platform Configuration Matrix
Maximo Asset Management Feature Packs
- Maximo Best Practices for System Performance 7.6.x
- Maximo Asset Management Wiki on developerWorks
- Support Forums for Maximo
Double-click launchpad64.exe, which will bring up the Welcome screen.
Looking at the left side, click Installation Planning.
Here you can access the installation documentation directly from the IBM website. You need the documentation 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.)
On the left, select Install IBM Maximo Asset Management.
This screen is where you select whether 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. when installing Db2 and WebSphere to the same server, make sure you have the resources available on the server.
From this screen, you can also install a second instance of these products. [I do not cover that option at this time; it is not yet installed!]
Click 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 am installing 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.
The screen capture shows four packages that will be installed:
1. IBM Installation Manager 1.8.8. After installing itself, Installation Manager installs Maximo, WebSphere and Db2. (Db2 uses its own installer, which we built into an Installation Manager package.)
2. Maximo 7.6.1
3. DB2 11.1
4. WebSphere 184.108.40.206, which includes IBM HTTP Server and the web server plug-in, the customization toolbox and IBM WebSphere Java SDK 1.8. Maximo 7.6.1 requires JDK 1.8.
Clicking Next displays a progress bar, the first of many you will see.
Once that is completed, then to the license page.
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 and click Next.
This screen shows, and lets me change, where the products are going to be installed.
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.
Here we select languages. I am installing to an English language only server, so I click Next.
Here is the summary of packages to be installed.
On this page, we complete configuration information for DB2 and WebSphere.
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, click Next to go to the next item to be configured. The Install button does not become active until all required information has been entered.
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.
Now the Install button is enabled, so click Install.
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 is done in a later step, when configuring a new deployment.
For my installation, I accept all defaults.
On this screen, you can see that most functions are handled by using a wizard interface. You have several options: you can go step-by-step through each of the configuration screens, entering or changing information and clicking the next button. You can also navigate on the left side between different screens. You see field indicators (validation) that flag problems more quickly. Error and progress messages are written to the console area on the bottom of the screen.
Most fields and controls have hover help. In addition, there are (?) icons that indicate item help and section help, depending on where they are placed. Clicking the help text opens contextual assistance without leaving the panel. For page level context help, Click for More Information links to get access to additional pages for more help. It is available by pressing F1, going through the Help menu, or clicking the Help button.
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 configure WebSphere administrative server security here. Enter a username (default value is wasdmin) and password for access into the WebSphere administrative console. Click Next.
For Windows installations, here you indicate whether the services are to be run as Windows services, and which account is used to run the services. I using the defaults, and click Next.
On this screen, configure Administrative security. If you have IBM Security 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. (Set up the VMMSYNC or LDAPSYNC cron task 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, still.
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 Hostname 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 installation documentation, found here.
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 following Maximo 7.6 best practices.
Checking off Deploy the product into a clustered environment deploys Maximo if the clustering is configured, 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 enter 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).
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.)
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 cleared everything but Validate the configuration properties , and clicked Finish.
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 maximo-x.war and start the MAXIMO and maximo-x applications. All of these tasks will take a while.
Note the information messages as the scroll in the console underneath.
Installation is now complete!