Installing and Deploying Maximo 220.127.116.11+ to DB2 11.1.1 and WebSphere 9.0.0
Richard Lesses 2700011KU1 Visits (9551)
For installing WebSphere 9, see Inst
For installing DB2 11.1.1, see Ins
See the Technote on WebSphere 9 performance and steps to setting Cust
This example uses Maximo 18.104.22.168, but applies to supported Maximo versions, 22.214.171.124 and later.
Install Maximo Asset Management 126.96.36.199
Download Maximo 7.6 (only) and Maximo Feature Pack 188.8.131.52 or later. Expand MAM_184.108.40.206_WIN64.
Launch Installation Manager.
From File, select Preferences.
Click on Add Repository...
Go to the location you extracted MAM_220.127.116.11_WIN64 to.
Add repository.config from Conf
Add the Maximo Feature Pack you will be installing.
Click on Install.
Tick IBM Maximo Asset Management, Version 18.104.22.168 and install it.
In this example, it is installed to the default Windows directory C:\IBM\SMP.
Notice: As you follow the steps below, you will notice that I used the 22.214.171.124 version of the Configuration Tool, and that it works with both WebSphere 126.96.36.199 and Db2 11.1.1, which are configured manually in my previous two blog posts. This is a bit of cheating on my part. We cannot guarantee that the Configuration Tool will work outside of this very by-the-book installation.
Using Configuration Tool is not necessary for installing Maximo to Db2 or to WebSphere. See http
Click on Configure a New Deployment
Define Deployment Environment
DB2 was configured manually on this server. Enter the fully-qualified domain.
WebSphere was configured manually in the previous blog post. Select the radio button next to WebSphere is already configured and check Bypass WebSphere validation.
Screens not shown:
The maximo.ear and maximo-x.war will need to be deployed manually.
Updated 5 Apr 2018