Skip to Main Content
Feature Request FR-2799
Product Area APIs
Status DELIVERED

9 Voters

Provide API to change(create) Remote Server entries

ilmarsk Public · Oct 14 2022

Currently, there is no API to work with Remote Server entries. There are several use cases where changes, particularly to the Base/Endpoint URL post-install, are needed.  One of them is to allow the end user to define a connection to the server for their instance.  Apex app is built with predefined rest sources & synchronizations, but URL will change based on the tenant. I.e. 3rd party app provides REST API where each tenant gets a unique URL (hostname, etc) with the same data structures for each tenant. 

Minimum desired behavior: 

APEX_REMOTE_SERVER.SET_SERVER(p_static_id, p_endpoint_url);

Apex forum questions are referenced below:

https://community.oracle.com/tech/developers/discussion/4480768/how-to-create-rest-enabled-sql-dynamically

https://community.oracle.com/tech/developers/discussion/4504757/how-to-change-the-remote-server-base-url-programmatically-api#latest

This has been delivered in Oracle APEX 24.2!

Comments

Comments

  • patrick wolf Admin OP 2.8 years ago

    Just for clarification, are you looking for an API to permanently update a Remote Server definition after installation (similar to apex_application_install.set_remote_server), or an API that temporarily changes the Remote Server for the current user session? This would especially be tricky in the REST synchronization feature which runs outside of the user context.

  • ilmarsk OP 2.7 years ago

    To satisfy the current use case the ability to permanently update a Remote Server definition with API after installation is all that is needed. Thank you.

  • jon dixon OP 1.1 years ago

    There is also a use case for this API when cloning instances. For example, if you clone PROD to DEV, you may need to update Remote Server URLs to point to the DEV equivalent of the REST API.

  • richard martens OP 9 months ago

    I upvoted..

    One of our clients has this "problem" / “challenge”: 180 sets of endpoints (each having roughly 20 endpoints)

    we solved as follows:

    • create an ORDS service that will act as a proxy
      you can add a parameter to that service to instruct the ORDS service where to get the source data (or where to POST,PATCH,DELETE)
    • the APEX application will only see the ORDS service. for APEX there is only one source
      ORDS will proxy all requests to the endpoints