I hope somebody will point out that I'm missing something obvious. As part of my interface setup I try to group interfaces logically by assigning proper parties to them. However, I'm unable to set the sending party for an ABAP consumer proxy that sends a message to a PI 7.31 AEX (Java-only stack).
I researched the following:
Use parameters in the URL that is defined in the RFC destination for connecting and sending messages to PI: I'm using the URL as described in the online help Connecting the ABAP Backend to Advanced Adapter Engine. Manipulating the URL by adding the other parameters for specifying sender party etc. (see for example OSS note 856597 - FAQ: XI 3.0 / PI 7.0/7.1/7.3 SOAP Adapter) has no effect. I suspect that the parameter ximessage=true essentially means take the header data from the message and ignore any other parameters specified.
Modify the message via ABAP code prior to sending: Unless I'm missing something in the documentation (e.g. see Creating and Configuring Service Providers and Consumers - Protocols), there is no way to set sender party. I can see that I could set the receivers, but any sender attributes seem only available for read-only access.
I had given up as it seemed that nobody had a solution to this problem. However, as you replied to my really old question, I noticed in the related questions a link to ABAP Proxy with Party from 2009, where udo.martens provided the answer: Looks like you simply have to pick the party when you create the communication component by assigning the business system from the SLD, you can pick the party that you want to assign. Duh!
Looks like I did poor research as I had missed this question and answer (from 2009!) and in hindsight it seems that this is a spot that I should have looked at. Thanks for commenting on this old question as it caused me to take another look. I must admit that I haven't tested the solution as I just saw it and I don't want to update at this time all our configurations. However, I'm convinced it would work.
Can you please provide more details as to my understanding the config entry Configure Sender/Receiver ID cannot be used to change message parameters. Instead the parameters are used to drive other configuration options for specific messages or a group of messages like for example using different IS URL's (e.g. see OSS note 1334174 - Interface-specific IS_URL parameter) or setting up Event driven message processing.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.