Introduction
Recently, our team migrated the server from an Oracle T8 to an M8 server. As a result, the Oracle APEX URL changed from:
https://test.com:8080/ords/apex
to:
https://test.com:8080/ords
This change impacted our application significantly, as the original URL was hardcoded in various parts. To prevent such issues in the future, we tested a solution in one of our UAT environments. This document provides a step-by-step guide on how we updated the URL mapping.
Step 1: Define the Target URL
In our UAT environment, the current URL is:
https://test.com:8080/ords
To maintain consistency in the URL structure, we aim to configure it to appear as:
https://test.com:8080/ords/apex
Step 2: Update the URL Mapping in url-mapping.xml
We adjusted the URL mapping file to include the desired path. The configuration changes include:
Pool Name: Set to the database name.
Base Path: Set to /apex. This can be adjusted based on specific requirements.
Configuration Steps
To configure the URL mapping, execute the following command:
java -jar clientinfo.war map-url –type base-path /apex mytestdb
Example Command
$JAVA_HOME/bin/java -jar ords.war map-url –type base-path /apex doyensysdb
After executing this command, the configuration in url-mapping.xml should look like:
<pool name=”testdb” base-path=”/apex”/>
Reference
For further details, refer to the official Oracle documentation:
How to Configure APEX Listener / Oracle REST Data Services (ORDS) 2.0 to Serve Multiple APEX Instances
Conclusion
By following the above steps, we successfully updated the URL mapping and ensured consistency across environments. Moving forward, we recommend avoiding hardcoding URLs in applications to prevent similar migration challenges.
