In this chapter, we will look at how to set up the MTS environment, how to
obtain MTS, how to install it, and a few installation options. We will also look at both hardware
and software platform requirements.
Configuring
a Server to Run MTS
MTS 2.0 is bundled with Windows NT 4.0 in the Windows NT 4.0 Option Pack and
is available as a free download over the Internet or for purchase in a CD format. It will run
on Windows 95 or Windows NT. To run MTS on Windows 95, you must have previously installed DCOM
support for Windows 95. For Windows NT, MTS requires at least Service Pack 3, which is included
with the Option Pack. This chapter will limit its focus to using MTS on Windows NT Server.
Before installing MTS on a Windows NT Server, verify that at least 30 megabytes
of disk space are available and that the server has at least 32 megabytes of RAM. The Windows
NT 4.0 Option Pack also comes with Internet Information Server (IIS) 4.0 and other components
such as Microsoft Message Queue. Even though MTS can be installed alongside these Option
Pack components, it is also capable of being used independently.
Installing MTS
Whether you are running the setup program from the Internet or from CD, installation
is the same. First you must consider how MTS will be used for your application. More particularly,
your decisions will depend on how clients will be using your Transaction Server components.
For example, if your application will be a distributed Windows application in which the client is using
a standard Windows program that will be communicating with your components across the network, then
it is not necessary to install IIS. The same holds true if the client using your components
will run them on the same machine as MTS. However, you might be using MTS to house components that
will be used in an Internet or Intranet application. In this case, it is typical to install IIS alongside
MTS.
The only exception to this is when the MTS components will be called remotely
by the IIS machine. In either case, MTS installs relatively easily (see Figure 15.2).
FIGURE 15.2 MTS fits into an all Windows environment or a Web environment seamlessly
Of course your installation might encompass a combination of these elements. For
example, although the primary client interface might be Web-based, the Web server will be running
remotely and will be calling your component through DCOM. Occasionally you may need to provide
access via the Web and through networked Windows programs to your components. An application
might be designed in this way in order to separate user activity from administrative activity.
However, adding and removing Option Pack components at a later date is a painless process.
Installation Options
The Option Pack provides you with three installation options that determine
which MTS components are installed:
-
Minimal. The Minimal installation will install the MTS runtime environment and
the MTS Explorer.
-
Typical. Typical installations install everything in the Minimal installation along
with the core documentation for MTS.
-
Custom. Custom installation allows you to install the documentation geared for
developers as well as samples to help in the development process.
The steps involved in installing MTS include the following:
STEP BY STEP
15.1 Installing MTS Without Other Option Pack Components
The MTS portion of the Option Pack installation is simple, consisting of only
a few steps:
-
Start the installation program from the CD or from the Internet.
-
Choose the type of installation you want. If you will not be installing other
Option Pack components, choose custom and deselect every check box including the
one for MTS (see Figure 15.3).
FIGURE 15.3 Deselecting all components allows you to add only the components
you want and their dependent components
-
Select the Transaction Server component but do not check the check box. While
it is selected, click on the Show Sub-components button.
-
Check all three check boxes (see Figure 15.4). Transaction Server Core Components
correspond to the components associated with a Minimum Install. Transaction Server
Core Documentation corresponds to a Typical install. Notice that core documentation
includes documentation for the Administrative features of MTS. If you want documentation
for development, it is available only by selecting a Custom install and checking
the Transaction Server Development option.
FIGURE 15.4 All three Transaction Server Components are relevant to the developer
-
Click OK. Notice that many of the other Option Pack components are automatically
checked. This is to be expected because MTS is dependent on some of these components.
-
Click Next to finish the installation.
