We have struggled a lot of how to set up multiple dev env.

We are now setting upp for each developer a Win2003 image conected to a
central SQL 2005 server and all in same AD using AD accounts for all creted
users including CS2007 setup (as in install doc from CS2007 RTM).

We successfully have setup DEV01.
We setup DEV02 usind AD.MSCS_Admin and a "Add Web Server" to connect to
CS2007 central admin DB and Site.

There are several steps that we more or less guess how to handle (Example,
Copy the azsman.XML files from DEV01 to DEV02 to have same rigths and make
Manager apps up)

After the setup therea are still some questions and at this moment we cant
be shure to have a correct working installation, examples caching, refresh
in Manager etc.

Is there no document explaining the exact HowTo add a new server to an
existing CS2007 site? Or how to setup multiple dev environment best
practices for CS2007?

We consume far too much time testing configurations to set this up in a
proper way. We like to have an efficient development environment up now.

Best regards, Johan Sörlin, Sigma Sweden

[ Post a follow-up to this message ]

I'm struggling with the same problem and was planning on going down the same
road you did: central SQL2005 with developers having VMs with a CS server
installation that points to that database.

Did you have any problems with the developer's local ASPNET worker account
being able to access the database?


Thomas

"Johan Sorlin" wrote:

> We have struggled a lot of how to set up multiple dev env.
>
> We are now setting upp for each developer a Win2003 image conected to a
> central SQL 2005 server and all in same AD using AD accounts for all crete
d
> users including CS2007 setup (as in install doc from CS2007 RTM).
>
> We successfully have setup DEV01.
> We setup DEV02 usind AD.MSCS_Admin and a "Add Web Server" to connect to
> CS2007 central admin DB and Site.
>
> There are several steps that we more or less guess how to handle (Example,
> Copy the azsman.XML files from DEV01 to DEV02 to have same rigths and make
> Manager apps up)
>
> After the setup therea are still some questions and at this moment we cant
> be shure to have a correct working installation, examples caching, refresh
> in Manager etc.
>
> Is there no document explaining the exact HowTo add a new server to an
> existing CS2007 site? Or how to setup multiple dev environment best
> practices for CS2007?
>
> We consume far too much time testing configurations to set this up in a
> proper way. We like to have an efficient development environment up now.
>
> Best regards, Johan Sörlin, Sigma Sweden
>
>

[ Post a follow-up to this message ]

No. We have konfigured the ASPNET accout and the IIS_WPG on Win2003.
(You add doamin user to IIS_WPG). Couldnt find the document we followed on
this now.

We now have setup one virtual image and copied it to all our developers.
Yes, the server complains about other servers with same name, but thats the
only problem. We will get education on CS2007 late september. After thet we
will look in to this again. There is a Multi_dev_Setup.doc document from MS
for CS2002.
We got that and tip to do the same with CS2007. The answer below says SQL
Server to each developer, the CS2002 doc has acentral SQL Server.

Also there are licensing concerns. You can only add one CS2007 server for
the development licens. (The copy same server technic fixes this. Also every
developer has all services local, like DM etc, to debug)

In the discussions with Microsoft we got the following embryo to multidev:

 ========================================
==========
Best Practices.

===============
1) Each developer has Commerce Server and SQL installed locally.

2) Each developer maintains their own MSCS_Admin database. ( This tip was
from one of our consultants who found that this works every time for them.)

3) Each Developer can choose to either

a. Point their resources locally and maintain local copies of
the Profiles and Catalog Databases or

b. Use a Centralised SQL Server.

4) Don’t use the Add Web Server command if you’re using a Centralised
MSCS_Admin database. This makes Commerce Server think it is operating in a
Web Farm and so you can only specify one host name for all of the developers
machines. Using localhost as the secure and non secure Host Name will allow
you to do this if you need to.

5) Use the Query String Builder for URL’s in your code.

6) Download the IIS 6 Resource Kit and use the SelfSSL tool for testing
HTTPS connections.
 ========================================
============

[ Post a follow-up to this message ]