In the recent past, we had to move from our old desupported load balancer to a newer certified version of load balancer in our ERP environment. The old desupported load balancer was Cisco Load Director. The new supported version is Cisco Content Switching Module.
Actually, we (DBAs) do not handle the configuration and setup of the load balancer. However, we are responsible to ensure that the load balanced ERP environment meets our requirements and the ERP environment is available to the users.
One of the "simple" requirements for CSM was that the Servers which would be defined as "Real Servers" in CSM needed to be in a specific VLAN segment. This would mean that the IP addresses for the real servers (in our case online servers - apache / forms) had to be changed. We started with this background and had to take care of the following steps to complete the migration successfully:
1. Change the IP address of the ERP Mid-tier servers.
2. Update the host DNS records to reflect the new IP.
3. Configure the CSM with our load balancing requirements.
4. Update the DNS records for the virtual URL for ERP.
5. Update Oracle Applications (fnd_nodes) with the new ip address information.
6. Update the firewall rules to allow access to the new IP addresses.
By the way, our load balancing requirements were very simple. We have three online mid-tier servers and we wanted the requests to be routed in a round robin fashion on Apache, Forms and Mobile Supply Chain Application ports. We also wanted buddy enabled between Apache and Forms. This will ensure that the apache and forms sessions from a same IP will be directed to the same mid-tier. Also, we wanted "sticky" to be at 60 minutes. This ensures that one IP address will stay on one midtier with an idle time of upto 60 minutes.
- Aravind Kamath
Subscribe to:
Post Comments (Atom)
Posts
No comments:
Post a Comment