hello
yes it is possible to do the load balancing in
orion
i am attching one html file just go through
if.
In case u want more help just reply
me.
bye
sachin
- Original Message -
From:
Mahesh M
Kagalkar
To: Orion-Interest
Sent: Friday, February 01, 2002 8:01
PM
Subject: Load balancing
Dear Sir,
Currently Iam working in a project which is using
Orion server.This is for the first time Iam using this server.Can you please
tell me how to do load balancing in Orion?Is load balancing
possible in Orion?
Waiting for your reply..
regds
Mahesh K
~~~Mahesh M
KagalkarIonidea Enterprise Solutions pvt ltd.38-40, Export
PromotionIndustrialPark, Whitefield,Bangalore-560 066Voice :
8411366-71Fax : 8411391E-mail : [EMAIL PROTECTED]
[EMAIL PROTECTED]
[EMAIL PROTECTED]~~~
Title: Orion HTTP Clustering
Orion HTTP Clustering and Load Distribution
$Revision: 1.0 $
This document will show you how to set up HTTP
Clustering and Load Distribution using the Orion application server.
Note:
This article assumes that you are familiar with
how to use Orion.
Introduction
Before you start, make sure you have downloaded and installed the following
software on at least 2 servers:
Java Development Kit (1.2 or later)
Orion (1.3.5 or later)
You also need a network with operational multicast facilities.
If you don't have access to 2 servers but want to test this, you can install
2 Orions on the same box and make sure that they are not using the same ports
for the RMI server and for the HTTP server.
This article has the following sections:
Introduction
Introduction to clustering
State replication
Cluster islands
Load distribution
Setting up a load distributed cluster with Orion
Step 1: Install your web-application on all the Orions
in your cluster
Step 2: Set up your web-application to replicate its state
Step 3: Configure your cluster islands
Step 4: Tell the back-ends about the load balancer
Step 5: Starting and using the load balancer
Step 6: Start the back-ends
Step 7: Test it
To do
If you already know about clustering and load distribution in
general and just want to know the steps to set it up for Orion,
you may skip to Setting up a load distributed
cluster with Orion.
Introduction to clustering
For at least two reasons you often want your web site to be served by more
than one web server:
Fault tolerance
Handling larger loads than one server can survive
The act of letting two individual servers work together to perform one task
is often referred to as clustering. Clustering is an essential piece
to solving the needs for today's large websites.
State replication
Originally, HTTP was designed as a stateless protocol. Every request had all
the info the server needed to perform a certain task. Doing clustering for a
stateless system is trivial and only requires that a request can be handled
by more than one server that share the same document hierarchy. In today's world,
the picture is not as simple. The need for user sessions with data stored on
the server about a specific website user resulted in the invention of the HTTP
cookie. A cookie is a way for a web server to store data in the web browser.
This cookie is passed back to the server on later requests. This is often used
to associate some data on the server (state) with a specific user. A
typical example is that of a webshop shopping cart. The user adds the goods
he wish to purchase to the cart and the server associates the user's cookie
with a certain cart stored on the server.
As you might have guessed this means that clustering gets somewhat more complex.
It is no longer enough that the document hierarchy is shared between the web
servers, but now the state stored on a server will mean that requests sent to
different servers will result in different results. Somehow we need to solve
that. There are two obvious solutions to the problem:
When a web site user has any state on the server associated with him, make
sure that he always get directed to the server which holds his state. If the
server can no longer respond, for any reason, let him log in again to a new
server.
Replicate all state on a server to at least one other server. Make
sure the user gets send to a server that holds his state. If his
original
