With my development about 1/2 done, I have been interested in moving what I have to a test environment, and I am having a horrible time. Here is the problem: The web server that will host the Commerce Server application will be on a separate server than the databases. I installed Commerce Server on the web server without event. I also was able to configure the databases so that the MSCS_Admin and CatalogScratch databases were created on the right server. Here's where the fairy tale ends however.
The installation instructions say to then unpack the CSharpSite pup package. Well, since I don't want to use the default ootb site, I instead unpacked MY packaged site from my development machine. Again, the databases were created on the correct DB server (the same as where the Admin Database is), and the Commerce Server Manager matches my dev box perfectly.
The main issue is this. We have a domain group for Catalog Admins, and my domain account is a member of this group. I set up azman so that this group qualifies as Catalog Administrator, the highest level of authorization. I have tested the catalogwebservice and invoked a method successfully. This proves I have IIS and the Database connectivity set up correctly... but when I go into the Business Application (Catalog Manager), I see no catalogs, and furthermore, I don't have the option to create one. When I add my domain user account by itself (without the group) to azman, it works just fine.. this is baffling.. i just don't get it..
I do have another minor issue, but at least solving this one will make me feel so much better about where this is going. Anyone have any ideas
Thanks,
Dave
Commerce Server Deployment Nightmare
nglow
Dave,
I had exactly the same issue with my deployment. Azman "seems" to have trouble using Domain groups but it works fine if you setup local (machine) groups and add domain users to those groups. I'm not exactly sure how this affects a web farm deployment but for a single web server situation it seems to work. I haven't had the time to research this issue so I'm not quite sure if this is a bug in azman or not.
Jeff Lynch
MVP Windows Server System - Commerce Server
http://codebetter.com/blogs/jeff.lynch
Leaf.
You dont see the catalogs in the Businer Manager unless you add the user to the Authorization Manager
http://blogs.msdn.com/vinayakt/archive/2006/06/28/Securing-the-catalog-system.aspx
John.Q.Francis
Vinayak,
Are you saying that the authorization stores will not allow windows groups to be added for admin functionality in a production environment I will need to have someone do an azman config each time a new user is given permission to add catalogs rather than just having a domain admin add the user to a predefined group
I have already added the user to the group that I specified as the admin for the catalog system. this did not work.
GAtkins
Jeff,
Thanks for the response. The installation instructions say that CS2007 supports the distributed configuration, and am specifically requested to create all of these groups for each web service as domain accounts, so I hope that it can be supported. On my development machine, the entire environment is running fine but this is because, as you said, everything is on one machine with local service accounts and perms groups, but in production, DB and the CS2007 install will be on separate machines.. so this could throw a wrench in everything :)
Thanks again,
Dave
ititrx