Glassfish JEE Server Administration - Module 4 Load Balancer

Module-4: Load Balancer Integration
1
Danairat T.
Line ID: Danairat
FB: Danairat Thanabodithammachari
+668-1559-1446

Contents
Module-4: Load Balancer Integration
• Creating HTTP Load Balancer
• Exporting loadbalancer.xml file from Glassfish Enterprise Server
• Installing Web Server and Load Balancer Plug-in
• Importing loadbalancer.xml file to Load Balancer Server
• Testing access Application from Load Balancer
• Reviewing Load Balancer http access log
• Monitoring Application Server Cluster
• Back up the Glassfish Domain, Load Balancer Clients, Clusters
configuration and Deployed Applications
• Reviewing Start All Servers Order
• Test deleting Load Balancer, Cluster, Instances and Restore
• Re-Testing the restored applications
• Reviewing Stop All Servers Order
2

The Architecture and Configuration Steps
3
app 01
- DAS
-Node Agent
“app01”
- Instance01
app 02
-Node Agent
“app02”
- Instance02
web 01 Session replication
Users
Load distribution
Load distribution
FirewallFirewall
request
LB Plug-in
Configuration Steps:-
• Creating HTTP Load Balancer
• Exporting loadbalancer.xml file from
Glassfish Enterprise Server
• Installing Web Server and Load
Balancer Plug-in
• Importing loadbalancer.xml file to
Load Balancer Server
• Testing access Application from
Load Balancer
• Reviewing Load Balancer http
access log
• Monitoring Application Server
Cluster
• Back up the Glassfish Domain,
Load Balancer Clients, Clusters
configuration and Deployed
Applications
• Reviewing Start All Servers Order
• Test deleting Load Balancer,
Cluster, Instances and Restore
• Re-Testing the restored applications
• Reviewing Stop All Servers Order

Creating HTTP Load Balancer
4
1. “HTTP Load Balancer” -> “New ”
2. Enter name “lb01” below details, click “OK”

Creating HTTP Load Balancer
5
3. Restart the instances by click “stop” -> “start”.

Exporting loadbalancer.xml file from Glassfish Enterprise Server
6
Click “Export Now ” from the “Export” tab menu in the “lb01”. Enter the file name as “loadbalance.xml”.
For this training, We will use this file to
import to load balance server (web01) later.

Installing Web Server and Load Balancer Plug-in
7
1. At machine “web01”, edit hosts file to be able to access “app01” and “app02”
2. Extract the .gz file to some directory

8
3. Run the “./setup” as below.

9
4. Follow the installation wizard created installed directory and select “custom”.

10
5. Select “Server Core”, “Administration Command Line”, “Sample Applications”.
6. Select install Java SE Development Kit (JDK) 1.5.0_15.
7. Select “Create an Admin Server,
Web Server Instance”

11
8. Enter the password. For this training, use “password”.

12
9. Click “Install Now”

13
10. Click “Finish” and review the installed directory.

14
11. Start Web admin server and instance server.
12. Test access at port 80

15
13. Monitor access log and error log at /sun/webserver7/https-web01/logs/

16
1. At web01 machine, start http “admin-server “and stop “https-web01” instance.
Installing The Glassfish Load Balancer Plugin for Sun WebServer

17
2. Run the setup file (using the same one as set up the Application Server)

18
3. Follow the installation and Create the installed directory.

19
4. Select only “Load Balancing Plugin”, “No Administration Tools”
5. Use existing JDK

20
6. Enter your web instance installed location
7. Enter web server admin’s password.

21
8. Follow the installation step and click “Finish”.

22
9. Review the Load Balancer Plugin installed location.

Importing loadbalancer.xml file to Load Balancer Server
23
1. Copy “loadbalancer.xml” which export from AppServer to /sun/webserver7/https-web01/config
2. (Re)start web server instance

Monitor the Load Balancer Server
24
Monitor the load balance health check status.

Testing access Application from Load Balancer
25
1. At app01 machine, start app01 DAS and node agent

26
2. At app02 machine, start app02 node agent

27
3. Test access the web application from web01 load balancer. Success!

28
4. Test add session data.

29
5. Test stop the instance which is now service to the user session.

30
6. Click “Reload Page”
7. The Load Balancer perform “Fail Over” to another machine instance. Success!
The User Session is
maintainable after “Fail Over”

31
8. Start all instances

32
9. Stop another instance to test Load Balance again

33
10. Monitor the Load Balancer Health Check at web01 machine /sun/webserver7/https-web01/logs/errors
The LB detected
the app01 is in
unHealthy state

34
11. Re-test, Click “Reload Page”
12. The Load Balancer performs “Fail Over” from
app01 to “app02”
The User Session is
maintainable after “Fail Over”

35
13. Start all instances to return the server in normal state.

36
The LB detected
that app01 is in
a healthy state

Reviewing Load Balancer http access log
37
You can monitor the LB access log at /sun/webserver7/https-web01/logs/access

Monitoring Application Server Cluster
38
1. From “cluster01” menu, you can click on each instance to see the status details

39
2. Review the Log. Testing the “Call Flow” monitoring by click “Enabled” and “Save”

40
3. Test access application via LB and see the “Call Flow” data details

41
4. Review the Monitor -> “Runtime status

42
5. Test “Generate Report” to see the cluster diagnostic data.

43
6. The result report can be viewed by Web Browser

44
7. The result report is also including the node agents details

45
8. The cluster Log configuration is separated from the default “Server” configuration
9. The “Availability Service” is enabled by default

46
10. Review the Web Container, EJB Container and JMS Availability.

47
11. You can see the “Listener Port” number from the cluster -> Instance or from “System Properties” menu

48
12. The “GMS” for cluster communication properties

49
13. The default port numbers for each available services

50
14. The JVM setting is subject to provide the Java Virtual Machine Optimization

Back up the Glassfish Domain, Load Balancer Clients, Clusters
51
1. At app01 machine, Stop node agent and DAS then run backup command.

Back up the Glassfish Domain, Load Balancer Clients, Clusters
52
2. Review the backup content details

Reviewing Start All Servers Order
53
1. At app01, Start DAS, node agent.

Reviewing Start All Servers Order
54
2. At app02, start node agent
3. Start Web Server which is now act as Load Balancer
4. Test access
application via
LB.

Test deleting Load Balancer, Cluster, Instances and Restore
55
1. Test deleting Load Balancer configuration 2. Continue deleting the Cluster.

Test deleting Load Balancer, Cluster, Instances and Restore
56
3. After delete cluster and Load Balancer from DAS and access application from http://web01,
The application will display “unavailable”

Re-Testing the restored applications
57
4. At app01, stop node agent and DAS 5. Restore from backup file

58
6. At app01, start DAS and node agent
7. At app02, start node
agent

59
8. Login to admin console and review all configuration were came back from the restore

60
9. The application is now back to service after done restore. Success

61
10. Test add session data to the web application which is located in “app01”

62
11. Test stop instance01 which is now service to user session.

63
12. The Load Balancer from “web01” detected the “app01” is in unhealthy state.
tail -f /sun/webserver7/https-web01/logs/errors

64
13. Click “Refresh Page” 14. Fail Over to “app02”. Success

65
15. Start all instances to be in normal state.

66
The LB detected
that app01 is in
a healthy state

Reviewing Stop All Servers Order
67
1. Stop Web Server 2. Stop node agent and app02 3. Stop node agent and DAS at app01

68
Danairat T.
Line ID: Danairat
FB: Danairat Thanabodithammachari
+668-1559-1446
Thank you

Glassfish JEE Server Administration - Module 4 Load Balancer

Recommended

More Related Content

What's hot (20)

Similar to Glassfish JEE Server Administration - Module 4 Load Balancer (20)

More from Danairat Thanabodithammachari (20)

Recently uploaded (20)

Glassfish JEE Server Administration - Module 4 Load Balancer