Database Reference
In-Depth Information
•
UseRavenTimeoutPersister()
: Using RavenDB to store Timeout Man-
ager
•
DisableTimeoutManager()
: As Timeout Manager is on by default for
server roles, use this method to turn off Timeout Manager
The gateway persister
Another persister for NServiceBus is the gateway pieces of NSB; see
ht-
of a gateway example can be found at
https://github.com/Particular/NSer-
viceBus.Msmq.Samples
.
The persister will keep track of message IDs for duplication.
Some persisters that are offered are as follows:
•
UseRavenGatewayPersister()
: This uses the RavenDB message persist-
ence via the gateway.
•
UseRavenGatewayDeduplication()
: This uses RavenDB for message
deduplication via the gateway.
•
RunGateway()
: This is used as a configuration to run the gateway. By default,
a gateway will use RavenPersistence (see the
GatewayDefaults
class).
•
UseInMemoryGatewayPersister()
: This uses the in-memory and volatile
message persistence via the gateway.
•
UseInMemoryGatewayDeduplication()
: This uses an in-memory mes-
sage deduplication for the gateway.
•
UseNHibernateGatewayPersister()
: This configuration will use the
NHibernate framework to persist the NSB gateway data.
•
DisableGateway()
: The gateway is turned on by default for the master role.
Call the
DisableGateway()
method to turn the gateway off.
By default, the RavenDB database will be used.
The subscription storage
The subscription storage is an IBus configuration to set where the subscription metadata
information will reside. It will define the subscription endpoint information in publish/
subscribe. The subscription storage keeps track of publish/subscribe endpoint information.
More information on subscription storage can be found at
http://docs.particular.net/NSer-
viceBus/publish-subscibe-configuration
.
This is not the messaging process itself, that is,
the publisher message being sent and saved, because that will be the transport setting, but
this is the information saved for NSB saying that specific messages are sent and received
by each subscription endpoint. Without this information, subscription message routing
