Oracle Analytics Cloud and Server

Welcome to the Oracle Analytics Community: Please complete your User Profile and upload your Profile Picture

OAS 2024 (7.6): Unable To Establish A Connection With REST API Connector

Accepted answer
241
Views
21
Comments
2

Answers

  • Dhaval Parikh Stantec
    Dhaval Parikh Stantec Rank 5 - Community Champion

    @Gianni Ceresa Tried importing the JSON file too but its throwing an error. Below is the screenshot :

    Yes, I did customize the template I downloaded. Currently I am just using my SSO as basic auth. I am not sure though if I am using all the right info. I tried replacing the info in the template to best of my knowledge. It throws an error saying one of the endpoint's URL is invalid (same as the above error message). I will have to dig more.

  • Dhaval Parikh Stantec
    Dhaval Parikh Stantec Rank 5 - Community Champion

    @SteveF-Oracle I will check with my DBAs and revert. Thanks!

  • Remove the final / in the base URL, and add the / before the relative URL of the endpoint. Actually, in your JSON file the endpoint is a full URL, not just a relative one (the GUI shows the relative one), therefore you maybe just need to remove the / in the base URL.

    This is for the test API (I tested with a file 25 minutes ago in a probably unpatched OAS 2024, can't be sure about that as it's an Oracle managed instance).

  • Dhaval Parikh Stantec
    Dhaval Parikh Stantec Rank 5 - Community Champion

    @Gianni Ceresa My json file doesn't have a / in base URL but somehow when I import it automatically adds it. Are you suggesting I manually make the changes after importing?

  • Gianni Ceresa
    edited September 5

    (Sorry for the not-fully-complete replies, let's blame 11:30pm :D )

    I tried again with a file (the forum add new lines everywhere, I don't have any empty new line in my file):

    {
    "name": "Test 002",
    "description": "Testing...",
    "baseURL": "https://api.restful-api.dev",
    "endpoints": {
    "objects": "https://api.restful-api.dev/objects"
    },
    "authentication": {
    "type": "noauth"
    }
    }

    Saved it as OAS_rest.json, zipped into OAS_rest.zip.

    I thought the / was an issue, but it isn't…
    This is the connection after importing the file. I clicked save, and it just saved it.

    The connection is saved just fine and works.

    As said I don't know the patching status of that OAS instance, it is labeled "OAS March 2024", and AFAIK it isn't an instance that is not patched: it's installed when OAS is released and it stays like that till the year after.

  • Dhaval Parikh Stantec
    Dhaval Parikh Stantec Rank 5 - Community Champion

    @Gianni Ceresa I copied the exact details from above JSON file you shared and it still gives me an error. Looks like a patching issue @SteveF-Oracle was alluding to

  • SteveF-Oracle
    edited September 5
    $ opatch lspatches
    36823918;OAS STACK PATCH BUNDLE 7.6.0.0.240710 (Patch 36823847)
    36814917;OAS BUNDLE PATCH 7.6.0.0.240708
    36805124;WLS PATCH SET UPDATE 12.2.1.4.240704
    36770738;FMW Thirdparty Bundle Patch 12.2.1.4.240625
    36769312;OWSM BUNDLE PATCH 12.2.1.4.240625
    36741053;WebCenter Core Bundle Patch 12.2.1.4.240617
    36706228;OSS 19C BUNDLE PATCH 12.2.1.4.240606
    36700543;ADF BUNDLE PATCH 12.2.1.4.240605
    36649916;One-off
    36553894;RDA release 24.3-2024716 for OFM 12.2.1.4 SPB
    36392269;DATABASE RELEASE UPDATE 19.23.0.0.0 FOR FMW DBCLIENT (36392269)
    36316422;OPSS Bundle Patch 12.2.1.4.240220
    1221422;Coherence Cumulative Patch 12.2.1.4.22
    36485914;WLS STACK PATCH BUNDLE 12.2.1.4.240405 (Patch 36485713)
    34542329;One-off
    34809489;One-off
    35965629;ADR FOR WEBLOGIC SERVER 12.2.1.4.0 CPU JAN 2024
    33093748;One-off
    35065206;One-off
    31032676;One-off
    30657796;One-off

    I reproduced the UI bugginess with the July 2024 bundle patch applied, so it is not fixed by a published patch.

    I tested also in OAC (September 2024 update), the connection was created fine. It did appear that there were two endpoints, but after saving, and upon inspection, there was only one endpoint.

    That tells me there have been some fixes/improvements that may need to be back ported to OAS.

    I am happy to file a bug/defect, but it is better if there is a service request.

    @Dhaval Parikh Stantec - If you could file one, then post back, that will help with follow-up.

    Attaching a short .mp4 video to the SR is also helpful and referencing this community URL.

  • Dhaval Parikh Stantec
    Dhaval Parikh Stantec Rank 5 - Community Champion

    @SteveF-Oracle

    Could you please file a bug/defect for this issue? That would help it gain more visibility and potentially increase its priority. I would have done it but I don't want to mention anything in SR that would confuse things further

  • Dhaval Parikh Stantec
    Dhaval Parikh Stantec Rank 5 - Community Champion

    @Gianni Ceresa

    That is very likely the case. I will check with my DBAs and Networks team to confirm. Thanks for your help, as always!