cancel
Turn on suggestions
Auto-suggest helps you quickly narrow down your search results by suggesting possible matches as you type.
Showing results for 
Search instead for 
Did you mean: 

XI protocol error occurred in abap proxy scenario- plz

Former Member

on ‎09-13-2006 6:13 AM

0 Kudos

Scenario is asynchronous

Http -> XI ->R/3(abap server proxy)

sender: Through http client

receiver is abap server proxy

<u>Repository objects:</u>

Sender: sender_DT, sender_MT, sender_MI(outbound asynchronous)

Receiver: imported RFC from R/3 client 550, receiver_MI(which has message type refered to the imported RFC)

Interface mapping: source=sender_MI, receiver_MI.

Proxy generated on R/3 client 550 for receiver_MI.

<u>Configuartion objects:</u>

Sender: business service, no comm channel since http sender.

receiver: R/3 business system

Comm channel: receiver_cc type of XI.

transport protocol: http

message protocol : XI 3.0, since both XI and R/3 on webas 6.4

addressing type: URL

target host: diamond

service number: 8005

path: /sap/xi/engine?type=entry

Authentiction data:

user name: user22

passwrod; correct

logon client: 400 which is the same client I developed ll the design and config objects.

Recevr determinaion, interface determination and recevr agrrement looks fine.

The error iam getting is:

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

- <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">LOOP_IN_MESSAGE_ROUTING</SAP:Code>

<SAP:P1>is.05.diamond</SAP:P1>

<SAP:P2>IS</SAP:P2>

<SAP:P3>XI</SAP:P3>

<SAP:P4 />

<SAP:AdditionalText />

<SAP:ApplicationFaultMessage namespace="" />

<SAP:Stack>XI protocol error occurred</SAP:Stack>

<SAP:Retry>M</SAP:Retry>

</SAP:Error>

<b>

Please reply , your help is appreciated.</b>

Thanks

KK

Show replies
Show replies
Answer

Accepted Solutions (0)

Answers (3)

Answers (3)

stefan_grube
Active Contributor
‎09-13-2006 4:32 PM
0 Kudos

> receiver: R/3 business system

> Comm channel: receiver_cc type of XI.

> transport protocol: http

> message protocol : XI 3.0, since both XI and R/3 on

> webas 6.4

>

> addressing type: URL

> <b>target host: diamond</b>

> <b>service number: 8005</b>

> path: /sap/xi/engine?type=entry

>

>

> Authentiction data:

> user name: user22

> passwrod; correct

> <b>logon client: 400</b> which is the same client I

> developed ll the design and config objects.

You have to put the server, port and client of the R/3 system, not the XI system.

Regards

Stefan

Show replies
Show replies
Former Member
‎09-13-2006 5:24 PM
0 Kudos

Stefan thanks,

I tried as you suggesetd putting the info of R/3 for

server: diamond

port: 8005

client: 550

user id: user05

pwd: correct

But I get the below error, suggest me what permission should this userid have?

<?xml version="1.0" encoding="UTF-8" standalone="yes" ?>

- <!-- Call Adapter

-->

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

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

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

<SAP:P1>401</SAP:P1>

<SAP:P2>Unauthorized</SAP:P2>

<SAP:P3 />

<SAP:P4 />

<SAP:AdditionalText><!DOCTYPE html PUBLIC"-//W3C//DTD HTML 4.01Transitional//EN"><html><head><title>Logon Error

stefan_grube
Active Contributor
‎09-13-2006 9:39 PM
0 Kudos

So the R/3 is just another client on the XI server?

The User needs the role SAP_XI_APPL_SERV_USER. If your proxy calls any BAPIs ar other standard function modules, the user might need additional roles.

Regards

Stefan

Former Member
‎09-13-2006 10:15 PM
0 Kudos

<i>So the R/3 is just another client on the XI server?</i>

R/3(550) and Xi(400) are different systems with different clients

My bad actually the service number for R/3 was enetered wrong so now i modified it to the below values.

confirm me if I m right, I entered new value for XI coom channel :

target host: diamond - host of the R/3 system,

service number:8000- http service of R/3 target system, which is found from SMICM -> services

path:/sap/xi/engine?type=entry, this if foudn from teh SLD-> business systems-> XI 400->pipeline url

Now with the above given values, whenI run the scenario the message is in "scheduled for outbound processing" state for long. the queue ID for this messg shows 'sysfail' status.

Help me on to make sure I am doing this right and troubleshoot.

<b>Thansk so much for ur reply</b>

stefan_grube
Active Contributor
‎09-14-2006 9:31 AM
0 Kudos

Check this guide:

https://websmp103.sap-ag.de/~sapidb/011000358700001697502004E.PDF

Du all steps in chapter 8 (Connecting Business Systems with an

Integration Engine to the Central Integration

Server)

Regards

Stefan

Former Member
‎09-13-2006 7:40 AM
0 Kudos

Hi ,

Check this note 565692

Sekhar

Show replies
Show replies
Former Member
‎09-13-2006 3:28 PM
0 Kudos

Is there something basic I am doing wrong?

<b>Plz reply your help is appreciated</b>

Former Member
‎09-13-2006 3:31 PM
0 Kudos

Hi,

Can you tell us what exactly you need?If you need to call a RFC in R/3 use a RFC adapter as your receiver commn. channel. Tell us your requirement for more help.

Regards,

Jai Shankar.

Former Member
‎09-13-2006 4:12 PM
0 Kudos

the situation is basically to send message to and RFC which internally updates a table, as u said we could use RFC adapter. but the rule/requirement is to use abap proxy.

let me know if it is not clear or you need more info

Shabarish_Nair
Active Contributor
‎09-13-2006 4:18 PM
0 Kudos

if you have a RFC already defined then you can use the same. But in case of the incoming data being very large in size, it wud be better to use a ABAP proxy approach instead of a RFC.

Former Member
‎09-13-2006 4:26 PM
0 Kudos

yeah I have RFC already defined, but since the requireent is to use abap proxy i am going with it.

Plz advice on the actual error - XI protocol error occurred

Former Member
‎09-13-2006 4:32 PM
0 Kudos

Hi,

Could you list your receiver determination and interface determination just so we can see it is fine.

it looks like the routing of the XI message is in a endless loop.

Cheers

Colin.

Former Member
‎09-13-2006 5:55 PM
0 Kudos

Recerv determination has:

sender-

business service defined

interface: outbound asynch.

receiver:

R/3 business system,

interface determination in which the receiver interface is referred.

receiver agreement for the XI receiver Comm channel

Former Member
‎09-13-2006 6:10 PM
0 Kudos

<b>Experts plz reply this is urgent.

Your rpely is highly appreciated.</b>

Thanks

KK

Former Member
‎09-13-2006 7:03 AM
0 Kudos

Hi,

Do you need to configure a HTTP-RFC or HTTP-Proxy scenario? YOu are mixing up both. AFIK this is not allowed. Let us wait for the experts to comment....

Regards,

Jai Shankar.

Show replies
Show replies
Ask a Question