Tuesday, May 15, 2018

MTS Explorer snap-in

Microsoft Transaction Server (MTS) is configured using the MTS Explorer snap-in, a graphical management tool used to deploy and manage solutions across a network. MTS Explorer provides developers and administrators with a complete view of all the components deployed within a solution.
To open Microsoft Transaction Server snap-in
  1. On the Start menu, point to Programs, Microsoft Internet Information Server, Microsoft Transaction Server, and then click Transaction Server Explorer.
  2. The Microsoft Transaction Server snap-in opens in Microsoft Management Console.
  3. The Microsoft Transaction Server Explorer includes point and click wizards for assembling and configuring a solution from pre-built packages and components. A package is a set of components that perform related application functions.
These wizards include:
  • Package Wizard. To create packages.
  • Component Wizard. To add components to a package. The wizard either lists all components already registered in the system, or enables the administrator to register new components.
  • Add Server Wizard. To .export a package to a remote server, dynamically adding servers to a distributed solution.
  • Add Clients Wizard. To add client systems to a distributed solution.
  • Configure Wizard. To set the transactional properties of components deployed within a package.
  • Security Wizard. To configure the security attributes of components and packages.
The Microsoft Transaction Server Explorer includes the following GUI utilities:
  1. Transaction Lists. To list the properties of the running transactions.
  2. Transaction Statistics. To track transaction performance.
  3. Trace Messages. To view trace messages.
The following is an example of a standard transaction that occurs in the banking industry.

Architecture

The bank application consists of four components:
  1. Account. Uses ODBC calls to modify an account record in a single database.
  2. MoveMoney. Performs debit, credit, and transfer operations against different bank databases.
  3. Receipt. Generates a unique ED number for each bank transaction.
  4. UpdateReceipt. Allocates ranges of unique ED numbers for receipts.

Transaction

This is an example of a simple application getting all of the benefits of a sophisticated, high-end server infrastructure—including transactions, location transparency, thread and process management, and database connection pooling—through integration with Microsoft Transaction Server (MTS).
  • The client initiates a bank transaction by invoking MoveMoney.
  • MoveMoney invokes an Account component for each database that it needs to modify. MoveMoney'also invokes the Receipt component for each bank transaction.
  • MTS makes sure that the work of all these components executes as a single unit (or transaction), even though these are different components that could be written in different languages.
    Each one of these components is built as a simple, single-user ActiveX component, yet executes as "multiuser" through MTS thread and process management services.
  • The Account Components access the SQL Server database via MTS ODBC resource dispensers, a mechanism for high-performance database access.

No comments:

Post a Comment

Featured on Text Engineer

How to Select A Web Hosting Provider?

Most of us face difficulty choosing when we have too many options. Well, talking about IDEAL, do you believe there is IDEAL web host...