Skip to Main Content

ORDS, SODA & JSON in the Database

Announcement

For appeals, questions and feedback about Oracle Forums, please email oracle-forums-moderators_us@oracle.com. Technical questions should be asked in the appropriate category. Thank you!

Interested in getting your voice heard by members of the Developer Marketing team at Oracle? Check out this post for AppDev or this post for AI focus group information.

ORDS Upgrade from 20.2 to 24.4 - Help

uservaDec 28 2024 — edited Dec 29 2024

We have installed ORDS 20.2.1.r2270350 deployed it on weblogic 12c installed on a Windows server and enabled the oauth2 authentication in year 2020. We have multiple clients registered and more than 25 endpoints.

Current Setup:

Server: Windows

Application Server: Weblogic 12.2.1.4.0

DB Version: Oracle Database 19c Enterprise Edition Release 19.0.0.0.0

ORDS Version: 20.2.1.r2270350

Java Version: 1.8

Renamed ords.war file before installation to data-api.war to change the base URI. Below is my sample endpoint url named people

“https://xxxx.yyyy.net:9002/data-api/pm/data/people”

As the support for our current version ends in Dec 2024, we have started an analysis to upgrade the ORDS software to 24.4 and this is the first time we are doing the ORDS upgrade. After initial analysis, i see there are many enhancements since 22.2 and the upgrade approach has also changed as the legacy commands no longer work.

I have gone through the below articles

Oracle REST Data Services version 22.1: Read the README!

ORDS 22.1.1 – Upgrading using the new CLI and Installer

ORDS Standalone 22.x – Don’t rename ORDS.war

Migration of Legacy Configuration

I am a bit confused, about the final approach on the upgrade from 20.2 to 24.4 as we have renamed the war file in our initial setup.

Can i blindly just use the below approach and commands to proceed with my upgrade, i just want to make sure all my existing registered clients and endpoints work as is.

  1. Stop all the Managed Servers in Weblogic.
  2. Existing ORDS Directory (D:\Middleware\ORDSDEV) & Config Directory (D:\Middleware\ORDSDEV\config) & war file name is data-api.war which is deployed on weblogic.
  3. Install JDK 23, as 1.8 is no longer supported by latest version of ORDS.
  4. Copy the latest ords software unzipped to a folder on the server say example software.
  5. Go to the Software folder (D:\software) and rename ords.war to data-api.war to match my old war file name.
  6. Navigate to the Bin folder under the software folder (D: software/bin) and use the below commands.

Set Config (to use existing 20.2 config path) & Install

D:\software\bin> ords --config D:\Middleware\ORDSDEV\bin install

Select Option 1 to Upgrade

how does the upgrade command know it has to upgrade my existing installation war file data-api.war using the new software & war, as i do not specify which war file to upgrade from except my old conifg path also we renamed war file from ords.war to data-api.war?

I see some steps in the documentation asking us to use the below command to migrate the config and upgrade from legacy to the latest. When to use this approach

ords --config <configuration_folder> install --interactive --legacy-config legacy_config_folder> --log-folder <log_folder>

Could someone please guide me on how I can proceed with the upgrade? My objective is to do an in-place upgrade of ORDS from 20.2 to 24.4 without recreating the clients & endpoints again.

Comments

thatJeffSmith-Oracle Feb 13 2025

Your ENTRA users will get authenticated via JSON Web Tokens, and their Entra roles will determine which ORDS REST APIs they can hit.

When they hit an endpoint, it'll execute code in the database as the database user that owns the schema where the REST API is defined, not as Entra defiend end user. In fact, the Entra users won't have accounts in the database (they could, but wont' need to).

The :current_user field as far as ords is concerned would be the corresponding oauth2 client or JWT issued for the authorizied session.

Your prehook should be able to alter the session to set the context that would put your RLS/VPD security policy in play.

1 - 1

Post Details

Added on Dec 28 2024
19 comments
746 views