How to Customize the Site Packager .ini Files
You can use .ini files as templates for creating custom .ini files for your own packages. You can use site packager .ini files to control how a PuP file is deployed when you silently unpack a site. For more information about silently unpacking a site, see What Is the Format of the BizData.ini File?
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 How to Run Site Packager from the Command Line.
Note the following:
-
When packaging a site, the list of resources in the .ini file is not read. Instead the entire site is packaged.
-
An application name must match the name of the packaged application. For example, if the package was created with the application name DefaultSite, the application name must be DefaultSite. If you change the name of the application, you must also change the VRoot.
The entries in this section are from the Site.ini file for a sample Commerce Server 2009 site named CSharpSite.
[General]
-
SiteName= is the only required property.
-
The SiteName property is localized. Therefore, it must match the Web site name in Microsoft Management Console (MMC) snap-in of Internet Information Services (IIS). If the property does not match, Site Packager cannot locate it.
SiteName=CSharpSite Description=Silent CSharpSite Install with Windows Authentication
The following entries list the resources that Site Packager can install. If you do not want to install a given resource, delete the resource line from the .ini file, and then renumber the resources. All of the resources are unpacked before any applications are unpacked:
NumOfResources= 7 NumOfApplications= 5 Resource0=Product Catalog Resource1=Transactions Resource2=Transaction Config Resource3=Biz Data Service Resource4=Site CS Authentication Resource5=Marketing Resource6=Inventory Application0=CatalogWebService Application1=CSharpSite Application2=MarketingWebService Application3=OrdersWebService Application4=ProfilesWebService NumOfConnStrs= 7
[ConnStrs]
We recommend that you use Windows integrated security. To use integrated security, in the connection string value (ConnStrValue) for each resource replace the parameter User ID=;Password=; with Integrated Security=SSPI.
The 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:
ConnStrResourceName0=Product Catalog ConnStrPropertyName0=connstr_db_Catalog ConnStrFriendlyResourceName0=Product Catalog ConnStrFriendlyPropertyName0=connstr_db_Catalog ConnStrValue0=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_ProductCatalog;Data Source=localhost; ConnStrResourceName1=Transactions ConnStrPropertyName1=connstr_db_Transactions ConnStrFriendlyResourceName1=Transactions ConnStrFriendlyPropertyName1=connstr_db_Transactions ConnStrValue1=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Transactions;Data Source=localhost; ConnStrResourceName2=Transaction Config ConnStrPropertyName2=connstr_db_TransactionConfig ConnStrFriendlyResourceName2=Transaction Config ConnStrFriendlyPropertyName2=connstr_db_TransactionConfig ConnStrValue2=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Transactionconfig;Data Source=localhost; ConnStrResourceName3=Biz Data Service ConnStrPropertyName3=connstr_db_bds ConnStrFriendlyResourceName3=Profiles ConnStrFriendlyPropertyName3=connstr_db_bds ConnStrValue3=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Profiles;Data Source=localhost; ConnStrResourceName4=Marketing ConnStrPropertyName4=connstr_db_Marketing ConnStrFriendlyResourceName4=Marketing ConnStrFriendlyPropertyName4=connstr_db_Marketing ConnStrValue4=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Marketing;Data Source=localhost; ConnStrResourceName5=Inventory ConnStrPropertyName5=connstr_db_inventory ConnStrFriendlyResourceName5=Inventory ConnStrFriendlyPropertyName5=connstr_db_inventory ConnStrValue5=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_ProductCatalog;Data Source=localhost; ConnStrResourceName6=Marketing ConnStrPropertyName6=connstr_db_Lists ConnStrFriendlyResourceName6=Marketing ConnStrFriendlyPropertyName6=connstr_db_Lists ConnStrValue6=Provider=SQLOLEDB;Persist Security Info=False;Integrated Security=SSPI;Initial Catalog=CSharpSite_Marketing_Lists;Data Source=localhost;
[Product Catalog]
ResourceFlags=2 PupFlags=1 ProgidPUP=Commerce.CatalogPUP ResourceType=Catalog FriendlyName=Product Catalog
[Transactions]
ResourceFlags=2 PupFlags=1 ProgidPUP=Commerce.OrdersPup ResourceType=Transactions FriendlyName=Transactions
[Transaction Config]
ResourceFlags=2 PupFlags=1 ProgidPUP=Commerce.OrdersPup ResourceType=TransactionConfig FriendlyName=Transaction Config
[Biz Data Service]
ResourceFlags=7 PupFlags=1 ProgidPUP=Commerce.UPMPuP ResourceType=BizDataStore FriendlyName=Profiles GlobalResourceName= (Add new global resource)
[Site CS Authentication]
ResourceFlags=3 PupFlags=1 ProgidPUP=Commerce.AuthPuP ResourceType=AuthManager FriendlyName=CS Authentication GlobalResourceName= (Add new global resource)
[Inventory]
ResourceFlags=2 PupFlags=1 ProgidPUP=Commerce.CatalogPUP ResourceType=Inventory FriendlyName=Inventory
[Marketing]
ResourceFlags=2 PupFlags=1 ProgidPUP=Commerce.MarketingPup ResourceType=Marketing FriendlyName=Marketing
[CatalogWebService]
ResourceFlags=5130 PupFlags=1 ProgidPUP=Commerce.AddressPuP ResourceType=Address FriendlyName=Address AccessFlags=513 AuthFlags=4 AppIsolated=0 AspCodePage=0 VRoot=CatalogWebService CSAppName=CatalogWebService Website=Default Web Site Machine=localhost
[CSharpSite]
ResourceFlags=10 PupFlags=1 ProgidPUP=Commerce.AddressPuP ResourceType=Address FriendlyName=Address AccessFlags=513 AuthFlags=7 AppIsolated=0 AspCodePage=0 VRoot=CSharpSite CSAppName=CSharpSite Website=Default Web Site Machine=localhost
[MarketingWebService]
ResourceFlags=9226 PupFlags=1 ProgidPUP=Commerce.AddressPuP ResourceType=Address FriendlyName=Address AccessFlags=513 AuthFlags=4 AppIsolated=0 AspCodePage=0 VRoot=MarketingWebService CSAppName=MarketingWebService Website=Default Web Site Machine=localhost
[OrdersWebService]
ResourceFlags=3082 PupFlags=1 ProgidPUP=Commerce.AddressPuP ResourceType=Address FriendlyName=Address AccessFlags=513 AuthFlags=4 AppIsolated=0 AspCodePage=0 VRoot=OrdersWebService CSAppName=OrdersWebService Website=Default Web Site Machine=localhost
[ProfilesWebService]
ResourceFlags=17418 PupFlags=1 ProgidPUP=Commerce.AddressPuP ResourceType=Address FriendlyName=Address AccessFlags=513 AuthFlags=4 AppIsolated=0 AspCodePage=0 VRoot=ProfilesWebService CSAppName=ProfilesWebService Website=Default Web Site Machine=localhost