Testing the Sticky Sessions Configuration in Apache HTTP Server
Testing the Sticky Sessions Configuration in Apache HTTP Server
To test the sticky sessions configuration changes, start the Tomcat instances and the Apache HTTP server and follow the test procedure in this section.
Test the back-end machines. Go directly to the
Data Integration Hub
Operation Console on the back-end machines. Verify that the behavior in a clustered environment is the same as in a single-server environment. Verify that the login and logout are successful.
Repeat this step for each back-end machine.
Verify that the Balancer Manager works properly. Go to
http://host:80/balancer-manager
. This page shows the status of all the configured workers. After restarting Apache, it should show that all the workers are OK and that no data has been transmitted or received.
You can only perform this step if you enabled monitoring in the Apache HTTP Server configuration file.
Log in to the
Data Integration Hub
Operation Console 1. Go to
http://host:80/
dih
-console/
. The
Data Integration Hub
Operation Console login page should be displayed. Log in into the
Data Integration Hub
Operation Console.
Verify the sticky session. Go back to the balancer manager page at
http://host:80/balancer-manager.
This page should show that all the session requests have been forwarded to a single back-end machine.
Log in to the
Data Integration Hub
Operation Console 2. Go to
http://host:80/
dih
-console/
, using a different browser than before, and log in to the
Data Integration Hub
Operation Console.
Verify sticky session 2. Go back to the balancer manager page at
http://localhost:80/balancer-manager
. This page should show that all the session requests have been forwarded to the other back-end machine.
The following image shows the expected results in the Balancer Manager: