cancel
Showing results for 
Search instead for 
Did you mean: 

Connecting C4A to HCP - Help Needed!

Former Member
0 Kudos

Good Day Everyone,

I have been following the step-by-step guide here + official user guide by SAP to connect my fully licensed C4A to a trial version of HCP.

Here is the story:

1) I wrote these codes in sapwebdisp.pfl and .txt file. Plus I added the C4A certificate in SAPSSLC.pse, and the HCP certificate in SAPSSLS.pse

2) I have managed to access C4A using my local host as you can see below (one item to worry less about).

3) Here is the frustrating part: every time I try to do the info access test by going to /hanatest/sap/bc/ina/service/v2/GetServerInfo I get the attached message. I am 100% sure that INA_USER is there. I did the same test using the actual hcp url ending with sap/bc/ina/service/v2/GetServerInfo and I got the result I was looking for. So what am I doing wrong?

I look forward to receiving a solution!

Accepted Solutions (1)

Accepted Solutions (1)

JohnL
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Mohammad,

Are you trying to connect an on-premise HANA system to your C4A system or a trial HCP system to your C4A system?

If its the latter, please follow this guide:

Thanks,

Former Member
0 Kudos

Hi John,

I am trying to do the latter. I have read the blog that you've suggested and unfortunately it is a bit outdated. C4A no longer supports HTTPS connection with Proxy (step 20).

I can only see it possible with an SAP web dispatcher or HTTP Apache Tomcat...

Thanks,

Moe

JohnL
Product and Topic Expert
Product and Topic Expert
0 Kudos

What do you mean C4A no longer supports HTTPS?

Where did you hear that?

You'll need to create a support incident to enable the Proxy option.

My version has it available:

Former Member
0 Kudos

So I need to raise a ticket to get a pretty screen like yours?

This is what I have on my connection screen.

JohnL
Product and Topic Expert
Product and Topic Expert
0 Kudos

Hi Moe,

Yes create an incident with SAP Product Support:

https://launchpad.support.sap.com/#incident/solution

Answers (0)