cancel
Showing results for 
Search instead for 
Did you mean: 

SOAP to RFC scenario (SFDC <->ECC synch)

Former Member
0 Kudos

Working on a SFDC to ECC synch scenario using SOAP to RFC interface. I generated the WSDL for SFDC team and tested on soapUI, I am able to see the successful request/response structure in sxmb_moni.

However, when the SFDC team is sending the request in real time from SFDC, the request is successful in SFDC but not reaching PI and hence there is no response. The error I see in sxmb_moni for this is

<SAP:Error SOAP:mustUnderstand="1" xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SAP:Category>XIServer</SAP:Category>

<SAP:Code area="INTERNAL">PROXY_NOT_ALLOWED_ON_IS</SAP:Code>

<SAP:P1 />

<SAP:P2 />

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText />

<SAP:Stack>Proxy calls are not permitted on sender or receiver side on the IS (client)</SAP:Stack>

<SAP:Retry>N</SAP:Retry>

</SAP:Error>

Are there any additional setting need to be done.

Please guide on this issue . Thanks

Edited by: jbagga on Nov 14, 2011 7:42 AM

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Dear jbaga,

Please verify user+password combination is right.

Is SFDC = Sales Force?

If so, we made succesfully such an integration, please contact me if more halp is needed.

Good luck

Answers (3)

Answers (3)

Former Member
0 Kudos

SFDC sending request to PI. SFDC Request is not hitting PI, neither traceable in MONI or RWB.

SFDC request is not hitting PI . The ForeFront has allowed the SFDC IP range to target PI using reverse proxy rules. But SFDC and Forefront both get the "HTTP 500 internal server error"

The question is , I am helpless until the request is monitored anywhere in MONI or RWB_communication channel

Also SFDC receives some fault message error along with HTTP 500 i.e. Header Missing in Soap Message Header. In this case, also if its PI related error there should be at least some track of request hitting PI in MONI or RWB. also tried creating a WSDL with PI username and password in the WSDL under Header tags, still the same situation

ALL Ports are open by BASIS team.

Can someone point out any helpful solution. URGENT !! Thanks a ton in advance.

EVERYTHING , THE ENTIRE REQUEST/RESPONSE STRUCTURE WORKS PERFECT WITH SOAPUI.

Former Member
0 Kudos

Which version of PI are you using? if you have access to NWA then you can enable the trace and see what exactly the problem while they are connecting to your PI box...

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

SFDC Team sends request from different network which is not part of your environment, they should

Have access to call your service (wsdl/service url) hence you need to open all ports and firewall stuff.

When you test your development within the same network using SOAP UI, thatu2019s why it worked, but SFDC donu2019t have access it seems.

Regards,

Raj

Former Member
0 Kudos

The sfdc team has login credentials for PI and the request seems to reach PI through a secured port we identified but again the error is : <SAP:Code area="INTERNAL">PROXY_NOT_ALLOWED_ON_IS</SAP:Code>

The PI development server is configured as integration server for other projects , if I change it to Application System it might effect their ques.

Kindly suggest .

Former Member
0 Kudos

Are you using a webdispatcher in your DMZ ?

Check the soap communication channel to see if you can see the request hitting the adatper .

I would also try the soap end point url supplied to the SFDC team on the browser of a system outside your network and see if you can access it over the internet .

baskar_gopalakrishnan2
Active Contributor
0 Kudos

Your proxy system should use local integration engine for the proxy communication. So you have to configure integration server as application in the ecc system and not in PI.

Former Member
0 Kudos

Hi All ,

Where does the question of proxy come into play , since it is a SOAP<->RFC scenario between SFDC and ECC synch. However, I configured the ECC to application server to give it a try.

The request is not hitting the PI as there is no backlog record in SM21. Are there any suggestions on what might be the issue ??

does SFDC need to incorporate loginf credential of PI in their request even when targeting unsecured port ?

Thanks

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

have you found entry in MONI? i think PI System point of view ports to be opened, check with Basis team.

Regards,

Raj

Former Member
0 Kudos

Hi folks,

So now the request from SFDC has reached forefront but when forefront is forwarding the request to PI , they are getting the response error HTTP 500 Internal Server Error. Any inputs on this ? I see no records in SXMB_MONI or communication channel for SFDC sender. Any specific configuration needs to be done on PI side.

P.S. The request.response structure is working fine with SOAPui but again thats within out landscape and at par with any network issues.

rajasekhar_reddy14
Active Contributor
0 Kudos

Hi,

You have to provide correct WSDL URL and Service URL, i believe they are calling wrong URL.

Regards,

Raj

Former Member
0 Kudos

Hey,

The URL is same as the one soapUI test case uses, which is successful.

Former Member
0 Kudos

Hi,

have you check this blog ?

[How do you activate ABAP Proxies?|https://www.sdn.sap.com/irj/sdn/weblogs?blog=/pub/wlg/3022] [original link is broken] [original link is broken];

because it seems you try to use the Integration Server, whereas you should use an Application server.

else you can use SDN button with "PROXY_NOT_ALLOWED_ON_IS", and you will see answers of this known error...

regards

Mickael

Edited by: Mickael Huchet on Nov 14, 2011 9:06 AM