Project Server and MOSS 2007

[BK]

We have MOSS 2007 and Project Server 2007. We want to deploy them
together in the same farm and utilize the workflow capabilities. Does
anyone have a good reference for this as we have some questions that
may be fairly basic and others I think will be harder to solve.

For instance, We are thinking that our main project site will be in
MOSS. Then when we create and publish a schedule the workspace for
that file will be under */PWA/. Is there a way to create project
workspace in MS Project as part of that main MOSS Project site.
Otherwise our structure will be

http://servername/ProjectA -- for the main site in MOSS
http://servername/PWA/... -- for the Project web access portion
http://servername/PWA/ProjectA -- for the MS Project specific
workspace

Is there a way to make the last part
http://servername/ProjectA/Management

Or to make it part of the MOSS site somehow, while maintaining the
issues, risk, etc. functionality.

Thanks
Bryant

 

[Ben Howard]

As there is no reliance on MOSS, I don't think you can do what you want.
Even workflow does not rely on MOSS, unless you want to use the shipped
proposals workflow, or you want to use SharePoint designer as your workflow
design tool. If you want to create your own workflow using VS.NET then you
don't need MOSS.

 

[Gary L. Chefetz [MVP]]

BK:

Each Project Workspace is its own site. You can create these under the PWA
site collection or create them in a separate site collection. In either
event, you have the top-level site collection in the URL such as:
http://<servername>/<sitecollection>/ProjectWorkspaceName in this case
<sitecollection> could equal "PWA" or "Sites" or whatever you prefer.


--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[James Fraser]

Each Project Workspace is its own site. You can create these under the PWA
site collection or create them in a separate site collection. In either
event, you have the top-level site collection in the URL such as:
http://<servername>/<sitecollection>/ProjectWorkspaceName in this case
<sitecollection> could equal "PWA" or "Sites" or whatever you prefer.

I wanted to pile on here and add something I recently learned.
In PWA 2007, each Project Workspace is created as a separate "Web"
while in Project Server 2003 they were created as "Site
Collections" ( I think. Someone please correct me if I'm wrong,)

Anyway, one functional difference is that in 2003, you could take the
WSS_Content database and attach it to a different site. This would
move the Project Workspaces to that different site.

This will not work in Project Server 2007, as the webs don't get
attached when you add a content DB.

Also note that the workspace content is kept in the SSP WSS Content
database, not the content database for the default web site as you
might expect.


Please correct me if you know different, but this is my experience...
James Fraser

 

[Gary L. Chefetz [MVP]]

James:

I'm fairly certain you can use a SharePoint migration tool to do this.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[James Fraser]

James:

I'm fairly certain you can use a SharePoint migration tool to do this.
[...]

Anyway, one functional difference is that in 2003, you could take the
WSS_Content database and attach it to a different site. This would
move the Project Workspaces to that different site.

Yes, STSADM.exe backup operations will backup and restore the "Webs"
and is now the method to restore sites for a Project Server 2007
instance.

But in Project Server 2003, a simple SQL restore of a content DB and
then adding that content DB to an already extended SharePoint url
would be a quick way to recover sites. This process will not work with
the 2007 content databases.


James Fraser

 

[BK]

Thanks Gary,

As a follow on, I want to describe our situation. We have Project
sites that are set up under MOSS as team collaboration sites. I
essentially want to know if I can use that site as my MS Project
workspace (It is ok if I have to use that template when setting up the
moss site). The kicker is that the MOSS site will be set up before
the Project Plan and I will need to link it to the existing MOSS site
after the project is published.

My first question is do you think this is possible? and if so what
functionality will I lose?

My reason for this endeavor is to integrate the issues / risks / other
task information from PWA into the my site section of MOSS so that
users have a central location for all of their project information.

Has anyone tried this?

By the way Gary I have the VBA Programming and Enterprise Project
Management books and both have been invaluable in getting us up to
speed on the Project platform to this point.

Thanks
Bryant

 

[Gary L. Chefetz [MVP]]

BK:

You can only use sites that are provisioned using the customized Project
Workspace template or a custom template based on that template. You cannot
use a SharePoint team site and connect it to Project Server. Your best bet
is to migrate the content when your project site is ready.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting: http://www.msprojectexperts.com
For Project Server FAQS: http://www.projectserverexperts.com

 

[BK]

BK:

You can only use sites that are provisioned using the customized Project
Workspace template or a custom template based on that template. You cannot
use a SharePoint team site and connect it to Project Server. Your best bet
is to migrate the content when your project site is ready.

--

Gary L. Chefetz, MVP
MSProjectExperts
For Project Server Consulting:http://www.msprojectexperts.com
For Project Server FAQS:http://www.projectserverexperts.com

I wanted to post and update everyone on what we are doing as a
resolution to this.

We have decided to make our Company wide "Site Template" a customized
version of the PS Project Workspace Template. We creates these in our
http://Servername/Projects/ site collection. We have turned off
automatic workspace provisioning in Project Server and instead when a
project is published, we point it to the already created workspace. I
has been working great. Thanks to everyone for the advice and
assistance. I hope to return the help soon enough.

Bryant