Hi,
I apologize in advance for opening a new question although I see similar ones already opened:
The thing is, in none of those threads I could find a valid resolution for the issue. As for the others, the issue occurs after executing correctly the following steps:
1) Create the open connector instance
2) Create the API provider
3) Create the API
and basically consists in a failed test to the channel resource (See screenshot below)
As already pointed out in linked threads I'm receiving an 404 error when testing the connectivity to the provider. Error that I'm ignoring as suggested as the endpoint looks to be reachable anyway.
I tried now repeating the config multiple times and waiting for some time for it to adjust by itself, but unfortunately it's not working and would like assistance in solving the issue.
Thanks,
BR
Answers (3)
There might be an system unavailability. Please validate this as follow.
Click under Design APIs on your configured API URL
After you opened the browser, activate the Developer Tools of your browser.
You should be able to see the HTTP Error.
Hi,
When I click on the path provided by the deployed API, I indeed get an error:
The error however is not a 404 but a 502 one (this has been the case also for my previous subaccount):
https://95792d12trial-trial.integrationsuitetrial-apim.us10.hana.ondemand.com/95792d12trial/v2/Slack
Thanks,
BR
Hi, it looks something went wrong with your credentials for the API provider.
Solutions:
1. Please set up your API provider again with the correct credentials
2. After you set up the API Provider navigate to the next set up step in the Exercise and configure your API "Design APIs".
Set up your API and validate if you are able to see the "Resources".
Please report feedback.
Thanks.
Hi,
I am using copy paste from the open connectors page, so not sure what could go wrong during the craetion of the API provider.
https://my.openconnectors.trial.us10.ext.hana.ondemand.com/instances/elements
I deleted and recreated the API provider, this time inserting random credentials; the weird this is that the message does not change.
I then corrected the credential copying and pasting organization and user secret.
I then deleted API v1 which was not working and created v2.
After deployment i went to check the available resources as suggested and I can see all the resources made available from the OpenConnectors Instance:
When testing the API again from the console, I get the same error as before:
https://95792d12trial.integrationsuite-trial01.cfapps.us10-001.hana.ondemand.com/shell/testconsole
Can it be that for whatever reason, the system is not able to get the token from the OpenConnectors credentials provided and therefore both gives an 404 error when testing the connection to the API provider and an internal error 500 when testing the API from the console?
Thanks,
BR
Hi,
I created today a fresh new trial account starting integration suite configuration from scratch hence all subsequent artifacts.
However the issue seems to be the same:
1) All role collections assigned
2) All capabilities seem provisioned and activated
https://95792d12trial.integrationsuite-trial01.cfapps.us10-001.hana.ondemand.com/shell/home
3) OpenConnectors Instance seem to be working fine as I am able to receive notifications
https://my.openconnectors.trial.us10.ext.hana.ondemand.com/elements/2103/api-docs?instanceId=4811860
4) API Business Hub Enterprise can be accessed correctly
https://95792d12trial.integrationsuitetrial-devportal.cfapps.us10.hana.ondemand.com/
5) Connection to OpenConnectors API provider looks to be fine
6) Testing the API from the console results in the same error as before
https://95792d12trial.integrationsuite-trial01.cfapps.us10-001.hana.ondemand.com/shell/testconsole
I wanted to try and use the same region used in the tutorial but unfortunately Frankfurt is not available anymore for trial.
Not sure what else I could check...
Thanks,
BR
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.