Oracle Application Server : Load Balancer
Load Balancing is a technique used to spread work between many computers , processors , disks and other resouces in order to get optimal resource utilization and decreasing computing time.
Load Balancing technique are used across various application and system which are 24/7 to accomodate world wide access. Failure of one particular resource will not affect the availability of the system , Failover of the system will also not affect the availability of the system and moreover Failback of the system will be invisible to the end users when the Load Balancer techniques are well in place.
A Load Balancer is a virtual server which consists of virtual IP Address and Port , which internally talks to the other available real IP Address and Ports. Internal mapping make the Virtual IP Access to get load balanced towards the available resources.
Persistance in a concept where once a server is selected , subsequent request to the server from the client will not change and hit the same server. There are cases where sometimes an application need to maintain client state on a particular server , there are other possibilities on the Persistance usage with the Load Balancer , once such is that when the data is cached on a particular server and the requirement is that the client needs to get always hit the server which has been used previously to get connected. This internally boosts the performance of the server not getting the cache generated again. There are more features of Load Balancer which varies with the vendor
Scalability with the Load Balancer
When large internet based applications are considered they need to scale automatically based on the load. Most of the firewall algorithm supports the same. Some of them are Round Robin , Squid Cache Server , PHP Scripts and more.
What about Multiple Providers
When your internet application gets loaded and your provider is not able to hold the load , the application will fail finally. With the help of Load Balancer it is easy to configure Multiple Provider where it helps the application to be available with several provider where by keeping the system up and available 24/7.
It is the time configured which indicated the failure of the physical server to respond. The most common way to get the timeout monitored is by pinging or by checking the port is open and active.
Tested LoadBalancer: The following are the some of the tested firewall that are found to be working good with version 10.1.2 and 10.1.3.
More information follow the link as the above information differ in future.
Options ABANDON and RESTART adop phase=apply patches=10721639 abandon=yes Used to specify whether to restart the previous run of a...
FS_CLONE Phase It is a stand-alone command used for file system cloning. Standard cloning (using adcfgclone.pl) cannot be used to synch...
Abort Phase If for some reason either the prepare or apply phase failed or gave problems, you can abort the patching cycle. After runnin...
Scenario You have noticed that the on the patch edition there are lot of patches applied. You did the cutover and now customer wants t...
Cleanup Phase Drops now-redundant columns and other objects which are not required after the cutover phase. It is important that we do n...
Scenario You have been asked to apply a patch and you completed the prepare phase and apply phase. Now customer has given a downtime f...
Scenario You have been asked to apply a patch and you start with the first phase “PREPARE”. Background Customer has recently...
FMW 11g Upgrade Master Index After upgrading Discoverer and Portal to 11g logging on the portal or discoverer results in ORA-7445 in the ...
Ready the instance for cutover Perform the final operations like Compile Invalids , Generate Derived Objects and Pre-compute DDL to be run...
R12.2 Highlights This release is largely focused on providing new technology stack components, new configuration options, and new syst...