How to Use Oracle HTTP Server as a Reverse Proxy for RDC or the TMS Browser Release 5.0.x and 5.1.x
(Doc ID 2016298.1)
Last updated on SEPTEMBER 27, 2021
Applies to:Oracle Clinical Remote Data Capture Option - Version 5.0.1 to 5.1.0 [Release 5.0.0 to 5.1]
Oracle Thesaurus Management System - Version 5.0.1 to 5.1.0 [Release 5.0 to 5.1]
Information in this document applies to any platform.
When you set up the Oracle HTTP Server (OHS) on a separate machine from the Oracle Clinical Remote Data Capture (RDC) application server, it becomes a reverse proxy server. Users access RDC through their browser, using a URL containing the host name and port number of OHS instead of the WebLogic Server.
Note: This document is written for RDC, but the same instructions apply for the Oracle Thesaurus Management System’s TMS Browser component.
This has two primary benefits:
- It provides an additional layer of security between the user and the application tier. OHS is installed in the "Demilitarized Zone" (DMZ) where it buffers the RDC application tier from direct internet contact.
- When there are multiple WebLogic Servers, an OHS reverse proxy server acts as a load balancer.
You can configure OHS to forward requests to either one WebLogic Server or to multiple WebLogic Servers. Multiple WebLogic Servers can be in a WebLogic Cluster or they can be independent servers. They can be on the same machine or multiple machines. The transmission of requests from the OHS reverse proxy server to the WebLogic Server(s) can be completed using either HTTP or HTTPS protocol.
This note is for Releases 5.0.1 and 5.1.0.
For the 5.2.x release see: How to Use Oracle HTTP Server as a Reverse Proxy for RDC / TMS Browser 5.2.x (Doc ID 2598776.1)
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!