| Author |
Message |
Jason Rodgers
Guest
|
 Posted:
Fri Jan 14, 2005 10:40 pm Post subject:
virtual server and top-level portal sites |
|
|
Is it true that one needs to create multiple virtual
servers in order to have multiple portal sites configured
as http://site1.mydomain.com and http://site2.mydomain.com,
etc.? If there is some web part in one site intended to
share the same content with that in the other site, is
there any way to achieve it?
Please advise on the steps to make this happen. Thanks. |
|
| Back to top |
|
 |
Steven Collier [MVP]
Guest
|
| Posted:
Mon Jan 17, 2005 12:28 am Post subject:
Re: virtual server and top-level portal sites |
|
|
There is a way to achieve this with WSS but not SPS. Do a search for Host
Header Mode in the admin guide for WSS and you should find details.
You can share data between sites quite easily using FrontPage to configure
dataview's from other sites.
Steven Collier
On 14/1/05 16:40, in article 179101c4fa57$b81773e0$a601280a@phx.gbl, "Jason
Rodgers" <anonymous@discussions.microsoft.com> wrote:
| Quote: | Is it true that one needs to create multiple virtual
servers in order to have multiple portal sites configured
as http://site1.mydomain.com and http://site2.mydomain.com,
etc.? If there is some web part in one site intended to
share the same content with that in the other site, is
there any way to achieve it?
Please advise on the steps to make this happen. Thanks.
|
|
|
| Back to top |
|
|
Hollis D. Paul
Guest
|
| Posted:
Mon Jan 17, 2005 5:53 pm Post subject:
Re: virtual server and top-level portal sites |
|
|
In article <179101c4fa57$b81773e0$a601280a@phx.gbl>, Jason Rodgers
wrote:
| Quote: | Is it true that one needs to create multiple virtual
servers in order to have multiple portal sites configured
as http://site1.mydomain.com and http://site2.mydomain.com,
etc.? If there is some web part in one site intended to
share the same content with that in the other site, is
there any way to achieve it?
Please advise on the steps to make this happen. Thanks.
This problem is usually encountered when you want to give outside users |
access to the same material you have on the intranet, except that you
want the outsiders to use SSL. In this case, when you create the site2
portal, you extend it using the configuration data base of the existing
site.
***************
Search on the SPPSAdminGuide.chm on Extranet and then select "About
Extending a Virtual Server"
Reasons for extending a virtual server
Generally, you extend a virtual server because you need to add more
capacity to your server, whether that server is a departmental server
or one of many in your server farm. More capacity can mean either more
space for Web site content or more connections to existing Web sites.
For example, if you have a site with many visitors, you can have
several virtual servers hosting the same content to increase the number
of concurrent users that you can support and balance the load for your
servers. You can extend a virtual server to do one of the following:
...
Connect to existing content
To have your new virtual server point to a Web site that is already in
use, either to allow for more connections to a site or to allow more
than one URL to point to a site, you can connect to an existing content
database. When you extend a virtual server, you can choose which
content database to use. The content databases are actually listed as
virtual servers, and the list contains all virtual servers that
currently exist on the server (in a single-server setting), or in the
server farm. Querying the configuration database generates this list,
which is why you must be connected to the configuration database before
you can extend a virtual server.
When you extend and connect to an existing content database, all of the
configuration data about the existing virtual server is applied to the
new virtual server. Any managed paths are also applied. This means that
if virtual server A contains the paths /teams, /sites, and /users, when
you extend virtual server B and connect to the content database for
virtual server A, virtual server B will also have the /teams, /sites,
and /users paths. You can direct a user to either virtual server A or
B, and the user will see the same content — A and B are essentially
mirrored virtual servers. For more information about URLs in Windows
SharePoint Services, see the Windows SharePoint Services Resource Kit.
There are more detailed articles in the same extranet list.
****************
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA |
|
| Back to top |
|
|
Jason Rodgers
Guest
|
| Posted:
Wed Jan 19, 2005 6:49 am Post subject:
Re: virtual server and top-level portal sites |
|
|
Thanks for the advice.
How about both sites having only portion of content in common?
| Quote: | -----Original Message-----
In article <179101c4fa57$b81773e0$a601280a@phx.gbl>, Jason
Rodgers
wrote:
Is it true that one needs to create multiple virtual
servers in order to have multiple portal sites configured
as http://site1.mydomain.com and http://site2.mydomain.com,
etc.? If there is some web part in one site intended to
share the same content with that in the other site, is
there any way to achieve it?
Please advise on the steps to make this happen. Thanks.
This problem is usually encountered when you want to give
outside users
access to the same material you have on the intranet,
except that you
want the outsiders to use SSL. In this case, when you
create the site2
portal, you extend it using the configuration data base of
the existing
site.
***************
Search on the SPPSAdminGuide.chm on Extranet and then
select "About
Extending a Virtual Server"
Reasons for extending a virtual server
Generally, you extend a virtual server because you need to
add more
capacity to your server, whether that server is a
departmental server
or one of many in your server farm. More capacity can mean
either more
space for Web site content or more connections to existing
Web sites.
For example, if you have a site with many visitors, you
can have
several virtual servers hosting the same content to
increase the number
of concurrent users that you can support and balance the
load for your
servers. You can extend a virtual server to do one of the
following:
...
Connect to existing content
To have your new virtual server point to a Web site that
is already in
use, either to allow for more connections to a site or to
allow more
than one URL to point to a site, you can connect to an
existing content
database. When you extend a virtual server, you can choose
which
content database to use. The content databases are
actually listed as
virtual servers, and the list contains all virtual servers
that
currently exist on the server (in a single-server
setting), or in the
server farm. Querying the configuration database generates
this list,
which is why you must be connected to the configuration
database before
you can extend a virtual server.
When you extend and connect to an existing content
database, all of the
configuration data about the existing virtual server is
applied to the
new virtual server. Any managed paths are also applied.
This means that
if virtual server A contains the paths /teams, /sites, and
/users, when
you extend virtual server B and connect to the content
database for
virtual server A, virtual server B will also have the
/teams, /sites,
and /users paths. You can direct a user to either virtual
server A or
B, and the user will see the same content - A and B are
essentially
mirrored virtual servers. For more information about URLs
in Windows
SharePoint Services, see the Windows SharePoint Services
Resource Kit.
There are more detailed articles in the same extranet list.
****************
Hollis D. Paul [MVP - Outlook]
Hollis@outhousebythesound.com
Mukilteo, WA USA
.
|
|
|
| Back to top |
|
|
|
|
|
|
FAQ
Memberlist
Register
Profile
Log in to check your private messages
Log in