BizTalk Server 2000 uses timeout values for database connection and command objects in the following two scenarios:
| � | When a transactional context in an orchestration schedule successfully completes.
-and-
|
| � | For all other database access by XLANG, which includes dehydration, rehydration, persisting at the beginning of a transactional context, and all other persistence. |
For each scenario, the connection and command timeouts are calculated as follows:
| � | When a transactional context in an orchestration schedule successfully completes:
| � | Transaction Timeout: Specified by the user in the BizTalk Orchestration Designer interface in the properties of the Transaction shape
| | � | Connection Timeout: Specified as a system default of 30 seconds, unless it is overridden by adding the following registry key value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler
Value: ADOConnectionTimeout | | � | Command Timeout: Equals the timeout value specified by the user for the Transaction Timeout |
|
| � | For all other database access by XLANG:
| � | Transaction Timeout: Uses the timeout configured in the XLANG Persistence Helper COM+ application, which is set to one hour by default
| | � | Connection Timeout: Specified as a system default of 30 seconds, unless it is overridden by adding the following registry key value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler
Value: ADOConnectionTimeout | | � | Command Timeout: Specified as a system default of 300 seconds, unless overridden by adding the following registry key value: HKEY_LOCAL_MACHINE\SOFTWARE\Microsoft\BizTalk Server\1.0\XLANG Scheduler
Value: ADOCommandTimeout |
|