Skip to Main Content

Application Development Software

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.

Jdeveloper 12.2.1.4: The target index.jsp cannot be started because it is not a runnable target.

James ArmstrongAug 12 2024 — edited Aug 12 2024

Hi,

I have a legacy app that I have migrated from Jdeveloper 11G to 12.2.1.4 using the “-migration” switch. I have built the app both on the command line using maven 3.2.5 as well as (after adding a couple of libraries) using maven bundled in Jdeveloper 12c.

I am trying to deploy this application to the integrated weblogic server and getting the error:

The target index.jsp cannot be started because it is not a runnable target.

This deployed in 11G.

What do I do to correct jdeveloper to use this index.jsp page as a runnable target. What are the criteria that Jdeveloper 12.2.1.4 is using to assess that index.jsp is NOT a runnable target.

Any advice is helpful,

Thanks,

James

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 Aug 12 2024
1 comment
165 views