다음을 통해 공유

What Is the Format of the BizData.ini File?

  • 아티클

The BizData.ini file specifies the parameters that are required to unpack the profiles data related to a site. To unpack a site that uses custom profile definitions silently with a script, you must create a BizData.ini file in addition to a Site.ini file. We recommend that you put both files, together with the profile definition files, in the %COMMERCE_SERVER_ROOT% directory. If your site does not use custom profile definitions, then a BizData.ini file is not required. For more information about the Site.ini file, see How to Customize the Site Packager .ini Files.

The BizData.ini file contains the following sections:

  • BizDataSchema

  • BizDataStoreFlags

  • UPM_SQLSource.SQLSource

The rest of this topic describes the sections and presents an example BizData.ini file.

BizDataSchema Section

The BizDataSchema section identifies the files to import during the unpacking process.

Specify the following attributes in the BizDataSchema section:

  • catalogSchema: The name of an SQL file that contains definitions for the Data Warehouse tables.

  • expressionSchema: The name of an SQL file that contains the definitions for the expressions tables.

  • expressionSprocs: The name of an SQL file that contains the definitions for the stored procedures that are used with expressions.

  • profileDefs: The name of an XML file that contains the profile definitions.

  • siteTermDefs: The name of an XML file that contains the site terms.

  • expressionDefs: Include the attribute, but do not provide a value.

The unpacking process tries to find the file in the package and then in the %COMMERCE_SERVER_ROOT% folder.

BizDataStoreFlags Section

The BizDataStoreFlags section contains flags that control the unpacking process.

Specify the following attribute in the BizDataStoreFlags section:

  • IsSilentMode: True to indicate that the unpacking process should not ask for user input; False if the unpacking process should ask for user input. If the value is False, any information that is provided in the BizData.ini file is used to populate the default values in the unpacking user interface.

UPM_SQLSource.SQLSource Section

The UPM_SQLSource.SQLSource section describes how to connect to the profiles database and unpack the profiles data.

Specify the following attributes in the UPM_SQLSource.SQLSource section:

  • IsBizDataStore: True to use the connection strings that were provided when the site was packaged; False to use the connection strings that are contained in the UPM_SQLSource.SQLSource section.

  • ProviderString: The provider-specific connection string required to implement a connection to the database (see example later in this document).

  • schemaDefs: The name of an SQL file that contains the definitions for the profile tables.

  • dataDefs: The name of an SQL file that contains the profiles. You may omit a value for the dataDefs attribute if you do not want to create any profiles when the site is unpacked.

  • Provider: The provider part of the connection string. Required only if you are using SQL authentication. If you are using Windows authentication, do not include this attribute.

  • DataSource: The name of the SQL instance. Required only if you are using SQL authentication. If you are using Windows authentication, do not include this attribute.

  • UserID: The user ID part of the connection string. Required only if you are using SQL authentication. If you are using Windows authentication, do not include this attribute.

  • Password: The password part of the connection string. Required only if you are using SQL authentication. If you are using Windows authentication, do not include this attribute.

    Dd451538.alert_caution(en-US,CS.90).gifImportant Note:

    After you unpack the site, you should remove the value of the Password attribute from the BizData.ini file, because the password is stored as plain text.

  • InitialCatalog: The name of the database. Required only if you are using SQL authentication. If you are using Windows authentication, do not include this attribute.

Example

The following example is the BizData.ini file for a sample Commerce Server 2009 site. This example uses Windows authentication.

[BizDataSchema]
catalogSchema=catalogSchema.sql
expressionSchema=es_create.sql
expressionSprocs=es_stored_procs.sql
profileDefs=ProfileSQL_Starter.xml
siteTermDefs=SiteTerms.xml
expressionDefs=ExpressionDefinition.xml

[BizDataStoreFlags]
IsSilentMode=True

[UPM_SQLSource.SQLSource]
IsBizDataStore=True
ProviderString=SQLOLEDB.1;Integrated Security=SSPI;Initial Catalog=StoreFrnt_Profiles;Data Source=CS-ROBIN;
schemaDefs=ProfileSQL_Starter.sql
dataDefs=

See Also

Other Resources

How to Run Site Packager from the Command Line

How to Customize the Site Packager .ini Files

Managing Site Packages