Connect Cloud connector to SCP

[perage]

Hi,

I've followed some guides on connecting my on-prem to SCO via a local cloud connector. I did this a few months ago, but the instance was deleted, and now cloud foundry is the only way to go.

I've managed to installed the CC and connected it to both SCP and to on-prem (see picture), but the menu item "Cloud connectors" are not showing in SCP, nor is it possible to make the destination connect.

Can anyone point me in the right direction in terms of troubleshooting? Should the "Cloud Connectors" menu item be present, or should it be to just create a destination?

[ErvinSzolke]

Hi,

please note that I also added tag "SAP Cloud Platform Connectivity" for better searchability.

Have a great weekend!

Ervin (moderator)

[todor_petrov]

Hi,

I noticed the same after the last update of the Cloud Platform Cockpit.

The menu for the Cloud Connector is gone, but when you create a destination and you have the newest cloud connector installed, you should be able to ping your connection and verify that it is working properly.

Br,

Todor

[perage]

I downloaded the latest CC now, but I still experence the same issue 😞

Host: 10.X.X.X
Port: 8000
Virtual host: demo
Virtual port: 8000

URL added to destination: http://demo:8000

[vbalko-claimate]

Hmmm, I still got my cloud connector on production SCP, but it disappeared from trial account. So it is probably about nerfing trial. Same as HTML5 Applications menu item disappeared from trial accounts lastly.

[MarkusTolksdorf]

In trial feature set B is used, which is not yet offering the Cloud Connector view. The runtime, however, works fine. It's only not possible to see the registered Cloud Connectors in the cockpit.

Best regards,
Markus

[perage]

markus.tolksdorf Should I be able to ping it from the destinations menu? Because I have doublechecked all entries, and I always get the same error; Failure reason: "Could not check at the moment. Please try again later

[MarkusTolksdorf]

The destination check does not work yet either - technical reason is the same like for the Cloud Connectors view

Best regards,
Markus

[perage]

Ok, thanks for the update markus.tolksdorf It seems very difficult to troubleshoot the connection then. I have a Neo trial where everything works, but that expires after today. I've created a destination with name demo (URL: http://demo:443) which point to local CC who is connected, with a reachable backend. In mobile service, I've added a new destination "demo" with cloud destination name "demo" and with path "/sap/opu/odata(...)/. When saved, it shows up as "https://destination/sap/opu/odata/sap/ztest_expand_srv/" and with basic authentication. Is the "https://destination" just a placeholder or is there a bug here since it's not using the destination url from SCP? The service cannot be ping'd here either, and in SCP iOS SDK Assistant, the metadata cannot be loaded, eventhough It works perfectly with the same paths on NEO.

[perage]

Hi markus.tolksdorf !

Is it at all possible to connect mobile services destination to the cloud connector in trial mode as it was with Neo? I've tried all possible combinations in SCPms, but the services aren't reached for the iOS assistant.

1. I have a cloud connector that is connected to the instance and with a reachable backend, with virtual host demo:443

2. I've created a destination named demo with url <http://demo:443> as proxy type on-prem

3. Crated a destination in SCPms with url http://demo:443/sap/opu/odata/sap/<my_z_service>/ and tried both with "use cloud connector" and without.

Doing exactly the same worked without any issues on Neo, but it's not reaching my backend with CF 😞 Any help us highly appreciated!

[MarkusTolksdorf]

You can use a Cloud Connector with trial. With regards to SCPms, an expert from that area. should comment what is possible.

Best regards,
Markus