Sharepoint Forum

Ask Question   UnAnswered
Home » Forum » Sharepoint       RSS Feeds

Portal Area

  Asked By: Carolyn    Date: Jun 16    Category: Sharepoint    Views: 924

Can any one explain me "What is portal area?"
and how it is different from portal site.



6 Answers Found

Answer #1    Answered By: Hema Hegde     Answered On: Jun 16

In simplest terms, a portal  site is the same thing as referring to a web
site as a whole. A portal area  is a page in that site. You can nest
portal areas just like how you can nest web site  pages into a hierarchy.

Here is an additional resource for you:

Answer #2    Answered By: Kyla Eckert     Answered On: Jun 16

i know that this concept. But can you tell me why do we need portal
area When these are same?

Answer #3    Answered By: Megan Martin     Answered On: Jun 16

I sense what you really want to know if why you may want a SharePoint
Portal Server (SPS) portal, not just how an area  is different than a

Perhaps you want SPS for its Enterprise Search vs. Windows SharePoint
Services (WSS) SQL full-text search with only a Web or a List as its
scope. Or perhaps you want My Sites or Shared Services. Audience
targeting, while immature, certainly has its usefulness.

While an Area is just another page based upon a unique site  definition
(AKA Web template or site definition Configuration), Listings (AKA News)
can be rolled-up and grouped (even by audience). Listings are key to
having a browsable Intranet. Also, SPS manages the area hierarchy so it
isn't fixed like WSS is.

Of course, a categorized directory of Webs that sports a browser-based
(vs. console only) means of creating new top-level Webs, Single Sign-On,
stored alerts, Active Directory profile management, and a dynamic vs.
static navigation (if you like it) can certainly be nice to have.

Does that help?

Answer #4    Answered By: Donta Kirkland     Answered On: Jun 16

When you say “portal site”, are you referring to SharePoint portal  site or WSS site  of the SharePoint portal site? The reason why I ask is because Heather was talking about portal site and its areas and you seemed to know that concept already so I was wondering if you meant how portal area  is different from a WSS site.

Answer #5    Answered By: Cade Velazquez     Answered On: Jun 16

Everyone, please do not use the term "site".

The SPPT documentation, screens, and API are far too ambiguous regarding
the term "site". The portal  Site Collection and all of its Areas are
referred to as a "site", an Area is sometimes referred to as a "site", a
WSS site  Collection is often referred to as a "site", the top-level Web
in a Site Collection is commonly referred to as a "site", a Subweb is
sometimes referred to as a "site", SPSite is called a "site" but so is
SPWeb. Stop the madness...

We start with a SharePoint _Farm_
A Farm can have one or more _Virtual Servers_ (IIS Web Sites)
A Virtual Server can have one or more _Managed Paths_ (including the
A Managed Path can have one or more _Site Collections_
A Site Collection must have one or more _Webs_ (or _Areas_ which is a
special kind of Web)
A Web can have one or more _Lists_
A List can have one or more _ListItems_
A ListItem must have one or more Fields

Of course, there are other hierarchies (Virtual Servers have Content
Databases, Libraries are a kind of list with Files, etc.) but let's at
least all agree on these. I commonly say,

"A _Site Collection_ is a collection of Webs (or Areas)."
"A _Web_ is a collection of Lists (and Libraries) and the pages to
manage them."

I know that the user interface uses the term "site" and sometimes even
"portal site" with reckless abandon but we don't have to.

That said, when you see the term "portal site" in SPS administration,
they really mean the Site Collection of Areas (think special Webs). An
Area is just a WSS Web based upon a unique Site Definition that
leverages special SPS metadata, SPS Web Parts, and SPS administrative

When you see the term "site" on the SPS Sites Directory Area, they
really mean a top-level Web in a Site Collection.

Remember, SPS is a product built on top of the WSS platform (C# notation

"SPS == Product"
"WSS == Platform"

So, while a "portal site" is radically different from a "WSS site" it
isn't because a WSS Web in a portal is any different than a WSS Web in
any other context. They are different because of the ambiguity in the
term "site".

Site Collections can be embedded within a common content database both
in SPS and WSS. So, I think that your real question should be, "If the
top-level Web in the new Site Collection I am creating is embedded
within the portal's content database logically located in the Managed
Path of the portal's Virtual Server, dependant on its URL, App Pool
security context, and common system resources (threads, database
connections, temp directory, etc.) will it meet my needs; or should the
top-level Web in the new Site Collection be stand alone in its own
Virtual Server?"

Answer #6    Answered By: Ariana Christensen     Answered On: Jun 16

Is this on your blog? Or at some other permanent location (URL)?

Everyone else -- once we have the location, please tell all your friends.

Didn't find what you were looking for? Find more on Portal Area Or get search suggestion and latest updates.