cancel
Showing results for 
Search instead for 
Did you mean: 

Problem with asynchronous client ABAP Proxy

Former Member
0 Kudos
294

Hi all

I have generated a asyncronous client ABAP Proxy. But when I try to call it I got the error:

HTTP_RESP_STATUS_CODE_NOT_OK

Call of URL http://xidev.cantv.com.ve:8000/sap/xi/engine terminated due to error in logon data.</p></td></tr><tr><td> </td></tr><tr><td class="emphasize"><strong>Note</strong><br>Logon performed in system XID . No logon data

and nothing arrives in my XI Integration Server.

However, I have a synchronous client ABAP Proxy in this same system, communicating to the same XI Integration Server, and it's working.

Is there any configuration I have to do so asynchronous client ABAP Proxies can manage to communicate to the Integration Server? Maybe some RFC Connections??

Any help will be welcome.

Thanks.

Accepted Solutions (0)

Answers (2)

Answers (2)

Former Member
0 Kudos

Hi,

The error that you have mentioned comes when the Username/password is incorrect. Try looking into the Username/Password that you would have provide while specifying your RFC Connections.

As u have told "u have a synchronous client ABAP Proxy communicating to the same XI Integration Server, and it's working",. This communication would have been from a different Client of the same System. If you try to execute the proxy from teh same client you ge the following error " INTERNAL.PROXY_NOT_ALLOWED_ON_IS". "Proxy calls on the sender or receiver side are not permitted on the IS (client)"

Regards,

Siva Maranani.

MichalKrawczyk
Active Contributor
0 Kudos

Hi,

you can try my previous responce:

Regards,

michal

Former Member
0 Kudos

Hi Michal.

Thanks but I've just solved the problem.

I was using the Integration Server URL in the Integration Engine Configuration, like:

http://<integration_server_host>:8000/sap/xi/engine?type=entry

I've justed created an HTTP Destination, pointing to this same address, but there I can specify the user/pwd I want to use. And the in the Integration Engine Configuration, I've just put:

dest://<HTTP_Destination>

This solved my problem.

MichalKrawczyk
Active Contributor
0 Kudos

you could have found the same solution

reading my post but I guess finding yourself

gave you more expirience

Regards,

michal