Windows Server

Steve Lupton · Guest

Is it possible to have sharepoint service virtual servers
(top-level portals) or sites using the same piece of the
content created at one site/portal with the same web part
template? i.e. with two top-level portals
http://portal1.acme.com and http://portal2.acme.com, or
sites http://portal1.acme.com/site1/ and
http://portal1.acme.com/site2/.

Jim Buyens · Guest

In WSS, you can only point a site collection at one portal site.

If, however, you have two portal sites, both can reference content from the
same WSS site. It's just that for the second portal site, at least, you have
to build the content link (the "listing") *from* the portal site.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

"Steve Lupton" wrote:

Steve Lupton · Guest

Could you detail it out or send me a link on how I can
build the content link?

Jim Buyens · Guest

Sure. On the portal home page, click Add Listing. Fill in the blanks and
click OK.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

"Steve Lupton" wrote:

Steve Lupton · Guest

Jim,

So basically, we are creating a list of links pointing to
the pages on the other portal. What I am trying to achieve
is to retrieving the content from the second portal and
displayed it in the context of the first portal, most
likely in a same web part component. Is it possible? Or
at least, from one site to another site in the same virtual
server?

Thanks for your help!

Steve Lupton

Jim Buyens · Guest

I presume that your two "portals" are two instances of SharePoint Portal
Server. If so, the usual arrangement is to have both of them point to content
physically located on some third server.

If, as I'm starting to suspect, your "portals" are something else, please
explain what they are.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

"Steve Lupton" wrote:

Steve Lupton · Guest

Sorry for the confusion. My portal here is not the site
managed in Sharepoint Portal. It is the site created in
WSS. I deeply appreciate your help.

Jim Buyens · Guest

As I now understand the original question, no, in general it's not possible,
using standard components, for team members or administrators to configure
one sharepoint site so that it displays content that resides within another
site,

In FrontPage, you can configure Data View Web Parts in one site to display
data from another site, but there seems to be a surprising amount of
resistance to this approach because it "unghosts" the page. The scenario
seems to be:

1. Design a site and implement it as a site definition (that is, as a group
of
hand-edited, highly interrelated XML files on the server.
2. Deploy mass numbers of these sites.
3. Subsequently change all these site at once by changing the site
definition.

The fact that step 3 is unsupported by Microsoft doesn't seem to deter anyone.

To my way of thinking, the preferred way of displaying content from one site
in many others is to write a Web Part with the name of the "source" site
either hard-coded, or specified in web.config, or in the Web Part Properties
task pane. But then, I don't mind writing Web Parts. Some people do.

Two more alternatives are:
1. Stop replicating all these sites that need access to the same data. Put
the data
in its own site and if a thousand people need access, give them all
access.
2. Use the product that's *designed* for integrating data from many
different sites:
SharePoint Portal Server.

Jim Buyens
Microsoft FrontPage MVP
http://www.interlacken.com
Author of:
*----------------------------------------------------
|\---------------------------------------------------
|| Microsoft Windows SharePoint Services Inside Out
|| Microsoft Office FrontPage 2003 Inside Out
||---------------------------------------------------
|| Web Database Development Step by Step .NET Edition
|| Microsoft FrontPage Version 2002 Inside Out
|| Faster Smarter Beginning Programming
|| (All from Microsoft Press)
|/---------------------------------------------------
*----------------------------------------------------

template?

"Steve Lupton" wrote:

Steve Lupton · Guest

Thank you for the advice, Jim!

Mike Walsh · Guest

Jason Rodgers in a slightly later thread was also using "portal" when
meaning WSS not SPS so it's a common enough mistake. The problems mainly
come if people don't have the time and energy (as Jim had here) to keep
replying to the thread so that they reach the "portal = WSS ..."
realisation.

As Jim wrote in that thread in Microsoft-speak portal means SharePoint
Portal Server and the main site in WSS is just "top-level site at the
server root".

For me if you just call it "WSS site" I'll get it (and none of us will think
"Ah, SPS 2003!)

Mike Walsh, Helsinki, Finland
WSS FAQ at http://wss.collutions.com
Please post questions to the newsgroup only.

"Steve Lupton" <lupton@discussions.microsoft.com> wrote in message
news:093701c4fb83$49cee580$a501280a@phx.gbl...

	Windows Server Forum Index -> Windows Services	All times are GMT
Page 1 of 1