Maximo SAAS on AWS–Chapter 103

In last tutorial on Maximo on AWS ,  we have moved our stuff to the EC2 instance and in this tutorial we will install the required Maximo software and other middleware components.

This installation is divided into three parts:

1. Maximo Base Install
2. WebSphere and IHS install
3. Plugin configuration and Horizontal node federation for scaling.

* SQL Server is not mentioned above because it is already installed and Maximo user is configured and has all the rights.

Maximo Base Install

Download the MAM from IBM portal.


Extract it and start launchpad64.bat (Windows)
Uncheck the Db2 and WebSphere 8.5.5 part because we already have SQL server configured and I faced some issue with automatic deployment of WebSphere via this wizard,so I will configure that manually.
Install the Maximo Asset management and the Installation Manager.
Make the install in C:\ibm\smp


Now your Maximo install is done and installation manager is configured to accept other software via Repository.

In future if you want to install any other software, Installation manager provides a feature where you can add local repository or import it from IBM site.We will see that in a while.

WebSphere and IHS Install

Now we will install the middleware components of Maximo, which includes WebSphere and IHS.
IHS provides unique capability to distribute the load among various WebSphere servers.


Download the WebSphere either via adding the repository to Installation manager or by direct download.I downloaded directly as shown below.

WAS ND Part no:

• CIK2HML
• CIK2IML
• CIK2JML

WAS 8.5.5 Supplement Installation
Download following part no.
Part No
CIK1VML
CIK1WML
CIK1XML



Make sure you install supplement for WAS 8.5 because it contains IHS and Plugins for IHS configuration.WebSphere customization toolkit will help us configure IHS plugin in front of WebSphere.
Add the below repo in Installation manager(Preferences page)
Online Repo

http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WCT.v85 

Extract  all the above components and add them as a local repository in Installation manager.
click on Add repository and locate the Disk 1 of WebSphere.


Similarly add all the components including the supplements folder , you might need to enter your IBM credentials for your online repository.



Make sure you install WCT for WAS 8.5 because it contains Plugins for IHS configuration.WebSphere customization toolkit will help us plugin IHS in front of WebSphere.

Repo

http://www.ibm.com/software/repositorymanager/com.ibm.websphere.WCT.v85 

Make sure you install supplement for WAS 8.5 because it contains Plugins for IHS configuration.WebSphere customization toolkit will help us plugin IHS in front of WebSphere.


Now you are all set and click on Install package option of Installation Manager.

You will be presented with following options

Accept License


Accept next two screens for language and package information.




IM will start collecting files.
Prompt for Disk 2 of WAS.



Locate the disk2 and press ok, do the same for disk 3(for both ND and supplement)
click on Install, it might take a time to download the online repository(if you have specified any)
Accept default for all options, change install path of all the application to
C:\IBM\XXX



But wait our Maxino 7.6 is compatible with only JDK 1.7.1 and above and will not work with current version of jdk which is 1.7.0 which will come with 8.5.5.0 so lets upgrade our WAS to 8.5.5.11 fix pack so that Maximo can run properly, please note this is mandatory step else it will not work.

To follow the upgrade thing please navigate to WAS 8.5.5 upgrade guide to 8.5.5.11

Later please come back and continue, also note that alternative to this is to go to WAS 9( I personally find lot of bugs on WAS 9 and had to come back to this version)


If you WAS is at 8.5.5.11, its the right time to move ahead and create a profile.

Since we need a horizontal architecture for our Maximo system, we will create an ND profile.




Go for the top one, Deployment manager profile and install it.
Accept defaults.


Two profiles will be created.




Start the deployment manager and the app server.







Web Sphere is installed, next step is to marry our bachelor http server with our deployment manager, merge http server inside the deployment manager so that HTTP server can work in unison with Deployment manager.

Start Node.


You will see status of node as green, if it is started properly.


Now we will use WCT to install and configure http server plugin.

open the customization toolbox and select webserver plugin configuration tool.



Locate the plugins



Click Create



Select httpd.conf file your HTTP Server.




IBM Http administration server need to go as a windows service.



Specify a unique name for webserver.


Locate the appserver folder




Select the Dmgr01 profile and click next.


Success


Lets go back to our Admin console and see this newly added webserver(port 80)
It didn’t appear for me so I manually created web server definition.
Important step: Enter plugin location while creating web server as C:\WebSphere\plugins
and accept default for rest.





Now add a new cluster to the cell.


Now create two new members, which will host our Maximo application.


Its a good idea to go to cluster and create new servers and add from there itself.
Make sure you assign enough memory to handle Maximo, I am giving 2gb for now to both.

Go to process definition of each server and assign, initial and maximum heap size of the server and save the configuration( Do it for both of the server)
Now find out the listen ports of both of your servers (Maximo 1 and Maximo 2 aka JVM)
So right now you have a vertical Maximo cluster which has different ports and is interfaced with a http server, but it won’t work because we have not added a virtual host which can map incoming http requests to port 80 and distribute it to JVMs.

Port for my Maximo 1 and Maximo 2 are 9082 and 9083 respectively, add these two ports to default_host(make sure port 80 is also there)
Now build your Maximo application by going to

Once it is built, install as an EAR on fast path and map to cluster and the webserver1.



Application built, get the database ready by running maxinst.

Since its SQL server, we will use PRIMARY table space.
Before that, edit your maximo.properties to point to database and enter credentials.


mxe.db.username=maximo
mxe.db.password=maximo

Now go to SMP/maximo/tools/maximo/


maxinst.bat –sPRIMARY –tPRIMARY( for sql server)




After this, your database is ready. Deploy the EAR on WAS and star the Maximo instance.

This is the end of how Maximo can be offered as SAAS on AWS using local SQL server as database, in next tutorial we will see how we add Amazon RDS service to host our Maximo database and how we will achieve Horizontal and Vertical cluster on Web sphere ND via two EC2 instances.

Part 4 >  Introducing RDS and Horizontal clustering to Maximo on AWS

Keep Reading !
Action Item : Subscribe & Share !