Def of CLUSTERING : It is a set of AppServers having same applications Installed,Grouped locally for WORKLOADMANAGEMENT (WLM)
(or)
-----> Grouping of AppServers under a single application / name
-----> Using Clustering we can create a scope and achieved through WORKLOADMANAGEMENT and FAILOVER
(OR)
-----> Every cluster member must have the same configuration and same version.We can say each cluster member is the clone to one another.
-----> Clustering concept is for High Availability and and Workload Management.
Q) How to install an application in one cluster member out of multiple members?
A) One cannot deploy application in one cluster member alone in the clustered environment since application which is deployed in one cluster member will be shared across to the other cluster members automatically. So logically it is equivalent, installing application in cluster level.
----> Make the "cluster member weight" where you DONT want the application to be installed as Zero.
There are 2 types of CLUSTERING
1) VERTICAL CLUSTERING : Deployed the application on one machine and we can run that application on our own box(or) machine.
----> In this Vertical Clustering Machine FailOver is not possible.
----> If the machine gets failed we cannot run that application (or) SINGLE POINT OF FAILURE.
---> If one Server fails the other Server will takes care
----> If machine fails nothing can be done.
(OR)
-----> All the JVMs resides on the same physical machine along with the DMGR.
-----> When the JVM failover happens other JVM in that cluster will handle the request as part of the High Availability.
-----> But when the physical machine failover happens we will lose every thing
2) HORIZONTAL CLUSTERING : Grouping of AppServers in which one AppServer should be on one node and Another AppServer should be on another node.
-----> Means if we take two machines one application should be deployed on different machines Remotely (or) one application should run in INDIA and another application should run in AMERICA.
-----> If Machine1 application will be deployed on Machine2 so we have to know the IP address of Machine1 then only it is possible to deployed that application Successfully.
----> Both Machines should have Internet Connection.
----> Here no SINGLE POINT OF FAILURE.
----> It Supports MACHINE FAILOVER.
(OR)
-----> DMGR and the JVMs resides on the different machines.This will work even when the physical machine failover is happened.
WORKLOADMANAGEMENT : Sharing requests across Multiple Servers.
SCALABILITY : can add 2/3 members or add a cluster member to existing member
LOADBALANCING : Allocate workload proportionality among available resources.
AVAILABILITY : System runs if server fails with Clustering. (or)
----> Applications are still available if a server fails.
Next Page : http://webspherelife.blogspot.com/2018/09/clustering-in-was-websphere-application.html
(or)
-----> Grouping of AppServers under a single application / name
-----> Using Clustering we can create a scope and achieved through WORKLOADMANAGEMENT and FAILOVER
(OR)
-----> Every cluster member must have the same configuration and same version.We can say each cluster member is the clone to one another.
-----> Clustering concept is for High Availability and and Workload Management.
Q) How to install an application in one cluster member out of multiple members?
A) One cannot deploy application in one cluster member alone in the clustered environment since application which is deployed in one cluster member will be shared across to the other cluster members automatically. So logically it is equivalent, installing application in cluster level.
----> Make the "cluster member weight" where you DONT want the application to be installed as Zero.
There are 2 types of CLUSTERING
1) VERTICAL CLUSTERING : Deployed the application on one machine and we can run that application on our own box(or) machine.
----> In this Vertical Clustering Machine FailOver is not possible.
----> If the machine gets failed we cannot run that application (or) SINGLE POINT OF FAILURE.
---> If one Server fails the other Server will takes care
----> If machine fails nothing can be done.
(OR)
-----> All the JVMs resides on the same physical machine along with the DMGR.
-----> When the JVM failover happens other JVM in that cluster will handle the request as part of the High Availability.
-----> But when the physical machine failover happens we will lose every thing
2) HORIZONTAL CLUSTERING : Grouping of AppServers in which one AppServer should be on one node and Another AppServer should be on another node.
-----> Means if we take two machines one application should be deployed on different machines Remotely (or) one application should run in INDIA and another application should run in AMERICA.
-----> If Machine1 application will be deployed on Machine2 so we have to know the IP address of Machine1 then only it is possible to deployed that application Successfully.
----> Both Machines should have Internet Connection.
----> Here no SINGLE POINT OF FAILURE.
----> It Supports MACHINE FAILOVER.
(OR)
-----> DMGR and the JVMs resides on the different machines.This will work even when the physical machine failover is happened.
WORKLOADMANAGEMENT : Sharing requests across Multiple Servers.
SCALABILITY : can add 2/3 members or add a cluster member to existing member
LOADBALANCING : Allocate workload proportionality among available resources.
AVAILABILITY : System runs if server fails with Clustering. (or)
----> Applications are still available if a server fails.
Next Page : http://webspherelife.blogspot.com/2018/09/clustering-in-was-websphere-application.html
No comments:
Post a Comment