Configuring the Rate at which Integration Server Drains the Outbound Document Store
You can configure how quickly the server empties the outbound document store by setting the Maximum Documents to Send per Transaction parameter on the Settings > Resources > Store Settings > Edit Document Store Settings page. By default, this parameter is set to 25 documents. To empty the outbound document store more quickly, increase the number of documents sent per transaction. Keep in mind that the amount of memory needed to send documents increases with the number of documents sent for each transaction. If you want to use less memory to empty the outbound document store and can allow the outbound document store to empty more slowly, decrease the number of documents sent for each transaction. However, it is advisable to drain the outbound document store as quickly as possible because Integration Server performs more quickly and uses fewer resources when publishing documents directly to the Broker.
You only need to configure the rate at which Integration Server drains the outbound document store (client side queue) if:
Integration Server publishes documents to the
Broker.
Integration Server does not use the outbound document store when publishing documents to
Universal Messaging.
The outbound document store is enabled for
Integration Server. That is, the watt.server.publish.useCSQ parameter is set to “always”.
Tip:
You can monitor the number of documents in the outbound document store by checking the value of the CSQ Count field for the Broker connection alias on the Messaging > webMethods settings page.
To configure how quickly
Integration Server empties the outbound document store
1. Open the Integration Server Administrator if it is not already open.
2. Go to Settings > Resources.
3. Click Store Settings, and then click Edit Document Store Settings.
4. Under Outbound Document Store, in the Maximum Documents to Send per Transaction, type the number of documents the server should send from the outbound document store to the Broker for each transaction.
If there is no configured Broker, the Integration Server Administrator displays " Broker Not Configured" next to the field name.
5. Click Save Changes.