Cuando usar una Web Application independiente: (Que es una Web Application, o Aplicación Web desde el punto de vista de SharePoint, para qué me sirve o cuando necesito una?)

Generally speaking, use dedicated Web applications to:

  • Separate content available to anonymous users from content available to authenticated users.

  • Isolate users. For example, you can ensure that partners do not have access to intranet content by placing partner sites in a separate Web application.

  • Enforce permissions. A dedicated Web application provides the opportunity to enforce permissions by policies by using the Policy for Web Application page in Central Administration. For example, you can create a policy to explicitly deny write access to one or more groups of users. Policies for a Web application are enforced regardless of permissions configured on individual sites or documents within the Web application.

  • Optimize database performance. Applications achieve better performance if they are placed in Web applications with other applications of similar data characteristics. For example, the data characteristics of My Sites typically include a large number of sites that are small in size. In contrast, team sites typically encompass a smaller number of very large sites. By placing these two different types of sites in separate Web applications, the resulting databases are composed of data with similar characteristics, which optimizes database performance.

  • Optimize manageability. Because creating separate Web applications results in separate sites and databases, you can implement different limits for each site's Recycle Bin, expiration, and size, and negotiate different service-level agreements. For example, you might allow more time to restore sites that are not critical to your business.

 

Respecto al uso de site Collections: (Que es un Site Collection o Colección de Sitios, desde el punto de vista de SharePoint, para qué me sirve o cuando necesito una?)

Site collections

A site collection is a set of Web sites that have the same owner and share administration settings. Each site collection contains a top-level Web site and can contain one or more subsites.

Capacity

The recommended guideline for acceptable performance is to implement fewer than 50,000 site collections per Web application. Scaling out by distributing site collections across multiple database servers provides additional storage capacity and throughput.

Sharing and isolation

Site collections introduce several sharing and isolation opportunities that affect permissions, navigation, and feature deployment.

The following items can be shared within a site collection and cannot be shared across site collections:

  • Master pages

  • Page layouts

  • Images

  • Site templates

Additionally, permissions and navigation are isolated at the site collection level in the following ways:

  • Subsites within a site collection can inherit permissions from the top-level site.

  • Site collections cannot inherit permissions from other site collections.

  • There is no built-in navigation from one site collection to another.

Finally, Office SharePoint Server 2007 aggregates search results across site collections based on a user’s permissions, regardless of the number of site collections or databases (depending on search scopes).

 

Finalmente, sobre sites: (Que es un Site o sitio, desde el punto de vista de SharePoint, para que me sirve o cuando necesito uno?)

Sites

A site is one or more related Web pages that are hosted inside a site collection.

Capacity

The guideline for acceptable performance is to implement fewer than 250,000 sites per site collection. You can create a very large total number of Web sites by nesting the subsites. For example, 100 sites, each with 1000 subsites, is 100,000 Web sites. The maximum recommended number of sites and subsites is 125 sites with 2,000 subsites each, for a total of 250,000 sites.

Sharing and isolation

Sites include built-in navigation from one subsite to another within a site collection. There is no built-in navigation from one site collection to another.

As with site collections, separate sites are vulnerable to cross-site scripting attacks from other sites within the domain.

Configurable elements

From within each site, you can add user or group accounts to the Owners group for that site.

 

 

Ahora, dentro de los sitios almacenamos información y/o documentos. (finalmente, como manejamos y utilizamos la información que almacenamos o subimos a un sitio de SharePoint –que finalmente se almacena en la base de datos previamente definida de SQL Server-).

Identify primary objectives for sites

SharePoint sites are flexible and can help you accomplish many different things. However, to have a useful and successful site or group of sites, you need to be able to focus the sites on some primary objectives. That is, you need to know what you are trying to accomplish with a site before you can design it. For example:

  • Do you want to communicate with others in your organization by posting bulletins or announcements and gathering feedback?

  • Do you want to foster team collaboration by giving team members a place to share ideas and work on projects together?

SharePoint sites can assist with both of these objectives. If you have multiple objectives, you might best be served by creating multiple, possibly interrelated, sites. However, you can have multiple objectives for a single site. If you are limited to a single site, organize the site so that users looking for the communication point can find it right away, and users looking to share information and ideas or store documents know where to start.

Review the following objectives. Consider which of these objectives most closely align with your needs for each site you are designing.

Document storage

Document storage and workflow are key functions of many sites, even sites that are primarily used for communication or collaboration. However, sometimes you might need a dedicated document storage site for your organization. Whether you require a special site for document storage depends on many factors, such as how many documents need to be stored, how many people are contributing documents, who needs to act on the documents, and so on. You will have time to explore how to structure document storage later in the planning process. For more information, see Plan document libraries (Windows SharePoint Services).

Document storage sites or document storage sections of other sites often include the following features:

  • The ability to check documents in or out, track changes to documents, and keep multiple versions of documents.

  • The ability to route documents for approval or through specific processes before publishing them to a larger audience.

    NoteNote:

    Windows SharePoint Services 3.0 includes a workflow capability that you can use to create a custom workflow process to route documents for approval.

  • The ability to tag documents with metadata, so that documents can be more efficiently sorted and managed.

Para más info: Plan document libraries y Plan site and features