Before
After
Assumptions
ORDS is installed as a service on Oracle Linux (You can run in standalone mode also)
ORDS is already configured and running
Oracle APEX application is available and accessible
You are using customer managed ORDS
ORDS is installed as a service on Oracle Linux (You can run in standalone mode also)
ORDS is already configured and running
Oracle APEX application is available and accessible
You are using customer managed ORDS
The One-Liner Solution
ords config set misc.defaultPage f?p=101:LOGIN_DESKTOP::::::
ords config set misc.defaultPage f?p=101:LOGIN_DESKTOP::::::
That's it. Restart ORDS and you're done. 101 is application ID
Breaking Down the Path
The format is: r/{workspace}/{app_alias}/{page_alias}
mtc = your workspace name
demo = your application alias
login = your landing page alias
Example
Let's say you want users to land directly on your sales dashboard:
sudo systemctl stop ords
sudo -iu oracle
ords config set misc.defaultPage f?p=101:LOGIN_DESKTOP::::::
exit
sudo systemctl start ords
Now when someone visits yourdomain.com
, they go straight to your dashboard instead of the default ORDS page. 101 is application id
Why This Works
ORDS has a built-in configuration parameter misc.defaultPage
that most people don't know about. Instead of setting up redirect rules elsewhere, you're just telling ORDS where to send users by default.
Quick Tips
Make sure your page alias exists and is published
Test in dev first
You need to restart ORDS for changes to take effect
Make sure your page alias exists and is published
Test in dev first
You need to restart ORDS for changes to take effect
That's the hack. Simple, clean, and no infrastructure changes needed.
Post a Comment
0Comments