Configuring Document Stores
Integration Server uses document stores to save documents to disk or to memory while the documents are in transit or waiting to be processed. Integration Server maintains three document stores for published documents.
Default document store. The default document store contains guaranteed documents delivered to the default
Broker client for the
Integration Server. When
Integration Server retrieves documents delivered to its default
Broker client,
Integration Server places the documents in the default document store. Documents remain in the default document store until the dispatcher determines which triggers subscribe to the document. The dispatcher then moves the documents to the trigger queues for the subscribing triggers.
Trigger document store. The trigger document store contains locally published guaranteed documents that are delivered to a specific
webMethods messaging triggers. For each trigger,
Integration Server creates a queue for locally published guaranteed documents in the trigger document store. A guaranteed document remains in the trigger queue within the trigger document store until the server successfully processes the document.
Outbound document store. The outbound document store, sometimes called a client-side queue, contains documents waiting to be sent to the
Broker.
Integration Server places documents in the outbound document store when the configured
Broker is not available. When the connection to the
Broker is restored,
Integration Server empties the outbound document store by sending the saved documents to the
Broker.
Note:
The outbound document store is used for guaranteed documents published to the Broker only.
Using Integration Server Administrator, you can configure properties for each document store.