Skip to Content
author's profile photo Former Member
Former Member

One sender - two receivers - same Message-ID?

Hi,

I don´t know if it is possible to send a message (which is, as you know identified by its Message-ID) to two receivers where at least one receiver has to keep the Message-ID of the xi-incoming message. This is necessary because it has to be used as part of the receiver-filename.

We work with triggerfiles, which identify in which sequence the Messages have to be processed at the receiver system. If you use more than one interface determination, for each receiver an new Message-ID is generated. This is what I want to prevent.

Does anyone know if this is possible using a business process. (XI3.0 SP17)

If yes, what is it to look like? I´m thinking about one receiver and two senders (in bp-design) :).

Regards,

Thomas

Add a comment
10|10000 characters needed characters exceeded

Assigned Tags

Related questions

1 Answer

  • author's profile photo Former Member
    Former Member
    Posted on Dec 04, 2007 at 04:48 PM

    so you wan't to generate two messages with same Message ID?

    or if your requirement is something else ,please explain that

    Thanx

    Aamir

    Add a comment
    10|10000 characters needed characters exceeded

    • Former Member Vijayashankar Konam

      Hi VJ,

      I think your doubts are reasonable, as this doesn´t fit the "Exactly once"-idea of messages. As soon as the bpe picks up the Message, you got no chance to save the original Message-ID. I just designed a little process to give it a try, but it didn´t work (i. e. the two new Message-IDs appeared for the BP-outgoing messages).

      Why I want to use it? This would be an addon for a more or less complex Szenario, which we cannot change without a redesign of the hole szenario ...

      I think we´ll have to let the application server generate the Message twice with different receiver agreements. Sounds ugly.

      Thank you for confirmation.

      Best regards

      Thomas

      Best regards

      Thomas

Before answering

You should only submit an answer when you are proposing a solution to the poster's problem. If you want the poster to clarify the question or provide more information, please leave a comment instead, requesting additional details. When answering, please include specifics, such as step-by-step instructions, context for the solution, and links to useful resources. Also, please make sure that you answer complies with our Rules of Engagement.
You must be Logged in to submit an answer.

Up to 10 attachments (including images) can be used with a maximum of 1.0 MB each and 10.5 MB total.