Install Project Server to existing WSS 3.0 service

[rwstrang]

Good morning,

Hopefully this is an easy one for someone out there. I have been tasked
with bringing up a Project Server 2007 server. I would like to configure
this installation to use an exsting implementation of WSS 3.0. There is a
ton of documentation on how to integrate with an existing MOSS 2007
implementation, but nothing for WSS 3.0. Can anyone point me in the right
direction?

-Rich

 

[Andrew Lavinsky]

The MOSS stuff should all apply more or less. Just less configuring of some
of the MOSS items.

You're best bet though is to 1) Deploy PWA in it's own site collection/content
db, and 2) If possible, deploy the workspaces in their own site collection/content
db.

Other than that, I would also ask why you want to combine MOPS and an existing
WSS farm. The general recommendation is to stand MOPS up as its own farm,
and then use links to make it look like it's integrated with your existing
WSS environment.


- Andrew Lavinsky
Blog: http://blogs.catapultsystems.com/epm

 

[rwstrang]

Thanks for the response,

I have no issues with standing up MOPS in its own farm, but I have one SQL
server available to me and it currently hosts the WSS databases. If I stand
up a MOPS farm and use the same SQL Server as the WSS farm would it cause
problems and conflict? If it would conflict, would creating a new instance
of SQL on that server be a solution?

-Rich

 

[Andrew Lavinsky]

I don't see any issues with that scenario. It's a pretty common usage scenario
in fact. As long as your SQL box has sufficient specs to support that, you
should be good.

....now we venture out of my comfort zone into SQL, but you may want to consider
using a separate instance of SQL on the same box. Consider if you might
move the Project Server dbs to a new server in the future. It'll be a lot
easier to stand up a new SQL box, and create an instance with the same name
as before than having to point everything to a whole new server. (Not sure
I phrased that accurately, but I hope you get the gist).

Other than that consideration, I don't know of another reason to split SQL
into multiple instances from a Project Server perspective.

- Andrew Lavinsky
Blog: http://blogs.catapultsystems.com/epm

 

[Gary Chefetz]

Andrew:

One of the big motivators is security.

 

[Andrew Lavinsky]

True.


- Andrew Lavinsky
Blog: http://blogs.catapultsystems.com/epm