How to configure 'Load Balancing' Across Different Reports Servers in an Oracle Clinical / RDC Onsite 4.6.x Environment. (Doc ID 1310771.1)

Last updated on SEPTEMBER 22, 2022

Applies to:

Oracle Clinical - Version 4.6.0 and later
Information in this document applies to any platform.

Goal

The purpose of this note is to provide details on the 'Application Server Level' configuration required that will ensure any reports based jobs are submitted to the Reports Server that resides on the combined OC/RDC 4.6 Application Server which the user is connected to. This brings about a kind of 'Load Balancing' where reports jobs are executed locally on the OC/RDC 4.6.x Application server users are connected to.

For example :
User 'A' > connects to OC/RDC 4.6 Server 'A' > Reports Job will run on Server 'A'.
User 'B' > connects to OC/RDC 4.6 Server 'B' > Reports Job will run on Server 'B'.

Note : this setup will also work on the OC 4.6.2 release. For OC release 5.x then please see the following note : How to configure 'Load Balancing' Across Different Reports Servers in an Oracle Clinical / RDC Onsite 5.x Environment. (Doc ID 2301876.1)

Solution

	To view full details, sign in with your My Oracle Support account.
	Don't have a My Oracle Support account? Click to get started!

In this Document

Goal

Solution

References

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.

How to configure 'Load Balancing' Across Different Reports Servers in an Oracle Clinical / RDC Onsite 4.6.x Environment. (Doc ID 1310771.1)

Applies to:

Goal

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!