Resource Tables in the Administration Database
The configuration data for Commerce Server 2009 resources that are supplied with Commerce Server 2009 is stored in a Microsoft SQL Server database that is named MSCS_Admin. There are seven tables in this database that are important to understanding how the configuration data associated with custom resources can be maintained in this database, exposed through Commerce Server Manager, and deployed with Commerce Server Site Packager.
The following table summarizes the purpose of each of these tables.
Note
Do not modify the definition of any of these core tables for any reason. They are provided here for reference.
Table name |
Description |
|---|---|
ExtendedProps |
Stores the characteristics of resource properties (resource property schema). |
pupdbscripts |
A deprecated table that is used when configuring the deprecated GenericPuP object. |
ResourceProps |
Stores actual resource property values, as defined in the ExtendedProps table. |
Resources |
Defines actual resource instances, as defined in the SystemProps table. |
SiteResources |
Serves as a lookup mechanism for all resources that are installed in a site. |
Sites |
The starting point for retrieving data about a site. |
SystemProps |
Stores the characteristics for resources (resource schema). |
Retrieving the value of a resource property is a multi-step process. The first step is looking up the site name in the Sites table. The Sites table leads to the SiteResources table. This leads to the Resources table and then leads to the ResourceProps table, where actual resource property values are stored.
The following table shows the managed code administration objects you use to access the resource tables, perform value retrievals, and set new values. Use these free-threaded managed code objects in the run-time code for your site.
Managed Object |
Description |
|---|---|
Provides methods for management of global resources. |
|
Provides methods for management of site resources. |
|
Provides methods for faster retrieval of global and site resource property values. |
In some limited circumstances, you may have to use the unmanaged versions of these classes: SiteConfig Object, SiteConfigReadOnly Object, GlobalConfig Object, and GlobalConfig2 Object. For an example of one such circumstance, see Creating an Instance of an Address Resource.