Article ID: 185541
Article Last Modified on 2/14/2007
APPLIES TO
- Microsoft FrontPage 98 Standard Edition
This article was previously published under Q185541
SUMMARY
This article describes how to install the FrontPage Server Extensions to a supported UNIX Web server.
MORE INFORMATION
Currently the supported UNIX platforms and Web servers are:
SUPPORTED PLATFORMS
Platform Version -------- ------- BSD/OS 2.1, 3.0 Digital UNIX 3.2c, 4.0 Intel x86 Linux 3.0.03 (Red Hat Software) HP/UX 9.03, 10.01 IRIX 5.3, 6.2 Solaris 2.4, 2.5 SunOS 4.1.3, 4.1.4.<BR/> SCO OpenServer 5 SCO UnixWare 7
SUPPORTED SERVERS
Server Version ------ ------- Apache 1.1.3, 2.0, CERN 3.0 NCSA 1.5.2 Netscape Commerce 1.12 Netscape Communications 1.12 Netscape Enterprise 2.0, 3.0 Netscape FastTrack 2.0
You can choose among several methods for installing the FrontPage Server Extensions.
Before you install the FrontPage Server Extensions on supported UNIX servers, it is recommended that you do the following:
- Log on to the UNIX computer as root.
- Download the FrontPage 98 Extensions (fp_install.sh) for your particular platform. The Change_server.sh file is optional for Apache Web servers.
- Uncompress fp30.<platform>.tar.z (where <platform> denotes the UNIX platform you are using).
- Place fp30.<platform>.tar, fp_install.sh in the /usr/local directory. NOTE: The fp_install.sh file should have the permissions set to 755. User - Read, Write, Execute Group - Read, Write Other - Read, Write
- If you do not have a previous version of the FrontPage extensions installed, you should also create a /usr/local/frontpage directory.
RUNNING THE INSTALLATION SCRIPT
- Run the script /usr/local/fp_install.sh.
- Follow the directions on the screen.
- The installation script checks for /usr/local/. The default installation directory is /usr/local/frontpage/. Installing the extensions to any other directory creates a link from /usr/local/frontpage/ to that directory.
- If fp30.platform.tar is not located in /usr/local/, you will be prompted for its location.
- If you are upgrading the Web server extensions, a success log will be created: /usr/local/frontpage/currentversion/upgrade_results.txt. NOTE: One user ID and one group ID own the Web content. The installation script can configure this for you. It is recommended that you choose a user ID with a value of more than 15 and a group ID with a value of more than 21. After your Web server or servers have been upgraded, you will be given the option of setting up your security.
- You are prompted to install the root Web. If you have not installed extensions to the root Web before or would like to change the administrator of the Web at this time, answer "y". Answering "y" will install the stub extensions to the root Web.
NOTE: The manner in which your existing Web content is configured determines the options you choose when you install the extensions. You will see the following options toward the end of the installation script:
"Install new sub/per-user webs now?"
If your content is stored in directories below your document root or in per-user Webs (http://example.microsoft.com/~user), you answer "y" to this question.
"Do you want to install Virtual Webs?"
If your content is stored in different virtual Webs as defined in your Web server's configuration file, you answer "y" to this question. You still have the option of installing subwebs on each virtual Web.
Option 3
If your content is stored in a separate Web server, run fp_install.sh on each Web server. You will also install root Webs and subwebs for each virtual server.
- If you answer "y", you will also be prompted for the path to the server configuration file for your Web server, the user name that you use to administer Webs through FrontPage Explorer, and this user's password. This does not have to be a UNIX user. You will also be asked for the group to which this Web should belong. Next, you are asked for the type of Web server that you are running. After installing the root Web, you are asked for the local character encoding and the default language. Unless your system has been configured differently, you can accept the defaults for these choices.
- After the stub extensions have been installed on the root directory, you are prompted to install the extensions for sub/per-user Webs. If you choose to install any sub/per-user Webs, you are first prompted for the FrontPage administrator's user name and password for this subweb. If the Web name is in the context ~username, you will be prompted for the group only. In all other cases, you will be prompted for both the user name and group that should own the Web. The install script will then chown and chmod the Web accordingly. When you have entered all of the sub/per-user Webs, press CTRL+D to quit.
- You are next prompted to install the extensions on any virtual Webs. Choosing "y" will display all of the virtual Webs that are defined in your configuration file. After choosing each virtual Web, you are prompted for any missing information, such as ports. The stub extensions will be installed to the root Web and subwebs as in the above steps.
FrontPage 98 extensions are now installed on your Web server.
The FrontPage Administrator utility Fpsrvadm.exe is used to verify, install, remove, or update the server extensions. This utility is usually located in the usr/local/frontpage/version3.0/bin directory.
REFERENCES
For additional information, click the article number below to view the article in the Microsoft Knowledge Base:
310931 FPSE2000: Where to Find the FrontPage 2000 Server Extensions Resource Kit (SERK)
The third-party products discussed here are manufactured by vendors independent of Microsoft; we make no warranty, implied or otherwise, regarding these products' performance or reliability.
Additional query words: extensions unix
Keywords: kbhowto KB185541
