The AdminSite object provides methods for administering a site, such as specifying data sources and user accounts. The object keeps a number of properties related to the configuration in the site dictionary, an implementation of a Dictionary object called MSCSSite. These properties include the short and long names of the site, the secure host, the nonsecure host, and the names of other Dictionary objects such as lists of named connection strings and named queries.
All site-related configuration properties are accessed through the site dictionary, and saved in the Site.csc file.
For information about the relationship between the AdminSite object, the site dictionary, and the Site.csc file, see “Managing the Commerce Server Site” in Architecture of a Business-to-Consumer Site in the Commerce documentation..
The AdminSite object is not used in Commerce Server sites themselves. The site configuration properties can be accessed from within Commerce Server site scripting pages by using FileDocument to read the properties into an instance of the site dictionary.
An instance of the AdminSite object is usually created by WebAdmin, the Commerce Server Snap-in for the MMC, and by the Site Foundation Wizard.
To create an AdminSite object, use the Server.CreateObject method, specifying Commerce.AdminSite as follows:
Set AdminSite = Server.CreateObject("Commerce.AdminSite")
Active Server Pages (ASP) scripts that access the Microsoft® Internet Information Server (IIS) metabase require administrator privileges on the computer on which IIS is running. When you execute these scripts from a remote computer, you must connect through a secure connection, such as the Microsoft® Windows NT® Challenge/Response Authentication method. It is suggested that you create a server or directory for your administrative .asp files and set the directory security authentication method to Windows NT Challenge/Response for the server or directory.