Home/ Questions/Q 3849102
In Process

The Archive Base Latest Questions

Editorial Team
  • 0
Asked: 2026-05-19T16:48:11+00:00

I have an orchestration called MyUsefulOrch , hosted in an application MySharedApp . MyUsefulOrch

  • 0

I have an orchestration called MyUsefulOrch, hosted in an application MySharedApp.

MyUsefulOrch has an inbound messagebox-direct-bound port to receive requests, and after doing some useful work, an outbound messagebox-direct-bound port to send a message to the caller.

Now, I have another orchestration called MyCallerOrch which wants to benefit from the useful processing provided by MyUsefulOrch. However, MyCallerOrch is hosted in a different application, MyCallingApp.

I do not want to have any references to the assembly which contains MyUsefulOrch from MyCallerOrch.

My problem now is making sure I can send a message to MyUsefulOrch from MyCallerOrch and receive a response from it.

Ahah! Correlation should do the trick! But how do I go about getting correlation to work in this scenario?

For example:

  • Would I put a correlation id in a property schema and stuff a guid into the message context under this property from MyCallerOrch just before sending it to the messagebox?
  • How do I ensure that MyCallerOrch receives only the responses it needs to receive from MyUsefulOrch?
  • Do I need to put the correlation id value into the message body of the messages which are sent between the two orchestrations?

I would greatly appreciate any help, ideally as descriptive as possible, about how to acheive this.

Many thanks in advance.

Share

Leave an answer

You must login to add an answer.

Need An Account,

1 Answer

  1. Editorial Team

    I think you are pretty much on the right track

    Since the 2 applications are going to send messages to eachother, if you use strongly typed schemas, both apps will need to know about the schemas.
    In this case recommend that you separate the common schemas off into a separate assembly, and reference this from both your orchestration apps.
    (Schemas registered on the Server must have unique XMLNS#ROOTs, even across multiple applications)

    However, if you really can’t stand even a shared schema assembly reference, you might need to resort to untyped messages.

    Richard Seroter has an example here

    His article also explains a technique for auto stamping a correlation GUID on the context properties.

    Edit : Good point. It is possible to promote custom context properties on the message without a Pipeline – see the tricks here and here – this would suffice to send the context property to MyUsefulOrch and similarly, the Custom context could be promoted on the return message from within MyUsefulOrch (since MyUsefulOrch doesn’t need any correlation). However I can’t think how, on the return to MyCallingOrch that the custom context property can be used to continue the “following correlation”, unless you add a new correlating property into the return message.

    • 0