topic Re: Abap Proxy - Webas in Application Development and Automation Discussions

Abap Proxy - Webas

former_member269988 — Thu, 07 Jul 2016 14:31:55 GMT

Hi Dear,

Please, i need a help of us.

I try connect SAP Ecc with Webservice (.net) without using SAP PI. I try using RFC, but I did not have success in the connection (although via SM59 has managed). Now i using abap proxy, but when the proxy test connect I received the following message:

"GET_BUSINESS_SYSTEM_ERROR An error occurred when determining the business system (COMMUNICATION_ERROR)"

I know someone tell me what could be done?

I try check SLDAPICUST

And SM59

Thanks a lot

Re: Abap Proxy - Webas

Harish — Fri, 08 Jul 2016 00:48:20 GMT

Hi Wilson,

The error is because of proxy connectivity setup in SAP ECC. Can you verify your connection based on below document

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/e0ac1a33-debf-2c10-45bf-fb19f6e15649?overridelayout=t…

regards,

Harish

Re: Abap Proxy - Webas

former_member269988 — Fri, 08 Jul 2016 12:28:26 GMT

Hi ,

thanks a lot of your feedback, but i don't use SAP PI to connect....i create a logical port (i know is obsolete) and run the proxy....now the error is this:

Re: Abap Proxy - Webas

HAL9000 — Fri, 08 Jul 2016 18:08:38 GMT

Hi Wilson,

the error message says:

"hostname 'sapclustereep' unknown"

Further info: FAQ Network Interface - Application Server Infrastructure - SCN Wiki -> last question

This means the given hostname cannot be resolved on the ABAP application server host which you wiped out.

If this hostname is correct, let your DNS configuration get checked by your network administrator.

Best regards,

Stefan

Re: Abap Proxy - Webas

former_member269988 — Fri, 08 Jul 2016 19:10:35 GMT

Hi , thank you of help.

But the connection is necessary useing the Sm59-TC/IP - SAPSLDAPI? I say this because the other error is "Server did not recognize the value of HTTP Header SOAPAction"

Re: Abap Proxy - Webas

former_member269988 — Wed, 20 Jul 2016 15:33:23 GMT

I resolved this problem in SOAMANAGER config.

Execute transaction SOAMANAGER,
select tab “Application and Scenario Communication”.
Select link “Single Service Administration”.

thanks all.