Q) What is work load manager in WebSphere? What is the default work load management policy?
A) ----> Workload management (WLM) is a WebSphere facility that provides load balancing and affinity between application servers in a WebSphere clustered environment.
----> WLM is an important fact of performance. WebSphere uses workload management to send requests to alternate members of the cluster.
----> WebSphere can also be configured to route concurrent requests from a user to the application server that serviced the first request. This is called session affinity and can be used to maintain a users session over concurrent HTTP requests.
----> WLM is configurable. The administrator should ensure that each machine or server in the configuration processes share the overall client load that is being processed by the system as a whole.
----> Workload should be spread among machines such that the workload corresponds to the machine processing power.
Q) What is High Availablity in WebSphere?
A) ----> High Availability means nothing but clustering concept .
----->Application should be live for the 365 day for those kind of application they kept in cluster. When the request comes from client it should handle. this concept is called as high availablity
(0R)
-----> Application availability for the users who are using it.
------> We can provide the high availability by installing the application in different cluster members.
-----> In case one of the Application Servers fails other Application server which is in the cluster group will server the request so then the customer request can served quickly.
VERTICAL CLUSTER CONFIGURATION :
STEP 1: Goto Cluster.
STEP2 : Click New.
STEP3: Give Cluster Name.
STEP4 : Prefer LOCAL (By default enable)
STEP5 : Click Next Button.
STEP6: Add Cluster Member 1
STEP7 : Weight (2 Members ---> Equivalent weight)
STEP8 : Add Cluster Member2
STEP9 : Generate unique HTTP ports.
STEP10 : Click Finish Button.
STEP11 : Select Scope.
STEP12 : Controlling Cluster.
STEP13 : Start Cluster Member1
STEP14 : Start Cluster Member2
STEP15 : LogOut from AdminConsole.
STEP16 : Again LogIn to AdminConsole.
STEP17 : See in AdminConsole both Clusters are started.
(or)
STEP BY STEP FOR CREATING CLUSTERS.
STEP 1 : ND - None Installation.
STEP 2 : Create 3 profiles DMGR , APPSRV1 , CUSTOM.
STEP 3 : Federation (APPSRV1 , CUSTOM) ------> DMGR.
STEP 4 : IHS (WEB SERVER + PLUG-IN )
STEP 5 : Map Web Server Instance in DMGR.
STEP 6 : Cluster Creation (Node A) ----> SRV 2
(Node B) -----> SRV 1
STEP 7 : Deployed Application under Cluster or Web Server Scope
STEP 8 : Ensure PLUG-IN Generation and Propogation.
STEP 9 : Restarts (SERVER 1 , SERVER 2 , WEB SERVER)
A) ----> Workload management (WLM) is a WebSphere facility that provides load balancing and affinity between application servers in a WebSphere clustered environment.
----> WLM is an important fact of performance. WebSphere uses workload management to send requests to alternate members of the cluster.
----> WebSphere can also be configured to route concurrent requests from a user to the application server that serviced the first request. This is called session affinity and can be used to maintain a users session over concurrent HTTP requests.
----> WLM is configurable. The administrator should ensure that each machine or server in the configuration processes share the overall client load that is being processed by the system as a whole.
----> Workload should be spread among machines such that the workload corresponds to the machine processing power.
Q) What is High Availablity in WebSphere?
A) ----> High Availability means nothing but clustering concept .
----->Application should be live for the 365 day for those kind of application they kept in cluster. When the request comes from client it should handle. this concept is called as high availablity
(0R)
-----> Application availability for the users who are using it.
------> We can provide the high availability by installing the application in different cluster members.
-----> In case one of the Application Servers fails other Application server which is in the cluster group will server the request so then the customer request can served quickly.
VERTICAL CLUSTER CONFIGURATION :
STEP 1: Goto Cluster.
STEP2 : Click New.
STEP3: Give Cluster Name.
STEP4 : Prefer LOCAL (By default enable)
STEP5 : Click Next Button.
STEP6: Add Cluster Member 1
STEP7 : Weight (2 Members ---> Equivalent weight)
STEP8 : Add Cluster Member2
STEP9 : Generate unique HTTP ports.
STEP10 : Click Finish Button.
STEP11 : Select Scope.
STEP12 : Controlling Cluster.
STEP13 : Start Cluster Member1
STEP14 : Start Cluster Member2
STEP15 : LogOut from AdminConsole.
STEP16 : Again LogIn to AdminConsole.
STEP17 : See in AdminConsole both Clusters are started.
(or)
STEP BY STEP FOR CREATING CLUSTERS.
STEP 1 : ND - None Installation.
STEP 2 : Create 3 profiles DMGR , APPSRV1 , CUSTOM.
STEP 3 : Federation (APPSRV1 , CUSTOM) ------> DMGR.
STEP 4 : IHS (WEB SERVER + PLUG-IN )
STEP 5 : Map Web Server Instance in DMGR.
STEP 6 : Cluster Creation (Node A) ----> SRV 2
(Node B) -----> SRV 1
STEP 7 : Deployed Application under Cluster or Web Server Scope
STEP 8 : Ensure PLUG-IN Generation and Propogation.
STEP 9 : Restarts (SERVER 1 , SERVER 2 , WEB SERVER)
No comments:
Post a Comment