Configure the Site Selector component in production environments
and realistic test environments.
About this task
Use this configuration method for a quick way to establish
a connection between servers and the CBR machine.
Review the new features section for what's been
added and improved in this release.
Procedure
- Prepare the servers
- For this example, set up your workstations on the same
LAN segment. Ensure that network traffic between the three machines
does not have to pass through any routers or bridges.
- Configure the network adapters of the three workstations.
This example assumes you have the following network configuration:
Workstation |
Name |
IP Address |
1 |
server1.mywebsite.com |
9.27.27.101 |
2 |
server2.mywebsite.com |
9.27.27.102 |
3 |
server3.mywebsite.com |
9.27.27.103 |
Netmask
= 255.255.255.0 |
Each of the workstations contains only one standard Ethernet
network interface card.
- Ensure that server1.mywebsite.com can ping both server2.mywebsite.com
and server3.mywebsite.com.
- Ensure that server2.mywebsite.com and server3.mywebsite.com
can ping server1.mywebsite.com.
- Ensure that Web servers on server2.mywebsite.com and
server3.mywebsite.com are operational. Use a Web browser to request
pages directly from http://server2.mywebsite.com (for example,
.../member/index.html) and http://server3.mywebsite.com (for
example, .../guest/index.html).
- Obtain another valid IP address for this LAN segment.
This is the cluster address you will provide to clients who wish
to access your site. For example: Name= www.mywebsite.com IP=9.27.27.104
- Configure Site Selector with the command line
- Start the ssserver from the <install_root>/ss/servers/bin directory.
Run the following command as root user or Administrator: ssserver
Attention: Start cbrserver (Content
Based Routing) from the Services panel as follows: Start
> Control Panel > Administrative Tools > Services.
- Start the name server on the Site Selector configuration: sscontrol
nameserver start
- Configure the site names (marketing.apps.mywebshop.com
and developer.apps.mywebshop.com) on Site Selector: sscontrol
sitename add marketing.apps.mywebshop.com and sscontrol
sitename add developer.apps.mywebshop.com
- Add the servers to the Site Selector configuration.
(Configure server1 and server2 to site name marketing.apps.mywebshop.com.
Configure server3 and server4 to site name developer.apps.myeebshop.com): sscontrol
server add marketing.apps.mywebshop.com:server1+server2 and sscontrol
server add developer.apps.mywebshop.com:server3+server4
- Start the manager function of Site Selector: sscontrol
manager start
- Start the advisor function of Site Selector (HTTP advisor
for marketing.apps.mywebshop.com and FTP advisor for developer.apps.mywebshop): sscontrol
advisor start http marketing.apps.mywebshop.com@80 and sscontrol
advisor start ftp developer.apps.mywebshop.com@21 Site Selector will now make sure that client requests
are not sent to a failed server.
- Ensure the Metric Server has been started on each of
the load-balanced servers.
Results
Your basic Site Selector configuration is now complete. Test
to see if the configuration is working:
- From a client, that has a primary DNS configured as the nameserver
responsible for mywebshop.com, try to ping one of the configured site
names.
- Connect to the application. For example:
- Open a browser, request marketing.apps.mywebshop.com and a valid
page should be served
- Open an FTP client to developer.apps.mywebshop.com and enter a
valid user and password
- Look at the results of the following command:
sscontrol
server status marketing.apps.mywebshop.com:
sscontrol
server status developer.apps.mywebshop.com:
The total hits
entry of each server should add up to the ping and application request