Customizing the Site Packager .ini Files

Commerce Server includes the packBlank.ini file with the BlankSite package. Separate .ini files are provided for the Retail and Supplier Solution Sites, available on the Commerce Server Web site. You can use these .ini files as templates for creating custom .ini files for your own packages. These .ini files are useful for doing automated builds of your packages, for example, in a production environment, in which you want to build every night and then install in the morning.

You can use the same .ini file for both packaging and unpacking. During the packaging or unpacking process, the pieces that are irrelevant to the task are ignored.

Run .ini files from the command line. For instructions and a sample command, see Running Site Packager from the Command Line.

The following is the content of the packBlank.ini file, including comments about each section. An asterisk (*) indicates comments:

[General]

SiteName=BlankSite
Description=Blank site
NumOfResources= 11
NumOfApplications= 2

*The following is a list of the resources to be installed. If you do not want to install a given resource, delete the resource line from the .ini file, and renumber the resources. The order in which the resources are unpacked does not affect the unpacking process. However, all of the resources are unpacked before the applications.

Note

• When packaging a site, the list of resources in the .ini file is not read. Instead the entire site is packaged.

Resource0=App Default Config
Resource1=Product Catalog
Resource2=Campaigns
Resource3=Site Data Warehouse
Resource4=Transactions
Resource5=Transaction Config
Resource6=Direct Mail
Resource7=Predictor
Resource8=Biz Data Service
Resource9=Group Data Warehouse
Resource10=Site CS Authentication
Application0=B2CSite
Application1=B2CBizDesk
NumOfConnStrs= 6

[App Default Config]

*App Default Config does not include a UseData flag because it contains only configuration information.

[ConnStrs]

*In this section the connection strings for the resources are listed. The connection strings take the following parameters:

ConnStrResourceName

The name of the resource.

ConnStrValue

The connection string value.

ConnStrPropertyName

The property name for the connection string.

The following sample shows the [ConnStrs] section:

ConnStrResourceName0=Product Catalog
ConnStrPropertyName0=connstr_db_Catalog
ConnStrValue0=Provider=SQLOLEDB;Persist Security Info=False;User ID=;Password=;Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName1=Campaigns
ConnStrPropertyName1=connstr_db_Campaigns
ConnStrValue1=Provider=SQLOLEDB;Persist Security Info=False;User ID=;Password=;Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName2=Transactions
ConnStrPropertyName2=connstr_db_Transactions
ConnStrValue2=Provider=SQLOLEDB;Persist Security Info=False;User ID=;Password=;Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName3=TransactionConfig
ConnStrPropertyName3=connstr_db_TransactionConfig
ConnStrValue3=Provider=SQLOLEDB;Persist Security Info=False;User ID=;Password=;Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName4=Biz Data Service
ConnStrPropertyName4=connstr_db_bds
ConnStrValue4=Provider=SQLOLEDB;Persist Security Info=False;User ID=;Password=;Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName5=Global Data Warehouse
ConnStrPropertyName5=connstr_db_dw
ConnStrValue5=Provider=SQLOLEDB;Persist Security Info=False;User ID=;Password=;Initial Catalog=BlankSite_dw;Data Source=SERVERNAME;

[Product Catalog]

*UseData indicates whether you want to include the data and the schema, or only the schema. 1 means you want to include both the data and schema. UseData does not affect applications, or the Profiles resource, CS Authentication resource, or the Data Warehouse resource.

UseData = 1 

[Campaigns]

UseData = 1

[Site Data Warehouse]

*Site Data Warehouse does not use a UseData flag because it includes only configuration information.

[Transactions]

UseData = 1

[Transaction Config]

UseData = 1

[Direct Mail]

*Use GlobalResourceName to assign the global resource to a global resource name that already exists on the computer. If the value of this setting is (Add New Global Resource), then the global resource is added to the site, instead of associated with an existing global resource.

GlobalResourceName=Direct Mail on SERVERNAME

[Predictor]

GlobalResourceName=Predictor on SERVERNAME

[B2CSite]

ASPDir=
VRoot=
Website=
UseData = 1

[B2CBizDesk]

ASPDir=
VRoot=
Website=
UseData = 1

[Biz Data Service]

*This UseData does not affect what is included for the Profiles service. The Profiles service takes only schema; it never takes data.

UseData = 1
GlobalResourceName= (Add new global resource)

[Global Data Warehouse]

*This UseData does not affect what is included for Group Data Warehouse. The Group Data Warehouse takes only schema; it never takes data.

UseData = 1
GlobalResourceName= (Add new global resource)

[Site CS Authentication]

GlobalResourceName= (Add new global resource)

All rights reserved.