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: 

Abap proxy call failed

Go to solution
Former Member

on ‎08-05-2005 8:21 AM

0 Kudos

Hi,

I am trying to call (synchronous mode) from XI 3.0 an ABAP proxy located on a R3 enterprise 4.7 ext 2.00 server.

Unfortunately, when I send the request message with the XI Adapter to the local integration engine using message protocol 2.0,

an error occured on the R3 system:

PROTOCOL.LOOP_IN_MESSAGE_ROUTING

...

<SAP:ErrorHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">

<SAP:Context></SAP:Context>

<SAP:Code p1="is.00.hermes" p2="IS" p3="XI" p4="">PROTOCOL.LOOP_IN_MESSAGE_ROUTING</SAP:Code>

<SAP:Text language="EN"></SAP:Text>

</SAP:ErrorHeader>

<SAP:HopList xmlns:SAP="http://sap.com/exchange/MessageFormat" Version="1.0">

<SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">

<SAP:MessageInbound>

<SAP:Type></SAP:Type>

<SAP:AdapterRefId>3.0</SAP:AdapterRefId>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

</SAP:MessageInbound>

<SAP:MessageOutbound>

<SAP:Type>IENGINE</SAP:Type>

<SAP:AdapterRefId>3.0</SAP:AdapterRefId>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

</SAP:MessageOutbound>

</SAP:Hop>

<SAP:Hop SystemName="is.00.hermes" Type="CENTRAL" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">

<SAP:MessageInbound>

<SAP:Type>IENGINE</SAP:Type>

<SAP:AdapterRefId>3.0</SAP:AdapterRefId>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

</SAP:MessageInbound>

<SAP:MessageOutbound>

<SAP:Type></SAP:Type>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

</SAP:MessageOutbound>

</SAP:Hop>

<SAP:Hop SystemName="UPG" Type="RECEIVER" TimeStamp="2005-08-04T18:11:25Z" WasRead="0">

<SAP:MessageInbound>

<SAP:Type>IENGINE</SAP:Type>

<SAP:AdapterRefId>2.0</SAP:AdapterRefId>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

</SAP:MessageInbound>

<SAP:MessageOutbound>

<SAP:Type>PROXY</SAP:Type>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

</SAP:MessageOutbound>

</SAP:Hop>

</SAP:HopList>

<SAP:MessageHeader xmlns:SAP="http://sap.com/exchange/MessageFormat" version="1.0" SOAP:mustUnderstand="1">

<SAP:From>

<SAP:Name>WebServer</SAP:Name>

<SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_out</SAP:Interface>

</SAP:From>

<SAP:To>

<SAP:Name>UPG</SAP:Name>

<SAP:Interface namespace="http://adixen.fr/test">DataUserQuery_in</SAP:Interface>

</SAP:To>

<SAP:MessageId>2B1B2E10-0513-11DA-A979-0013216B8075</SAP:MessageId>

<SAP:QualityOfService>BestEffort</SAP:QualityOfService>

<SAP:TimeSent>2005-08-04T18:11:24Z</SAP:TimeSent>

<SAP:Direction>Response</SAP:Direction>

<SAP:Document></SAP:Document>

</SAP:MessageHeader>

<SAP:InternalAttributesHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">

<SAP:AdapterInbound>PROXY</SAP:AdapterInbound>

<SAP:AdapterOutbound>IENGINE</SAP:AdapterOutbound>

</SAP:InternalAttributesHeader>

</SOAP:Header>

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

<SAP:Manifest xmlns:SAP="http://sap.com/exchange/MessageFormat" xmlns:xlink="http://www.w3.org/1999/xlink" version="1.0">

<SAP:Payload xlink:href="cid:payload-AF6BAB03175A80449497B3122C844D44@sap.com">

<SAP:Document>TraceDocument</SAP:Document>

</SAP:Payload>

</SAP:Manifest>

</SOAP:Body>

</SOAP:Envelope>--SAP_41F726EA34ED2F498C6BA328BAB08C43_ENDcontent-type:text/plaincontent-length:2912content-id:payload-AF6BAB03175A80449497B3122C844D44@sap.com

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

<SAP:TraceHeader xmlns:SAP="http://sap.com/exchange/MessageFormat">

<Trace level="1" type="B">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>

<Trace level="1" type="E">CL_XMS_TROUBLESHOOT-ENTER_PLSRV</Trace>

<Trace level="1" type="T">**************************************************** </Trace>

<Trace level="1" type="T">* * </Trace>

<Trace level="1" type="T">* * </Trace>

<Trace level="1" type="T">XMB entry processing </Trace>

<Trace level="1" type="T">system-ID = UPG</Trace>

<Trace level="1" type="T">client = 100</Trace>

<Trace level="1" type="T">language = E</Trace>

<Trace level="1" type="T">user = YLEBLEVEC</Trace>

<Trace level="1" type="Timestamp">2005-08-04T18:11:25Z </Trace>

<Trace level="1" type="T">* * </Trace>

<Trace level="1" type="T">* * </Trace>

<Trace level="1" type="T">**************************************************** </Trace>

<Trace level="1" type="B">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>

<Trace level="1" type="T">Message-GUID = 2B1B2E10051311DAA9790013216B8075</Trace>

<Trace level="1" type="T">PLNAME = SENDER</Trace>

<Trace level="1" type="T">QOS = BE</Trace>

<Trace level="1" type="B">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>

<Trace level="1" type="T">Get definition of pipeline PID= SENDER</Trace>

<Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>

<Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_LOG_TO_PERSIST</Trace>

<Trace level="1" type="B">PLSRV_CALL_INTEGRATION_SERVER</Trace>

<Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV</Trace>

<Trace level="1" type="B">CL_XMS_MAIN-CALL_PLSRV_LOCAL</Trace>

<Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>

<Trace level="1" type="T">URL for integration server read from global configuration </Trace>

<Trace level="1" type="T">URL= dest://INTEGRATION_SERVEUR</Trace>

<Trace level="1" type="B">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>

<Trace level="1" type="E">CL_XMS_MAIN-SET_TECHNICAL_ROUTING_PROPERTY</Trace>

<Trace level="1" type="B">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>

<Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-CALL_XMS_HTTP</Trace>

<Trace level="1" type="E">CL_XMS_PLSRV_CALL_XMB-ENTER_PLSRV</Trace>

<Trace level="1" type="E">PLSRV_CALL_INTEGRATION_SERVER</Trace>

<Trace level="1" type="E">CL_XMS_MAIN-CALL_PIPELINE_SYNC</Trace>

<Trace level="1" type="B">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="E">CL_XMS_MAIN-WRITE_MESSAGE_TO_PERSIST</Trace>

<Trace level="1" type="E">CL_XMS_MAIN-CALL_UC_EXECUTE</Trace>

<Trace level="1" type="E">CL_XMS_MAIN-ENTER_XMS</Trace>

<Trace level="1" type="E">CL_XMS_HTTP_HANDLER-HANDLE_REQUEST</Trace>

</SAP:TraceHeader>SAP_41F726EA34ED2F498C6BA328BAB08C43_END

I guess the error occurs before the call of my proxy. Can anyone help?

Thanks,

Yann

Show replies
Show replies
Answer

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
‎08-05-2005 8:41 AM
0 Kudos

Hi Yann,

there a note on this error: <b>565692</b>

but it only tells about incorrect config...

So chk is reciever determination is correctly configured or not.

Hope it helps.

Regards

Arpit Seth

Show replies
Show replies
Former Member
‎08-05-2005 9:18 AM
0 Kudos

I am not sure I have understood the whole picture.

What do you need to do on a R3 system (WAS ABAP 6.20) to be able to process ABAP proxies.

1. Install APPINT

2. Activate the local integration engine

3. Connect the server to SLD

4. SXMB_ADM : enter the Role = Application server and link to the central integration server

When calling the ABAP proxy you just need to send a message to R3host : http://<R3host>:<http_port>/sap/xi/engine?type=entry

The pipeline of the local integration engine of my R3 system should invoke without further configuration the target proxy thanks to the name of the requested interface?

Is everything correct?

Thanks,

Yann

Message was edited by: Yann Le Blevec

MichalKrawczyk
Active Contributor
‎08-05-2005 10:01 AM
0 Kudos

Hi Yann,

this is how you call ABAP proxies

XI -> R/3 (with proxy)

or R/3 proxy -> XI -> same R/3 proxy (sync call for instance)

>>Activate the local integration engine

you can only use this if you have XI SP13 and XI is installed on a different client (then R/3)

and your R/3 is ERP 2004

Regards,

michal

MichalKrawczyk
Active Contributor
‎08-05-2005 10:02 AM
0 Kudos

one more link:

local XI

http://help.sap.com/saphelp_nw04/helpdata/en/47/eaae42edc6b211e10000000a155106/content.htm

Regards,

michal

Former Member
‎08-05-2005 10:18 AM
0 Kudos

I am getting a bit confused here.

Lets say that's my XI server is 'HERMES', and my R3 4.7 ext 2.00 enterprise system is 'UPG'. I have install APPINT on 'UPG' to be able to communicate with my integration server 'HERMES'.

However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?

Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?

Thanks,

Yann

MichalKrawczyk
Active Contributor
‎08-05-2005 10:36 AM
0 Kudos

Hi,

>>>However to be able to process XML messages on 'UPG' I need to activate the service '/default-host/sap/xi/engine'. This service start my local integration engine, correct?

I thought you tried to send messsages from the same WAS local can be set on every client - the same as R3 - right

further reference (XI configuration guide):

<b>Connecting Business Systems with an Integration Engine to the Central Integration Server</b> <-- you have to do all of those steps on your R/3 (SLD, SICF, SXMB_ADM etc.)

>>>>Last question do I need to have 2 different clients on UPG, the one for my local integration engine and the other one for my ABAP proxies? Can they be on the same client?

yes you can send proxies (from r3) to XI from the same client as your R3 system (application system)

no need for a second client on R3 side:)

sorry if I confused you with my response

Regards,

michal

Message was edited by: Michal Krawczyk

Answers (0)

Ask a Question