Setting up Machine B (the Web Server and Finder Service machine)

This is the server machine, and it has the following software configuration:

Windows 95 with Service Pack 1
DCOM for Windows 95
Microsoft Personal Web Server for Windows 95

On this machine, machine B, we'll set up the

ATLFinder.exe

COM server class, and we will set pointers to the ATLDept.dll
class that will be residing on machine C. To prepare the machine for serving ATLFinder objects, perform the following steps:

Copy Regsvr32.exe
into \Windows\System
directory if it's not already there.
Copy the ATL support DLL, atl.dll
, over to \Windows\System
directory.
Run regsvr32 atl.dll
.
Copy the ATLFinder.exe
file over to a working directory.
Run ATLFinder /RegServer
to create the registry entries.

This is all that's needed for ATLFinder. In order to create the link to the required ATLDept objects, we need to do the following:

Copy the ATLDept.dll
file over to the working directory.
Run regsvr32 ATLDept.DLL
.
Remove the ATLDept.dll
file.
Start Oleview.exe
, select ATLDept1 Class on the left pane, and the Implementation tab on the right pane.
Select the Inproc Server tab and remove the Path to Implementation content.
Select the Activation tab on the right pane, click the Launch as Interactive User check box, and enter in the IP address of machine C into the Remote Machine Name edit.

This machine is now ready to support calls to ATLFinder1 classes and remote calls to ATLDept1 classes. Before moving on to set up machine C, it's a good idea to test the setup between machine A and machine B. To do this, we again acquire the assistance of

Oleview.exe

Start the ATLFinder server on machine B by typing ATLFinder /Server
at the command line.
Start Oleview.exe
on machine A.
Find the ATLFinder1 Class entry on the left pane and double-click on it.

If everything is setup correctly, after a little delay, you should see ATLFinder being expanded on the left pane with all its interfaces exposed. The ATLFinder1 Class entry is also in bold to indicate that an instance has been created successfully.

Using Object Viewer, you can then select the Object menu and Release Instance to release the selected instance.

This concludes and confirms the setup of machine B.

In actual deployment, under certain design circumstances, one may need to install the middle tier server components (such as ATLFinder) repeatedly on different systems. In these cases, of course, the Setup toolkit that comes with Visual C++ 5.0 may be used to create a setup script which can perform all of the above for us when the server object is installed on the system.