Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Update routing_content_core_6.partial.md #4124

Merged
merged 9 commits into from
Oct 22, 2019
Merged

Update routing_content_core_6.partial.md #4124

Show file tree
Hide file tree
Changes from 6 commits
Commits
Show all changes
9 commits
Select commit Hold shift + click to select a range
b2addba
Update routing_content_core_6.partial.md
seanfarmar Nov 19, 2018
18cea95
Update routing_content_msmqtransport_[1,).partial.md
seanfarmar Nov 19, 2018
0d2ec81
Update routing_content_core_[,6).partial.md
seanfarmar Nov 19, 2018
0ccd2d1
Update routing_content_core_6.partial.md
seanfarmar Nov 20, 2018
af38cb1
Update routing_content_msmqtransport_[1,).partial.md
seanfarmar Nov 20, 2018
5f7202a
Update routing_content_core_[,6).partial.md
seanfarmar Nov 20, 2018
0f02e6c
Update routing_content_msmqtransport_[1,).partial.md
seanfarmar Nov 21, 2018
c282f04
Update routing_content_core_6.partial.md
seanfarmar Nov 21, 2018
b93eaac
Multi-line note
mauroservienti Oct 22, 2019
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Jump to
Jump to file
Failed to load files.
Diff view
Diff view
6 changes: 5 additions & 1 deletion transports/msmq/routing_content_core_6.partial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -2,9 +2,13 @@ Mapping the logical destination to the physical address containing the queue and

The preferred way of configuring the physical routing is via the instance mapping file.


## Instance mapping file

NOTE: When using instance mapping:
* The settings will have no effect on **audit and error queues**.
mauroservienti marked this conversation as resolved.
Show resolved Hide resolved
* **publish/subscribe**: The publisher will be publishing messages only to the endpoint instances that have subscribed to the events, ignoring the settings in the mapping file (the adress of the subscriber that was provided in the subscription messgae will be used).
* **publish/subscribe**: The publisher's instances should be entered in the Instance mapping file (so the subscribers can send a subscription message to them)

The instance mapping file is a simple XML file that has to be located either on a local hard drive or a network drive. When using MSMQ as the transport, NServiceBus will automatically look for an `instance-mapping.xml` file in `AppDomain.BaseDirectory`.

NOTE: When running under ASP.NET the `instance-mapping.xml` file may not be located in `AppDomain.BaseDirectory`. In this case specify the path using the [`FilePath`](#instance-mapping-file-filepath) setting.
Expand Down
3 changes: 2 additions & 1 deletion transports/msmq/routing_content_core_[,6).partial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,5 +1,6 @@

Host name of the machine running each endpoint can be specified directly in the message-endpoint mapping configuration section by adding `@machine` suffix.

snippet: endpoint-mapping-msmq

When using MSMQ, if there is no `@machine` part, NServiceBus assumes the configured endpoint runs on a local machine.
When using MSMQ, if there is no `@machine` part, NServiceBus assumes the configured endpoint runs on a local machine.
5 changes: 5 additions & 0 deletions transports/msmq/routing_content_msmqtransport_[1,).partial.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -5,6 +5,11 @@ The preferred way of configuring the physical routing is via the instance mappin

## Instance mapping file

NOTE: When using instance mapping:
* The settings will have no effect on **audit and error queues**.
* **publish/subscribe**: The publisher will be publishing messages only to the endpoint instances that have subscribed to the events, ignoring the settings in the mapping file (the adress of the subscriber that was provided in the subscription messgae will be used).
seanfarmar marked this conversation as resolved.
Show resolved Hide resolved
* **publish/subscribe**: The publisher's instances should be entered in the Instance mapping file (so the subscribers can send a subscription message to them)
seanfarmar marked this conversation as resolved.
Show resolved Hide resolved

The instance mapping file is a simple XML file that has to be located either on a local hard drive or a network drive. When using MSMQ as the transport, NServiceBus will automatically look for an `instance-mapping.xml` file in `AppDomain.BaseDirectory`.

NOTE: When running under ASP.NET the `instance-mapping.xml` file may not be located in `AppDomain.BaseDirectory`. In this case specify the path using the [`FilePath`](#instance-mapping-file-filepath) setting.
Expand Down