Skip to Content

Both ICO and Receiver Determination exist for a Sender Interface and sender service.

Hello Experts,

In our PI 7.31 SP08 system, I am able to create both ICO and Receiver Determination objects for the same sender interface and service. Can you confirm if this is standard behavior?

Also, before creating the ICO, the configuration overview for the Receiver Determination object, showed the Interface determination, agreements and channel. Whereas after creating ICO, ICO is being shown in the configuration overview.

How does this work at runtime, does the routing happen on java stack or ABAP stack?

Regards,

Diptee

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • Best Answer
    May 01 at 05:35 AM

    Hello Diptee,

    Since your PI 7.31 SP08 is dual stack, so you have two choices to process XI messages, one is dual stack mode, the other is AAE mode(java only). If you want to use the message processing with dual stack mode, i.e. with Integration server(ABAP) involved, you should create the classical configuration objects, e.g. receiver determination, interface determination and etc.

    If you want XI message processed only in java stack, then please configure the ICO, then the messages will be processed on AAE, no Integration Server(ABAP) will be involved. ICO - A configuration object which decides the sender,mapping,routing,receiver rules.

    http://castdemy.com/whats-the-different-between-ae-vs-aae-vs-aex/

    Please let me know if anything unclear.

    Best Regards,

    Liz

    Add comment
    10|10000 characters needed characters exceeded

    • Manoj K Diptee Sawant

      Yes exactly ..the old interfaces which are configured with type G port will run via ABAP stack and if you planning to use ICO then redirect it via changing the port to tRFC type.

  • May 01 at 06:47 AM

    Just too add here , even though you have created RD and ICO for the outbound idoc only one gets triggerd thid depends on the Port configured in Partner profile in the backend ECC system if its tRFC port then ICO gets triggerd if Type G then classical .

    Add comment
    10|10000 characters needed characters exceeded