Appendix C - Oracle Real Application Cluster (RAC) Support

Load balancing, multi-node Oracle RAC

• One Bridge per RAC node (instance). A CBS Bridge should be configured to connect directly to each node (instance).
• One CBS Server per scheduled site. The servers should be configured to connect to the database server using a load-balancing connection.
• The IFS Applications client should be configured to connect to the database server using a load-balancing connection
• Each Bridge should be installed in a separate installation directory to avoid overwriting configuration files.

For example, to install on a 2-node Oracle RAC, where the nodes are named IFS1 and IFS2 and the load-balancing connection is IFS, the CBS Installation program (setup.exe) would need to be launched a minimum of three times, twice to install the bridges and once for each scheduled site. Also during each execution of the CBS Installation program to install the Bridge, pick a different installation directory to avoid conflicts.

1. Create three TNS entries for oracle connections. One for IFS1, one for IFS2 and a load-balancing connection for IFS.

2. Install a Communications Bridge against IFS1.
3. Install a Communications Bridge against IFS2.
4. Install a Scheduling Server for each scheduled site against IFS.
5. Configure the IFS Windows Clients to connect to IFS.

Note: Refer to the Oracle Net Services Administrator’s Guide for instructions on configuring the direct and load-balancing connections.

High Availability (HA) with Fail-Over RAC

• At the time that this document was produced, HA was not a currently supported configuration. Current configuration status can be found at the IFS Applications - Product Certification pages.