A while ago I posted a guide how to set up nginx as a reverse proxy in front of tomcat to run ORDS and APEX. See the post here.
An open problem was that APEX was still thinking it runs on port 80 with http, while nginx was running https on port 443.
Just recently I talked about changing the /ords URL to something else, now I want to show another way to manipulate the URL.
I always disliked deploying multiple ORDS instances, just to provide different paths to the same DB. This happened out of legacy or SEO purposes so far.
Now let’s set up a simple reverse proxy to achieve any URL structure you want for your APEX server.
Usually ORDS is deployed on Tomcat simply as /ords, right?
What do you do, if you want a different name than ords, let’s say you would like to see “bruce” in the URL? Simple solution: just rename ords.war to bruce.war before deploying to Tomcat.
But what if you want to have “mod/plsql“, as in http://myserver.tld:8080/mod/plsql ?
On a recent installation we had problems serving APEX static files (application and workspace), they would always report a 404 not found back from ORDS.
Recently we held the very first edition of the “APEX Alpe Adria” conference in Graz, Austria (see this old post about how it started). This conference is meant for everyone in the Adriatic Region, and everyone willing to travel there.
With more than 180 attendees it was a huge success for the first edition. Today I want to share how we managed the conference, website, call for papers, selection, name tags, and so on.
Hint: With Oracle APEX you can do just about everything.
We recently upgraded a Web server from Oracle REST Data Services 2.10 to the latest version 17.4.1 . This might sound like jumping from the stone age to spaceships, but there have been only roughly 3 years between those two versions.
The good news is, ORDS ran fantastically stable for so long, and would have continued to do so even longer, but we wanted to use the latest and greatest features, hence the decision to upgrade.