Trading Networks 10.3 | Administering and Monitoring B2B Transactions | Integration Server Administrator's Guide | Configuring Integration Server for webMethods Messaging | Configuring Document Stores | About the Trigger Document Store | Configuring the Trigger Document Store
 
Configuring the Trigger Document Store
When you configure the trigger document store, you specify the location of the store and the initial size of the store.
Note:
You do not need to configure the trigger document store if you use Universal Messaging as the messaging provider.
*To configure the trigger document store
1. Open the Integration Server Administrator if it is not already open.
2. In the Settings menu of the Navigation panel, click Resources.
3. Click Store Settings, and then click Edit Document Store Settings.
4. Set the Trigger Document Store fields as follows:
Field
Description
Store Location
The location of the trigger document store. By default, Integration Server saves the trigger document store in the following directory:
Integration Server_directory \instances\instance_name\DocumentStore
If you want to save the trigger document store in a different directory, specify the directory in this field. If the directory does not exist, the server creates it.
Important:
Make sure that you have write access to the specified directory and that the directory does not contain any characters considered illegal by your operating system.
Initial Store Size (MB)
The amount of disk space allocated to the trigger document store at start up. The trigger document store automatically increases when it receives data that exceeds the initial size. The default size is 35MB.
Important:
Make sure that there is enough free disk space on the Integration Server machine to accommodate the initial sizes of the default document store, the trigger document store, and the XA recovery store.
5. Click Save Changes.
6. If you changed one or more parameters that require server restart for the new value to take effect, restart Integration Server.
Note:
An asterisk (*) next to a parameter indicates that you need to restart the server for changes to take effect.