There are two reasons you would run the executable client package:
Essentially, after you execute the client package program on
the client computer, the MTS components will be registered. If it is a VB developer
machine, VB projects can reference the MTS component like they would any other
COM object. If it is a Web server that supports COM through some scripting mechanism,
such as Active Server Pages or Cold Fusion, the MTS object will be available to
any server-side script. If the computer is a Windows machine that will be running
Win32 software that makes calls to the MTS object, it will contain all the necessary
configuration. Whatever the reason, configuring the client is easy.
STEP BY STEP
16.2 Configuring the Client
-
The first thing that must be done is to locate the client package. The executable
for the client package will always be in a directory called Clients, which will
be in the same path as the PAK file that was exported by the Export Wizard. By
default, the name of the executable will be identical to the name of the PAK file
(except, of course, the extension will be .EXE).
-
Run the executable program.
-
A dialog box will briefly appear indicating that files are being copied.
-
After the last file is copied, the client configuration is done.
After the client package is complete, a few changes can be observed
in the system. First, the Add/Remove Program Properties control panel will contain
a new listing named Remote Application. This listing has the name of the package
appended to it. Figure 16.2 shows the Add/Remove control panel for a client that
has three MTS client packages installed. This can be used to uninstall the client
package if there is a need to do so.
FIGURE 16.2 This dialog box reveals that the client computer can use components
in the IRSC Components, MTSNEW, and Pubs Components packages.
Note that it is common for the package to undergo many changes from the time
it is first created. Each time a change is made that will affect clients—for
example, if more components are added or new interfaces are added to existing
components—the client package will have to be exported again. Also, the
client package will need to run on any client workstation that uses it again.
It is not necessary to uninstall the existing client package because any new versions
of it that are executed will automatically replace the old one. The number of
entries in the Add/Remove Program Properties control panel will not increase because
new versions of the client package are used to update the system.
