Kbase P19375: How to achieve load balancing with the AppServer?
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
27/10/2009 |
|
Status: Verified
GOAL:
How to achieve load balancing with the AppServer?
GOAL:
Load Balancing for AppServer
FACT(s) (Environment):
Progress 9.1x
All Supported Operating Systems
Progress 9.x
OpenEdge 10.x
FIX:
In order to achieve load balancing with the AppServer, the prerequisite
is having the "NameServer Load Balancing" license.
It is important to understand the way how Progress brokers registers
with the NameServer.
There are three main things to understand:
1. Broker name
2. Broker uuid
3. Broker supported AppService names
1. Broker name
This is the name that is used to identify the broker as
defined in the ubroker.properties e.g. "asbroker1". The only
important thing about this name is that it needs to be
unique within the ubroker.properties, that is within
the AdminServer instance.
2. Broker uuid
Second is the broker's uuid (Unique Universal IDentifier).
Using the Progress utility named 'genuuid' (generator for uuid)
you are guaranteed to obtain the unique ID valid at the time and
space within a single computer network. The algorithm
used is taking into account things as the hostname, tcpip address and
some other things that is explained in detail in our
Knowledge Center Solution 21175.
When you are using the Progress Explorer to create new broker
instances, this is done behind the curtains and automatically.
In the ubroker.properties you will see parameter 'uuid' for
every broker instance.
3. Broker supported AppService names
These are the names that the broker publishes when it registers
with the NameServer. All applications requesting the certain
AppService from the NameServer will obtain the information
about host and port where the broker supporting this AppService
is running. That means that in the 4GL application is actually
specified the AppService name and not the broker name.
The fact that you get automatically AppService name that is
the same as the broker name might be confusing. That means
that your broker named 'asbroker1' can also support Appservice
named 'asbroker1', but it also means that your new broker named
'MyBroker' can support AppServices named 'asbroker1,inventory,application1'.
Finally, when the NameServer with the Load Balancing is installed,
what really matters is that the license has been installed on the
machine where the NameServer will be running and
that all brokers registering with that NameServer have different
uuid regardless of their broker name or AppService names.
The uuid used to register with the NameServer is what counts.
Therefore, one can have 5 servers each running AppServer broker
named 'asbroker1' and each supporting AppService 'asbroker1'
as long as they have different uuid.
Configuring the weight factor for each AppServer is explained
in more detail in the Solution P5666.