404 Not Found, Implement Mapping for a new apex instance
(Doc ID 2253537.1)
Last updated on APRIL 17, 2023
Applies to:
Oracle REST Data Services - Version 3.0 and laterInformation in this document applies to any platform.
*** Check for relevance on Jul-22-2019 ***
Symptoms
ORDS 3.0.x has been deployed in Glassfish 4.x for APEX in database 12.1.0.2/
Apex 5.X with ORDS 3.0.2+ Glassfish 4.X
All runs successfully with the default configuration:
http://<HOSTNAME>:<PORT>/ords/
URL mapping was then configured using the following steps:
STEP:1 - Configure the new database:
Have followed ORDS configuration document: https://docs.oracle.com/database/ords-17/AELIG/configuring-REST-data-services.htm#AELIG7211 => Configuring Additional Databases
Changes
Adding a new mapping to a working ORDS configuration currently accessing another apex instance (same version, same virtual image name)
Cause
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
Symptoms |
Changes |
Cause |
Solution |
References |