cancel
Showing results for 
Search instead for 
Did you mean: 

Proxy communication in dual stack

Former Member
0 Kudos

I am working in dual stack SAP PI.

I have a Proxy to SOAP scenario.

I have created two RFC Destinations.

RFC Destination Type G, SAP_PROXY_ESR with path prefix /rep

RFC Destination Type H, PI_AEX with path prefix /sap/xi/engine?type=entry

now in ID, I have Integrated Configuration which by passes the ABAP stack and also I have the Receiver Determination, INterface Determinatiin, Receiver agreement and sender agreement for the old ABAP stack

Now when I use Proxy, can I use sender SOAP channel with XI protocol like in Java stack.

Or should I not use any comminication channel like the old XI/PI configurations

qhich is better approach

Accepted Solutions (0)

Answers (2)

Answers (2)

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Midhun,


RFC Destination Type G, SAP_PROXY_ESR with path prefix /rep

RFC Destination Type H, PI_AEX with path prefix /sap/xi/engine?type=entry

Since you are using dual stack and still want to maintain the old configuration, it would be advisable to maintain the type H only. Remove the type G with prefix /rep, that way the old configuration will still work (via XI adapter). Take note that the old config also requires two type T destinations, LCRSAPRFC and SAPSLDAPI.

If you want to use ICO, it is already mentioned by and .

Regards,

Mark

former_member190293
Active Contributor
0 Kudos

Hi Mark!

Just want to ask: does connection to ESR in transaction SPROXY remain working if we remove SAP_PROXY_ESR destination?

Regards, Evgeniy.

markangelo_dihiansan
Active Contributor
0 Kudos

Hi Evgeniy,

It will work if you have the type H and is specified in sxmb_adm too. Otherwise, it will result in a No connection to ESR error.

Regards,

Mark

former_member190293
Active Contributor
0 Kudos

Hi Mark!

Thanks for your answer. Didn't know about that.

Regards, Evgeniy.

markangelo_dihiansan
Active Contributor
0 Kudos

You are welcome. Still on PI 7.11, so the old config is used, but we can also use tne SOAP with XI protocol.

former_member182412
Active Contributor
0 Kudos
  • IF you create integrated configuration then create soap with xi 3.0 protocol
  • if you create classic configuration then use xi adapter
Former Member
0 Kudos

I created Integrated Configuration withh SOAP XI 3.0.

I have created RFC destination type H in ECC, with pipeline url, /sap/xi/engine?type=entry. I have also added the PI dual stack client number also

Will ICO work with  http destination type H?

ICO need http destination type G, right?

Former Member
0 Kudos

And we never used to use XI adapter for client proxy in XI. Client proxy didn't need sender com channel and sender agreement

former_member186851
Active Contributor
0 Kudos

In SM59

Create Two Connections of type G.

1.One For Sending to Soap Channel.

2.One for Sproxy display.

Then in PI Sender Soap Channel with XI 3.0 Protocol.

Check the below link

Former Member
0 Kudos

Thanks. That document is about single stack.

I was specifically asking for PI 7.3 with both options which should be selected

ICO or old configuration..

manoj_khavatkopp
Active Contributor
0 Kudos

The type 'H'  connection which you have created now points yo IE engine so you are good to go with classical config... And you don't need any sender channel.

If you want to go for ICO then you need to create type 'G'  pointing to AE engine.

Former Member
0 Kudos

I have SAP_PROXY_ESR, type G too with Java stack url

So I guess I can use both..

former_member190293
Active Contributor
0 Kudos

Hi Midhun!

In order to use proxy within your ICo you should create RFC destination of type "G":

And you should additionaly maintain Sender/Receiver ID in transaction SXMB_ADM (or just run transaction SXMSIF):

and set your previously created destination to RUNTIME parameter IS_URL in SXMB_ADM-Integration Engine Configuration with subparameter according to above setting:

With these settings your outbound proxy call will be sent to adapter engine, otherwise it will be sent to default destination (IS_URL without subparameter, which points to Integration Engine by default).

Regards, Evgeniy.