cancel
Showing results for 
Search instead for 
Did you mean: 

IDOC connectivity Third Party system with AEX 7.31

Former Member
0 Kudos

Hello,

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)

Thanks

Regards

   Thorsten

Accepted Solutions (0)

Answers (1)

Answers (1)

Bhargavakrishna
Active Contributor
0 Kudos

Hi Thorsten,

Have you tested the RFC connection and Remote log-on from sm59?

no server ist registered to the Program id

For RFC connection of type 'T' , the program ID must register in SAP gateway.

im not sure about the Third-party system.

Refer the below links to do the same..

http://madhutekur.wordpress.com/2008/08/10/registering-a-program-on-the-gateway/

http://help.sap.com/saphelp_nw04/helpdata/en/22/0429aa488911d189490000e829fbbd/content.htm

http://sap.ittoolbox.com/groups/technical-functional/sap-basis/rfc-server-program-cannot-be-register...

Ask your basis team to do that and check it..

Did you checked the connection between both SAP and Non SAP system?

For step by step guide:

http://www.saptechnical.com/Tutorials/XI/IDocToFile/IDocToFile1.htm

Trouble shooting:

http://www.sappi.sapag.co.in/sap-pi-troubleshooting/troubleshooting-file-to-idoc-scenario-in-xi/

Are you doing synchronous scenario (File to IDOC)?

Can you more brief about your issue's?

Hope it will helpful..

Regards

Bhargava krishna

Former Member
0 Kudos

Hi Thorsten,

Have you tested the RFC connection and Remote log-on from sm59?

no server ist registered to the Program id

For RFC connection of type 'T' , the program ID must register in SAP gateway.

im not sure about the Third-party system.

Refer the below links to do the same..

http://madhutekur.wordpress.com/2008/08/10/registering-a-program-on-the-gateway/

http://help.sap.com/saphelp_nw04/helpdata/en/22/0429aa488911d189490000e829fbbd/content.htm

http://sap.ittoolbox.com/groups/technical-functional/sap-basis/rfc-server-program-cannot-be-register...

Ask your basis team to do that and check it..

Did you checked the connection between both SAP and Non SAP system?

For step by step guide:

http://www.****************/Tutorials/XI/IDocToFile/IDocToFile1.htm

Trouble shooting:

http://www.sappi.sapag.co.in/sap-pi-troubleshooting/troubleshooting-file-to-idoc-scenario-in-xi/

Are you doing synchronous scenario (File to IDOC)?

Can you more brief about your issue's?

Hope it will helpful..

Regards

Bhargava krishna

Hello,

thanks for the answer, but the problem is not the registration to the message Server of AEX (Single Stack) - it is registered. But the problem is to configure the IDOC_AAE Adapter to use such an registered program to send Idocs to it.

All the other Links show hot to connect the IDoc Adapter (as a registered Server) to an SAP ABAP System, but we need to get connect to a third Party System with themself register with a programm ID.

Regards

   Thorsten

Bhargavakrishna
Active Contributor
Former Member
0 Kudos

Hello,

thanks,

the first link helps a little bit, but there ist no desription how to configure the sender Idoc Adapter (for the third Party System).

The other two links are for the "old" way with the ABAP Stack of PI, what is definitivly not working anymore withe nes IDOC Adapte on AEX Java Single Stack.

Regards

  Thorsten Stork

martin_pichlo
Participant
0 Kudos

Hello,

we have exactly the same issue for our customer. All "SAP IDoc -> SAP SAP" interfaces are are up and running. But we found no solution to set up interfaces for "SAP IDoc -> NON-SAP IDoc" and "NON-SAP IDoc -> SAP IDoc" interfaces.

Is there any documentation available how to set up connections "TCP/IP connection with reg. Programm ID"? The only official informations we found are Note 1729203, 1752276 and 1717833.

Regards

Martin

Former Member
0 Kudos

Hello,

this links are the description how it works with the "old" XI/PI Idoc Adapter ABAP, but we have a AEX 7.31 (Java Single Stack and have to work with the new IDOC_AAE Adapter).

Regards

  Thorsten Stork

Bhargavakrishna
Active Contributor
0 Kudos

Hi,

this links are the description how it works with the "old" XI/PI Idoc Adapter ABAP, but we have a AEX 7.31 (Java Single Stack and have to work with the new IDOC_AAE Adapter).

if you read the full document, IDOC_AAE explained is PI 7.3 version.

as per my knowledge apart from AEX, both are same, because IDOC_AAE (Java adapter) which is available in PI 7.3 dual stack /AAE/AEX is same.

did you tried implementing the scenario by following the guide..???

Regards

Bhargava krishna

Former Member
0 Kudos

Hello,

thanks for the response.

The IDOC_AAE Adapter is different from the IDOC Adapter at the ABAP Stack and that is the problem.

Your Links

http://scn.sap.com/thread/1708711

http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/d19fe210-0d01-0010-4094-a6fba344e...

The first thread (2010) is about the IDOC Adapter on the ABAP stack.

The second link opens an Config Guide for IDOC Scenarion an is from the Year 2005, so Pi 7.3 is not in there.

You talk about "the following guide", which guide do you mean exactly ? Which Page ?

Thanks

Rgards

  Thorsten

martin_pichlo
Participant
0 Kudos

Hi Bhargava,

I have checked you link, too. But I could not found any part which discripted how to create a tcp/ip or programm-id connection to PI Java Single Stack in your documents. Please have in mind, that there is no SM59 available in Java Single Stack....

Do you have any further ideas?

Regards

Martin

Bhargavakrishna
Active Contributor
0 Kudos

Hi,

Refer this http://scn.sap.com/docs/DOC-31398

Regards

Bhargava krishna

Bhargavakrishna
Active Contributor
0 Kudos

im not talking about PI.

In ECC

Bhargavakrishna
Active Contributor
0 Kudos

Hi,

Check in ECC not in PI..

martin_pichlo
Participant
0 Kudos

Hi Bhargava,

thank you for trying to help us. But your last reply is exactly the point... there is NO ECC and NO ERP involved in our scenario. Please read the description above.

The topic is: "How connect AAE IDOC PI to 3rt Party. For example PI to JCO.

So as result there is absoluty no point to configure any SM59, because there is no system which contains an ABAP Stack.......

Regards

Martin

Former Member
0 Kudos

Hello,

sorry, but the way to communicate via IDOC_AAE  to an SAP ECC works fine, but the Problem is to communicate with an non-SAP Idoc System (e.g. based on JCO).

So all the guides to configure the connection to SAP ECC do not help.

Regards

  Thorsten Stork

Bhargavakrishna
Active Contributor
0 Kudos

is that, non sap system is a uni-code system?

Former Member
0 Kudos

Hello,

yes the JCO Idoc Server is UNICODE.

Regards

  Thorsten Stork

Bhargavakrishna
Active Contributor
0 Kudos

also check

/people/ayyapparaj.kv/blog/2008/11/20/r3-to-java-sending-idocs-using-sapidoc-jar

/people/ayyapparaj.kv/blog/2008/11/21/java-to-r3-sending-idocs-using-sapidoc-jar

http://scn.sap.com/thread/1974709

http://scn.sap.com/thread/1985904

Regards

Bhargava krishna