Services Infrastructure for Project Server
Windows SharePoint Services Infrastructure for Project Server
Microsoft Office Project Server 2007 is now a full member of a Windows SharePoint Services server farm. Each Project Web Access site collection can include subsites and an optional project workspace site for each project. A server farm with one Project Server installation can include multiple Project Web Access applications and Shared Services Providers (SSPs).
Project Server can import SharePoint task lists as project proposals. This article describes how Project Server and Windows SharePoint Services work together, as well as some of the ways to use SharePoint data. The article includes the following sections.
*
Windows SharePoint Services Infrastructure
*
PSI Methods and Datasets for Project Workspaces
*
Using SharePoint Data
o
Resource Name Conflicts
o
Getting the Site ID for Impersonation
o
Problems with Importing SharePoint Task Lists
Windows SharePoint Services Infrastructure
Project Server middle-tier services are contained in an SSP virtual directory. You can see in Internet Information Services Manager that the Office Server Web Services application contains the name of the SSP virtual site (for example SharedServices1). Windows SharePoint Services manages the front-end Web sites in the associated content Web applications (Figure 1). The SSP manages shared services that are installed on the server. Windows SharePoint Services includes the Search, Incoming E-Mail, and Web Application services. Project Server includes the Project Application Service. Microsoft Office SharePoint Server 2007 includes Excel Calculation Services, Document Conversions services, and a higher-level Search service. When you provision a Project Web Access instance, the Shared Services Administration application creates a Project Web Access site that uses the Project Application Service.
The Project Web Access site is a Windows SharePoint Services SPSite object that is created under the top-level Web site of an extended SharePoint Web application.
Figure 1. Windows SharePoint Services infrastructure for Project Server
SharePoint infrastructure for Project Server
Project workspaces are Windows SharePoint Services SPWeb objects. You can choose to create a project workspace for a project when it is published. A project workspace functions as team collaboration Web site for the project, and contains the specialized SharePoint lists for project documents, issues, risks, and deliverables. A project workspace also includes other lists defined in the default team collaboration site definition, including announcements, events, project tasks, and so forth.
You can create a project workspace as a child of any site in the SharePoint content Web application. Project workspaces can be children of the Project Web Access site, other project workspaces, or even other SharePoint sites created from non-project site templates.
NoteNote:
While the design for workspace location is flexible, we recommend that you create project workspaces as children of the Project Web Access site to make it easier to locate related workspaces.
For example, suppose the URL of the default Web site of a Project Server installation is http://ServerName, and you extend the top-level Web site to host the project team site (http://ServerName/default.aspx). When you create an SSP, Windows SharePoint Services also creates the SSP administration site, with the Shared Services Administration: SharedServices1 home page (http://ServerName:11863/ssp/admin/default.aspx).
If you navigate to the Manage Project Web Access Sites page (http://ServerName:11863/ssp/admin/_layouts/managepwa.aspx) and provision a Project Web Access instance named ProjectServerName, the Project Web Access application is a subsite of the top-level Web site with the URL http://ServerName/ProjectServerName.
Sites created within the same site collection (that is, under the ProjectServerName site in the previous example) share the same SharePoint content database and can benefit from the cross-site aggregation features of Windows SharePoint Services. The Project Web Access site URL is the default path under which project workspaces are created. The default workspace URL helps to organize all of the collaborative data for projects in the Project Web Access instance. A Project Server administrator can change the default workspace URL in the Project Workspace Provisioning Settings page in Project Web Access (http://ServerName/ProjectServerName/_layouts/pwa/Admin/WorkspaceProvisioningSettings.aspx), or use an application that programmatically changes the default workspace with the Project Server Interface (PSI).
PSI Methods and DataSets for Project Workspaces
You expose all features of the Project Workspace Provisioning Settings page in Project Web Access by using the [WssInterop Web service] (http://ServerName/ProjectServerName/_vti_bin/psi/wssinterop.asmx). All project workspace programming begins with the creation of a WssInterop object. The WssInterop Web service defines the following three datasets:
*
ProjectWSSInfoDataSet Includes a reference to the server; name of the workspace subsite; and lists of issues, risks, deliverables, and other information for a project workspace. Use ReadWssData to get a ProjectWSSInfoDataSet for a specified project.
*
WssSettingsDataSet Contains one row in WssAdminDataTable that includes all of the properties for provisioning a project workspace in the Project Web Access instance. Use ReadWssSettings to get a WssSettingsDataSet; use UpdateWssSettings to change the provisioning settings.
*
WssServersDataSet Contains a list of all Web applications known to the Project Web Access instance. Use ReadWssServerInfo to return a WssServersDataSet. You can choose a Web application in the list for project workspace provisioning and linking.
For a code sample that uses ReadWssServerInfo, ReadWssSettings, and UpdateWssSettings, see Extending the Project Workspace Template.
For a sample that uses ReadWssData, see How to: Use the OLP to Link an Object to a Task.
For more information about Project Web Access architecture and the SSP, see Project Server Architecture and Project Server Programmability. For more information about Windows SharePoint Services site definitions, see Working with Templates and Definitions in the Windows SharePoint Services 3.0 SDK.
Microsoft Office Project Server 2007 is now a full member of a Windows SharePoint Services server farm. Each Project Web Access site collection can include subsites and an optional project workspace site for each project. A server farm with one Project Server installation can include multiple Project Web Access applications and Shared Services Providers (SSPs).
Project Server can import SharePoint task lists as project proposals. This article describes how Project Server and Windows SharePoint Services work together, as well as some of the ways to use SharePoint data. The article includes the following sections.
*
Windows SharePoint Services Infrastructure
*
PSI Methods and Datasets for Project Workspaces
*
Using SharePoint Data
o
Resource Name Conflicts
o
Getting the Site ID for Impersonation
o
Problems with Importing SharePoint Task Lists
Windows SharePoint Services Infrastructure
Project Server middle-tier services are contained in an SSP virtual directory. You can see in Internet Information Services Manager that the Office Server Web Services application contains the name of the SSP virtual site (for example SharedServices1). Windows SharePoint Services manages the front-end Web sites in the associated content Web applications (Figure 1). The SSP manages shared services that are installed on the server. Windows SharePoint Services includes the Search, Incoming E-Mail, and Web Application services. Project Server includes the Project Application Service. Microsoft Office SharePoint Server 2007 includes Excel Calculation Services, Document Conversions services, and a higher-level Search service. When you provision a Project Web Access instance, the Shared Services Administration application creates a Project Web Access site that uses the Project Application Service.
The Project Web Access site is a Windows SharePoint Services SPSite object that is created under the top-level Web site of an extended SharePoint Web application.
Figure 1. Windows SharePoint Services infrastructure for Project Server
SharePoint infrastructure for Project Server
Project workspaces are Windows SharePoint Services SPWeb objects. You can choose to create a project workspace for a project when it is published. A project workspace functions as team collaboration Web site for the project, and contains the specialized SharePoint lists for project documents, issues, risks, and deliverables. A project workspace also includes other lists defined in the default team collaboration site definition, including announcements, events, project tasks, and so forth.
You can create a project workspace as a child of any site in the SharePoint content Web application. Project workspaces can be children of the Project Web Access site, other project workspaces, or even other SharePoint sites created from non-project site templates.
NoteNote:
While the design for workspace location is flexible, we recommend that you create project workspaces as children of the Project Web Access site to make it easier to locate related workspaces.
For example, suppose the URL of the default Web site of a Project Server installation is http://ServerName, and you extend the top-level Web site to host the project team site (http://ServerName/default.aspx). When you create an SSP, Windows SharePoint Services also creates the SSP administration site, with the Shared Services Administration: SharedServices1 home page (http://ServerName:11863/ssp/admin/default.aspx).
If you navigate to the Manage Project Web Access Sites page (http://ServerName:11863/ssp/admin/_layouts/managepwa.aspx) and provision a Project Web Access instance named ProjectServerName, the Project Web Access application is a subsite of the top-level Web site with the URL http://ServerName/ProjectServerName.
Sites created within the same site collection (that is, under the ProjectServerName site in the previous example) share the same SharePoint content database and can benefit from the cross-site aggregation features of Windows SharePoint Services. The Project Web Access site URL is the default path under which project workspaces are created. The default workspace URL helps to organize all of the collaborative data for projects in the Project Web Access instance. A Project Server administrator can change the default workspace URL in the Project Workspace Provisioning Settings page in Project Web Access (http://ServerName/ProjectServerName/_layouts/pwa/Admin/WorkspaceProvisioningSettings.aspx), or use an application that programmatically changes the default workspace with the Project Server Interface (PSI).
PSI Methods and DataSets for Project Workspaces
You expose all features of the Project Workspace Provisioning Settings page in Project Web Access by using the [WssInterop Web service] (http://ServerName/ProjectServerName/_vti_bin/psi/wssinterop.asmx). All project workspace programming begins with the creation of a WssInterop object. The WssInterop Web service defines the following three datasets:
*
ProjectWSSInfoDataSet Includes a reference to the server; name of the workspace subsite; and lists of issues, risks, deliverables, and other information for a project workspace. Use ReadWssData to get a ProjectWSSInfoDataSet for a specified project.
*
WssSettingsDataSet Contains one row in WssAdminDataTable that includes all of the properties for provisioning a project workspace in the Project Web Access instance. Use ReadWssSettings to get a WssSettingsDataSet; use UpdateWssSettings to change the provisioning settings.
*
WssServersDataSet Contains a list of all Web applications known to the Project Web Access instance. Use ReadWssServerInfo to return a WssServersDataSet. You can choose a Web application in the list for project workspace provisioning and linking.
For a code sample that uses ReadWssServerInfo, ReadWssSettings, and UpdateWssSettings, see Extending the Project Workspace Template.
For a sample that uses ReadWssData, see How to: Use the OLP to Link an Object to a Task.
For more information about Project Web Access architecture and the SSP, see Project Server Architecture and Project Server Programmability. For more information about Windows SharePoint Services site definitions, see Working with Templates and Definitions in the Windows SharePoint Services 3.0 SDK.
Comments