Content Updated: August 15, 2003
Updated to include instructions about applying Commerce Server 2002 Service Pack 2.
This document provides detailed instructions for upgrading previous versions of Microsoft® Commerce Server to Microsoft Commerce Server 2002 Standard, Developer, or Enterprise Edition. This document assumes that you are upgrading a single computer.Commerce Server 2002 provides an Upgrade tool, CS2002Upgrade.exe, which you use to upgrade Commerce Server site resources and the Administration database. You must use the Upgrade tool to find out which resources you will need to upgrade from the previous version. You can also check the upgrade status of each site resource in Commerce Server Manager.
The following table lists the previous editions of Commerce Server and the supported upgrade paths.
| Upgrade from | To |
| Commerce Server 2002 Evaluation Edition | Commerce Server 2002 Enterprise Edition |
| Commerce Server 2002 Standard Edition | Commerce Server 2002 Enterprise Edition |
| Commerce Server 2000 | Any edition of Commerce Server 2002 |
| Site Server 3.0 | Any edition of Commerce Server 2002 |
When upgrading from any edition of Commerce Server 2000 to Commerce Server 2002, you should note the custom settings that you have made to the global resources and add them back in after your upgrade is complete.
Important If you are upgrading from a prerelease version of Commerce Server 2002, you must upgrade your Data Warehouse manually. See Upgrading a Prerelease Version of Data Warehouse.
Notes
If you have the Beta edition of Commerce Server 2002 installed, the license for that release expired on May 31, 2002. For more information, see Upgrading Commerce Server 2002 Evaluation Edition or Prerelease Versions.
Commerce Server 2002 does not directly support downgrading from Enterprise Edition to Standard Edition.
It is recommended that you read through this entire document before upgrading to Commerce Server 2002. The following topics are addressed:
The following table shows types of Commerce Server 2000 content and instructions for upgrading that content.
Note Data Transformation Services (DTS) packages created in Commerce Server 2000 cannot be used in Commerce Server 2002. For example, if you created DTS packages for importing data into the Data Warehouse, you must create new DTS packages in Commerce Server 2002. For information about creating new DTS packages, see SQL Server Books Online and "Importing Data into the Data Warehouse" in Commerce Server 2002 Help.
Important Before you upgrade any content on a server, make sure that no users are connected to that server. Otherwise, users may encounter non-functioning links in your Web site.
| To upgrade this type of content | Do this |
| Web pages (ASP and HTML files) | Use Microsoft Visual Studio®, Microsoft Application Center 2000, the Content Deployment tool, or another Web-page publishing tool.
For more information, see the Visual Studio or Application Center 2000 documentation. |
| Component Object Model (COM) applications | Transfer the appropriate dynamic-link libraries (DLLs) to the Web server, and then register them by using the command regsvr32 <dll-filename>. |
| Pipelines | Copy the appropriate pipeline (.pcf) files. |
Following is an overview of the steps required to upgrade from Commerce Server 2000 to Commerce Server 2002 Standard, Developer, or Enterprise Editions. Each of these steps is described in detail in the following topics.
Note To upgrade from any version of Commerce Server, you must run the Setup program through the user interface; you cannot run Setup in silent mode when upgrading to Commerce Server 2002.
Commerce Server 2002 has different software requirements than Commerce Server 2000. Before you upgrade, verify that you have installed all prerequisite software. For information about software requirements, see the Commerce Server 2002 Installation Guide at http://go.microsoft.com/FWLink/?LinkID=6125.
Note Commerce Server 2002 does not support upgrading from Microsoft Windows NT® Server 4.0 to Microsoft Windows® 2000 Server, and then installing Commerce Server 2002.
After you install Commerce Server 2002, it displays a dialog box that lists the resources you must upgrade.
Commerce Server 2002 provides an Upgrade tool, CS2002Upgrade.exe, that you use to upgrade Commerce Server 2000 site resources and the Administration database. After you run the Upgrade tool, it provides a list of resources that have not been upgraded from Commerce Server 2000. You can also check the upgrade status of each site resource in Commerce Server Manager.
It is strongly recommended that you perform the upgrade on a backup database.
When you upgrade from Commerce Server 2000, you also use the CS2002Upgrade.exe tool to upgrade the Data Warehouse resource.
Caution Run the migration scripts only once against the Data Warehouse database. If you run the scripts twice, the Data Warehouse database will be corrupted. To verify that the upgrade was successful, view the event log file and the MigrationTrace.txt file, located in the same path as the Upgrade tool. The upgrade for each site runs as a single transaction.
After you upgrade the Data Warehouse resource, you must change the connection strings and then update the Data Warehouse topology.
You perform these steps to make changes to your catalogs required by Commerce Server 2002.
After you upgrade the Commerce Server 2000 site resources, you must upgrade Commerce Server Business Desk to take advantage of the new Business Desk features.
After you upgrade to Commerce Server 2002, you must make a few additional changes to the site code in your Solution Sites.
After you upgrade to Commerce Server 2002, you must make a few additional changes to the site code in your Supplier Site.
To track the status of your Commerce Server 2002 upgrade, you can run the CS2002Upgrade.exe tool.
After you upgrade to Commerce Server 2002, you review specific files to check for errors and make certain the upgrade completed properly.
After you upgrade to Commerce Server 2002, it is recommended that you install Commerce Server 2002 Service Pack 2.
You use the following steps to upgrade to Commerce Server 2000 to Commerce Server 2002 Standard, Developer, or Enterprise Editions. Some versions of Commerce Server also require additional steps to complete the upgrade. You can find additional steps at the end of this procedure.
To upgrade all the resources in your Commerce Server application, you must first install Commerce Server 2002. For installation instructions, see the Commerce Server 2002 Installation Guide at http://go.microsoft.com/FWLink/?LinkID=6125.
Important The Commerce Server installation upgrades the Administration database. If you encounter problems while installing Commerce Server 2002 and the installation does not complete, the Administration database is not upgraded. The next time you try to install Commerce Server on the same computer, it will not detect that Commerce Server 2000 was installed previously, and as a result, the Administration database will not be upgraded. You must manually upgrade the Administration database.
For information about upgrading the Administration database, see Command line options for upgrading the Administration database and site resources (excluding the Data Warehouse).
Notes
After you install Commerce Server 2002, you do not use Commerce Server Site Packager to upgrade your the Business Desk application. To upgrade Commerce Server Business Desk, see Upgrading Commerce Server Business Desk.
After the Commerce Server 2002 installation process completes, a dialog box is displayed that lists the Commerce Server resources you need to upgrade.
To upgrade these resources, you use the Commerce Server 2002 Upgrade tool, CS2002Upgrade.exe, to run the migration scripts to upgrade Commerce Server 2000 site resources and the Administration database. The migration scripts are located on the Commerce Server 2002 CD in \Program Files\Microsoft Commerce Server 2002\Upgrade\Scripts. For detailed instructions about using the CS2002Upgrade.exe tool, see To upgrade site resources (excluding the Data Warehouse).
You can use the Upgrade tool to upgrade one resource at a time, or you can upgrade a combination of the following resources:
Note The Data Warehouse resource can only be upgraded as a single resource.
The Upgrade tool does not upgrade the following site resources:
Caution It is strongly recommended that you do not run the migration scripts directly on the Commerce Server databases.
It is strongly recommended that you perform the upgrade on backup databases. When you upgrade a resource, any customizations that were made to the Commerce Server 2000 resource schemas are lost. After you run the Upgrade tool, your site developer can move the customizations from the production databases to the upgraded backup databases.
Command line options for upgrading the Administration database and site resources (excluding the Data Warehouse)
The following table contains a list of the available command line options for upgrading the Administration database and site resources, and provides parameter syntax and a description of each option. The options appear in the order in which they should be upgraded. All command line options are case-insensitive.
Note The Data Warehouse resource requires additional command line options and cannot be combined with the other resources. For instructions, see Upgrading the Data Warehouse Resource.
Note If you have Microsoft SQL Server™ cluster servers, you can use option –N to upgrade each SQL server in the cluster for each resource.
| Option | Parameters | Description |
| -A | {connection string (optional)} | Upgrades the Administration database (MSCS_Admin).
You can specify a connection string to the Administration database. If a connection string is not specified, the connection string is obtained from the registry. |
| -C | {site name (optional)} | Upgrades the Product Catalog resource.
You can specify a site name. If no site name is specified, all installed sites are upgraded. |
| -T | {site name (optional)} | Upgrades the Transactions resource.
You can specify a site name. If no site name is specified, all installed sites are upgraded. |
| -G | {site name (optional)} | Upgrades the Transaction Config resource.
You can specify a site name. If no site name is specified, all installed sites are upgraded. |
| -U | {site name (optional)} | Upgrades the Profiles resource.
You can specify a site name. If no site name is specified, all installed sites are upgraded. |
| -M | {site name (optional)} | Upgrades the Campaigns resource.
You can specify a site name. If no site name is specified, all installed sites are upgraded. Note In Commerce Server 2002 Campaigns, you can specify the order in which percentage and dollar off discounts that have the same priority are applied. By default, dollar off discounts apply first. It is recommended that you view the Commerce Server 2000 discounts that contain percentage and dollar off discounts that have the same priority, and modify them if necessary. |
| -B | {site name (optional)} | Upgrades the Business Desk Permissions resource.
You can specify a site name. If no site name is specified, all installed sites are upgraded. |
| -N | {connection string } | Specifies the connection string to the database for the Business Desk Permissions, Product Catalog, Transactions, Profiles, and Campaigns site resources. This option overrides upgrading the site.
Note You must use this option for each server in the cluster. |
To upgrade site resources (excluding the Data Warehouse)
Important It is strongly recommended that you perform the upgrade on a backup database. When you upgrade a resource, any customizations that were made to the Commerce Server 2000 resource schemas are lost. After you run the Upgrade tool, your site developer can move the customizations from the production databases to the upgraded backup databases.
If you encounter problems while installing Commerce Server 2002 and the installation does not complete, the Administration database is not upgraded, and you must manually upgrade the Administration database. For information about upgrading the Administration database, see Command line options for upgrading the Administration database and site resources (excluding the Data Warehouse).
CS2002Upgrade <command line option {parameters}>
where CS2002Upgrade is the name of the upgrade tool.
For example, to upgrade the Product Catalog resource for the Retail site, and the Transactions Config resource for all installed sites, type:
CS2002Upgrade -C Retail -G
Or, to upgrade the Product Catalog resource using the connection string option, type:
CS2002Upgrade –C –N "Provider=SQLOLEDB;User Id=myuserid;Password=;Data Source=MyCatalogServer;Initial Catalog=MycatalogDatabase;"
For a list of command line options, see Command line options for upgrading the Administration database and site resources (excluding the Data Warehouse).
Note The Upgrade tool generates a trace file named CS2002Upgrade.log, which is located in the directory where CS2002Upgrade.exe is run. It is recommended that you check the CS2002Upgrade.log file for error messages for all upgraded resources (excluding the Data Warehouse).
If your Commerce Server 2000 Data Warehouse needs to be upgraded, the name of the database appears in a dialog box with a list of other resources after the Commerce Server 2002 installation process completes.
Commerce Server 2002 provides an Upgrade tool that you use to run the migration scripts to upgrade the Commerce Server 2000 Data Warehouse resource. The migration scripts are located in the Commerce Server 2002 folder in \Program Files\Microsoft Commerce Server 2002\Upgrade\Scripts.
The Data Warehouse and Analysis resources are upgraded at the same time, as one resource.
Caution Do not run the migration scripts directly on the Commerce Server databases; instead, use the migration tool (CS2002Upgrade.exe).
Run the migration scripts only once against the Data Warehouse database. If you run the scripts twice, the Data Warehouse database will be corrupted.
This section includes:
When you upgrade the Data Warehouse resource, the Analysis report definitions are installed and a new online analytical processing (OLAP) database is installed. The new report definitions utilize the cube designs in the new OLAP database and contain SQL queries that operate with the upgraded Data Warehouse.
The completed reports that were run before the upgrade will not exist in the upgraded database and will not appear in the Completed Reports module. However, the actual report files will be located in the virtual root directory in case you need to refer to them. (For example, <drive letter>:\retailbizdesk\analysis\completed reports.)
The Data Warehouse and Multiple Sites
When you upgrade the Data Warehouse resource, a site name parameter is required. To upgrade a Data Warehouse that contains more than one site, you select any one site within the Data Warehouse resource.
Because the entire Data Warehouse resource is upgraded, the data for all sites in the Data Warehouse is upgraded, regardless of the site name that you select. You update the site-specific topology information by running the Configuration synchronization DTS task after upgrading the Data Warehouse.
Notes
Creating the New Data Warehouse Database
The Data Warehouse upgrade process creates a new Data Warehouse database and a new OLAP database rather than upgrading the existing Data Warehouse database.
You can either create the new Data Warehouse database manually, or you can choose to have it created as part of the upgrade process. When you create the database manually, you can control elements such as the initial size of the database and where the files are placed. If the upgrade process creates the database, then the Upgrade tool determines the initial size and location.
A new OLAP database is always created as part of the upgrade process. You do not need to create it.
If for any reason the creation of the new Data Warehouse database fails, you must create it manually. For information about creating the Data Warehouse database, see Command Line Options for Upgrading the Data Warehouse.
Note Because the new database is in Unicode, the default size of the database is one-and-a-half times the initial size of the original database.
Command Line Options for Upgrading the Data Warehouse
When you run the Upgrade tool, you can create the new Data Warehouse database by specifying the server name using the -R option and the database name using the -D option in the Upgrade tool command line options. The Upgrade tool creates the data and log files for the new database in the SQL Server default directory.
If the new database already exists before you run the Upgrade tool, it should be empty. If the new database is not empty, the behavior of the Upgrade tool is undefined. You use the -D option in the Upgrade tool command line options to specify the name of the database that already exists.
The following table lists the available options for upgrading the Data Warehouse resource and provides parameter syntax and a description of each option. For detailed instructions for using these options, and an example, see Running the Data Warehouse Resource Upgrade.
| Option | Parameters | Description |
| -d | Upgrades the Data Warehouse resource. | |
| -S | {site name (required)} | Specifies the site for which to upgrade the Data Warehouse resource.
Note To upgrade a Data Warehouse that contains more than one site, you select any one site within the Data Warehouse resource. Because the entire Data Warehouse resource is upgraded, the data for all sites in the Data Warehouse is upgraded, regardless of the site name that you select. |
| -U | {user name} | Specifies the user name to connect to the new database. |
| -P | {password} | Specifies the password to connect to the new database. |
| -R | {destination server} | Upgrades the server on which the new database is to reside.
Note If you specify "localhost" as the destination server, it will only create the Data Warehouse database. It will not create the OLAP database. |
| -D | {destination database} | Specifies the database to which the Data Warehouse data is upgraded.
Note The connection string information in the Administration database is not upgraded to point to the new database. You must manually update the connection string. |
| -C | {Destination catalog} | Specifies the destination catalog.
The schema script that is provided with Commerce Server 2002 contains the catalog DWSchema, which is required to upgrade the Data Warehouse. |
| -E | Specifies Windows NT Authentication.
Note The -U and -P options cannot be combined with this option. |
Notes
CS2002Upgrade -C "Retail-1"
Before Upgrading the Data Warehouse Resource
Before you upgrade the Data Warehouse resource, consider the following recommendations:
Running the Data Warehouse Resource Upgrade
You use the Upgrade tool to run the Data Warehouse resource upgrade. However, after you upgrade the Data Warehouse resource, the Administration database continues to point to the Data Warehouse that existed before the upgrade. To point the Administration database to the new Data Warehouse, you must modify the connection strings in the Administration database, and then run the Configuration synchronization Data Transformation Services (DTS) task.
After you upgrade the Data Warehouse resource, you must run the Profile Data Import DTS task to upgrade the site terms in the Data Warehouse. For information about running the Profile Data Import DTS task, see "Running the Profile Data Import DTS Task" in Commerce Server 2002 Help.
Caution Run the migration scripts only once against the Data Warehouse database. If you run the scripts twice, the Data Warehouse database will be corrupted. To verify that the upgrade was successful, view the event log file and the MigrationTrace.txt file, located in the same path as the Upgrade tool. The upgrade for each site runs as a single transaction.
To run the Data Warehouse resource upgrade
CS2002Upgrade <command line option {parameters}>
where "CS2002Upgrade" is the name of the upgrade tool.
For example, to upgrade the Data Warehouse resource for the Retail site on MSServer2, type:
CS2002Upgrade -d -S Retail -U sa -P "myPwd-1" -R "MSServer2" -C DWSchema -D Retail_NewDW
For a list of command line options for the Data Warehouse, see Command Line Options for Upgrading the Data Warehouse.
Note The Data Warehouse upgrade generates a trace file, MigrationTrace.txt, which is located in the directory where CS2002Upgrade.exe is run. It is recommended that you check the migration trace file for migration error messages.
After you upgrade the Data Warehouse resource, you must update the Data Warehouse connection strings. This information is stored in the Administration database and is configured using Commerce Server Manager. You must then run the Configuration synchronization DTS task to update the connection string information in the Data Warehouse database.
Note When the Upgrade tool creates the new OLAP database, the user ID and password in the database connection string for the Analysis server is reset to blank. You must add a correct user ID and password.
To update the Data Warehouse connection strings
| Use this | To do this |
| SQL Server Authentication | Select this option to use a supplied user name and password to authenticate your logon information. |
| Windows NT Authentication | Select this option to specify that the provider request a secure (or trusted) connection to an instance of SQL Server running on Microsoft Windows 2000. |
| Server | Type the name of the SQL Server computer on which the Data Warehouse resides. |
| Database | Type the name of the connected Data Warehouse database. |
| Use this | To do this |
| Server | Type the name of the primary OLAP server on which the Analysis cubes reside. |
| Database | Type the name of the primary OLAP database that contains the Analysis cubes. |
| Use this | To do this |
| Server | Type the name of the secondary OLAP server on which the Analysis cubes reside. |
| Database | Type the name of the secondary OLAP database that contains the Analysis cubes. |
| Use this | To do this |
| Connect using HTTP | Select this option if you want to connect by using HTTP. |
| Server | Type the name of the OLAP server on which the Analysis cubes reside. |
| Database | Type the name of the OLAP database that contains the Analysis cubes. |
Running the Configuration Synchronization DTS Task
After you update the Data Warehouse connection strings, which are stored in the Administration database, you must run the Configuration synchronization DTS task to import the site configuration information stored in the Administration database to the Data Warehouse.
Note If you do not run the Configuration Synchronization DTS task, all of your data will appear in Greenwich Mean Time (GMT).
To run the Configuration synchronization DTS task
The DTS <New Package> window appears.
OR
Set the operation level to Data Warehouse level for all sites in a Data Warehouse, select the Data Warehouse name, and then click OK.
The data in your Data Warehouse is now synchronized with your application.
Running the Report Preparation DTS Task
After you run the Configuration synchronization DTS task, you must run the Report preparation DTS task to process the new online analytical processing (OLAP) cubes. The OLAP cubes must be processed for the reports to run in the Analysis modules.
Note If you do not run the Report Preparation DTS task, your basket events and sales data will not be processed.
To run the Report preparation DTS task
| Use this | To do this |
| Description | Type a description of the Report preparation task. |
| Data Warehouse | Select the Data Warehouse for which you are populating the OLAP cubes. |
| Sites | Select the site for which you are populating the OLAP cubes. |
| Processing Mode | Select Full to process the OLAP cubes in their entirety. |
| Retry Properties | Type the number of times you want the task to retry connection failures to the Data Warehouse. The default number of retry attempts is 10. |
| Seconds between retries | Type the number of seconds you want the task to wait between retry attempts. The default time interval is 30 seconds. |
The Executing Package dialog box appears, showing the progress of your import. When the import process is complete, the Package Execution Results dialog box informs you that it completed successfully.
The data is loaded into the OLAP cubes. You can now use the Commerce Server Business Analytics System, including Commerce Server reports, to analyze the data in the Data Warehouse.
After you upgrade to Commerce Server 2002, there are several catalog changes that you may want to make to your Commerce Server Catalog System, depending on your configuration. The following topics provide you with step-by-step information for making these changes.
This section includes:
Upgrading the Commerce Server 2000 Catalog System to the Commerce Server 2002 Multilingual Catalog System
Using the Upgrade tool, CS2002Upgrade.exe, you can convert your Commerce Server 2000 Catalog System to the Commerce Server 2002 multilingual Catalog System.
Note Since you could not create multilingual properties in Commerce Server 2000, you previously had to create different properties such as "Name_FR," "Name_English," and "Name_DE."
In Commerce Server 2002, you can now create a single multilingual property such as "Name." When the migration tool upgrades from a Commerce Server 2000 multilingual implementation to a Commerce Server 2002 multilingual implementation, it backs up the existing CatalogAttributes and CatalogDefintionProperties tables to the following property tables:
CatalogAttributes_CS2k_Multilingual_Upgrade
CatalogDefintionProperties_CS2k_Multilingual_Upgrade
To upgrade Commerce Server 2000 Catalog System to the Commerce Server 2002 Multilingual System
The following table lists the available options for upgrading your Commerce Server 2000 Catalog System to the Commerce Server 2002 Multilingual Catalog System.
| Option | Parameters | Description |
| -L | Specifies the option for converting the Commerce Server 2000 Catalog System to the Commerce Server 2002 multilingual catalog System. | |
| -N | {connection string (required)} | Specifies the connection string to the catalog database. |
| -X | {xml file name (required)} | Points to an XML file that specifies the mapping between the two-character or three-character language extension you used in your Commerce Server 2000 implementation and a culture name. For information about culture names for languages, see the languages.xml file, located on the Commerce Server 2002 CD-ROM in \Program Files\Microsoft Commerce Server 2002. |
To upgrade the Commerce Server 2000 Catalog System to the Commerce Server 2002 multilingual Catalog System
CS2002Upgrade <command line option {parameters}>
where CS2002Upgrade is the name of the upgrade script.
The following is an example of a typical XML file used to migrate a Commerce Server 2000 Catalog System to a Commerce Server 2002 multilingual Catalog System. This converts properties such as Description_ena, and Description_fr to a single multilingual property named Description.
<?xml version="1.0"?>
<UpgradeInfo>
<Language languagecode="ena" culture_name="en-AU"/>
<Language languagecode="fr" culture_name="fr-FR"/>
</UpgradeInfo>
CS2002Upgrade –L –N "Provider=SQLOLEDB; Integrated Security = SSPI;
Data Source=mycatalogserver;Initial Catalog=mycatalogdatabase;" -X "languages.xml"
For a list of command line options, see Command Line Options for Converting Catalog Properties.
Note The Upgrade tool generates a trace file named CS2002Upgrade.log, which is located in the directory where CS2002Upgrade.exe is run. It is recommended that you check the CS2002Upgrade.log file for error messages for all upgraded resources (excluding the Data Warehouse).
Converting Commerce Server 2002 Non-multilingual Properties to Multilingual Properties
After you upgrade the Product Catalog resource, you can use the Upgrade tool, CS2002Upgrade.exe, to convert the non-multilingual catalog properties in your catalog system to multilingual properties.
Command line options for converting catalog properties
Command line options for converting catalog properties
The following table contains the available options for converting your existing catalog properties to multilingual properties and provides parameter syntax and a description of each option.
| Option | Parameters | Description |
| -L | Use this option for converting non multilingual properties to multilingual properties | |
| -N | {connection string (required)} | Specifies the connection string to the catalog database. |
| -X | {xml file name (required)} | Specifies the list of properties to be converted to multilingual properties. |
CS2002Upgrade <command line option {parameters}>
where "CS2002Upgrade" is the name of the upgrade script.
Following is an example of a typical XML file to convert Description and Notes properties to multilingual properties:
<?xml version="1.0"?>
<UpgradeInfo>
<PropertyName>Description</PropertyName>
<PropertyName>Notes</PropertyName>
</UpgradeInfo>
CS2002Upgrade –L –N "Provider=SQLOLEDB; Integrated Security = SSPI;
Data Source=mycatalogserver;Initial Catalog=mycatalogdatabase;" –X "myxmlfile.xml"
Note The Upgrade tool generates a trace file named CS2002Upgrade.log, which is located in the directory where CS2002Upgrade.exe is run. It is recommended that you check the CS2002Upgrade.log file for error messages for all upgraded resources (excluding the Data Warehouse).
Commerce Server uses SQL Server full-text search for searching catalogs. When you upgrade your Product Catalog resource to Commerce Server 2002, it changes the word-breakers (locales) used for searching non-multilingual data to neutral word-breakers. Non-multilingual data is the data contained in properties that are defined as non-multilingual and have a single value in all languages (for example, Manufacturer Name).
If you want to use language specific word-breakers for searching non-multilingual data in your catalogs, you must perform the following steps. You can perform this procedure either before or after you upgrade.
Note Word-breakers are used by SQL Server for performing a full-text search.
The following table provides a list of word-breakers and their LCIDs. You can use these LCIDs in the languages.xml file.
| Locale | Locale ID |
| Neutral | 0 |
| Chinese_Simplified | 0x0804 |
| Chinese_Traditional | 0x0404 |
| Dutch | 0x0413 |
| English_UK | 0x0809 |
| English_US | 0x0409 |
| French | 0x040c |
| German | 0x0407 |
| Italian | 0x0410 |
| Japanese | 0x0411 |
| Korean | 0x0412 |
| Spanish_Modern | 0x0c0a |
| Swedish_Default | 0x041d |
<?xml version = '1.0' encoding='utf-8' ?>
<Languages>
<Language culture_name="Neutral" word_breaker="0x409"/>
</Languages>
This example uses the English word-breaker LCID = <0x409> to search non-multilingual data in your catalogs.
UpdateLanguageInfo.vbs "<path of the languages.xml file created above>"
After you upgrade from Commerce Server 2000 or from a prerelease version of Commerce Server 2002, you must perform additional steps to upgrade your Business Desk to take advantage of the new Commerce Server 2002 Business Desk features. These steps should also be performed if you have created custom Business Desk modules.
Important You must upgrade the Data Warehouse before upgrading Business Desk. If you attempt to upgrade Business Desk first, you might encounter errors. For more information about Business Desk errors, see Known Issues.
The changes you make to your Business Desk modules will support the following new features:
This section includes:
Follow the required steps to upgrade Business Desk to the appropriate version:
Upgrading to the Developer or Enterprise Editions of Commerce Server 2002
To upgrade your Business Desk to the Commerce Server 2002 Developer or Enterprise Editions from a Prerelease Version of Commerce Server 2002, perform the following steps.
Note If you are upgrading from Commerce Server 2000, perform these additional steps.
Upgrading to the Standard Edition of Commerce Server 2002
To upgrade your Commerce Server 2000 Business Desk or Prerelease version of Commerce Server 2002 Business Desk to the Standard Edition of Commerce Server 2002, complete the following steps:
Note After you delete an existing Commerce Server Business Desk application, the application files are not deleted from Commerce Server Manager.
Note If you are upgrading from Commerce Server 2000 perform these additional steps.
Removing the Original Business Desk Application from the Existing Site
The application configuration data is deleted from the Administration database. The physical files are not deleted.
Adding the New BlankBizDesk Application
| Use this | To do this |
| IIS computer name | Type the computer name of the IIS Web server, and then click Refresh. |
| IIS Web site | Select the name of the IIS Web site. |
| IIS path | Type the name of the IIS path with a different location than the existing Commerce Server 2000 site and the existing Business Desk application. |
Adding the Business Desk Permissions Resource
| Use this | To do this |
| SQL Server computer | Type the name of the computer that contains the database. |
| Database name | Type the name for the database. |
| Use Windows Integrated Security | Select this option if you want to use Integrated Windows authentication.
When you use Windows integrated security, user names and passwords are not stored in the SQL Server connection string and are not affected by SQL password resets. For information about Commerce Server 2002 security, see "Securing Your Site" in Commerce Server 2002 Help. Note It is strongly recommended that you use Windows Integrated Security, and that you secure your databases by using Windows Authentication. |
| Use a specific user name and password | Select this option if you want to use SQL Server authentication when connecting to the databases. |
| SQL Server Login Name | Type a SQL Server login user name that has permissions on the SQL Server computer on which the site databases are to be created.
Note For security purposes, do not use the sa login for access to the databases. To change the login information for the Administration database after it is created, use SQL Server Enterprise Manager. |
| SQL Server Login Password | Type the SQL Server login password for the databases.
Note You should always use a "strong password" when creating SQL Server login passwords. For more information about strong passwords, see "Using Strong Passwords" in Commerce Server 2002 Help. |
Note For information about how to complete the Data Link Properties dialog box, click Help in the Data Link Properties dialog box to open the Microsoft Data Link Help file.
| Use this | To do this |
| Use Windows Integrated Security | Select this option if you want to use Windows Integrated authentication.
When you use Windows integrated security, user names and passwords are not stored in the SQL Server connection string and are not affected by SQL password resets. For information about Commerce Server 2002 security, see "Securing Your Site" in Commerce Server 2002 Help. Note It is strongly recommended that you use Windows Integrated Security, and that you secure your databases by using Windows Authentication. |
| Use a specific user name and password | Select this option if you want to use SQL Server authentication when connecting to the databases. |
| SQL Server Login Name | Type a SQL Server login user name that has permissions on the SQL Server computer on which the site databases are to be created.
Note For security purposes, do not use the sa login for access to the databases. To change the login information for the Administration database after it is created, use SQL Server Enterprise Manager. |
| SQL Server Login Password | Type the SQL Server login password for the databases.
Note You should always use a “strong password” when creating SQL Server login passwords. For more information about strong passwords, see "Using Strong Passwords" in Commerce Server 2002 Help. |
Installing the Business Desk Client
For information about installing the Business Desk client, see the Commerce Server 2002 Installation Guide.
Note Repeat these steps for each site for which you are upgrading Commerce Server Business Desk.
After you upgrade to Commerce Server 2002, you must edit certain ASP files to enable the functionality required by the Retail and Supplier Solution Sites.
This section includes:
Edit the product.asp file to enable users to browse the catalog variants that you have added to a virtual or base catalog.
listGetVariantPropertiesToShow(ByVal fldsProps)
If (fldProp.Name <> "TimeStamp") And (fldProp.Name <> "cy_list_price") Then
If (fldProp.Name <> "TimeStamp") And (fldProp.Name <> "cy_list_price") And (fldProp.Name <> "VariantID") Then
Commerce Server 2002 changes the way site caches are refreshed in Business Desk. If you have not modified the BDRefresh.asp or RefreshApp.asp files in your site, then you can replace them with the versions in the new Retail site.
If you have modified these files, you must incorporate the Commerce Server 2002 BDRefresh.asp and RefreshApp.asp file changes manually. After you upgrade to Commerce Server 2002 you will receive the following error message when you publish changes on your Web site: "The refresh of the site is not implemented correctly. See documentation regarding site refresh."
The change is published, but you will continue to receive the error message until a code change is made to Bdrefresh.asp and Refreshapp.asp.
To edit the BDRefresh.asp file so that the site caches work properly, do the following:.
Dim sCacheName, sUrlReturnTo, oCacheManager, MSCSCatalogManager
Dim sCacheName, sUrlReturnTo, oCacheManager, MSCSCatalogManager
and ending with:
Response.Redirect(sUrlReturnTo)
with the following text:
Dim sCacheName, oCacheManager, MSCSCatalogManager
sCacheName = Request.QueryString("cache_name")
Set oCacheManager = Application("MSCSCacheManager")
' Refresh the supplied cachename...
If StrComp(sCacheName, "CatalogCache", 1) <> 0 Then
oCacheManager.RefreshCache(sCacheName)
If sCacheName = "ShippingManagerCache" Then
' Expire the cached HTML fragment for shipping methods.
oCacheManager.RefreshCache("StaticSectionsCache")
End If
To edit the RefreshApp.asp file so that so that the site caches work properly do the following:
'Const SCHEMA_CATALOG = "Profile Definitions"
Const Refresh_ErrorMessage = "A refresh error has occurred."
Const Code_ErrorMessage = "Error Code: "
Const Source_ErrorMessage = "Error Source: "
Const Description_ErrorMessage = "Error Description: "
sReturnTo = Request.QueryString("return_to")
Response.Write Err.Description
and ends with:
End If
Response.Write(sGetScriptError(Err))
Err.Clear
End If
ProfileRefresh()
ProfileRefresh(), insert the following function before the line On Error Goto 0:
' sGetScriptError
' Description: Returns error string populated from error object
' Parameters: oErr Object. VBScript Err object
' Returns: String. error string with object properties displayed in an HTML table
' Notes : none-----------------------------------------------------------------------------
Function sGetScriptError(oErr)
dim sText
const L_ScriptErrorTitle_ErrorMessage = "Script Error:"
const L_ScriptErrorNumber_ErrorMessage = "Number:"
const L_ScriptErrorDescription_ErrorMessage = "Description"
const L_ScriptErrorSource_ErrorMessage = "Source:"
const L_ScriptErrorHelpFile_ErrorMessage = "Help File:"
const L_ScriptErrorHelpContext_ErrorMessage = "Help Context:"
sText = ""
sText = sText & "<TABLE><COLGROUP><COL WIDTH='35%'><COL
WIDTH='65%'></COLGROUP>"
sText = sText & "<TR><TH ID='bddetailtitle' COLSPAN=2>" &
L_ScriptErrorTitle_ErrorMessage
sText = sText & "<TR><TH>" & L_ScriptErrorNumber_ErrorMessage & "<TD>0x" &
Hex(oErr.number)
sText = sText & "<TR><TH>" & L_ScriptErrorDescription_ErrorMessage & "<TD>" &
oErr.description
sText = sText & "<TR><TH>" & L_ScriptErrorSource_ErrorMessage & "<TD>" &
oErr.source
sText = sText & "<TR><TH>" & L_ScriptErrorHelpFile_ErrorMessage & "<TD>" &
oErr.helpFile
sText = sText & "<TR><TH>" & L_ScriptErrorHelpContext_ErrorMessage & "<TD>" &
oErr.helpContext
sText = sText & "</TABLE>"
sGetScriptError = sText
End Function
After you upgrade to Commerce Server 2002, you must edit certain ASP files to enable the functionality required by the Supplier Solution Site.
This section includes:
Edit the get_profiles.asp file to enable the Partner Service functionality for a delegated administrator on the Supplier site. For example, a delegated administrator can use Partner Service to look at users in other organizations. If these code changes are not made, the feature will not function correctly.
rsGetOrgDetails
FIELD_ORG_ORG_ID, _
FIELD_ORG_NAME, _
GetOrgAttributeFromID
FIELD_ORG_ORG_ID, _
FIELD_ORG_NAME, _
Edit the catalog.asp file so that catalog set restrictions can be viewed from the site.
mscsUserCatalogsetID
Set rsOrg = rsGetProfileByKey(FIELD_ORG_ORG_ID, org_id, PROFILE_TYPE_ORG, False)
Set rsOrg = rsGetProfileByKey(FIELD_ORG_NAME, org_id, PROFILE_TYPE_ORG, False)
mscsUserCatalogsFromID(ByVal CatalogSetID)
Set mscsCatalogSets = Server.CreateObject("Commerce.CatalogSets")
Set mscsCatalogSets = Server.CreateObject("Commerce.CatalogSets2")
mscsCatalogSets.OrganizationObjectJoinKey = FIELD_ORG_NAME
mscsUserCatalogs()
Dim userCatalogsetID
userCatalogsetID = mscsUserCatalogsetID()
set mscsUserCatalogs = mscsUserCatalogsFromID(userCatalogsetID)
Edit the html_lib.asp file so that passwords can be retrieved from the cache when copying users from the site.
RenderPasswordBox
Dim sNewValue
If (IsArray(sValue)) Then
sNewValue = sValue(0)
Else
sNewValue = sValue
End If
RenderPasswordBox = "<INPUT TYPE=""PASSWORD"" NAME=""" & sName & """ VALUE=""" & sNewValue & """ SIZE=""" & iSize & """ MAXLENGTH=""" & iMaxLength & """" & sAttList & ">"
Edit the login.asp file so that if IIS is reset during a session, users will be prompted to log on again.
if objAuth.IsAuthenticated(30)
if objAuth.IsAuthenticated(30)
and ending with:
Set objAuth = Nothingwith the following text:
PrintLogin
End If
Set objAuth = Nothing
Edit the requisition.asp file so that orders can be viewed from the site.
Function rsGetOrdersListoSearchInfo.user_org_id = mscsUserProfile(USER_ORGID).Value
Dim org_id
Dim rsOrg
If Not IsNull(org_name) Then
' Set rsGetProfile's bForceDBLookUp to False to avoid a database look-up.
Set rsOrg = rsGetProfileByKey(FIELD_ORG_NAME, org_id, PROFILE_TYPE_ORG, False)
If Not rsOrg Is Nothing Then
oSearchInfo.user_org_id = rsOrg.Fields.Item("GeneralInfo.org_id").Value
End If
End IfEdit the stepsrch.asp file so that property definitions that include hyphens (–) can be searched.
Sub PerformSpecificationSearchsColList = sColList + "," + oCatalog.IdentifyingProductPropertysColList = sColList + ",[" + oCatalog.IdentifyingProductProperty + "]"After IIS restarts, installation of the Supplier Solution Site on a two-computer configuration is complete.
For instructions about managing the Supplier Solution Site, see the Business-to-Business Tutorial
To track the status of your Commerce Server 2002 upgrade, you can run the CS2002Upgrade exe tool without any command line options. After you run the Upgrade tool, it provides a list of resources that have not been upgraded from Commerce Server 2000. You can also check the upgrade status of each site resource in Commerce Server Manager.
This section includes:
Tracking the Status of the Upgrade
To track the status of the upgrade using the upgrade tool, to the following:
A list is displayed, showing the resources that have not yet been upgraded from Commerce Server 2000.
Tracking the Data Warehouse Database Creation
After you upgrade your Data Warehouse, verify that the new database was created. While upgrading the Data Warehouse Resource, if the source database is for any reason missing, the migration tool does not return an error message, but instead returns a message like the following:
"Starting Commerce Server 2002 Upgrade on 05/12/02 17:16:33
The current version number is : 4.5.2092.00
Upgrading Resources for site : Retail
Upgrading Resource : Global Data Warehouse
Commerce Server 2002 Upgrade Completed"
The Event Viewer does not return an error message either. The log file Migration.txt that logs the upgrade progress is not created.
Important You must review the database files and verify that the new database was created.
Error messages are not displayed on the screen. To check for error messages, see the following files. The upgrade for each site runs as a single transaction. To verify that the upgrade was successful, view the following files:
After you upgrade to Commerce Server 2002, it is recommended that you install Commerce Server 2002 Service Pack 2. Service Pack 2 contains hot fixes and security updates to the Commerce Server 2002 product since its release. For a list of the hotfixes included in this Service Pack, and their related Knowledge Base articles, see Microsoft Knowledge Base article number 825330, available at http://go.microsoft.com/fwlink/?LinkId=18630.
Service Pack 2 does not update the Solution Sites, but it does include updated files for Business Desk.
When you upgrade from Commerce Server 2002 Standard Edition to Enterprise Edition, you must make several changes to take advantage of the additional features. The following sections list those features and how to add them to Commerce Server after you upgrade.
Note When you upgrade from Standard Edition to Enterprise Edition, and use an existing Data Warehouse resource that was created by using Standard Edition, only Standard Edition reports are available.
This section includes:
If you installed the Predictor resource as part of your Enterprise Edition suite, you need to add the Predictor resource to your site.
To add the Predictor resource to Enterprise Edition
If you have upgraded from Commerce Server 2002 Standard Edition to Enterprise Edition, and if you used the Data Warehouse resource that was created by using Standard Edition, then you must also run the following Data Transformation Services (DTS) tasks:
The following sections provide requirements and instructions for upgrading to Commerce Server 2002 from early or prerelease versions of Commerce Server 2002.
Note If you are upgrading from a prerelease version of Commerce Server 2002, you must use the Upgrade tool, CS2002Upgrade.exe, to upgrade site resources and the Administration database. After you run the Upgrade tool, it provides a list of resources that have not been upgraded from your prerelease version. You must upgrade the listed resources.
Important If you are upgrading from a prerelease version of Commerce Server 2002, you must upgrade your Data Warehouse manually. See Upgrading a Prerelease Version of Data Warehouse.
This section includes:
To upgrade the Data Warehouse from a prerelease version to Commerce Server 2002, you must install Commerce Server 2002 and then perform the following steps. This upgrade will enable users to obtain all Enterprise Edition reports if you are upgrading to the Enterprise Edition.
Delete all Prerelease Data Warehouse Resources
Back up and Delete your Data Warehouse Databases
Unpack the Data Warehouse Resource
Import Data into the Data Warehouse
Delete all Prerelease Data Warehouse Resources
In this step, you delete the site reference to a Data Warehouse and the global resource from the Administration database.
Data for the all resources is deleted from the Administration database.
Back up and Delete your Data Warehouse Databases
Note If the physical files still exist, stop Microsoft SQL Server 2000, delete the physical files, and then restart SQL Server.
Unpack the Data Warehouse Resource
Use Commerce Server Site Packager to unpack the Blank Solution Site. This step adds a new global Data Warehouse resource to your site.
Import Data into the Data Warehouse
Use the Commerce Server Data Transformation Services (DTS) tasks to re-import data into the Data Warehouse. You must run the following DTS tasks:
For instructions or more information, see "Importing Data Into the Data Warehouse" in Commerce Server 2002 Help.
During the upgrade from Commerce Server 2000 to Commerce Server 2002 Standard Edition, your global resources, Predictor resource and Direct Mailer, are automatically uninstalled.
However, the resources at the site level have a reference to the global resource, which is no longer present. This reference will cause errors. For example, the following error message may appear for Predictor or Direct Mailer:
Starting Commerce Server 2002 Upgrade on 03/07/02 16:09:33
The current version number is: 4.5.xxxx.00
Upgrading Resources for site: Retail
Upgrading Resource: Product Catalog
[Predictor on CSDW41]: An attempt to de-reference this global resource failed
because the resource does not exist. Please check your sites in Commerce Server Manager and delete all references to this resource.
This resource does not exist for the site you are upgrading.
There were errors upgrading this resource.
Commerce Server 2002 Upgrade Completed
You must delete the reference to the Predictor resource to complete your installation.
To delete the reference to the Predictor resource:
Important Perform these steps for each site that you are upgrading.
Note When you use the migration tool (CS2002Upgrade.exe) to upgrade Commerce Server 2000 to Commerce Server 2002 Standard Edition, the Data Warehouse resource does not appear in the list of resources that need to be upgraded. It will only appear in the list after the pre-existing site reference to the Predictor global resource is deleted.
This section provides a list of known issues and late-breaking news related to upgrading from Commerce Server 2000 to Commerce Server 2002.
This section includes:
If you are upgrading Business Desk from an earlier version of Commerce Server to Commerce Server 2002 and you receive errors when unpacking a site, the following error message may appear in c:\pup.log:
Failed to call method Run on Commerce.SyncAdminInterface.[11:09:40] Error importing object data for BlankBizDesk from file D:\Documents and Settings\Administrator\Local Settings\Temp\1\BlankBizDesk 80004005:Method '~' of object '~' failed
Before you upgrade Business Desk, you must first upgrade the Data Warehouse resource. To upgrade the Data Warehouse, see Upgrading the Data Warehouse Resource.
The recent Microsoft Knowledge Base article called "Cumulative Patch for Internet Explorer," found at http://go.microsoft.com/FWLink/?LinkID=9694, may cause a Commerce Server Business Desk application error.
For more information, see the Microsoft Knowledge Base article "MS02-047 Causes Commerce Server Business Desk Application Error" at go.microsoft.com/FWLink/?LinkID=9693.
The Retail and the Supplier Active Directory Solution sites use a different join key for the organization profile. The former uses a GUID while the latter uses the organization name. If you have based your site on the Supplier Active Directory Solution site, and you have made changes to your site such that the org_id value in the UserObject profile is a GUID, you will need to run the following SQL script:
update userobject
set userobject.g_org_id = organizationobject.u_Name
from userobject, organizationobject
where userobject.g_org_id = organizationobject.g_org_id
This script can be found in the directory: \Program Files\Microsoft Commerce Server 2002\Upgrade\Scripts\UpdateOrgID.sql
Commerce Server 2002 differs from previous versions of Commerce Server in that, when it parses positive integer values, it checks for overflow. For example, if you try to enter a value greater than 2 to the 31st power, it is handled as an error. Previous versions of Commerce Server passed inaccurate data without flagging the error.
You can choose to create an environment that uses Commerce Server Standard Edition, Enterprise Edition, and Developer Edition. This configuration might be useful if, for example, you purchase Developer Edition first, then Standard Edition, and then later decide you want the additional functionality provided in Enterprise Edition.
Following are the supported deployment scenarios using multiple different editions of Commerce Server. Other configurations are not supported.
If you upgrade from a prerelease version of Commerce Server 2002 Standard Edition to Commerce Server 2002 Enterprise Edition, some of your Enterprise Edition Business Desk Reports may be missing. The Standard Edition includes 21 reports and the Enterprise Edition includes 35 reports. To obtain the additional reports see, Upgrading a Prerelease Version of Data Warehouse,
If you need to install Commerce Server 2002 Standard Edition and you currently have Commerce Server 2002 Evaluation Edition installed, you must perform the following steps:
If you have Commerce Server 2000 Solution Sites (the Retail or Supplier sites) that need to be unpacked after you install Commerce Server 2002, you must perform the following steps.
Note In this example, you are unpacking a Commerce Server 2000 Retail Solution Site on Commerce Server 2002.
CS2002Upgrade.exe –G –C
If you have upgraded Commerce Server 2000 to Commerce Server 2002, note that the Commerce Server Site Packager log (pup.log) has been changed from straight ASCII to Unicode to enable better localization.
To read the new log file more easily, it is recommended that you rename your old pup.log file so that a new log file with only Unicode format will be created.
After upgrading to Commerce Server 2002, you might not be able to log in when you attempt to open the default login page for the Supplier Site.
If AuthFilter was loaded in any version of Commerce Server 2000, including Service Pack 1.0 and Service Pack 2.0, and you upgrade to Commerce Server 2002, then the IIS path for the SiteAuth.dll is not changed. You must manually point the SiteAuth ISAPI filter in IIS to the new directory with the Commerce Server 2002 AuthFilter dll.
Note The arrow to the left of the AuthFilter name, CS Auth, is red and pointing down.
To test your changes, browse back to the Filter Name text box in the IIS Default Web Site Properties dialog in the IIS Manager. Make certain your CS Auth name now has a green arrow pointing up. Your AuthFilter has now been reconfigured to use the new Commerce Server 2002 AuthFilter.
When you upgrade from Commerce Server 2000 to Commerce Server 2002, your unpublished custom catalogs are automatically converted to virtual catalogs. However, if any of your custom catalogs are published, they are converted to base catalogs.
If you want to migrate your existing published custom catalogs to virtual catalogs, , delete them and create new custom catalogs that are not published before you upgrade to Commerce Server 2002. After you upgrade, your newly created unpublished catalogs will be converted to virtual catalogs.
When you use the migration tool (CS2002Upgrade.exe) to upgrade Commerce Server 2000 to Commerce Server 2002 Standard Edition, the Data Warehouse resource does not appear in the list of resources that need to be upgraded.
It appears in the list after the pre-existing site reference to the Predictor global resource is deleted.
By default you cannot use the same server to run Microsoft SQL Server for bothCommerce Server 2000 and Commerce Server 2002. When you install Commerce Server, the Setup program creates the administration database name, MSCS_Admin.
However, you can change the name of this database after Setup creates it, so it is possible to have a SQL Server machine maintain both a Commerce Server 2000 and Commerce Server 2002 Administration database.
Note The MSCS_Admin database schema is different for each version of Commerce Server.
The following additional Profile definition properties have been added to Commerce Server 2002. However, these properties are not added during the upgrade process from Commerce Server 2000 to Commerce Server 2002. To add them, you must modify the run-time UserObject table, and add these properties to the upgrade scripts.
The following table lists the properties and provides instructions for modifying them.
| Profile definition | Property group | Property | Instructions |
| MSCommerce | UserSiteTerms | languages | Use the XML code listed in the topic Language Site Term XML Example and add the new Commerce Server 2002 site term elements to the list. |
| UserObject | GeneralInfo | languages | Extend the UserObject profile with a property of type siteterm that references the language siteterm. To add this property to the upgrade script, you must modify the run-time UserObject table. |
| UserObject | GeneralInfo | address_list | Extend the UserObject profile with a multi-valued property of type profile that references the address profile. To add this property to the upgrade script, you must modify the run-time UserObject table. |
The following procedure provides an example of how to add the language site term to your existing Profile schema. For more information about extending the UserObject profile, see "Adding a New Property to a Profile Definition" in Commerce Server 2002 Help.
To export the schema from the database
To import the new XML file into the database
Your XML file has been imported.
Language Site Term XML Example
The following XML code includes the values for the Language site terms that have been added to Commerce Server 2002. You can add these properties to the upgrade scripts to extend the UserObject profile. For instructions on how to add the Language Site Term to your existing Profile Schema, see Profile Definition Properties.
<?xml version="1.0"?>
- <Document xmlns="urn:schemas-microsoft-com:bizdata-profile-schema">
- <Catalog name="Site Terms" displayName="Site Terms" version="1">
- <Profile name="MSCommerce" displayName="Site Terms" description="Site Terms for Microsoft Commerce Server" isProfile="0">
- <Group name="UserSiteTerms" displayName="User Site Terms">
- <Property name="Languages" displayName="Languages" propType="STRING">
<Attribute name="af" displayName="Afrikaans" description="0x0036" />
<Attribute name="af-ZA" displayName="Afrikaans - South Africa" description="0x0436" />
<Attribute name="sq" displayName="Albanian" description="0x001C" />
<Attribute name="sq-AL" displayName="Albanian - Albania" description="0x041C" />
<Attribute name="ar" displayName="Arabic" description="0x0001" />
<Attribute name="ar-DZ" displayName="Arabic - Algeria" description="0x1401" />
<Attribute name="ar-BH" displayName="Arabic - Bahrain" description="0x3C01" />
<Attribute name="ar-EG" displayName="Arabic - Egypt" description="0x0C01" />
<Attribute name="ar-IQ" displayName="Arabic - Iraq" description="0x0801" />
<Attribute name="ar-JO" displayName="Arabic - Jordan" description="0x2C01" />
<Attribute name="ar-KW" displayName="Arabic - Kuwait" description="0x3401" />
<Attribute name="ar-LB" displayName="Arabic - Lebanon" description="0x3001" />
<Attribute name="ar-LY" displayName="Arabic - Libya" description="0x1001" />
<Attribute name="ar-MA" displayName="Arabic - Morocco" description="0x1801" />
<Attribute name="ar-OM" displayName="Arabic - Oman" description="0x2001" />
<Attribute name="ar-QA" displayName="Arabic - Qatar" description="0x4001" />
<Attribute name="ar-SA" displayName="Arabic - Saudi Arabia" description="0x0401" />
<Attribute name="ar-SY" displayName="Arabic - Syria" description="0x2801" />
<Attribute name="ar-TN" displayName="Arabic - Tunisia" description="0x1C01" />
<Attribute name="ar-AE" displayName="Arabic - United Arab Emirates" description="0x3801" />
<Attribute name="ar-YE" displayName="Arabic - Yemen" description="0x2401" />
<Attribute name="hy" displayName="Armenian" description="0x002B" />
<Attribute name="hy-AM" displayName="Armenian - Armenia" description="0x042B" />
<Attribute name="az" displayName="Azeri" description="0x002C" />
<Attribute name="Cy-az-AZ" displayName="Azeri Cyrillic - Azerbaijan" description="0x082C" />
<Attribute name="Lt-az-AZ" displayName="Azeri Latin - Azerbaijan" description="0x042C" />
<Attribute name="eu" displayName="Basque" description="0x002D" />
<Attribute name="eu-ES" displayName="Basque - Spain" description="0x042D" />
<Attribute name="be" displayName="Belarusian" description="0x0023" />
<Attribute name="be-BY" displayName="Belarusian - Belarus" description="0x0423" />
<Attribute name="bg" displayName="Bulgarian" description="0x0002" />
<Attribute name="bg-BG" displayName="Bulgarian - Bulgaria" description="0x0402" />
<Attribute name="ca" displayName="Catalan" description="0x0003" />
<Attribute name="ca-ES" displayName="Catalan - Spain" description="0x0403" />
<Attribute name="zh-CN" displayName="Chinese - China" description="0x0804" />
<Attribute name="zh-HK" displayName="Chinese - Hong Kong SAR" description="0x0C04" />
<Attribute name="zh-MO" displayName="Chinese - Macau SAR" description="0x1404" />
<Attribute name="zh-SG" displayName="Chinese - Singapore" description="0x1004" />
<Attribute name="zh-TW" displayName="Chinese - Taiwan" description="0x0404" />
<Attribute name="zh-CHS" displayName="Chinese Simplified" description="0x0004" />
<Attribute name="zh-CHT" displayName="Chinese Traditional" description="0x7C04" />
<Attribute name="hr" displayName="Croatian" description="0x001A" />
<Attribute name="hr-HR" displayName="Croatian - Croatia" description="0x041A" />
<Attribute name="cs" displayName="Czech" description="0x0005" />
<Attribute name="cs-CZ" displayName="Czech - Czech Republic" description="0x0405" />
<Attribute name="da" displayName="Danish" description="0x0006" />
<Attribute name="da-DK" displayName="Danish - Denmark" description="0x0406" />
<Attribute name="div" displayName="Dhivehi" description="0x0065" />
<Attribute name="div-MV" displayName="Dhivehi - Maldives" description="0x0465" />
<Attribute name="nl" displayName="Dutch" description="0x0013" />
<Attribute name="nl-BE" displayName="Dutch - Belgium" description="0x0813" />
<Attribute name="nl-NL" displayName="Dutch - The Netherlands" description="0x0413" />
<Attribute name="en" displayName="English" description="0x0009" />
<Attribute name="en-AU" displayName="English - Australia" description="0x0C09" />
<Attribute name="en-BZ" displayName="English - Belize" description="0x2809" />
<Attribute name="en-CA" displayName="English - Canada" description="0x1009" />
<Attribute name="en-CB" displayName="English - Caribbean" description="0x2409" />
<Attribute name="en-IE" displayName="English - Ireland" description="0x1809" />
<Attribute name="en-JM" displayName="English - Jamaica" description="0x2009" />
<Attribute name="en-NZ" displayName="English - New Zealand" description="0x1409" />
<Attribute name="en-PH" displayName="English - Philippines" description="0x3409" />
<Attribute name="en-ZA" displayName="English - South Africa" description="0x1C09" />
<Attribute name="en-TT" displayName="English - Trinidad and Tobago" description="0x2C09" />
<Attribute name="en-GB" displayName="English - United Kingdom" description="0x0809" />
<Attribute name="en-US" displayName="English - United States" description="0x0409" />
<Attribute name="en-ZW" displayName="English - Zimbabwe" description="0x3009" />
<Attribute name="et" displayName="Estonian" description="0x0025" />
<Attribute name="et-EE" displayName="Estonian - Estonia" description="0x0425" />
<Attribute name="fo" displayName="Faroese" description="0x0038" />
<Attribute name="fo-FO" displayName="Faroese - Faroe Islands" description="0x0438" />
<Attribute name="fa" displayName="Farsi" description="0x0029" />
<Attribute name="fa-IR" displayName="Farsi - Iran" description="0x0429" />
<Attribute name="fi" displayName="Finnish" description="0x000B" />
<Attribute name="fi-FI" displayName="Finnish - Finland" description="0x040B" />
<Attribute name="fr" displayName="French" description="0x000C" />
<Attribute name="fr-BE" displayName="French - Belgium" description="0x080C" />
<Attribute name="fr-CA" displayName="French - Canada" description="0x0C0C" />
<Attribute name="fr-FR" displayName="French - France" description="0x040C" />
<Attribute name="fr-LU" displayName="French - Luxembourg" description="0x140C" />
<Attribute name="fr-MC" displayName="French - Monaco" description="0x180C" />
<Attribute name="fr-CH" displayName="French - Switzerland" description="0x100C" />
<Attribute name="gl" displayName="Galician" description="0x0056" />
<Attribute name="gl-ES" displayName="Galician - Spain" description="0x0456" />
<Attribute name="ka" displayName="Georgian" description="0x0037" />
<Attribute name="ka-GE" displayName="Georgian - Georgia" description="0x0437" />
<Attribute name="de" displayName="German" description="0x0007" />
<Attribute name="de-AT" displayName="German - Austria" description="0x0C07" />
<Attribute name="de-DE" displayName="German - Germany" description="0x0407" />
<Attribute name="de-LI" displayName="German - Liechtenstein" description="0x1407" />
<Attribute name="de-LU" displayName="German - Luxembourg" description="0x1007" />
<Attribute name="de-CH" displayName="German - Switzerland" description="0x0807" />
<Attribute name="el" displayName="Greek" description="0x0008" />
<Attribute name="el-GR" displayName="Greek - Greece" description="0x0408" />
<Attribute name="gu" displayName="Gujarati" description="0x0047" />
<Attribute name="gu-IN" displayName="Gujarati - India" description="0x0447" />
<Attribute name="he" displayName="Hebrew" description="0x000D" />
<Attribute name="he-IL" displayName="Hebrew - Israel" description="0x040D" />
<Attribute name="hi" displayName="Hindi" description="0x0039" />
<Attribute name="hi-IN" displayName="Hindi - India" description="0x0439" />
<Attribute name="hu" displayName="Hungarian" description="0x000E" />
<Attribute name="hu-HU" displayName="Hungarian - Hungary" description="0x040E" />
<Attribute name="is" displayName="Icelandic" description="0x000F" />
<Attribute name="is-IS" displayName="Icelandic - Iceland" description="0x040F" />
<Attribute name="id" displayName="Indonesian" description="0x0021" />
<Attribute name="id-ID" displayName="Indonesian - Indonesia" description="0x0421" />
<Attribute name="it" displayName="Italian" description="0x0010" />
<Attribute name="it-IT" displayName="Italian - Italy" description="0x0410" />
<Attribute name="it-CH" displayName="Italian - Switzerland" description="0x0810" />
<Attribute name="ja" displayName="Japanese" description="0x0011" />
<Attribute name="ja-JP" displayName="Japanese - Japan" description="0x0411" />
<Attribute name="kn" displayName="Kannada" description="0x004B" />
<Attribute name="kn-IN" displayName="Kannada - India" description="0x044B" />
<Attribute name="kk" displayName="Kazakh" description="0x003F" />
<Attribute name="kk-KZ" displayName="Kazakh - Kazakhstan" description="0x043F" />
<Attribute name="kok" displayName="Konkani" description="0x0057" />
<Attribute name="kok-IN" displayName="Konkani - India" description="0x0457" />
<Attribute name="ko" displayName="Korean" description="0x0012" />
<Attribute name="ko-KR" displayName="Korean - Korea" description="0x0412" />
<Attribute name="ky" displayName="Kyrgyz" description="0x0040" />
<Attribute name="ky-KZ" displayName="Kyrgyz - Kazakhstan" description="0x0440" />
<Attribute name="lv" displayName="Latvian" description="0x0026" />
<Attribute name="lv-LV" displayName="Latvian - Latvia" description="0x0426" />
<Attribute name="lt" displayName="Lithuanian" description="0x0027" />
<Attribute name="lt-LT" displayName="Lithuanian - Lithuania" description="0x0427" />
<Attribute name="mk" displayName="Macedonian" description="0x002F" />
<Attribute name="mk-MK" displayName="Macedonian - FYROM" description="0x042F" />
<Attribute name="ms" displayName="Malay" description="0x003E" />
<Attribute name="ms-BN" displayName="Malay - Brunei" description="0x083E" />
<Attribute name="ms-MY" displayName="Malay - Malaysia" description="0x043E" />
<Attribute name="mr" displayName="Marathi" description="0x004E" />
<Attribute name="mr-IN" displayName="Marathi - India" description="0x044E" />
<Attribute name="mn" displayName="Mongolian" description="0x0050" />
<Attribute name="mn-MN" displayName="Mongolian - Mongolia" description="0x0450" />
<Attribute name="no" displayName="Norwegian" description="0x0014" />
<Attribute name="nb-NO" displayName="Norwegian Bokml - Norway" description="0x0414" />
<Attribute name="nn-NO" displayName="Norwegian Nynorsk - Norway" description="0x0814" />
<Attribute name="pl" displayName="Polish" description="0x0015" />
<Attribute name="pl-PL" displayName="Polish - Poland" description="0x0415" />
<Attribute name="pt" displayName="Portuguese" description="0x0016" />
<Attribute name="pt-BR" displayName="Portuguese - Brazil" description="0x0416" />
<Attribute name="pt-PT" displayName="Portuguese - Portugal" description="0x0816" />
<Attribute name="pa" displayName="Punjabi" description="0x0046" />
<Attribute name="pa-IN" displayName="Punjabi - India" description="0x0446" />
<Attribute name="ro" displayName="Romanian" description="0x0018" />
<Attribute name="ro-RO" displayName="Romanian - Romania" description="0x0418" />
<Attribute name="ru" displayName="Russian" description="0x0019" />
<Attribute name="ru-RU" displayName="Russian - Russia" description="0x0419" />
<Attribute name="sa" displayName="Sanskrit" description="0x004F" />
<Attribute name="sa-IN" displayName="Sanskrit - India" description="0x044F" />
<Attribute name="Cy-sr-SP" displayName="Serbian Cyrillic - Serbia" description="0x0C1A" />
<Attribute name="Lt-sr-SP" displayName="Serbian Latin - Serbia" description="0x081A" />
<Attribute name="sk" displayName="Slovak" description="0x001B" />
<Attribute name="sk-SK" displayName="Slovak - Slovakia" description="0x041B" />
<Attribute name="sl" displayName="Slovenian" description="0x0024" />
<Attribute name="sl-SI" displayName="Slovenian - Slovenia" description="0x0424" />
<Attribute name="es" displayName="Spanish" description="0x000A" />
<Attribute name="es-AR" displayName="Spanish - Argentina" description="0x2C0A" />
<Attribute name="es-BO" displayName="Spanish - Bolivia" description="0x400A" />
<Attribute name="es-CL" displayName="Spanish - Chile" description="0x340A" />
<Attribute name="es-CO" displayName="Spanish - Colombia" description="0x240A" />
<Attribute name="es-CR" displayName="Spanish - Costa Rica" description="0x140A" />
<Attribute name="es-DO" displayName="Spanish - Dominican Republic" description="0x1C0A" />
<Attribute name="es-EC" displayName="Spanish - Ecuador" description="0x300A" />
<Attribute name="es-SV" displayName="Spanish - El Salvador" description="0x440A" />
<Attribute name="es-GT" displayName="Spanish - Guatemala" description="0x100A" />
<Attribute name="es-HN" displayName="Spanish - Honduras" description="0x480A" />
<Attribute name="es-MX" displayName="Spanish - Mexico" description="0x080A" />
<Attribute name="es-NI" displayName="Spanish - Nicaragua" description="0x4C0A" />
<Attribute name="es-PA" displayName="Spanish - Panama" description="0x180A" />
<Attribute name="es-PY" displayName="Spanish - Paraguay" description="0x3C0A" />
<Attribute name="es-PE" displayName="Spanish - Peru" description="0x280A" />
<Attribute name="es-PR" displayName="Spanish - Puerto Rico" description="0x500A" />
<Attribute name="es-ES" displayName="Spanish - Spain" description="0x0C0A" />
<Attribute name="es-UY" displayName="Spanish - Uruguay" description="0x380A" />
<Attribute name="es-VE" displayName="Spanish - Venezuela" description="0x200A" />
<Attribute name="sw" displayName="Swahili" description="0x0041" />
<Attribute name="sw-KE" displayName="Swahili - Kenya" description="0x0441" />
<Attribute name="sv" displayName="Swedish" description="0x001D" />
<Attribute name="sv-FI" displayName="Swedish - Finland" description="0x081D" />
<Attribute name="sv-SE" displayName="Swedish - Sweden" description="0x041D" />
<Attribute name="syr" displayName="Syriac" description="0x005A" />
<Attribute name="syr-SY" displayName="Syriac - Syria" description="0x045A" />
<Attribute name="ta" displayName="Tamil" description="0x0049" />
<Attribute name="ta-IN" displayName="Tamil - India" description="0x0449" />
<Attribute name="tt" displayName="Tatar" description="0x0044" />
<Attribute name="tt-RU" displayName="Tatar - Russia" description="0x0444" />
<Attribute name="te" displayName="Telugu" description="0x004A" />
<Attribute name="te-IN" displayName="Telugu - India" description="0x044A" />
<Attribute name="th" displayName="Thai" description="0x001E" />
<Attribute name="th-TH" displayName="Thai - Thailand" description="0x041E" />
<Attribute name="tr" displayName="Turkish" description="0x001F" />
<Attribute name="tr-TR" displayName="Turkish - Turkey" description="0x041F" />
<Attribute name="uk" displayName="Ukrainian" description="0x0022" />
<Attribute name="uk-UA" displayName="Ukrainian - Ukraine" description="0x0422" />
<Attribute name="ur" displayName="Urdu" description="0x0020" />
<Attribute name="ur-PK" displayName="Urdu - Pakistan" description="0x0420" />
<Attribute name="uz" displayName="Uzbek" description="0x0043" />
<Attribute name="Cy-uz-UZ" displayName="Uzbek Cyrillic - Uzbekistan" description="0x0843" />
<Attribute name="Lt-uz-UZ" displayName="Uzbek Latin - Uzbekistan" description="0x0443" />
<Attribute name="vi" displayName="Vietnamese" description="0x002A" />
<Attribute name="vi-VN" displayName="Vietnamese - Vietnam" description="0x042A" />
</Property>
</Group>
</Profile>
</Catalog>
</Document>