Appendix D Server Extensions for Microsoft FrontPage

This appendix describes using server extensions on your iPlanet Web Server that provide support for Microsoft's FrontPage. These extensions provide the internal server-side support you need if you are using FrontPage webs.

• Overview
• Downloading the Extensions
• Installing FrontPage Server Extensions
• Further Information

• When a user moves a page between folders in a FrontPage web, the extensions automatically update all links to that page from every other page in the web.
• You can specify which users have permission to administer, author or browse a FrontPage web.
• When FrontPage web users participate in a discussion group, the extensions take advantage of the available WebBots to maintain an index of links to discussion articles, tables of contents, and search forms.

• Types of FrontPage Webs
• Domain Names And FrontPage Webs


• Security Issues

• As private domain names, such as www.mycompany.com. These are usually implemented as virtual servers on the same physical server machine using multi-hosting. Private domain name customers each get their own root web and have the option of creating sub-webs.
• As a common or shared domain but with private virtual servers, as in www.mycompany.myprovider.com, where myprovider.com is a shared domain and www.mycompany is a private virtual server. Private virtual server customers on a shared domain each get their own root web and have the option of creating sub-webs.
• As a URL on an Internet service provider's server machine, as in www.myprovider.com/mycompany. URL customers get a single sub-web.

• FrontPage 97 Server Extensions (version 2.0):

• [NT] You can download an executable file.
• [Unix/Linux] You can download from Ready-to-Run Software's web site an install script and a set of server extensions. Download two tar files for your platform (for Solaris, they are vt20.solaris.tar.z and wpp.solaris.tar.z, which is part of the WPP Kit Software).
• [Unix/Linux] You can download from Microsoft's web site an install script and a set of server extensions. Download two tar files for your platform (for Solaris, they are vt20.solaris.tar.z and wpp.solaris.tar.z, which is part of the WPP Kit Software.)
• FrontPage 98 Server Extensions (version 3.0):

• [NT] You can download an executable file.
• [Unix/Linux] You can download from Ready-to-Run Software's web site an install script and a set of server extensions. Download the fp_install.sh file and the tar file for your platform (for Solaris, it is fp30.solaris.tar.z)
• [Unix/Linux] You can download from Microsoft's web site an install script and a set of server extensions. Download the fp_install.sh file and the tar file for your platform (for Solaris, it is fp30.solaris.tar.z).
• FrontPage 2000 Server Extensions (version 4.0):

• [NT] You can download an executable file, fp2kserk.exe, which gives information on how to set up and use a FrontPage-extended web. You can download a set of server extensions from the Microsoft web site, fpse2k_x86_ENG.exe.
• [Unix/Linux] You can download an install script and a set of server extensions from the Ready-to-Run Software web site. Download the
  fp_install.sh file and the tar file for your platform (for Solaris, it is fp40.solaris.tar.Z).
• [Unix/Linux] You can download an install script and a set of server extensions from the Microsoft web site. Download the fp_install.sh file and the tar file for your platform (for Solaris, it is fp40.solaris.tar.Z).

• Space Requirements
• Preliminary Tasks


• Some Additional Considerations

• Do not remove any of the internal files needed by FrontPage such as the .nsconfig file. Doing so disables access control for content upload.
• You cannot set a web to be restricted to valid end-users only. If you set this, you receive a message that says "This server does not support restricting end user access."
• [Unix/Linux only] When you install the stub extensions, you should set the web owner to be the same as the iPlanet Web Server user. This is so that the FrontPage extensions have write permissions to certain directories, namely the https-instance/config directory and the doc root. The fpsrvadm.exe script, which installs stub extensions to the webs, asks for the web owner.

• Windows NT systems
• Unix/Linux systems - FrontPage97 extensions
• Unix/Linux systems - FrontPage98 extensions
• Unix/Linux systems - FrontPage2000 extensions

1. Run the server extensions setup program for your language and processor type.

For example, for English FrontPage98 extensions, it is the fp98ext_x86_enu.exe file. The server extensions are copied to the folder C:\Program Files\MicrosoftFrontPage\Version 3.0. For English FrontPage2000 extensions, it is the fpse2k_x86_ENG.exe file. The server extensions are copied to the folder C:\Program Files\Common Files\Microsoft Shared\Web Server Extensions\40.

2. After installing FrontPage 2000 with the Server Extensions Resource Kit, launch the Server Extensions Administrator under Start | Programs | Administrative Tools , right-click on your machine's host name under Console Root | FrontPage Server Extensions, and select New Web. Follow the steps in the wizard to select your server instance and configure it for FrontPage Server Extensions.
3. Select the virtual servers on which the FrontPage Server Extensions should be installed and click OK.
4. Enter the name of a new FrontPage administrator account and a password.
5. You can add other administrator accounts after installing the server extensions using the Permissions command in the FrontPage Explorer.

• The FrontPage Server Extension .dll and .exe files are copied to the \bin subdirectory and to the default \windows\system directory.
• The ISAPI (.dll) or CGI (.exe) files used by FrontPage to implement the Server Extensions functionality in the user's webs are copied to the \isapi and \_vti_bin directories, respectively. They are also copied into the document root of each virtual server on which you are installing the FrontPage extensions.
• The FrontPage Server Administrator (fpsrvwin.exe) and a command line version (fpsrvadm.exe) are copied to the \bin directory. The FrontPage Server Administrator is a tool for installing, updating, verifying, or removing the FrontPage Server Extensions.

• The FrontPage Server Extensions .dll and .exe files are copied to the \bin subdirectory and to the default \windows\system directory.
• The three ISAPI (.dll) or CGI (.exe) files used by FrontPage to implement the Server Extensions functionality in the user's webs are copied to the \isapi and \_vti_bin directories, respectively. They are also copied into the document root of each virtual server on which the FrontPage extensions are installed.
• The FrontPage Server Administrator (fpsrvwin.exe) and a command line version (fpsrvadm.exe) are copied to the \bin directory. The FrontPage Server Administrator is a tool for installing, updating, verifying, or removing the FrontPage Server Extensions.
• The Server Extensions Resource Kit.
• HTML Administration forms, a set of HTML forms for remotely administering the FrontPage Server Extensions via web browsers. Also a command line utility (fpremadm.exe) for remote administration of the FrontPage Server Extensions is installed in the \bin directory.

• The FrontPage Server Extensions .dll and .exe files are copied to the \bin subdirectory and to the \WINNT\system32 directory.
• The three ISAPI (.dll) or CGI (.exe) files used by FrontPage to implement the Server Extensions functionality in the user's webs are copied to the \isapi and \_vti_bin directories, respectively. They are also copied into the document root of each virtual server on which the FrontPage extensions are installed.
• The FrontPage Server Administrator (fpsrvwin.exe) is not used or installed with FrontPage 2000. You must use the Server Extensions Administrator (under Start | Programs | Administrative Tools) or the command line version (fpsrvadm.exe), which is copied to the \bin subdirectory. The FrontPage Server Administrator is a tool for installing, updating, verifying, or removing the FrontPage Server Extensions.
• The Server Extensions Resource Kit is copied to the \serk subdirectory.
• HTML Administration forms, a set of HTML forms for remotely administering the FrontPage Server Extensions via web browsers, are copied to the \admcgi and \admisapi subdirectories. Also a command line utility (fpremadm.exe) for remote administration of the FrontPage Server Extensions is installed in the \bin directory.

• Modifies the magnus.conf file
• Modifies the server's configuration file (obj.conf) to add ObjectType directives, marking three of the \_vti_ directories as containing executables.
• Adds the following seven subdirectories are created under your server's document root:

\_private
\_vti_bin (contains shtml.exe)
\_vti_bin\_vti_adm (contains admin.exe)
\_vti_bin\_vti_aut (contains author.exe)
\_vti_cnf
\_vti_log
\_vti_pvt
\_vti_txt
\images

• Creates .nsconfig files in the \_vti_bin, \_vti_adm,\_vti_aut directories and the document root directory.

• For FrontPage 97 and 98, execute the fpsrvwin.exe file (located in the \bin directory of your FrontPage directory) to set the server port, test the extensions, install the extensions to other virtual servers, and update extensions.
• For FrontPage 2000, run the Server Extensions Administrator (under Start | Programs | Administrative Tools) or the command line version (fpsrvadm.exe).
• Select the server and web you want to work with:

• A remote machine must have the FrontPage97, FrontPage98, or FrontPage 2000 program installed (Macintosh or Windows only). Once the FrontPage program is started, the user is prompted for the name of a server to edit or open.
• If the user wants to edit a web on a different machine, click on "MoreWebs", on the line to select a web server or disk location type in the servername:portnumber of the web to edit then click OK.
• Select the web you wish to edit from the list of webs on the host machine.
• You need to provision each additional web. You can do this from the client side, with the FrontPage client provided the client has the right authorization (the administrator username and password) for the root web. You can also provision user webs from the server side by using the program fpsrvadm.exe to set the password for an individual web. You need to make sure that the new FrontPage web does not inherit the administrator username and password from the root web.
• Locate the fpadmin.htm file, typically in the \admin\cgi directory (97 and 98) or \admcgi directory (2000) of your FrontPage program directory. You can use this to configure your FrontPage web.
• Users can edit the local web that is displayed when FrontPage is started, but they must have a valid user ID and password to modify it.

1. Log in as the root user so you can install the FrontPage Server Extensions from the tar file:

cd /usr/local

2. Untar the downloaded file.

This creates a /usr/local/FrontPage/version2.0 directory and installs several other new directories under the document root directory. For example, for the FrontPage 97 extensions on a Solaris platform, you untar the vt20.solaris.tar.z file:

tar xvf /usr/tmp/vt20.solaris.tar

3. Change directories to /usr/local/frontpage/version2.0.

cd frontpage/version2.0

4. Create a directory named /extensions and move the _vti_bin directory into it.

mv _vti_bin extensions

5. Install the WPP kit to /usr/local/frontpage/version2.0.

For Solaris, use this code:

tar xvf /usr/tmp/wpp.solaris.tar

6. Rename the directory /executables (/usr/local/frontpage/version2.0/executables) to /_vti_bin:

mv executables _vti_bin

7. Move the file fpsrvadm.suid.exe to the /bin directory:

mv fpsrvadm.suid.exe bin

8. Run the fp_install.sh shell program and follow the on-screen instructions, which ask for the information described in the following table.

When you are prompted for the name of the server configuration file, enter the pathname of your server's magnus.conf file.

• Modifies magnus.conf
• Creates a configuration file named /usr/local/frontpage/hostname:port.cnf
• Modifies the server's configuration file (obj.conf) to add ObjectType directives, marking three of the /_vti_ directories as containing executables.
• Adds seven subdirectories under the server's document root:

/_vti_bin (contains shtml.exe)
/_vti_bin/_vti_adm (contains admin.exe)
/_vti_bin/_vti_aut (contains author.exe)
/_vti_cnf
/_vti_pvt
/_private
/_vti_log
/_vti_txt
/images

• Creates .nsconfig files in the /_vti_bin, /_vti_adm, /_vti_aut and the document root directories.

1. Execute the fpsrvwin.exe file to set the server port, test the extensions, install the extensions to other virtual servers, and update extensions.
2. A remote machine must have the FrontPage 97, 98, or 2000 program installed (Macintosh or Windows only).

Once the FrontPage program is started, the user is prompted for the name of a server to edit or open.

3. If the user wants to edit a web on a different machine, click on "MoreWebs" on the line to select a web server or disk location type in the servername:portnumber of the web to edit. Choose OK.
4. Select the proper web from the list of webs on the host machine to edit.

1. Log in as the root user so you can install the FrontPage Server Extensions from the tar file.
2. Type cd /usr/local, or cd to the directory where the two downloaded files (fp30.solaris.tar.Z and fp_install.sh) are located.
3. Run the fp_install.sh shell program and follow the on-screen instructions, which ask for parameter information.

When you are prompted for the name of the server configuration file, enter the pathname of your server's magnus.conf file.

• Modifies magnus.conf
• Creates a configuration file named /usr/local/frontpage/hostname:port.cnf
• Modifies the server's configuration file (obj.conf)to add ObjectType directives, marking three of the /_vti_ directories as containing executables.
• Adds seven subdirectories under the server's document root:

/_vti_bin (contains shtml.exe)
/_vti_bin/_vti_adm (contains admin.exe)
/_vti_bin/_vti_aut (contains author.exe)
/_vti_cnf
/_vti_pvt
/_private
/_vti_log
/_vti_txt
/images

1. Log in as the root user so you can install the FrontPage Server Extensions from the tar file.
2. Type cd /usr/local, or cd to the directory where the two downloaded files (fp40.solaris.tar.Z and fp_install.sh) are located.
3. Run the fp_install.sh shell program and follow the on-screen instructions, which ask for parameter information.

When you are prompted for the name of the server configuration file, enter the pathname of your server's magnus.conf file.

• Modifies magnus.conf
• Creates a configuration file named /usr/local/frontpage/hostname:port.cnf
• Modifies the server's configuration file (obj.conf)to add ObjectType directives, marking three of the /_vti_ directories as containing executables.
• Adds seven subdirectories under the server's document root:

/_vti_bin (contains shtml.exe)
/_vti_bin/_vti_adm (contains admin.exe)
/_vti_bin/_vti_aut (contains author.exe)
/_vti_cnf
/_vti_pvt
/_private
/_vti_log
/_vti_txt
/images

http://www.microsoft.com

http://www.rtr.com