Additional Header Informations in Sender-Proxy for XI Routing

[Former Member]

Hi All,

I'm using an ABAP-Proxy to send data to XI. There should be a routing rule to decide, which Business System will be the receiver of the message.

As the size of the Message is quite large I'd like to do without Message Mapping. But in this case I don't have the needed information for routing in the XI Message Content.

Is there any possibility to fill some context objekt in the sender proxy, which I can use for the rounting in XI. I found some parameters like URLParamOne, URLParamTwo, .... or HeaderFieldOne, HeaderFieldTwo, ...

Does anybody know, whether I have access to any of these informations in my sender proxy.

Thanks a lot for your help

Barbara

[MichalKrawczyk · Accepted solution]

Hi,

>>URLParamOne, URLParamTwo, .... or HeaderFieldOne

these are not for XI adapter but for plain http adapter

XI adapter does not have any Adapter-Specific Message Attributes

as far as I remember

that you can do is to use conditions in receiver determination

this is the proper way of determining the receiver system

Regards,

Michal Krawczyk

[Former Member · Accepted solution]

Michael,

thanks for your reply.

I was afraid that the parameters are only valid for plain http adapter.

Unfortunatily the field with the routing criteria is not available within the message content.

Another question: Is it possible add information about receiver business system already in the sender proxy?

If no, I have to add another field to the sender interface which i will use for routing. Then I have to apply a message mapping where this field is getting suppressed.

Barbara

[former_member181962 · Accepted solution]

Hi Barbara,

What is the routing rule for your case?

You said there are no fields in the payload which determine the routing.

In this case, you can see if one of the existing fields in the outbound interface can be used to hold this information.

If there is no such possibility, as you said, you have to add a field to the outbound interface and you have to REGENERATE and REIMPLEMENT the proxy , as the structure of the interface got changed.

And one more thing, for determining the Receiver, there is no need to do mapping.

YOu can simple specify the condition in the receiver determination

http://help.sap.com/saphelp_nw04/helpdata/en/26/5ccd3bb4560f01e10000000a11402f/content.htm

Regards,

Ravi

[Former Member · Accepted solution]

Ravi,

thanks a lot for your reply.

Unfortunatly there seems to be no possibility to add these infomation tho the "Proxy-Header".

Yes, I will enhance my sender interface with a field that contains the needed information.

I don't need t he mapping for receiver determination, but to suppress this additional field in the receiver interface. Not a really elegant solution, but however, there seems to be no other sulution.

Thanks to everybody for the quick and qualified help

Barbara

[former_member181962 · Accepted solution]

Hi Barbara,

I think there is a way (Using File Content Conversion in Receiver File adapter) to have only the fields that we wanted.

YOu can try to implement that solution in order to avoid the mapping (Just to eliminate the extra field)

http://www.riyaz.net/blog/xipi-file-content-conversion-for-complex-structures/

Regards,

Ravi

[Former Member · Accepted solution]

Ravi,

I added another field to each the line of my message interface. This contains relevant information for routing, but is not needed in the receiver file.

In the file adapter I give to this field the length 0. So it isn't written into the file.

This is my configuration

LINES.fieldFixedLengths 180,0

LINES.fixedLengthTooShortHandling Cut

LINES.endSeparator '0x0D''0x0A'

thanks a lot

Barbara

[Former Member]

Kindly check this [http://help.sap.com/saphelp_nw04/helpdata/en/ba/f21a403233dd5fe10000000a155106/frameset.htm]

[former_member200962]

I found some parameters like URLParamOne, URLParamTwo, .... or HeaderFieldOne, HeaderFieldTwo, ...

I think these are Adapter Secific Message Attributes (ASMA)....and can be used in the Communication Channel in XI/PI.....a UDF in Message Mapping, a logic in XSLT helps in configuring these at runtime....not sure if these can be used in Proxy.