This blog post (and the parts before and after 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 2
When you click the Finish button the previous screen, the Deployment configuration tool will launch.
This initial part of the configuration that was done through the Middleware Installer (MWI) tool in Maximo 7.5. Here, you will prepare the WebSphere instance for use with Maximo. That includes setting up application servers, creating profiles, configuring IBM HTTP Server, setting the administrative security mode. Since this 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 is done in a later step.
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 (defaults to MXServer) and the web server (defaults to webserver1). You also configure the WAS admin server security here, providing a username (defaults to wasdmin) and password for access into the WebSphere administrative console.
For Windows installations, here you indicate whether the services should be run as Windows services, and which account is used to run the services.
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.)
On this screen, you can validate the changes (by unchecking the two bottom checkboxes) before applying any of them. This is a great feature. I cannot stress just how neat it is.
And away we go! Some time later...
WebSphere is now prepped and ready to be installed to by the next configuration tool, which is covered in the next blog post.