Oracle9i Release 9.0 New Features in Oracle Services for Microsoft Transaction Server

Oracle Services for Microsoft Transaction Server releases prior to 9.0 required a Windows NT service named Oracle Service for MTS to be created for each Oracle database server. This enabled the database to participate in Microsoft Transaction Server transactions. However, only one Oracle Service for MTS was supported for each database server. The Oracle Service for MTS is no longer required. All code and logic to enable database servers to participate in Microsoft Transaction Server transactions are now embedded in the Microsoft Transaction Server application process.

Because of this, this release offers:

Better performance

Communication between the Microsoft Transaction Server application and the Oracle Service for MTS is no longer required.

High availability

The database server is no longer dependent on the Oracle Service for MTS. Previously, if the Oracle Service for MTS was stopped, the database server was unable to participate in Microsoft Transaction Server transactions.

Improved scalability

The code that enables a database server to participate in Microsoft Transaction Server transactions is now embedded in each Microsoft Transaction Server application process.

Minimal configuration is necessary

The Oracle MTS Recovery Service is automatically created and configured on each computer in the middle tier during Oracle Services for Microsoft Transaction Server installation.

Changes have also been made to the call level interface (CLI) that starts the enlistment of Oracle connections in Microsoft Transaction Server-started transactions. OraMTSSvcEnlist() and OraMTSSvcEnlistEx() are provided for backward compatibility only. In addition, there are three new APIs:

The Oracle Manager for MTS Services snap-in for the Microsoft Management Console is no longer included. This snap-in was required to create the Oracle Service for MTS in releases prior to Oracle9i release 9.0.