How to Unpack a Site
You can unpack a site by using the Quick Unpack option or the Custom Unpack option. The Custom Unpack option lets you specify a different virtual directory and Web server for unpacking Commerce Server applications. Custom Unpack also lets you choose different database names for Commerce Server resources. By using Custom Unpack, you can associate the site together with instances of existing global resources instead of creating new instances.
By default, Site Packager unpacks each application into the IIS Default Web Site in a virtual directory that matches the application name. To improve the security of your site, you should create a new IIS Web site instead of using the Default Web Site for the Commerce Server sites that you unpack. You can change the name of the virtual directory that contains each application. To change the IIS Web site or virtual directory when you unpack a site, you must use the Custom Unpack option in Site Packager.
When you add application files to a Web server in a Web farm, you associate that Web server together with the application in Commerce Server Manager. Site Packager displays the name of the IIS Web site where the application will be installed and the IIS application path for each Commerce Server application. Site Packager always creates a log file for all its actions at %SystemDrive%\Pup.log. You can review this file to diagnose any errors that occur during packaging or unpacking a site. Commerce Server always appends this file together with the logs from subsequent runs of Site Packager.
When you unpack a site and an application that already is in the Administration database, Site Packager assumes that you are adding a Web server to the application.
Commerce Server 2009 provides the CSharp site and the Default site packages that include the Commerce Server 2009 Web services, such as the Catalog Web Service, Marketing Web Service, Orders Web Service, and the Profiles Web Service.
The following instructions explain how to unpack the CSharp site on one computer by using either the Quick Unpack option or the Custom Unpack option in Site Packager. Before you unpack the site, note the following:
To unpack the CSharp site onto a virtual directory other than the default, you must use the Custom Unpack option.
Before you unpack the CSharp site, verify that you are logged on as a member of the Administrators group.
Make sure that you have administrator credentials on the SQL Server on which you create the resource databases.
If you cancel the unpacking process, databases created during the unpacking process will not be deleted.
Warning
If you unpack a Web application to the root of a Web site, we recommend that you do not unpack other any other applications to Virtual Directories in the same Web site. Instead, unpack them to a different Web application site. This makes sure that the settings of one Web application do not conflict with the child or parent Web application
Note
For best performance, unpack the catalog and inventory resources to the same database. We do not recommend unpacking catalog and inventory to databases on different SQL Server computers.
To unpack a site by using the Quick Unpack option
Click Start, point to Programs, point to Microsoft Commerce Server 2009 , and then click Site Packages.
In the Pup Packages folder, double-click CSharp.pup.
On the Unpack page, select the Quick unpack option, and then click Next.
On the Quick Unpack page, do the following:
Note
The Quick Unpack option uses default locations for virtual directories in the package. If you want to specify a location other than the default location, use Custom Unpack. Custom Unpack lets you specify different virtual directories for unpacking Commerce server applications.
Use this
To do this
Site name
Type CSharpSite as the name of the Web site.
IIS Web site
Accept the Default Web Site as the IIS Web site.
SQL Server Computer
Type the name of the computer that is running SQL Server on which you want to unpack the CSharp site.
Use Windows Integrated security
Select this option to use Windows Integrated security for the databases. We recommend this configuration.
Use a specific user name and password
Select this option if you want to use SQL Server authentication when you connect to the databases. We do not recommend this configuration.
SQL Server Login Name
Type the SQL Server login name for the databases.
SQL Server Login Password
Type the SQL Server login password
On the Quick Unpack page, click Next.
On the first of two Profiling System pages, click Next to accept the default settings.
On the second Profiling System page, click OK to accept the default settings.
In the Commerce Server Site Packager dialog box, review the list of resources that you configured to use Windows Integrated security, and then click OK.
These resources require access permissions on the appropriate Windows accounts. You will assign permissions in the following post-installation steps.
On the Unpacking is complete! page, click Finish.
To unpack a site by using the Custom Unpack option
Click Start, point to Programs, point to Microsoft Commerce Server 2009 , and then click Site Packages.
In the Pup Packages folder, double-click CSharp.pup.
In Commerce Server Site Packager, on the Unpack page, click Custom unpack, and then click Next.
On the Unpack Method page, select Create a new site to unpack the CSharp site package file, and then click Next.
On the Site Name page, in the Site name box, type CSharpSite, and then click Next.
On the Select Resources page, do the following:
Use this
To do this
Resources to unpack
Specify the resources that you want to unpack. If the resource is included in this list, its settings and schema will be unpacked.
Add
Move items selected in the Available resources list to the Resources to unpack list.
Add All
Move all items in the Available resources list to the Resources to unpack list.
Remove
Move all items selected in the Resources to unpack list to the Available resources list.
Remove All
Move all items in the Resources to unpack list to the Available resources list.
Click Next.
On the Global Resource Pointer page, do the following:
Use this
To do this
Global resource pointers
Select the Resource to map.
The Maps to global resource column indicates whether a new global resource will be created locally (Add new global resource), or an existing global resource will be pointed to.
Existing global resource
From the drop-down list, select either an existing global resource you want the resource that is being unpacked to map to, or select the Add new global resource option, to create a new global resource.
The list contains global resources created during Commerce Server setup.
Click Next.
On the Database Connection Strings page, do the following:
Use this
To do this
Resource
Select the resource on which you want to perform an action, such as changing a database server. Hold down the SHIFT or CTRL keys to select multiple resources.
Modify
Click to modify the connection strings that were defined for the selected resource(s). You can specify a different server or database.
Defaults
Click to return the connection strings to the default settings for the selected resource(s). The default settings consist of two databases, one for the Data Warehouse, and one for the other resources. Both databases are stored locally.
New Database
Click to create a new database for the selected resource(s). Use this command if you want to put the database on a different computer.
You cannot rename a SQL database.
Click Next.
On the Select Applications page, in the Applications in the package list, clear the check boxes for the applications that you do not want to unpack, and then click Next.
On the Select IIS Computers, Web Sites and Paths page, do the following:
.gif "Important note")
Important Note:The Commerce Application Name and the Virtual Directory Path must be unique for all Commerce Server site and Web services that you install.
Note
Site Packager creates a subfolder by using the application name and puts all associated files in this folder. By default, the CSharp site package names this folder CSharpSite. You can change this folder name to suit the business needs.
Use this
To do this
Commerce Application
From the list of applications, select the application on which you want to perform an action, such as changing the IIS Web site.
Commerce Application Name
Accept the default application name of CSharpSite.
Important Note:
The Commerce Application Name should be unique across all applications in the commerce Web site.IIS Web site
Select an existing IIS Web site to which you want to unpack the application files.
Important Note:
If you have already unpacked a site to an existing IIS Web site and you do not want to overwrite the exiting site, you must use a different IIS Web site.Virtual Directory path
Specify the name of the IIS path of the CSharp site. This name will appear in the URL path of the site. You should change the path name for each new site and new application that you unpack so that you do not override the content of applications that have previously been unpacked.
Important Note:
The virtual directories for each application must point to different locations and not conflict with any other virtual directories. This includes ones that are not in the site, so that the files in the virtual directories do not overwrite each other..gif "Note")
Note:
To unpack an application to the root of the Web site, use the ‘/’ character or leave this field blank.Click Next.
Commerce Server starts unpacking the CSharp site.
On the first Profiling System page, accept the defaults, and then click Next.
On the second Profiling System page, accept the defaults, and then click Next.
In the Commerce Server Site Packager dialog box, click OK.
On the Unpacking is Complete! page, view the list of databases and applications that were packed or unpacked, and their locations. You can also access the Site Packager log file to view errors.
If errors occurred, or you select to cancel the Site Packager, the following dialog boxes display:
The Errors Occurred during unpacking dialog box displays when errors occurred during the unpacking process.
The Packaging has been terminated dialog box displays when you select to cancel packaging of a site.
Use this
To do this
SQL databases created
View the SQL databases that were created and the computers on which they are installed.
Note:
If you cancel the unpacking process, databases that were created during the unpacking process will not be deleted.IIS applications created
View the applications for which databases were created and the Web site on which they are installed.
View Log File
Click to open the Site Packager log file. It lists all the events that occurred as long as Site Packager was running. Use this to obtain information if errors occurred.
Click Finish to close Site Packager.