Tryag File Manager
Home
-
Turbo Force
Current Path :
/
usr
/
local
/
frontpage
/
version5.0
/
help
/
1033
/
Upload File :
New :
File
Dir
//usr/local/frontpage/version5.0/help/1033/wsgpMrg.htm
<html> <head> <meta http-equiv="Content-Type" content="text/html; charset=windows-1252"> <meta name="GENERATOR" content="Microsoft FrontPage 4.0"> <meta name="ProgId" content="FrontPage.Editor.Document"> <title>Microsoft FrontPage Server Extensions Server Administration Help</title> <SCRIPT LANGUAGE="JavaScript"> <!-- if (navigator.userAgent.indexOf("MSIE 5") != -1) { document.write("<LINK REL=STYLESHEET HREF=\"ows.css\" TYPE=\"text/css\">"); document.write("<STYLE>"); document.write("<<!-->"); document.write("<A:hover {color:386BCC}>"); document.write("<//-->>"); document.write("</STYLE>"); } else { if (navigator.appName == "Netscape") { document.write("<LINK REL=STYLESHEET HREF=\"owsns.css\" TYPE=\"text/css\">"); } else { document.write("<LINK REL=STYLESHEET HREF=\"owsns.css\" TYPE=\"text/css\">"); } } //--> </SCRIPT> <SCRIPT language=JavaScript src="ExpColla.js"></SCRIPT> </head> <body marginwidth="0" marginheight="0" rightmargin="0" background="bg_help.gif" alt="Help background image"> <table width="100%" cellpadding="0"> <tr> <td><img src="desg12.gif" width="101" height="51" alt="" border="0"></td> <td> <table "valign="top" width="100%" cellpadding="1" cellspacing="0"> <tr> <td align="right" valign="bottom"> </td> </tr> <tr> <td align="right" valign="bottom"><a class="owsnav" href="wsgIndex.htm">Index</a> </td> </tr> <tr> <td align="right" valign="bottom"><a class="owsnav" href="wsgTOC.htm">Contents</a> </td> </tr> </table> </td> </tr> <tr> <td width="100%" colspan="2"><a href="wsgHome.htm"><img align="right" src="home.gif" width="12" height="11" alt="home" valign="top" border="0"></a><hr NOSHADE size="1"> </td> </tr> <tr> <td colspan="2" align="right"><p class="ptrail"><a href="wsghow.htm" class="owsnav">How do I...</a></p></td></tr> </table> <table class=content" width="100%" cellpadding="8"> <tr> <td> <H1 class="portal"><A name="IDX_wsgpmrg1"><!--webbot bot="PurpleText" preview = "(1)subwebs;(2)merging with parent webs;(1)merging subwebs;(2)with parent webs;(1)Server Administration page;(2)merging subwebs;(1)Web sites;(2)merging;(1)parent webs;(2)and subwebs;(1)joining subwebs with parent webs" --></A>Merge a subweb to a parent Web site</H1><br> <table border="0" cellpadding="0" cellspacing="0" class="exptbl"> <tr> <td> <LABEL for="mTools"> <IMG align="right" valign="top" border="0" width="9" height="9" src="plus.gif" class="clsImgButton" id="mToolsBtn" onClick="ToggleDisplay(mToolsBtn, mToolsItems);" alt=""> </LABEL> </td> <td> <A class="clsTocHead" href="javascript:void();" id="mTools" onClick="return ToggleDisplay(mToolsBtn, mToolsItems);"> About Webs and subwebs </A> </td> </tr> </table> <DIV class="clsTocItem" id="mToolsItems"> <SCRIPT>mToolsItems.style.display='none';</SCRIPT> <DIV class="clsTocItem1"> <p>When working with a large Web site, it's often easier to break up the site into smaller subwebs. A subweb is a complete Microsoft FrontPage-based Web site that is located in a subdirectory of the <a href="wsgGloss.htm#rootweb" class="glossterm"> root Web</a> site or of another subweb. Each subweb can have many levels of subdirectories. </p> <p>A root Web site is an FrontPage-based Web site that is the top-level content directory of a Web server or, in a <a href="wsgGloss.htm#multihosting" class="glossterm">multi-hosting</a> environment, of a virtual Web server. The content of the root Web site can be contained in many levels of subdirectories. However, there is only one root Web site per Web server or <a href="wsgGloss.htm#virtualserver" class="glossterm">virtual server</a>. </p> <p>For example, if a company has an intranet, a good strategy is to have a subweb for each major department. That way, each group can manage their own site and the main <a href="wsgGloss.htm#homepage" class="glossterm"> home page</a> in the parent Web site can provide links among the departmental sites. </p> <p>There are several benefits to setting up your Web sites with subwebs:</p> <ul> <li>Each subweb can be maintained by a different owner. <li>Each subweb can maintain separate security settings. <li>Performance can improve, because the time required to <a href="wsgGloss.htm#recalculateweb" class="glossterm"> recalculate</a> <a href="wsgGloss.htm#hyperlink" class="glossterm"> hyperlinks</a> is directly proportional to the number and size of the documents stored in a single Web.</li> </ul> <p>Even though subwebs appear below other Web sites in the Web server's file system and <a href="wsgGloss.htm#URL" class="glossterm"> URL</a> space, the content of a subweb is not included in its parent Web site. An <a href="wsgGloss.htm#authorrole" class="glossterm"> author</a> of an FrontPage-based Web site does not automatically have permission to edit any of its subwebs, and users cannot browse from a parent Web site to a subweb. FrontPage Server Extensions 2002 maintains this separation of content automatically.</p> </DIV> <table border="0" cellpadding="0" cellspacing="0" class="exptbl"> <tr> <td> <LABEL for="mJourn"> <IMG align="right" valign="top" border="0" width="9" height="9" src="plus.gif" class="clsImgButton" id="mJournBtn" onClick="ToggleDisplay(mJournBtn, mJournItems);" alt=""> </LABEL> </td> <td> <A class="clsTocHead" href="javascript:void();" id="mJourn" onClick="return ToggleDisplay(mJournBtn, mJournItems);"> About managing subwebs </A> </td> </tr> </table> <DIV class="clsTocItem" id="mJournItems"> <SCRIPT>mJournItems.style.display='none';</SCRIPT> <DIV class="clsTocItem1"> <p>Using the site administration Web pages you can:</p> <ul> <li>Create or delete subwebs</li> <li>Merge subwebs</li> <li>Recalculate a Web or subweb</li> <li>Specify unique permissions for the subweb or use the user accounts and <a href="wsgGloss.htm#role" class="glossterm"> roles</a> of the parent Web</li> </ul> <h2>Administrative options not available when working in a subweb</h2> <p>Some site administration options are not available from within a subweb; these include:</p> <ul> <li><a href="wsgGloss.htm#usageanalysis" class="glossterm">Usage analysis</a></li> <li>Some <a href="wsgGloss.htm#serverhealth" class="glossterm">server health</a> settings</li> </ul> <p>Also, if a subweb is set up to use the parent Web site's account and roles, options for managing accounts and roles do not appear. </p> <p>To configure any of the above options, you must use the site administration pages from the root-level Web site of the server or virtual server. </p> </DIV> </DIV> <table border="0" cellpadding="0" cellspacing="0" class="exptbl"> <tr> <td> <LABEL for="mNap"> <IMG align="right" valign="top" border="0" width="9" height="9" src="plus.gif" class="clsImgButton" id="mNapBtn" onClick="ToggleDisplay(mNapBtn, mNapItems);" alt=""> </LABEL> </td> <td> <A class="clsTocHead" href="javascript:void();" id="mNap" onClick="return ToggleDisplay(mNapBtn, mNapItems);"> Should I create a subweb or a virtual server? </A> </td> </tr> </table> <DIV class="clsTocItem" id="mNapItems"> <SCRIPT>mNapItems.style.display='none';</SCRIPT> <DIV class="clsTocItem1"> <p>There are many factors to consider when organizing your Web server's content into sub-areas. In general, you should create a virtual server when:</p> <ul> <li>You want the content area to have its own root-level Web name. For example, http://server-name.</li> <li>You believe the content will increase greatly over time.</li> </ul> <p>You should create a subweb when:</p> <ul> <li>Having a root-level Web name isn't important. For example, http://server-name/subweb.</li> <li>You are dividing your content up into relatively small areas with no major growth anticipated.</li> </ul> <p>To create a new virtual server, you use the Apache tools for UNIX.</p> </DIV> </DIV> </DIV> <table border="0" cellpadding="0" cellspacing="0" class="exptbl"> <tr> <td> <LABEL for="mNac"> <IMG align="right" valign="top" border="0" width="9" height="9" src="plus.gif" class="clsImgButton" id="mNacBtn" onClick="ToggleDisplay(mNacBtn, mNacItems);" alt=""> </LABEL> </td> <td> <A class="clsTocHead" href="javascript:void();" id="mNac" onClick="return ToggleDisplay(mNacBtn, mNacItems);"> About merging subwebs </A> </td> </tr> </table> <DIV class="clsTocItem" id="mNacItems"> <SCRIPT>mNacItems.style.display='none';</SCRIPT> <DIV class="clsTocItem1"> <P>When you merge a <a href="wsgGloss.htm#subweb" class="glossterm">subweb</a>, it remains simply another folder with Web pages under the parent Web. You will lose no information on pages within the subweb; however the subweb loses whatever unique permissions it might have had. Any subwebs below the merged subweb are promoted to subwebs under the parent Web site.</P> <p> To merge a subweb, use the site administration page for the Web site that contains the subweb.</p> </DIV> </DIV> <ol> <li>On the <b> Server</b> <b> Administration</b> page, under <b>Virtual Servers</b>, click the name of the <a href="wsgGloss.htm#virtualserver" class="glossterm"> virtual server</a> that contains the subweb.</li> <li>Under <b>Subwebs</b>, click <b>Merge a subweb</b>.</li> <li>Click the <b>Web Name</b> list and then click the name of the <a href="wsgGloss.htm#subweb" class="glossterm"> subweb</a> that you would like to merge with the parent Web.</li> <li>Click <b> Merge Subweb</b>.</li> </ol> </td></tr></table> <table class="footer" align="center"> <tr> <td><img src="1p.gif" height="10px" width="10px"></td> </tr> <tr> <td> <p><a class="owsnav" href="wsgHome.htm">Home</a> | <a class="owsnav" href="wsgIndex.htm">Index</a> | <a class="owsnav" href="wsgTOC.htm">Contents</a></p> </td> </tr> <tr> <td>©1995-2001 Microsoft Corporation<br> All rights reserved. <a href="wscopyrt.htm">Terms of use.</a></p> </td> </tr> </table> </body> </html>