![]() |
![]() |
![]() |
![]() |
Installing the FrontPage Server Extensions on UNIX Where You Can Get the FrontPage Server ExtensionsThe Microsoft FrontPage 2000 Server Extensions for UNIX platforms are available for downloading at
the
FrontPage section of MSDN The installation package for a UNIX platform contains the installation script, fp_install.sh, and a compressed tar file containing all server extensions files. The tar file is named fp40.platform.tar.Z, where platform is the UNIX platform to which the server extensions are being installed. For example, fp40.solaris.tar.Z is the compressed tar file for Solaris servers. FrontPage Server Extensions Supported PlatformsThe following table lists UNIX-based Web servers for which the FrontPage Server Extensions are available.
What Gets Installed?The FrontPage Server Extensions are installed in /usr/local/frontpage by default. If you install them somewhere else, there must be a link from /usr/local/frontpage to the installation area. (The installation script will create this link for you.) Even if you do not install the server extensions in /usr/local, the directory must exist. If you do not have this directory on your server, the installation script will create it. Along with the server extensions, the following are installed:
Using the Setup ScriptFrontPage Server Extensions setup has four steps. (You may not need to perform all the steps.) First, the server extensions and other files are uncompressed, untarred, and saved to their locations on the server computer. Next, if your Web server has an earlier version of the server extensions, it is upgraded to FrontPage 2000. Next, if your Web server has never had the server extensions before, they are installed. Lastly, if you have one or more virtual servers, the FrontPage Server Extensions are optionally installed on them. The FrontPage Server Extensions installation script is fp_install.sh. You must be logged on as "root" to run this script. Untarring the FrontPage Server Extensions
By default, the server extensions are installed in /usr/local/frontpage/. You can accept the default or specify another location. If you select another location, a symbolic link will be created from /usr/local/frontpage/ to the directory you choose. The installation directory must be on a local partition, and the partition must not be mounted NOSUID.
Upgrading earlier versionsAfter upgrading all servers to the server extensions, you can choose to set up the security of your FrontPage-extended webs interactively, or you can have fp_install.sh generate a script to perform the operation.
Installing a root web and subwebs for the first timeDuring installation of the stub server extensions on a subweb, you are prompted for the subweb name. If the name is of the form ~webname (a "per-user" web), then "webname" is used as the name of the subweb's owner in the UNIX file system. If not, you are prompted for the name of the owner. You are also prompted for the name of the group owner. For each subweb that you choose, you are also prompted for the administrator's name and password. For each FrontPage-extended web, fp_install.sh will then chown the content in the Web to be owned by the specified UNIX user and group. If the FrontPage-extended web is not on the FrontPage Apache patch Web server, fp_install.sh will also chown the stub versions of the server extensions executable files. For details, see Setting the Server Extensions to SUID/SGID. The server extensions then do the following for each root web or subweb:
Installing on virtual serversBefore installing, you are prompted for a web administrator name and password. You will need this name and password when administering or authoring the Web from a FrontPage client. After installing the root web, you are prompted for your system's local character encoding and default language. During installation of the stub server extensions on a subweb, you are prompted for the subweb name. If the name is of the form ~webname (a "per-user" web), then "webname" is used as the name of the subweb's owner in the UNIX file system. If not, you are prompted for the name of the owner. You are also prompted for the name of the group owner. For each subweb that you choose, you are also prompted for the administrator's name and password. For each FrontPage-extended web, fp_install.sh will then chown the content in each Web to be owned by the specified UNIX user and group. If the FrontPage-extended web is not the FrontPage Apache patch server, fp_install.sh will also chown the stub versions of the server extensions executable files. For details, see Setting the Server Extensions to SUID/SGID. The server extensions then do the following for each root web or subweb:
For a complete list of the contents of a FrontPage installation, see Files and Permissions For UNIX Web Servers. For a discussion of security considerations you should be aware of when installing the server extensions on UNIX, see Security on UNIX. For information on administering the FrontPage Server Extensions once they are installed, see Administrative Tools and Techniques. Installing the Apache PatchOn some Web servers, such as NCSA and Apache, the FrontPage Server Extensions need to modify the Web server's configuration file to mark directories containing the server extensions as executable. Because creating a subweb using the FrontPage client requires the client to write to the Web server's configuration file on these servers, which the Web server process owner usually does not have permissions to do, administrators cannot create FrontPage-extended subwebs in this way. On these servers, the fpsrvadm.exe utility or fpinstall.sh must be manually run as "root" on the host computer to modify the Web server's configuration file and create subwebs. For the Apache Web server, FrontPage supplies an optional patch to overcome this limitation. With this patch, copies of the FrontPage Server Extensions executable files are not stored in each FrontPage-extended web, but are stored in one centralized location. This makes it unnecessary to mark directories in each Web as executable, and makes it possible for the FrontPage client to create new FrontPage-extended webs without modifying server configuration files. There are two ways to convert your current Apache Web server to the FrontPage patched Apache Web server:
To install the pre-compiled FrontPage Apache patch, you use the script change_server.sh. This script steps you through upgrading an Apache server to the FrontPage patched Apache server, and upgrading any FrontPage-extended Apache webs to use the FrontPage patch. To use the script, you must be running as "root." Before installing the FrontPage Apache patch, back up your current Apache server, FrontPage installation directory, server configuration file directory, and all Web content. To install the FrontPage Apache patch:
The script: If you choose the interactive option, the script will prompt you for the UNIX user ID and group ID of each root web and subweb that you have upgraded. For each FrontPage-extended web, change_server.sh will chown all the FrontPage-created directories and content in each Web to be owned by the specified user and group. If you choose the script option to set up security, change_server.sh will generate the script. Before running the script, however, you must fill in the UNIX user IDs and group IDs you want to associate with each web. If you choose "y," the script set_default_perms.sh is invoked. This script sets permissions on /usr/local/frontpage/version4.0 and all directories below it to the defaults. For a complete listing of default FrontPage Server Extensions permissions, see "Files and Permissions for UNIX Web Servers."
For FrontPage to work once the new server is installed, the FrontPage Apache stub, in /usr/local/frontpage/version4.0/apache-fp/_vti_bin/fpexe, must be owned by, and user ID set to, "root": change_server.sh does this for you. After installing the FrontPage Apache patch, you must restart the server. Compiling and Installing Your Own Version of the Apache PatchMicrosoft makes the source code of the FrontPage Apache patch file available. To compile an Apache Web server with any custom or non-standard modules along with the FrontPage Apache patch, follow the directions in this section. If you do not want to compile your own Apache Web server, follow the directions in Installing the Apache Patch to install the pre-compiled FrontPage Apache patch. Before compiling and installing the Apache patch, you must install the FrontPage Server Extensions. When the setup script untars the FrontPage Server Extensions, it also untars the FrontPage Apache patch source file, fp-patch-apache_1.3.x.
For a server that uses the 1.3.0 or earlier directory structure:
|
![]() |
![]() |
TOP![]() |
||
Last Updated June 1999
©1999 Microsoft Corporation. All rights reserved. Terms of Use. Disclaimer |