Multiple Instances of Project Server 2003

[jcluthe]

Hopefully this is not a duplicate question, I scanned for a while
before I posted.

I need to set up Project Server 2003 so that multiple groups can have
their own instances. I want to set it up so that the server name is the
same, just the instance name changes....for example,
http://sadl40000/<instance1>, http://sadl40000>/<instance2>. I have
been reading & reading and I am not getting a definate answer on how to
do this. Anyone know what I'm talking about?

I already have the initail instance set up by the installer,
http://sadl40000/projectserver.

Thanks,

John

 

[Dale Howard [MVP]]

John --

You need to download and use the Edit Site tool for this purpose. It is
available for free download at:

http://www.microsoft.com/downloads/...3e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

Carefully read the instructions document included in the download. I
believe you will find that it can solve your problem nicely. Hope this
helps.

 

[Marc S.]

John,

Download and install the EditSite tool to create additional instances for
your Project Server installation:
http://www.microsoft.com/downloads/...3e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

After installing there's two things you need to do:
1/ Register the pds.wsdl for the new instances on your website (e.g.
ProjectServer2 on Default Web Site). Right click the name of the instance,
choose Properties, click the 'configuration' button, click 'add' and browse
for the following file: X:\Program Files\Common
Files\MSSOAP\BINARIES\SOAPIS30.DLL. Verbs: Limit to GET, POST.
If you check the configuration for your default instance (that was created
automatically during the installation) you will notice that the pds.wsdl is
already contained in the list of application extensions in properties. For
all instances created with the EditSite tool, however, this is not the case.
2/ Run the EditSite tool and check the connection of your current
instance/site by clicking the 'Test' button. Correct connection information
for either ProjectServerUser or ProjectUser, depending on which connection
test fails.

You can treat the several instances like completely separate installation as
far as user permissions are concerned. Simply add/remove all the users that
should have/have not access to the instance.

Hope this helps...

Marc S.

 

[jcluthe]

Thanks, that worked perfectly.

John,

Download and install the EditSite tool to create additional instances for
your Project Server installation:
http://www.microsoft.com/downloads/...3e-54e1-40a9-9bb8-2dd293226b6f&DisplayLang=en

After installing there's two things you need to do:
1/ Register the pds.wsdl for the new instances on your website (e.g.
ProjectServer2 on Default Web Site). Right click the name of the instance,
choose Properties, click the 'configuration' button, click 'add' and browse
for the following file: X:\Program Files\Common
Files\MSSOAP\BINARIES\SOAPIS30.DLL. Verbs: Limit to GET, POST.
If you check the configuration for your default instance (that was created
automatically during the installation) you will notice that the pds.wsdl is
already contained in the list of application extensions in properties. For
all instances created with the EditSite tool, however, this is not the case.
2/ Run the EditSite tool and check the connection of your current
instance/site by clicking the 'Test' button. Correct connection information
for either ProjectServerUser or ProjectUser, depending on which connection
test fails.

You can treat the several instances like completely separate installation as
far as user permissions are concerned. Simply add/remove all the users that
should have/have not access to the instance.

Hope this helps...

Marc S.