Your server application's executable file is copied into a directory specified by the administrator installing the application. For a Windows NT Server application, this directory must be on the computer on which you are running the installation program, though this computer need not be a Microsoft Exchange Server computer.
For example, if you want to run a gateway on Computer A, you must run the setup program and install the executable file on Computer A, even though Computer B may be the Microsoft Exchange Server computer to which you will connect the gateway.
An SMTP gateway called Pro-SMTP is written by the fictitious company Pro-Electron, Inc. When this gateway is installed to a Microsoft Exchange Server called Proton, the gateway name Pro-SMTP is used as the Extension-Name, and the files are to be used on the i386 (Intel) platform.
In this installation, the setup program copies both PROADMIN.DLL (the Administrator extension DLL) and PROADMIN.HLP (the Help file for the gateway's extension property pages) to \\PROTON\ADD-INS\PRO-SMTP\I386. The proxy generation DLL for this gateway is copied to the \\PROTON\ADDRESS\PRO-SMTP\I386 directory.
The gateway setup program displays a dialog box so the administrator can choose the destination of the gateway's executable file. This destination directory is saved into the Windows NT Registry on the server application's computer.
Note The Common-Name attribute of a directory object is a concatenation of the values used for Extension-Name and Platform. For example, the gateway in the preceding example would have a Common-Name of Pro-SMTP:i386, and the Microsoft Exchange Server Administrator program would recognize it by this name only. Therefore, your installation program must use the Extension-Name and Platform values consistently when it copies files and when it is imports the application's directory object.
The GWSETUP.C and MBSETUP.C sample installation files first build a list of files to be copied, and then call the CopyFilesInCopyList function of the Setup toolkit.