ABAP Proxy Inbound & Outbound: Change in ECC Client

[Former Member]

Hello! All

We have our inbound & outbound ABAP proxy scenario between PI Client 150 & ECC Client 100 working fine.

However, due to some testing requirement with other ECC Client (Client 250), we need to set up inbound & outbound proxy communication between Pi Client 150 and the new Client 250 as well.

Hence, we need the existing inbound & outbound ABAP proxy scenarios to continue to function and additinally set up connectvity between PI Client 150 & new ECC Client 250 parallely.

Can you please let us know the steps we need to provide to Basis to achieve this and interms of development effort on PI, we are assuming we just work with the new ECC Client 250 business system in setting up for config objects.

Here are the points we need some help & Clarity on:

1. What are basis steps needed on ECC side(SXMB_ADM?) & PI Side (sm59 & SLD?)

2. PI devlopment can be driven of the new business ystem associated with the new ECC client 250.

3. Differences between the inbound & outbound proxy set up for sending and receiving ABAP proxy messages parallely between PI Client 150 & ECC CLient 100 & ECC Client 250.

Your help is greatly appreciated!!

Thank you,

Ritu

Edited by: Ritu Tiwari on Nov 11, 2010 11:39 PM

[Former Member · Accepted solution]

Hi,

Is both the client belong to same ECC system or different systems??

Case 1:- Both client belong to same ECC system:-

If its cross cleint then in that case ur development done in client 100 will be seen in client 250 as well.

1. U need to create Business system for cleint 250 and configure the configuration scenario for client 250 in PI.

2. RFC destination pointing to PI is required in 250 client.

3. RFC destination pointing to 250 cleint is required in PI system

Case 2:- They belong to different systems

1. All proxy set up required in ECC client 250.

2. RFC destination required XI as well as PI.

3. Proxy geenrationand Code has to be written again.

4. ID configuration scenario to be created.

chirag

[Former Member · Accepted solution]

Thank you for your detailed response!!! Chirag

Yes, its the same ECC box only the client is different.

Hence, based on your case 1 points, there is no further proxy set up required if its the same ECC box and we only need to create HTTP destination on the new Client to PI and PI to the new ECC Client?

Thanks,

Ritu

Edited by: Ritu Tiwari on Nov 12, 2010 2:39 PM

[Former Member · Accepted solution]

yes follow the steps anf if u face any issue then post the error or questions.

chirag