Step 6: Unpack the Supplier Solution Site on Computer 2
To run the Business Desk application for the Supplier Solution Site, you will need to unpack the Supplier Solution Site on Computer 2.
To unpack the Supplier Solution Site on Computer 2
Download the Solution Sites packages by running the Microsoft Commerce Server 2002 Solution Sites.msi file at https://go.microsoft.com/fwlink/?LinkId=6491.
Click Start, point to Programs, point to Administrative Tools, point to Microsoft Commerce Server 2002, and then click Commerce Server Manager.
Expand Commerce Server Manager, and then click Commerce Sites.
Right-click Commerce Sites, point to New, and then click Unpack Site.
In the Unpack Site From dialog box, enter the path or navigate to the file supplieractivedirectory.pup that you downloaded in step 1, and then click Open.
Commerce Server Site Packager is started.
In the Unpack dialog box, select Quick unpack, and then click Next.
In the Quick Unpack dialog box, do the following:
Use this To do this Site name Type the name for the site, if you want to change it. .gif "Ee825138.note(en-US,CS.20).gif")
Notes- Do not use special characters (including /, \, ?, &, <, >, :, *, |, #, @, %, and ') that might not be recognized by SQL Server databases. For more information, see SQL Books Online.
- The site name can contain a maximum of 127 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.
Do not use any of the following words as the site name:
"App Default Config," "BDSecurity," "Biz Data Service," "Campaigns," "Direct Mail," "Global Data Warehouse," "Predictor," "Product Catalog," "Site CS Authentication," "Site Data Warehouse," "Transaction Config," or "Transactions."
IIS Web site Select the name of the IIS Web site where the application(s) will be installed. 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.
SQL Server Computer Type the name of the SQL Server computer that will contain the databases for the site. Use Windows Integrated security Select this option if you want to use integrated Windows authentication. Windows authentication is the recommended configuration. Note- 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.
Use a specific user name and password Select this option if you want to use SQL Server authentication when connecting to the databases. Note- You should always use a strong password when creating passwords. For more information about strong passwords, see Using Strong Passwords.
SQL Server Login Name Type the SQL Server login name for the databases. Note- For security purposes, do not use the sa login for access to the databases. To change the login information for the Administration database after it is created, use SQL Server Enterprise Manager.
SQL Server Login Password Type the SQL Server login password for the databases. Note- You should always use a strong password when creating SQL Server Login passwords. For more information about strong passwords, see Using Strong Passwords.
Click Next.
If the Data Warehouse resource was installed during the installation process, 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 your global Data Warehouse resource. Server Type the name of the SQL Analysis Services (OLAP) computer. Database Type the name of the OLAP database to use. Click OK.
If the Profiles resource was installed during the installation process, the first of two Profiling System dialog boxes appears. To specify the settings for the Profiles resource, do the following:
Use this To do this Profile Schema Definition Specify the profile schema definition to import. Site Terms Definition Specify the site terms definition to import. Expression Definition Specify the expression definition to import. Click Next.
If the Profiles resource was installed during the installation process, the second of two Profiling System dialog boxes appears. To specify the settings for the Profiles resource, do the following:
Use this To do this Profiling System Connection String Specify the files to import into the OLEDB data store. Click Modify to specify a different database. Schema definition scripts (*.sql, *.vbs) Specify the schema definition scripts to import. Note- Site Packager uses a default schema definition script. 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 Packing Extended Profile Schema.
Data population scripts (*.sql) Specify the data population scripts to import. Click OK.
Note- 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.
In the Profiling System dialog box, type the Domain, User name, and Password for the domain that you previously created. You must type the User name in the form of domain\username. This step allows the user profiles created in the Supplier Solution Site to be stored in Active Directory (Computer 1).
Click OK.
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.
To close Site Packager, click Finish.
You have successfully unpacked the Supplier Solution Site on the second computer. Continue to Step 7: Verify Software Configuration on the Two Computers.
See Also
Copyright © 2005 Microsoft Corporation.
All rights reserved.