Skip to Content
avatar image
Former Member

IDOC connectivity Third Party system with AEX 7.31


actual we want to migrate an szenario from an old XI/PI System, where we connect to a third party system (non-ABAP)

via the idoc adapter, to a new AEX 7.31 PI.

In the past, the following communication take place :

Idocs to the third Party :  the third party system registers with an program id to the message server of the PI and in the Idoc receiver communication channel, uses the the RFC destination of type "tcpip" and transfer it to the third party system.

Idocs from third party :  the third party connects as an RFC client (Paramter : client, host, user, password ...) to the the idoc adapter service on the ABAP Stack.

Now, we have to achieve the same funcionality with the AEX 7.31.

For test purpose we build a szenarion :

1.  File --> PI (AEX) --> Idoc (Third Party - JCO 2.1.10 IDoc Server)

2.  File <-- PI (AEX) <-- Idoc (Third Party - JCO 2.1.10 IDoc Client)

We set the parameter from Note1729203 to allow communikation to non-ABAP systems, and we tried to implement

the Note 1752276 but the to dos are not desribed really deep.

Interface 1 :

For the interface (1) wen send an idoc to the JCO  Idoc Server the message is set to delivered but no message is received

to the Idoc Server. Even if we stop the idoc server and no server ist registered to the Program id, the message

will be set to delivered and the message is gone.

Interface 2 :

How can we achive that the third party system can connect to PI as a RFC Client with  (Paramter : client, host, user, password .) like in the past with PI (ABAP Stack) ?

BTW : We have to connect severals third party system (wich can be based on JCO 2.1.x or classic RFC-SDK)




Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

1 Answer