Cloud Connector and SAP CAL (ABAP Trial 7.40 with BW)

[Former Member]

Hi!

I'm trying to get access to an oData-service that exists on my CAL-Instance.

I've managed to set up Cloud Connector and have it running together with the HCP.

When I create a virtual system, it cannot be found when I try to create a destination in HCP.

However, if I use the real domain (http://abapci.dummy.nodomain:5000) I can create a destination.

But, when using that destination, I always receive a "Forbidden" answer in the WEB IDE when trying to consume the oData metadata.

I Followed the "Getting started with SAP Netweaver Application Server  for ABAP...." and opened up the ports on the ABAP Server instance, but still no go.

Any ideas what I'm doing wrong?

Regards,

Magnus

[Former Member · Accepted solution]

OK, back to square one I guess...

This is what I have done so far:

Created a new instance of the ABAP AS 7.40 with BW on Hana DB SP08 DevEdt from SAP CAL.

Updated Cloud Connector to 2.6.1.1

In the Principal Propagation Tab I see following:

How do I create the certificates needed using XCA?

I'm a bit lost as to what is really needed here...

This is how my setup looks like:

HANA CLOUD PLATFORM (trial)

AWS Instance running an NW AS ABAP Server and a Front End Server

CC is installed on the same server running NW AS ABAP

I have done all initial configurations, and I'm able to see the Cloud Connector in the Cloud Cockpit.

[Former Member · Accepted solution]

After a couple of hours banging my head against the wall and the keyboard, I managed to see this in the WEBIDE

This is how my destination looks like:

I created a connection where the Virtual and "Real" domain name were the same, and it seems to be the trick.

As for the Certificates... I just imported the same certificate that I'm using for SCN and everything else SAP-related.

Will try to create a new virtual host with a different name, but with the same settings as above in order to check if it might work

[MarkusTolksdorf · Accepted solution]

Hi Magnus,

do you really want to use Principal Propagation with the CAL system? This will require a trust setup as described in the respective documentation. Not a simple task. For the WebIDE setup you don't need it.

Best regards,

Markus

[Former Member · Accepted solution]

Sure Enough...

Gives

Error log in WEBIDE/HCP Cockpit:

2015-10-27T12:19:15,417+0000#4036112341#ERROR#HTTP protocol error occurred while connecting to remote host http://abap_server:50000. Reason: URI does not specify a valid host name: http:/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/$metadata

Logging in HCC shows...Well... Nothing...

Which seems fair since we haven't the correct URI to begin with...

Any ideas why the Virtual Hostname is not picked up correctly?

[Former Member · Accepted solution]

Thanks Marcus

I changed to No Authorization (meaning that I will have to provide the password upon consumption of the service if I understand correctly).

I will try with Basic Authentication later on.

Do you know what might be causing the URI-error when using a Virtual host-name other than the Internal?

[MarkusTolksdorf · Accepted solution]

Hi Magnus,

this is a good question. As I don't know WebIDE internals I cannot comment on this.

Best regards,

Markus

[Former Member · Accepted solution]

I finally have an answer...

Since Underscore "_" is not a valid character in an URL,  the same constraints applies to the Virtual Hostname and thus it's throwing all kinds of errors.

Changed the "_" to a "." and it's working. YAY!

[MarkusTolksdorf]

Hi Magnus,

can you check in audit log, whether the call is really reaching the Cloud Connector? If Cloud Connector is the one who denies the request, you will see an entry there.

Best regards,

Markus

[Former Member]

Hi Markus,

finally got some time to look at the trail, and it seems that the CC denies the call.

2015-10-20 14:42:41, User Administrator created new parameter BackendMapping. Value: abap_serv:6500 --> abapci.dummy.nodomain:50000 # netweaverGW # HTTP

2015-10-20 14:42:51, User Administrator created new parameter AllowedResource. Value: abap_serv:6500/ # enabled

2015-10-20 14:43:09, User Administrator changed parameter AllowedResource from abap_serv:6500/ # enabled to abap_serv:6500/ # enabled

2015-10-20 14:44:31, Denying access to system abapci.dummy.nodomain:50000

How would I proceed?

[Ulrich_Schmidt]

Hi Magnus,

hmm, can it be that you "confused" the virtual host and the real host? In the log entry from 14:42:41 it looks like you have created a mapping with virtual host = "abap_serv:6500" and real host = "abapci.dummy.nodomain:500000". The cloud application then sends a request with virtual host = "abapci.dummy.nodomain:500000" and as there is no entry for such a virtual host in the backend mappings, the request is of course denied... 🙂

I would expect that if you delete the backend mapping

abap_serv:6500 --> abapci.dummy.nodomain:50000

and instead create one for

abapci.dummy.nodomain:50000 --> abap_serv:6500

it will work... (Provided that "abap_serv" is indeed the physical hostname of the machine, where your NetWeaver Gateway system is running.)

Best Regards, Ulrich

[Former Member]

Hi Ulrich,

Yes... One might think that's the case. But, unfortunately not 

Cloud Connector

HCP-Cockpit Destination

Set to virtual host

Gives following error in WEBIDE

HCP-Cockpit Destination

Set to "real host"

Gives following error in WEBIDE

I found the following document (Installing and configuring Hana Cloud Connector for OnPremise oData access), which I will read in the meantime waiting for your input

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/1019847e-e2aa-3210-6f97-93fbd7694...

[MarkusTolksdorf]

Hi Magnus,

hmm, configuration seems to be fine, however, why is the cloud using then the internal host? It should not know it at all ...

So far you posted only trace entries of SCC side, can you also create a trace on cloud side so that we could check whether there is something wrong?

Best regards,

Markus

[Former Member]

The error entries that I can find in the logging for WEBIDE, all look the same as the example below:

2015-10-24T12:28:48,939+0000#3076794584#ERROR#HTTP protocol error occurred while connecting to remote host http://abap_serv:6500/. Reason: URI does not specify a valid host name: http:/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/$metadata

Is there a way to expand the logging, in order to not only show the errors?

I did a check in the Debugging Console in my browser and found that there actually are two different kind of errors in the answer from the GET request:

Internal: Error 500: Internal Server Error

"Real Host-name" Error 403: Forbidden

The requests look like:

Internal: https://webide-s<myID>trial.dispatcher.hanatrial.ondemand.com/destinations/ABAP_TEST_2/sap/opu/odata...

"Real Host-name": https://webide-s<myID>trial.dispatcher.hanatrial.ondemand.com/destinations/ABAP_TEST/sap/opu/odata/I...

I get the same errors when I enter those addresses in the browser and try to access them.

[Ulrich_Schmidt]

Hmm, wait a moment: are you executing the app out there on the Cloud, or on a test-server running locally in your WebIDE?

When running locally, your test-server of course has direct access to all hostnames inside your LAN and does not need the Cloud Connector.

Or alternatively: if it's running outside in the Cloud, then the 403 you get when using the real hostname, can be explained easily: the SCC does not have a mapping for the real hostname and therefore refuses the call with 403.

Now it only needs to be found out, why we get the 500 when using the "virtual" hostname (which should be the correct setting). So using "abap_serv:6500" in the Destination on HCP is correct. What error do you then get again in the SCC in the ljs_trace.log? (A "Payload Trace" on SCC side might be helpful in this case as well?!) Probably for some reason the SCC is not able to open a network connection to host abapci.dummy.nodomain?!

This error here I don't understand at all:

"HTTP protocol error occurred while connecting to remote host http://abap_serv:6500/. Reason: URI does not specify a valid host name: http:/sap/opu/odata/IWFND/CATALOGSERVICE;v=2/$metadata"

Is the HCP side using the destination incorrectly??? The hostname is missing in the URI !?!? How can this happen?

Best Regards, Ulrich

[Former Member]

Ulrich,

I'm using a SAP Cloud Appliance Library instance of the "SAP NW AS ABAP & SAP BW 7.40 SP8 on HANA" Solution.

Just as you wrote your lates post, I terminated the instance

I will try to create a new one and see if the problem still exist after doing the initial configurations.

Also, this time I will update the CC.

Regards,

Magnus