Unpacking a Site to a Remote Web Server

In Commerce Server 2002, you can specify a remote Web server on which you want to install the applications in your package using the Custom Unpack mode of Site Packager. Note the following requirements for unpacking a site or application to a remote Web server:

• To unpack the Data Warehouse resource, the computer on which you are running Site Packager must have the Analysis Manager component of Analysis Services installed. You do not need to have the Analysis database on the same computer on which you have unpacked the Solution site.
• The remote Web server must have Commerce Server 2002, Internet Information Services (IIS), and the Analysis database installed.
• When unpacking the Data Warehouse resource to a remote computer that only has the Analysis Manager component installed (instead of full Analysis Services), create a new registry key called Server Connection Info so that Analysis cubes can be installed. Create this key under HKEY_LOCAL_MACHINE\Software\Microsoft\Olap Server with the following two string values:
  • Locks Directory with the value <analysis server installation drive>:\\\\<root analysis server installation directory>\\bin. For example, <d:\\\\Microsoft Analysis Services\\bin. This value specifies the location where the Analysis Manager components are installed.
  • Remote Locks Directory with the value MsOLAPRepository$.
• Members of the Administrators group, on the remote computer, must be granted operator privileges for the Web site in which you will unpack your Commerce application. For more information, see the "Assigning Web Site Operators" topic in the IIS online help. Additionally, the local computer, in which you are running Site Packager, must be granted access by IIS on the remote computer. For more information, see the "Granting and Denying Access to Computers" topic in the IIS online help. Site Packager does not check for this condition. If this condition is not met, then the site will not unpack, and an error will not be displayed.
• The administrator, who is unpacking the site or application, must provide login credentials for a valid Windows account, which is a member of the administrator group on the remote computer. Site Packager does not check for this condition. If this condition is not met, then the site will not unpack, and an error will not be displayed.
• The administrator group on the remote computer, must grant write access to the local administrator group, to create new folders and files, in which Site Packager writes creates on the remote computer. Site Packager does not check for this condition. If this condition is not met, then the site will not unpack, and an error will not be displayed.
• The application on the remote computer must be associated with the same administration database as all other applications for this Commerce site. You can also use this feature to add applications to a site, or Web servers to an application on a remote machine.

Use the following procedures if you are unpacking a site to a remote Web server:

1. Start unpacking a site to a remote Web server
2. Add the resources you want to unpack to the new site
3. Select the applications you want to unpack
4. Specify the settings for the selected resources
5. Complete the unpacking process

Start unpacking a site to a remote Web server

1. Click Start, point to Programs, point to Microsoft Commerce Server 2002, and then click Commerce Site Packager.

2. In the Commerce Server Site Packager dialog box, select Unpack from a package file (pup), and then click Next.

3. In the Unpack dialog box, type the path and file name of the file you want to unpack, or click the Browse button.

   If you clicked the Browse button, in the Open dialog box, navigate to the folder that contains the file you want to unpack, select the file, and then click Open.

4. When the Unpack dialog box reappears, select Custom unpack, and then click Next.

Add the resources you want to unpack to the new site

1. In the Unpack Method dialog box, select Create a new site, and then click Next.

2. In the Site Name box, type the name for the site, and then click Next.

   Notes

   • To avoid unpacking errors, do not use special characters in your site name that are not recognized by SQL Server databases. For more information, see SQL Books Online.
   • Do not specify a site name of more than 127 single-byte or double-byte characters.
   • Do not name your site "Commerce." This is a reserved OLAP database name. Naming your site "Commerce" could cause the overwriting of your OLAP database the next time you unpack a site.

3. In the Select Resources dialog box, select the resources you want to add, and then click Next.

   Note

   • In the Select Resources dialog box, you must install the CS Authentication and Profiles resources together. They do not work unless both are installed.

4. In the Global Resource Pointers dialog box, click Next.

   You use this dialog box to map to existing global resources or to create new ones.

5. In the Database Connection Strings dialog box, Site Packager lists the databases it will create and the servers on which it will create them. To change the databases and servers, click Modify, and then type the new database(s) and server name(s).

   Note

   • If you want to copy a database connection string, select the row that contains the connection string you want to copy, and then click Modify. In the Data Link Properties dialog box, select or type the server and database name(s) you want to copy, and then click OK. In the Database Connection Strings dialog box, reselect the row that contains the connection string you want to copy, and then click Copy. Select the row(s) to which you want to copy the connection string, and then click Paste.

6. Click Next.

   The Commerce Server Site Packager dialog box appears if Site Packager needs to create a database(s). The information you provide in this dialog box is used to connect to the Master database on your SQL Server installation.

7. In the Commerce Server Site Packager dialog box, do the following:

   Use this	To do this
   Use Windows Integrated security	Select this option if you want to use integrated Windows authentication for the databases. This is the recommended configuration. When you use Windows integrated security, user names and passwords are not stored in the SQL Server connection string, and are not affected by SQL password resets. For information about Commerce Server security, see Securing Your Site in Commerce Server Help.
   Use a specific user name and password	Select this option if you want to use SQL Server authentication when connecting to the databases.
   SQL Server Login Name	Type the SQL Server login name for the databases.
   SQL Server Login Password	Type the SQL Server login password.

8. Click OK.

Select the applications you want to unpack

1. In the Select Applications dialog box, verify that the applications you want to unpack are selected, and then click Next.

2. In the Select IIS Computers, Web Sites and Paths dialog box, select an application in the Application column, and then do the following:

   Use this	To do this
   IIS computer name	Type the computer name of the remote IIS Web server for the selected applications. To add the list of Web sites for the computer, click Refresh.
   IIS Web site	Select the name of the IIS Web site for the selected applications. Note If you unpack a site onto the IIS Administrative Web site, the site and Business Desk will not function due to IIS administration security limitations.
   IIS path	Type the name of the IIS path for the selected applications. Note To unpack an application to the root of the Web site, use the ‘/' character or leave this field blank.

   Notes

   • Each application in the Select IIS Computers, Web Sites and Paths dialog box must be configured separately.
   • Site Packager unpacks each application under the home directory of its corresponding IIS Web site. Within the home directory, Site Packager creates a subfolder using the IIS virtual directory name of the application.

3. Click Next.

   A message appears indicating that you must run the Unpack.bat file for each application that is being unpacked to a remote computer. After unpacking is complete, see the Site packager log file for the specific location of each Unpack.bat file.

Specify the settings for the selected resources

1. If you added the Data Warehouse resource to the site, the Data Warehouse dialog box appears. To specify the settings for the Data Warehouse resource, do the following:

   Use this	To do this
   Name	Type a name for the global Data Warehouse resource.
   Server	Type the name of the SQL Analysis (OLAP) computer.
   Database	Type the name of the Analysis (OLAP) database to use.

2. Click OK.

   If you added the Profiles resource to the site, the first of two Profiling System dialog boxes appears.

3. If you are unpacking a Solution Site, click Next to accept the default entries.

4. To specify your own profile settings, do the following:

   Use this	To do this
   Profile Schema Definition	When you pack a site, Site Packager extracts the profile schema from your Profiles database and stores it in an XML file. Specify that XML file here so it is unpacked. When you unpack a Solution Site, accept the default XML file, ProfileDefinition. This file contains the following profile definitions: Address, BlanketPOs, Organization, Targeting Context, and User Object.
   Site Terms Definition	When you pack a site, Site Packager extracts the site terms definition from your database and stores it in an XML file. Specify that XML file here so it is unpacked. When you unpack a Solution Site, accept the default XML file, SiteTerms. This file contains the predefined site terms for your use.
   Expression Definition	When you pack a site, Site Packager extracts the definitions for expressions that you defined using Business Desk and stores them in an XML file. Specify that XML file here so it is unpacked. When you unpack a Solution Site, a default XML file, ExpressionDefinition, is provided. This file does not contain any predefined expressions for the Solution Sites.

5. Click Next.

   If you added the Profiles resource to the site, the second of two Profiling System dialog boxes appears.

6. If you are unpacking a Solution Site, click Next to accept the default entries.

   To specify your own profile settings, do the following:

   Use this	To do this
   Profiling System Connection String	Accept the default connection string to the Profiles database, or click Modify to configure the connection string. Note If you change the XML file, Commerce Server does not preserve the connection string information. The new XML file can contain a different type and number of aggregated data stores than the data stores that are in the default XML file. Therefore, you must re-enter the connection string.
   Schema definition scripts (*.sql, *.vbs)	Specify the schema definition script that will create the Profiles tables in the runtime data stores (the SQL tables that store the data for the user, address, organization, and so forth.) When you unpack a Solution Site, SCHEMAUPM_SQLSource.SQLSource creates the tables for the default profile definitions: Address, BlanketPOs, Organization, Targeting Context, User Object. For a sample script, see ProfileSQL.sql, which is located in \Program Files\Microsoft Commerce Server 2002. If you modify the UserObject table or other profile schema definitions, you must use SQL Server Enterprise Manager to generate a script to use here. For more information, see Packaging Extended Profile Schema.
   Data population scripts (*.sql)	If you have extracted the profile data from a Profiles database, you can specify data population scripts so when you unpack, that data is imported into your new Profiles database. For a sample script that contains data for two users, see PopulateProfileSql.sql, which is located in \Program Files\Microsoft Commerce Server 2002. For information about using scripts with site packager, see Using Scripts with Site Packager.

7. Click OK.

Complete the unpacking process

1. If you are using Windows Integrated security, in the Commerce Server Site Packager dialog box, review the list of resources that are being unpacked and require access permissions on the appropriate Windows accounts, and then click OK.

2. In the Unpacking is complete! dialog box, review the list of SQL Server databases and IIS applications that were created. To review the list of events in the Site Packager log file, click View Log File.

   Note

   • When unpacking to a remote server, Site Packager logs most of the status information to the Pup.log file on the local computer. However, some status information is also logged in the Pup.log file on the remote computer. You should view both Pup.log files.

3. In the Unpacking is complete! dialog box, click View Log File, to review the list of events in the Site Packager log file.

   The Site Packager log (Pup.log) file appears.

4. In the log file, search for the text string "unpack.bat" that is associated with the site you unpacked. After you find “unpack.bat” you will see the following log entry:

   \\<ServerName>\<DriveLetter>$\inetpub\wwwroot\<SiteName>\unpack.bat has been created.
    Execute this batch file to complete the unpacking of the <ApplicationName> application,
   

   where <ServerName> is the name of the remote Web server, <DriveLetter> is the drive letter of the remote server to which the site was unpacked, <SiteName> is the name of the site that was unpacked to the remote Web server, and <ApplicationName> is the name of the application that was unpacked to the remote Web server.

5. Execute the Unpack.bat file on the remote Web server to complete the unpacking process.

   Note

   • After you create an application, an unpack.vbs script may exist in the root directory (if you unpack the Blank site, it will not exist). Make sure you delete or secure the file immediately after unpacking. Anonymous users can access the file. Unauthorized use of this script file could lead to denial of service or the breaking of site settings. For information about securing your site, see Securing Your Site.

6. To close Site Packager, click Finish.

Copyright © 2005 Microsoft Corporation.
All rights reserved.