This blog post (and the parts before it) have been updated and combined into Installing Maximo Asset Management 7.6 (Windows) from Start to Finish (2017 edition).
Continuing from Installing Maximo 7.6: A first look, part 3
This will be a long post, because, as with the previous ones, it will consist mainly of screen shots.
When you complete WebSphere configuration and deployment, when it brings you back to the Configuration screen, it will look different than before (the Prepare WebSphere Application Server for configuration option is gone).
Next, we click on Configure a New Deployment. It brings up this screen.
From the Database type dropdown, you can select Oracle database or Microsoft SQL Server, and provide it with the host name. What does Create and configure the database mean? Different things for different databases. For DB2, it means it will create the database, necessary users and schema first. It will not create the schema and database for Oracle and SQL Server, however. You will have needed to create them prior to running this configuration step. Instructions for doing so are contained 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, which is to 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.
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.
Once it 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.
The next two screens are for configuring the database. The options will be different, depending on whether you are using DB2, Oracle database, or Microsoft SQL Server.
In the next screen you enter the passwords for the application server (WebSphere only).
Here you configure WAS security. If you are using J2EE application security, you indicate so here, and configure the directory server as well. I am going with native Maximo authentication. Perhaps I will create blog post that will cover setting up Maximo 7.6 with application server security enabled sometime in the future.
In these two following screens you indicate your base language and additional languages you want to install.
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 click Finish.
So validate away...
Once the 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 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.
From here you can perform many standard Maximo configuration tasks - but I think the configuration tool should get its own blog entry. Bye for now!