Tuning Parameters

Tuning Parameters

This topic is related to the Base EDI adapter, which has been deprecated in BizTalk Server 2006 R2. The Base EDI adapter can be used in upgrade scenarios, but for new installations of BizTalk Server 2006 R2, use the native EDI and AS2 functionality. For more information, see BizTalk Server 2006 R2 EDI and AS2 Processing.

The tuning parameters enable you to fine-tune the operations of the BizTalk Server 2006 Base EDI adapter. Many of these parameters refer to memory usage—for example, the cache to allocate to each partner, or the maximum number of translation threads that can run concurrently.

How best to tune the parameters described below depends on the structure of your deployment and the types of operations it performs. In most cases you will have to experiment with the settings to tune your deployment for optimal performance.

The tuning parameters are managed from three different locations: from the EDIBTSmmc.msc snap-in console (accessible from the <drive>\Program Files\Microsoft BizTalk Server 2006\EDI\Subsystem folder), from the BizTalk Server 2006 Administration Console, and from the Windows registry.

Use this To do this

Check send queue every

Enter the duration of a cycle (in seconds). The Base EDI adapter checks the send queue for outbound documents every X seconds. The Base EDI adapter usually waits some time before it starts sending documents (to reduce communication cost).

Maximum Mapping errors

Enter the value for the maximum number of translation errors the Base EDI adapter can report for one interchange. Setting this number higher than 1 means that the Base EDI adapter does not stop checking a document after the first error has been detected.

Cache Partners

Enter the number of partners you want to cache. The Base EDI adapter uses the cache to speed up access to partner details. You should set this to the number of partners you communicate with, although it consumes some memory. The Base EDI adapter uses a statistical caching mechanism. The most frequently used partners are most likely to stay in the cache.

Cache Custom Numbers

Enter the number of custom numbers you want to cache. The Base EDI adapter uses the cache to speed up access to custom number details. The Base EDI adapter uses a statistical caching mechanism. The most frequently used custom numbers are most likely to stay in the cache.

Maximum Number of translate threads

(EDIBTSmmc snap-in) Specifies the number of concurrent translation threads that are available to translate to and from native EDI format. The more concurrent translation threads you make available, the faster translations will be performed when handling large numbers of documents. You should configure this setting in accordance with the amount of available memory, your processor speed, and the maximum number of files that can be open at the same time (each translate session opens two files).

Database pool size

(EDIBTSmmc snap-in) Specifies the number of simultaneous connections that can be used by the BizTalk EDI server to connect to the EDI database.

BatchSize

(BizTalk Server Administration Console) Specifies the maximum number of documents that will be sent from the Base EDI adapter to the EDI subsystem in a single session. Setting this to a higher number reduces processing overhead in BizTalk Server, thus increasing the speed at which documents are sent. However, setting BatchSize to a large number reduces the effect of concurrent transmissions, which can slow down communications.

Sessions

(BizTalk Server Administration Console) Specifies the number of concurrent transmitting sessions that will be available for sending documents from the Base EDI adapter to the EDI subsystem. The more concurrent transmitting sessions that are available, the faster documents will be passed between the Base EDI adapter and the EDI subsystem.

BTSSubmit

(Windows Registry - HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\EDI Subsystem for Microsoft BizTalk Server\6.0) Specifies the number of concurrent transmitting sessions that will be available to send documents from the EDI subsystem to the Base EDI adapter. The more concurrent transmitting sessions that are available, the faster documents will be passed between the EDI subsystem and the Base EDI adapter.

FileFetch

(Windows registry) Specifies the number of concurrent file connector sessions that will pick up documents from the file system. The more concurrent file connector sessions that are available, the faster documents will be picked up and processed from the file system.

FileSubmit

(Windows registry) Specifies the number of concurrent file connector sessions that will submit documents to the file system. The more concurrent file connector sessions that are available, the faster documents will be processed and submitted to the file system.

FileSubmitBatchSize

(Windows registry) Specifies the number of files that will be sent in a single session by the file connector. Setting this to a higher number may reduce overhead in connecting to file systems, thus speeding up transmissions. However, setting FileSubmitBatchSize to a large number reduces the effect of concurrent transmissions, which can slow down communications.

Community Additions

ADD
Show:
© 2016 Microsoft