Skip to main content

HAPROXY as the Reverse Proxy and usage with EBS/Oracle Apps

HAPROXY as the Reverse Proxy and usage with EBS/Oracle Apps


HAProxy is a free, very fast, and reliable solution offering high availability, load balancing, and proxying for TCP and HTTP-based applications. It is particularly suited for very high traffic websites and powers quite a number of the world's most visited ones.


Benefits of Reverse Proxy

  • Load Balancing
  • Web Caching
  • Improved performance
  • Clients never know where is Server
  • More Efficient and Secure SSL encryption


Integration with Oracle EBS

  • TLS Termination point in front of the Oracle EBS.
  • Up-to-date TLS endpoint 
  • Certificates signed with SHA-2 (signature algorithm: sha256WithRSAEncryption)
  • TLS 1.2 with stronger cipher suites
  • Can be implemented on same node as application Node
  • TLS 1.0, TLS 1.1, TLS 1.2 supported
  • Works with both Self signed and CA certificates.


HAProxy can provide an up-to-date TLS endpoint with the following configuration options:
Certificates signed with SHA-2 (signature algorithm: sha256WithRSAEncryption)
TLS 1.2 with stronger cipher suites



















Who Can Use

While HAProxy is a capable proxy and a load balancer, If you are using Oracle Linux 6 (or Red Hat), you can simply install the OS-provided RPM package. If you are using AIX or Solaris, it is possible to download the HAProxy source code and compile it for that operating system (remember to configure HAProxy for SSL/TLS). Windows and HP-UX are not currently supported by the build system supplied with HAProxy.
In the case that you cannot or prefer not to run HAProxy on the same host as OHS 10g, you can run HAProxy on a different host with a supported operating system. For example, you can run HAProxy on Linux on real hardware or in a virtual machine.





If you like please follow and comment

Comments

Popular posts from this blog

WebLogic migration to OCI using WDT tool

WebLogic migration to OCI using WDT tool Oracle WebLogic Deploy Tool (WDT) is an open-source project designed to simplify and streamline the management of Oracle WebLogic Server domains. With WDT, you can export configuration and application files from one WebLogic Server domain and import them into another, making it a highly effective tool for tasks like migrating on-premises WebLogic configurations to Oracle Cloud. This blog outlines a detailed step-by-step process for using WDT to migrate WebLogic resources and configurations. Supported WLS versions Why Use WDT for Migration? When moving Oracle WebLogic resources from an on-premises environment to Oracle Cloud (or another WebLogic Server), WDT provides an efficient and reliable approach to: Discover and export domain configurations and application binaries. Create reusable models and archives for deployment in a target domain. Key Pre-Requisites Source System: An Oracle WebLogic Server with pre-configured resources such as: Applica...

How to Validate TDE Wallet Password in Oracle Database

How to Validate TDE Wallet Password in Oracle Database Validating the Transparent Data Encryption (TDE) wallet password is crucial, especially when ensuring that the password is correct without using the OPEN or CLOSE commands in the database. This blog post explains a straightforward method to validate the TDE password using the mkstore utility. Steps to Validate TDE Wallet Password Follow these steps to validate the TDE wallet password: Step 1: Copy the Keystore/Wallet File Navigate to your existing TDE wallet directory. Copy only the ewallet.p12 file to a new directory. If a cwallet.sso file exists, do not copy it . The absence of cwallet.sso ensures that the wallet does not use auto-login, forcing the utility to prompt for the password. Step 2: Validate Using mkstore Use the mkstore utility to check the contents of the wallet file. The mkstore utility will prompt you for the TDE wallet password, allowing you to validate its correctness. Command Syntax To display the conten...

Rename a PDB in Oracle Database Multitenant Architecture in TDE and Non TDE Environment

Rename a PDB in Oracle Database Multitenant Architecture I am sharing a step-by-step guide to help you rename a PDB. This approach uses SQL commands. Without TDE or encryption Wallet Initial Check Check the Current Database Name and Open Mode: SQL > SELECT NAME, OPEN_MODE FROM V$DATABASE; NAME OPEN_MODE --------- -------------------- BEECDB READ WRITE List Current PDBs: SQL > SHOW PDBS; CON_ID CON_NAME OPEN MODE RESTRICTED ---------- ------------------------------ ---------- ---------- 2 PDB$SEED READ ONLY NO 3 FUAT READ WRITE NO We need to RENAME FUAT to BEE  Steps to Rename the PDB Step 1: Export ORACLE_SID Set the Oracle SID to the Container Database (CDB): export ORACLE_SID=BEECDB Step 2: Verify Target PDB Name Availability If the target PDB name is different from the current PDB name, ensure no service exists with the target PDB name. Run SQL to Check Exi...