No Connection to Integraion Builder in SPROXY transaction

[Former Member]

Hello

I am trying to activate ABAP Proxies for SAP WebAS 6.4 system as given in weblog

/people/vijaya.kumari2/blog/2006/01/26/how-do-you-activate-abap-proxies

I did all the steps mentioned

1] Created HTTP destinations which is successful

2] Created Integration server configuration in SXMB_ADM pointing to XI

3] Created TCP/IP destinations

Still its giving the above problem. Is anything missing?

Thanks in advance.

Regards

Rajeev

[udo_martens · Accepted solution]

Hi Rajeev,

you ve already configured runtime parameter - good to have, if IB Repository connection works

Click on the error message at sproxy, there must be a helping popup, which leads you to the result. You have to put access to IB Repository, either at exchange profile or in table sproxset.

- IB-Address: Exchange Profil, Sektion Connections: com.sap.aii.connect.repository.name

- IB-Port: Sektion Connections: com.sap.aii.connect.repository.httpport

- Path: Sektion Connections: com.sap.aii.connect.repository.contextroot

- User: Sektion ApplicationSystem: com.sap.aii.applicationsystem.serviceuser.name

- Password: Sektion ApplicationSystem: com.sap.aii.applicationsystem.serviceuser.pwd

Regards,

Udo

[Former Member · Accepted solution]

Udo,

Here are the results for the reports list as mentioned in those popup

1] SPROX_CHECK_IFR_ADDRESS

Exchange Profile: http://xihost/rep

In Table ...:HTTP Destination:

..

..

Status: OK: Address maintained

2] SPROX_CHECK_HTTP_COMMUNICATION

HTTP is funcitoning properly

3] SPROX_CHECK_IFR_RESPONSE

HTTP error (return code 400, message "ICM_HTTP_CONNECTION_FAILED")

Did'nt understand why this is returning HTTP error because my RFC destination to XI server works properly.

Thanks and Regards

Rajeev Patkie

[Former Member · Accepted solution]

Rajeev,

Have a look at Michal's blog for time outs...

/people/michal.krawczyk2/blog/2006/06/08/xi-timeouts-timeouts-timeouts

Regards,

Jai Shankar

[prabhu_s2 · Accepted solution]

rajeev...follow this thread...hope it shud give some useful tip

[udo_martens · Accepted solution]

Hi Rajeev,

did u put access to IB Repository at Exchange Profile or at SPROXSET?

What are the values of that parameter?

Assumedly you have to put a full qualified hostname, or open a port or correct the pass or something like that.

Regards,

Udo

[prabhu_s2 · Accepted solution]

have a reference to this blog

<a href="/people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi:///people/krishna.moorthyp/blog/2006/07/23/http-errors-in-xi

[Former Member · Accepted solution]

Udo,

In SPROXSET I have given destination name which I created of type hTTP (in test connection this works).

Exchange profile u meant was exchange profile of XI server right? I am trying to check that but I guess I am not authorized for that.

Thanks and Regards

Rajeev

[prabhu_s2 · Accepted solution]

hi rajeev

one quick overview....did u check ur rfc connectivity from r3...is it of type H? if this is not giving any error then troubleshooting the rest will be much easy.

[Former Member · Accepted solution]

Prabhu S,

As I said earlier my RFC destination of type H works fine.No problem at all in that.

Regards

Rajeev

[udo_martens · Accepted solution]

Hi Rajeev,

that might be the problem: SPROXSET parameters will be excecuted only if no parameter in exchange profile found. So you can try and check til your fingers are black, he, he..

Regards,

Udo

[Former Member · Accepted solution]

Yes that was the problem. In exchange profile I replaced IP instead of hostname and it worked.

Thank you all for ur replies.

Regards

rajeev

[prabhu_s2 · Accepted solution]

thats kool ....can u close the thread if anwsered

[Former Member · Accepted solution]

Hi,

I had the same problem and I take advantage of this discussion, but I put the full qualified host name and works fine too

Thanks

Fabricio

[Former Member · Accepted solution]

Hi,

I had the same problem and I take advantage of this discussion, but I put the full qualified host name and works fine too

Thanks

Fabricio

[Former Member]

hi rajeev,

Hope you have used PIAPPL User in Integration builder.

Just check that PIAPPL user has not got locked in XI...

And if it is so... unlock it and then set its password in Upper case. It is must to have this password in upper case.

Then give the same password in Integration builder.

Then go to SPROXY Transaction.

Go to -> Connection test.

Check all the steps that they r working fine or not.

Also check that ur ICM service is running or not?

In SICF activate all XI related and integration builder related Services.

Then also if it is not working... tell what error you r getting.

Regards,

Hetal.

Note : Reward points for helpful answers.

[bhavesh_kantilal]

Rajjev,

Make sure that the passwords mainained are correct.

Also recheck the same with the Post Installation Guide -->Section 8

https://www.sdn.sap.com/irj/sdn/go/portal/prtroot/docs/library/uuid/ac6de690-0201-0010-54ac-8923089d...

Regards

Bhavesh

[Former Member]

Hello

But when I test the HTTP destination it is successful.

Heres what response I got from that.

HTTP/1.0 500 Empty HTTP request received

Content-Type: text/xml

Content-Length: 815

content-id: <soap-B4951CC426240F4BAFD125FD5BB57723@sap.com>

soapaction: 'http://sap.com/xi/XI/Message/30'

server: SAP Web Application Server (1.0;700)

<SOAP:Envelope xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/">

<SOAP:Header>

</SOAP:Header>

<SOAP:Body>

<SOAP:Fault xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/"><faultcode>SOAP:Client</faultcode><faultstring>Empty HTTP request received</faultstring><faultactor>http://sap.com/xi/XI/Message/30</faultactor><detail><SAP:Error xmlns:SAP="http://sap.com/xi/XI/Message/30" xmlns:SOAP="http://schemas.xmlsoap.org/soap/envelope/" SOAP:mustUnderstand="1"><SAP:Category>XIProtocol</SAP:Category><SAP:Code area="MESSAGE">EMPTY_HTTP_REQUEST_RECEIVED</SAP:Code><SAP:P1/><SAP:P2/><SAP:P3/><SAP:P4/><SAP:AdditionalText/><SAP:ApplicationFaultMessage namespace=""/><SAP:Stack>Empty HTTP query received; message processing not possible

</SAP:Stack></SAP:Error></detail></SOAP:Fault>

</SOAP:Body>

</SOAP:Envelope>

That means its able to connect to XI system.

Thanks and Regards

Rajeev

[prabhu_s2]

rajeev

did check the user anme and pwd correctness for the rfc connectivity?

[prabhu_s2]

rajeev

can u also check this thread for more input on this issue:

[Former Member]

Where to check that? actually i did'nt came across any RFC..pl do let me know.

Regards

Rajeev

[prabhu_s2]

check in sm58 of r3...see from there u r able to login to xi by test connection.

[Former Member]

Prabhu S,

Actually I have created a RFC destination of type R3 for XI. From there I could able to Remote Login to my XI server. But I am trying to understand the need of RFC. For proxy communication I guess we configure HTTP communication channels. I am having WebAS 6.4 infact my business system is on NetWeaver2004s and I am trying to connect to XI (which is another server) which is also on NetWeaver2004s.

Thanks and Regards

Rajeev

[Former Member]

>>Actually I have created a RFC destination of type R3 for XI.

Rajeev, yo should ahve a RFC destination of type H to XI

In SXMB_ADM-->destination you have to give dest://<RFCdestination name>

Regards,

Jai Shankar

[prabhu_s2]

it is not of type r3 !!!

[prabhu_s2]

<i><b>Actually I have created a RFC destination of type R3 for XI. From there I could able to Remote Login to my XI server. But I am trying to understand the need of RFC. For proxy communication I guess we configure HTTP communication channels. I am having WebAS 6.4 infact my business system is on NetWeaver2004s and I am trying to connect to XI (which is another server) which is also on NetWeaver2004s.</b></i>

refer to pg# 27 of this <a href="https://websmp102.sap-ag.de/~sapidb/011000358700001697502004E.PDF">SAP Exchange Infrastructure 3.0 Configuration Guide</a>

[Former Member]

This problem is due to improper HTTP destinations..

Can you recheck this...

Regards,

Jai Shankar

[prabhu_s2]

check the rfc in r3...also whats the error u are getting?

Message was edited by:

Prabhu S