cancel
Showing results for 
Search instead for 
Did you mean: 

Transferring message between two Integration servers using th XI adapter

Former Member
0 Kudos

Hello all,

I have the following scenario:

1) Local SAP R3 sends an iDoc to a local Integration server (XI3.0)

2) The local IS transfers the iDoc to a remote IS (XI3.0) through HTTP.

3) The remote IS is supposed to send the iDoc to it's own SAP R3 system.

Here is what I tried:

On my local Integration Server:

- I have defined the remote IS as a "normal" business system.

- I have created an XI adapter as a receiver communication channel with HTTP 1.0 protocol.

- I set the URL option and set the correct host name and port.

- I have entered the pipeline url: /sap/xi/engine?type=entry

It seems that all the parameters are correct but the HTTP response contains error 404.

Any ideas ?

Thank you,

Elad Saar.

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hi Elad,

We did XI-XI communictions a bit different, we approached it as a B2B scenario. We defined a Party for the sending XI system and we created an abstract interface with the Idoc messagetype (because you need on both sides the same interface name/namespace and we use naming conventions).

In the receiver agreement of the sending XI system you have to replace the party and service name with the ones you have did setup on the receiving XI.

I hope this helps you in the right directions

Cheers,

Frank

Former Member
0 Kudos

Dear Frank,

It seems that the 404 error code was receive due to wrong port definition, so that's solved....

And after solving the port definition conflict, I receive a 405 error code ( Any ideas ? )

Besides that, I would like to refer to your solution:

Do I have to use an abstract interface for XI-XI communication ?

Wouldn't it work with normal iDoc interface ?

Thank you for your quick replay.

Elad.

Former Member
0 Kudos

Hi Elad,

What is the error message you got with the 405 error code?

I think it must work with the iDoc interface, because the interfacename and namespace are the same.

Cheers,

Frank

Former Member
0 Kudos

Dear Frank,

The error message was ICM_HTTP_INTERNAL_ERROR, but this error was solved as well.

The entire scenario for XI-XI communication now works just fine (I found out there is no need for abstract interface).

Thank you very much for your answers,

they were quit helpful.

Elad Saar.

Former Member
0 Kudos

Hy Elad,

could you please tell me how you resolve the error ICM_HTTP_INTERNAL_ERROR 405, because i'm having the same error randomly

thanks

Answers (0)