Endpoints can receive messages from external systems (such as BizTalk, TIBCO, etc). To ensure those messages can be handled correctly by NServiceBus, additional information might be required which are otherwise provided by NServiceBus automatically.
Depending on the serializer used by the receiving endpoint, that information might also be provided in other ways.
Embedding type info in the message body is currently supported by the following serializers
To visualize messages from third party systems correctly within ServiceInsight, additional headers are necessary
- NServiceBus.ConversationId If not provided, then the external message won't be included in the conversation it started. ConversationId will be generated though for all the following messages sent using NServiceBus.
- NServiceBus.OriginatingEndpoint Name of the third party endpoint sending the message, for e.g. BizTalk.ProcessOrder
- NServiceBus.OriginatingMachine Server where the third party endpoint is located, for e.g. BizTalkServer