This documentation relates to an earlier version of the SharePoint Connector.
View

Unknown macro: {spacejump}

or visit the current documentation home.

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 3 Current »

There are several options for integrating SharePoint and Confluence from a site infrastructure standpoint.

On this page:

Terminology

Before discussing the options, we need to describe the structure and terminology of SharePoint and Confluence.

SharePoint Terminology

SharePoint has the following concepts:

  • Farm
  • Web Application
  • Site Collection
  • Site

In SharePoint a farm is the top level entity. An enterprise may have a production farm and a development/test farm for their intranet. You typically do not have multiple farms to cover something like an intranet except in circumstances such as regional separation across the globe. The same applies to an extranet or a public facing website. There can be many servers within a farm and they can perform different roles such as a search index server, a web front end server, database servers, etc.

A farm can have multiple web applications. A web application is usually a security boundary since it maps to an IIS web site which can have some added control over access. For example, one web application may allow anonymous access and another may not.

A web application can have multiple site collections. A site collection is simply a collection of sites. It has a single top level site, also called the root site. Each site can have any number of child sites.

You might have a site collection per department or you might have all departments in the same site collection. If you use 'My Sites', you will have a separate site collection per user.

Confluence Terminology

Confluence has the following concepts:

  • Installation
  • Cluster node
  • Space
  • Page

An enterprise may have several Confluence installations (similar to SharePoint farms). Each Confluence installation can be hosted in a single server or on several cluster nodes.

A single Confluence installation can have multiple spaces. A space can have multiple pages. The pages can be organised in a hierarchical fashion where one page is the parent of another page.

Integration

Now that we have the terminology set out, we can discuss how SharePoint and Confluence integrate with each other.

SharePoint Integration with Confluence

SharePoint integrates with Confluence through its web parts and through search. You can point a single SharePoint site at a single Confluence installation. You can point as many SharePoint sites at Confluence as you like, regardless of whether they are in the same or different farms, web applications or site collections. They can point to the same Confluence installation or different Confluence installations.

One limitation is that the Confluence web parts within a particular SharePoint site must point to the same Confluence installation. The web parts can, however, point to different spaces or pages within the Confluence installation. If you have several Confluence installations, you can have one SharePoint site point to one Confluence installation and another SharePoint site point another Confluence installation.

The issues that address this limitation are CSI-131 and CSI-144.

The above point also causes a limitation with the integrated search where SharePoint can only show search results for a single Confluence installation from a single SharePoint search site. However, you can have multiple SharePoint search sites and each one could show results from different Confluence installations.

The issue that addresses this limitation is CSI-109. Note that issue CSI-238 would replace the need for CSI-109.

Confluence Integrating with SharePoint

Confluence integrates with SharePoint through the sp-list macro. the sp-link macro and a search link. You can point a single Confluence installation at one or more SharePoint sites or site collections. The search link is separate from these settings and can only point to a single SharePoint search results site/page. If you have multiple installations of Confluence, you can point each one to the same or different SharePoint site collections.

Licensing

Once you have determined how you are going to integrate SharePoint and Confluence, you can determmine how your software will be licensed.

Microsoft Office SharePoint Server (MOSS) must be licensed with Microsoft. Windows SharePoint Services (WSS) 3.0 is free.

Each Confluence installation must be licensed with Atlassian. Cluster nodes are licensed separately. A 4-node cluster needs four Confluence licenses.

The Confluence SharePoint Connector must also be licensed with Atlassian. You must have a single license for the Confluence SharePoint Connector for every Confluence installation (or cluster node in an installation) that integrates with SharePoint. If you have one Confluence installation, you only need one license for the Confluence SharePoint Connector even if several SharePoint farms, web applications or sites are connecting to your Confluence installation.

RELATED TOPICS

Comparing SharePoint Versions and Editions
Installing the SharePoint Connector

  • No labels





Except where otherwise noted, content in this space is licensed under a Creative Commons Attribution 2.5 Australia License.