|Oracle® Services for Microsoft Transaction Server Developer's Guide
10g Release 1 (10.1) for Windows
Part Number B10114-01
This appendix describes differences between using Oracle Services for Microsoft Transaction Server (OraMTS) on Windows operating systems.
This appendix contains these topics:
Note:Oracle Services for Microsoft Transaction Server configuration is the same on Windows 2000, Windows NT, Windows XP and Windows Server 2003.
Table A-1 Microsoft Transaction Server Differences on Windows Platforms
|Feature||On Windows NT||On Windows 2000||On Windows XP and Windows Server 2003|
|Microsoft Transaction Server
||Microsoft Transaction Server is an add-on.||The functionality of Microsoft Transaction Server is integrated within the operating system as a COM+ server (COM+ transactions) and as a .NET server.||The functionality of Microsoft Transaction Server is integrated within the operating system as a COM+ server (COM+ transactions) and as a .NET server.|
|Microsoft Management Console||You must obtain the Microsoft Management Console from Microsoft Corporation.||Microsoft Management Console is automatically included.||Microsoft Management Console is automatically included.|
|Component object model||COM is the name.||COM+ is the name.||COM+ is the name.|
|Installing and configuring transactional applications||Choose Start > Programs > Windows NT 4.0 Option Pack > Microsoft Transaction Server > Transaction Server Explorer||Choose Start > Programs > Administrative Tools > Component Services||Choose Start > Programs > Administrative Tools > Component Services|
|Transaction Coordinator||Microsoft Distributed Transaction Coordinator (MS DTC) is the name.||Microsoft Distributed Transaction Coordinator (MSDTC) is the name.||Microsoft Distributed Transaction Coordinator (MSDTC) is the name.|
|Microsoft Application Demo||The Microsoft application demo, a Visual C/C++ bank sample application, is available with Microsoft Transaction Server.||The Microsoft application demo is not shipped.||The Microsoft application demo is not shipped.|
If transaction requests are timing out before completing, the transaction timeout parameter may be set too low. Increase the transaction timeout parameter to ensure that transactions have enough time to complete.
To increase the transaction timeout parameter on Windows 2000:
Go to the Windows 2000 computer on which Microsoft Transaction Server is installed.
Choose Start > Programs > Administrative Tools > Component Services.
The Component Services window appears.
Double-click Console Root in the Component Services window.
Double-click Component Services.
Right-click My Computer.
A menu appears with several options.
The My Computer Properties dialog box appears.
Choose the Options tab.
Enter a value in the Transaction Timeout field and click OK.
The transaction timeout value is increased. For most environments,
60 seconds may be enough. However, if the transaction is competing with numerous concurrent transactions, this value may be too low.