Skip to content
Permalink
Branch: master
Find file Copy path
Find file Copy path
Fetching contributors…
Cannot retrieve contributors at this time
24 lines (16 sloc) 1.29 KB

The message persistence requires and adds these tables to your schema:

  1. jasper_incoming_envelopes - stores incoming and scheduled envelopes until they are successfully processed
  2. jasper_outgoing_envelopes - stores outgoing envelopes until they are successfully sent through the transports
  3. jasper_dead_letters - stores "dead letter" envelopes that could not be processed. See <[linkto:documentation/messaging/handling/dead_letter_queue]> for more information
  4. EnvelopeIdList - table type that is used by some of the functions listed below

and also these functions that are all used by the durable messaging in its "message recovery" functionality:

  1. uspDeleteIncomingEnvelopes
  2. uspDeleteOutgoingEnvelopes
  3. uspDiscardAndReassignOutgoing
  4. uspMarkIncomingOwnership
  5. uspMarkOutgoingOwnership

Managing the Sql Server Schema

In testing, you can build -- or rebuild -- the message storage in your system with a call to the RebuildMessageStorage() extension method off of either IWebHost or IJasperHost as shown below in a sample taken from xUnit integration testing with Jasper:

<[sample:MyJasperAppFixture]>

See this GitHub issue for some utilities to better manage the database objects.

You can’t perform that action at this time.