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/
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/
