In our last tutorial on how to move Maximo to AWS , we saw how all the components were installed on different nodes and how horizontal and vertical clustering will work on WebSphere, In this part of the tutorial we will be doing final testing of our architecture and will start Maximo on both the nodes federated and running in a single Cluster
Topics
Lets identify the default http port of our MaximoServer3(Custom node) and add it to virtual host.
Now lets generate the Web Server (HTTP) plugin again and propagate it, so that our HTTP server knows about the new servers on different nodes and can do Round Robin.
Ref:Generate propagate
Again I faced the unexpected- unsupported Class version error while starting my third (maximoserver3) on custom profile and reason is that it might be using the older version. So again we need to do managesdk to enable newer version of JDK for this WAS profile
java.lang.RuntimeException: java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=psdi/iface/gateway/
So I tested my Java on second node and found out this.
Still on 1.6, Bummer !
Lets enable the latest Java so that our dear Maximo can run here as well.
Ok we are good to go, Lets stop and start the cluster again.
Please note that, if you change any of the following in WAS cell during this process:
Server Configuration, including ports
Make sure all servers have at least 2 Gb of heap else it will fail.
Enough said, lets see the whole infra in action.
Ripple start the servers and you should see
Its the right time to attach an S3 bucket and mount it to your instances, so that documents(doc links) can be stored there. Refer the article on how to mount s3 bucket on windows to configure this step.
Now we have an S3 drive which can hold our documents and can be plugged into Maximo.
Assuming your drive is ready , lets follow this link to configure doc links for Maximo 7.6.
Now its right time to add load balancer to your configuration to avoid single point of failure.
Create a new ELB and add target as one of our HTTP server.
Use this.
Add listener, for now let it be 80 port only.
Select both zones, continue and select a security group, make sure that SG allows 80 port.
Configure routing now.
Now lets select targets for our group, we need to add the http server here ( http://httpserverip/maximo)
Register your targets here, please note you will see both of your nodes here, you need to select a target where http server is running.Its a good idea to run two http servers on both the nodes( both web servers should have the plugin configuration) so that in case of failure other server can serve to the JVM on another nodes. Also ELB will have two targets to route traffic to , if you have two http servers.In the configuration I explained in earlier chapters, I only explained 1 http server, which could do round robin to both the nodes.
Now review and generate the load balancer, your LB will be active in minutes and will give you the DNS name.This DNS name should be shared with users who want to access the Maximo Application.
This will be the end of Maximo as a service on AWS series, send your reviews and feedback and please follow on google+.
Index of Maximo AWS series.
Chapter 101
Chapter 102
Chapter 103
Chapter 104
Chapter 105
Chapter 106
Keep Reading !
Action Item: Subscribe and Share !
Topics
- Final Configuration
Lets identify the default http port of our MaximoServer3(Custom node) and add it to virtual host.
Now lets generate the Web Server (HTTP) plugin again and propagate it, so that our HTTP server knows about the new servers on different nodes and can do Round Robin.
Ref:Generate propagate
Again I faced the unexpected- unsupported Class version error while starting my third (maximoserver3) on custom profile and reason is that it might be using the older version. So again we need to do managesdk to enable newer version of JDK for this WAS profile
java.lang.RuntimeException: java.lang.UnsupportedClassVersionError: JVMCFRE003 bad major version; class=psdi/iface/gateway/
So I tested my Java on second node and found out this.
Still on 1.6, Bummer !
Lets enable the latest Java so that our dear Maximo can run here as well.
Ok we are good to go, Lets stop and start the cluster again.
Please note that, if you change any of the following in WAS cell during this process:
Server Configuration, including ports
- Virtual Hosts
- Application Mapping
- New Cluster member
- Server addition
Make sure all servers have at least 2 Gb of heap else it will fail.
Enough said, lets see the whole infra in action.
Ripple start the servers and you should see
Its the right time to attach an S3 bucket and mount it to your instances, so that documents(doc links) can be stored there. Refer the article on how to mount s3 bucket on windows to configure this step.
Now we have an S3 drive which can hold our documents and can be plugged into Maximo.
Assuming your drive is ready , lets follow this link to configure doc links for Maximo 7.6.
Now its right time to add load balancer to your configuration to avoid single point of failure.
Create a new ELB and add target as one of our HTTP server.
Use this.
Add listener, for now let it be 80 port only.
Select both zones, continue and select a security group, make sure that SG allows 80 port.
Configure routing now.
Now lets select targets for our group, we need to add the http server here ( http://httpserverip/maximo)
Register your targets here, please note you will see both of your nodes here, you need to select a target where http server is running.Its a good idea to run two http servers on both the nodes( both web servers should have the plugin configuration) so that in case of failure other server can serve to the JVM on another nodes. Also ELB will have two targets to route traffic to , if you have two http servers.In the configuration I explained in earlier chapters, I only explained 1 http server, which could do round robin to both the nodes.
Now review and generate the load balancer, your LB will be active in minutes and will give you the DNS name.This DNS name should be shared with users who want to access the Maximo Application.
This will be the end of Maximo as a service on AWS series, send your reviews and feedback and please follow on google+.
Index of Maximo AWS series.
Chapter 101
Chapter 102
Chapter 103
Chapter 104
Chapter 105
Chapter 106
Keep Reading !
Action Item: Subscribe and Share !
No comments:
Post a Comment