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 at https://go.microsoft.com/fwlink/?linkid=6491. 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 at 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 sections that are irrelevant to the task are ignored.

You 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= 12

  • NumOfApplications= 2

    Ee824475.note(en-US,CS.20).gifNote

    • When a Commerce Server site is unpacked, it typically installs two applications: one for the Web site that users access, and one for Commerce Server Business Desk.

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 then 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 any applications are unpacked.

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=BizData Service
  • Resource9=Global Data Warehouse
  • Resource10=Site CS Authentication
  • Resource11=BDSecurity
  • Application0=BlankSite
  • Application1=BlankBizDesk
  • NumOfConnStrs= 7

Ee824475.important(en-US,CS.20).gifImportant

  • An application name must match the name of the packaged application. For example, if the package was created with the application name BlankSite, the application name must be BlankSite. If you change the name of the application, you must also change the VRoot.
  • The App Default Config and BDSecurity resources are the minimum requirements for unpacking. The BDSecurity resource is not required if you customize your own Business Desk (remove any dependencies on the BDSecurity component).

[ConnStrs]

Following are the connection strings for each resource. 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 is a sample of the [ConnStrs] section:

Ee824475.note(en-US,CS.20).gifNote

  • It is recommended that you use Windows integrated security. To use integrated security, in the connection string value (ConnStrValue) for each resource replace the parameters ‘User ID=;Password=;' with ‘Integrated Security=SSPI'. For more information about Windows integrated security, see Using Windows Authentication.
ConnStrResourceName0=Product Catalog
ConnStrPropertyName0=connstr_db_Catalog
ConnStrValue0=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security='SSPI';Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;ConnStrResourceName1=Campaigns
ConnStrPropertyName1=connstr_db_Campaigns
ConnStrValue1=Provider=SQLOLEDB;Persist Security Info=False; Integrated Security='SSPI';Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName2=Transactions
ConnStrPropertyName2=connstr_db_Transactions
ConnStrValue2=Provider=SQLOLEDB;Persist Security Info=False; Integrated Security='SSPI';Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName3=TransactionConfig
ConnStrPropertyName3=connstr_db_TransactionConfig
ConnStrValue3=Provider=SQLOLEDB;Persist Security Info=False; Integrated Security='SSPI';Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName4=Biz Data Service
ConnStrPropertyName4=connstr_db_bds
ConnStrValue4=Provider=SQLOLEDB;Persist Security Info=False; Integrated Security='SSPI';Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;
ConnStrResourceName5=Global Data Warehouse
ConnStrPropertyName5=connstr_db_dw
ConnStrValue5=Provider=SQLOLEDB;Persist Security Info=False; Integrated Security='SSPI';Initial Catalog=BlankSite_dw;Data Source=SERVERNAME;
ConnStrResourceName6=BDSecurity
ConnStrPropertyName6=connstr_db_bdsecurity
ConnStrValue6=Provider=SQLOLEDB;Persist Security Info=False; Integrated Security='SSPI';Initial Catalog=BlankSite_commerce;Data Source=SERVERNAME;

[Direct Mail]

Use GlobalResourceName to assign the global resource to a global resource name that already exists on the computer.

Ee824475.note(en-US,CS.20).gifNotes

  • You cannot use Add New Global Resource with Direct Mail. You must specify an existing resource that already exists on the computer.
  • The string is localized; therefore, it must match the resource name listed in Commerce Server Manager. If the string does not match, Site Packager cannot locate it.
GlobalResourceName=Direct Mail on SERVERNAME

[Predictor]

Ee824475.note(en-US,CS.20).gifNotes

  • You cannot use Add New Global Resource with Predictor. You must specify an existing resource that already exists on the computer.
  • The string is localized; therefore, it must match the resource name listed in Commerce Server Manager. If the string does not match, Site Packager cannot locate it.
GlobalResourceName=Predictor on SERVERNAME

[BlankSite]

ASPDir=
VRoot=
Website=
Machine=

Ee824475.note(en-US,CS.20).gifNotes

  • Website= is the only required property.
  • The Website property is localized; therefore, it must match the Website name in the MMC snap-in of Internet Information Services (IIS). If the property does not match, Site Packager cannot locate it.
  • The Machine property is used for unpacking an application to a remote Web server. Leave this field blank to unpack on the local server.

[BlankBizDesk]

ASPDir=
VRoot=
Website=
Machine=

Ee824475.note(en-US,CS.20).gifNotes

  • Website= is the only required property.
  • The Website property is localized; therefore, it must match the Website name in the MMC snap-in of Internet Information Services (IIS). If the property does not match, Site Packager cannot locate it.
  • The Machine property is used for unpacking an application to a remote Web server. Leave this field blank to unpack on the local server.

[Biz Data Service]

Ee824475.note(en-US,CS.20).gifNote

  • The string is localized; therefore, it must match the resource name listed in Commerce Server Manager. If the string does not match, Site Packager cannot locate it.
GlobalResourceName= (Add new global resource)

[Global Data Warehouse]

Ee824475.note(en-US,CS.20).gifNote

  • The string is localized; therefore, it must match the resource name listed in Commerce Server Manager. If the string does not match, Site Packager cannot locate it.
GlobalResourceName= (Add new global resource)

[Site CS Authentication]

Ee824475.note(en-US,CS.20).gifNote

  • The string is localized; therefore, it must match the resource name listed in Commerce Server Manager. If the string does not match, Site Packager cannot locate it.
GlobalResourceName= (Add new global resource)

Copyright © 2005 Microsoft Corporation.
All rights reserved.