Installing Content Connector

  • Article
On This Page

System Requirements System Requirements
System Configurations Supported by Content Connector System Configurations Supported by Content Connector
Installing Content Connector Installing Content Connector
Unpacking the Sample Site Unpacking the Sample Site
Launching the Method Systems Business Desk Launching the Method Systems Business Desk
Deleting a Content Connector Site Deleting a Content Connector Site
Uninstalling Content Connector Uninstalling Content Connector

System Requirements

MSCMS 2001 Content Connector for Commerce Server 2000 is an application that ships on the Microsoft Content Management Server 2001 product CD and is installed separately as described in this chapter. Content Connector combines the content management of Content Management Server 2001 with the e-commerce and personalization capabilities of Microsoft Commerce Server 2000.

Content Connector software requirements

This chapter assumes you have already met the software requirements for Microsoft Content Management Server 2001 and Microsoft Commerce Server 2000.

Following are the software requirements for MSCMS 2001 Content Connector for Commerce Server 2000. The "Supported versions" is the range of product versions, from the earliest version on which Content Connector has been tested, to the most recently tested version. These are the versions on which you can install Content Connector. There may be more recently released versions of the individual products, but we can't guarantee Content Connector will install properly on them.

Product name

Supported versions

Microsoft Commerce Server 2000

Final release, SP1

MSCMS 2001 server

4.1

System Configurations Supported by Content Connector

You can configure your system in a single-server configuration or a multiple server configuration. How you configure your system will determine how you choose to unpack the sample site or custom site (see the section "Unpacking the sample site" in this chapter).

Single-server software configuration

Install Content Connector on the same machine as Commerce Server 2000 and Content Management Server 2001.

There are no additional changes to the hardware requirements already stated for Content Management Server 2001 and Commerce Server's server computer. Refer to Chapter 1, "Getting Started" and Commerce Server 2000 Help for additional system configuration information.

SQL server must be installed somewhere on the network that is accessible to the machine.

Once the servers are configured, you can access your site through the Site Builder or the Business Desk.

Multiple-server software configuration

Any computer in your configuration that acts as a Web server for the Method Systems sample site application must have the following installed on it:

  • Commerce Server 2000 Web server

  • MSCMS 2001 server

  • MSCMS 2001 Content Connector for Commerce Server 2000.

Following is a suggested configuration for multiple servers.

Machine A

This machine is a Web server for Commerce Server and the Method Systems Business Desk application. The software configuration for the Commerce Server administrator machine is as follows:

  • Install the full Commerce Server 2000

  • Do not install MSCMS 2001 or Content Connector on this machine

  • Windows 2000 server or advanced server.

Machine B, C

These machines are Web servers for the Method Systems (or your custom site) Web site application. The software configuration for the Web server machines (multiple) is as follows:

  • Commerce Server 2000 Web server only

  • MSCMS 2001 server

  • MSCMS 2001 Content Connector

  • Windows 2000 advanced served with network load balancing (NLB).

Database server

  • SQL Server 7 or SQL Server 2000

  • Windows 2000 server or advanced server

Client 1, 2, 3

  • Web browser and/or

  • MSCMS 2001 Site Builder and/or

  • Commerce Server 2000 Business Desk.

Installing Content Connector

Before beginning the Content Connector installation, ensure that Commerce Server 2000 and Content Management Server 2001 are installed and functioning.

From the CD, launch the setup program for Content Management Server 2001 by double-clicking setup.exe.

Step

Dialog box title

Action

1

Install splash screen

Click Install Components.

2

Install splash screen

Click Install Content Connector.

3

Welcome

Click Next.

4

Installation Requirements Check

If all prerequisites are met, click Next. The installation will not continue if these requirements are not met.

Adding custom resource types

Step

Dialog box title

Action

1

SQL Database Connection

Select the SQL Server where the Commerce Server Administration database is located. Type the username and password for the database connection. Click Next.

Installing files and components

Step

Dialog box title

Action

1

Ready to Install the Program

Click Install to begin the installation. This takes a few seconds.

2

InstallShield Wizard Completed

Click Finish.

Once the install is completed, unpackage the Method Systems sample site.

Unpacking the Sample Site

You must install Content Connector before unpacking a site.

Unpacking the sample site on a single-server configuration

From Program Files\Microsoft Content Management Server\Server\Content Connector\CS2000\SitePackage, double-click the MethodSystems.pup file.

Step

Dialog box title

Action

1

Unpack

Select Quick Unpack. Click Next. The unpacking takes a few minutes.

2

Quick Unpack

Ensure the site name is set to MethodSystems. Enter the SQL user name and password if it is not already done. Click Next. This takes a few minutes.

3

Data Warehouse

Accept the defaults. Click OK. Unpacking proceeds. This takes a few minutes.
If you are not an MSCMS 2001 administrator for this machine, you will get a message dialog box. Click OK. A login dialog box opens. Type an MSCMS 2001 administrator user name and password in the appropriate fields. Click OK.

4

Profiling system

Accept the defaults. Click Next.

5

Profiling system

Accept the defaults. Click Next.

6

Unpacking is Complete!

Click Finish.

Note The PreMethodSystems.vbs file must stay with the MethodSystems.pup file. If you move the MethodSystems.pup file to another location, be sure to move the PreMethodSystems.vbs file as well.

Unpacking the sample site on a multiple-server configuration

All necessary software should be installed on the respective machines before unpacking the solution site or your custom site. See the section "Multiple-server software configuration" in this chapter for information on software configuration for multiple servers.

Note Do not attempt to run the site or the Business Desk until you have unpacked the Method Systems site (or your custom site) on Machines A and B.

Step 1: Unpack MethodSystems.pup (or custom site) on Machine A:

Because this machine does not have Content Connector installed you must copy the MethodSystems.pup and the PreMethodSystems.vbs files to this computer.

Note When you begin unpacking the site, the PreMethodSystems dialog box warns you that there is no Content Connector or Content Management Server 2001 on this machine. Ignore this error message.

Double-click MethodSystems.pup. The unpack window opens.

Step

Dialog box title

Action

1

Unpack

Select Custom Unpack. Click Next.

2

Unpack Method

Select Create a new site. Click Next.

3

Site Name

Either leave the default of MethodSystems or if this is your own custom site, type a new name <MyCustomSite>. Click Next.

4

Select Resources

Select Content Data and click Remove. All remaining resources and data will unpack on this machine. (Content Data cannot be unpacked on this machine because it requires Content Connector components; Content Connector does not reside on this machine.)

5

Global Resource Pointers

Accept the defaults for mapping global resource pointers to global resources.

6

Database Connection Strings

If the SQL server is on this machine, accept the defaults. If it is on a remote machine proceed with the following six steps:
1. Click New Database. A SQL dialog box opens.
2. Enter the SQL user name, for example, <MyCustomSite_Commerce> and password for this database connection. Click OK
3. Click New Database again.
4. Enter the SQL user name, for example, <MyCustomSite_dw> and password for this database connection. Click OK.
5. Click Modify. The Data Link Properties box opens.
6. Reconfigure the connection strings as appropriate for the resources you are unpacking.
Note Use the same site database for all site resources, except the data warehouse.

7

Select Applications

Uncheck the MethodSystems connector site application. (Only the Business Desk application is unpacked on this machine. The MethodSystems application cannot be unpacked here because it can only run on a Content Connector Web server machine.)

8

Select IIS Web Sites and Virtual Directories

1. Select an IIS Web site and virtual directory for each application.
2. Select the MethodSystems biz desk Application in the left window.
3. In the IIS virtual directory field, type your new site name, for example, <MyCustomSitebizdesk>.

9

Unpacking

The site begins unpacking. This takes a few minutes.

10

Data Warehouse

If this is a custom site, rename the data warehouse file <MyCustomDataWarehouse>. Click OK. Unpacking proceeds; this takes a few minutes.

11

Profiling System

Accept the defaults. Click Next.

12

Profiling System

Accept the defaults. Click OK (this takes a few minutes).

13

Unpacking is Complete!

Click Finish.
Step 2: First unpack of MethodSystems.pup (or custom site) on Machine B

Now you must add the Content Data resource to the site. This machine uses Content Connector components to import Content Management Server 2001 object data.

From the Microsoft Content Management Server\Server\Content Connector\CS2000\SitePackage, double-click the MethodSystems.pup file. The unpack window opens.

Step

Dialog box title

Action

1

Unpack

Select Custom Unpack. Click Next.

2

Unpack Method

Select Add resources in the package to an existing site. Click Next.

3

Site Name

Ensure the selected site name is MethodSystems or if this is a custom site, the custom name you chose when unpacking on Machine A, <MyCustomSite> should be visible. Click Next.

4

Select Resources

Select Content Data and click Add. (Only this resource unpacks on this machine.) Click Next.

5

Global Resource Pointers

Accept the defaults for mapping global resource pointers to global resources. Click Next.

6

Unpacking

The site begins unpacking. This takes a few minutes.

7

Unpacking is Complete!

Click Finish.

A new directory (MethodSystems or <MyCustomSite>) is now added to the Site Package directory.

If you want to make this site available for guests, add guest user rights to the site through the Site Builder. (See Chapter 13, "Managing Content Connector User Authentication" and Chapter 3 "Setting Up Publishing: Assigning Publishing Rights in the MSCMS 2001 Site Administrator's Guide for information on adding guest user rights to the Subscriber group "CS2000 Guests" in the Site Builder.)

The Method Systems sample solution site is best demonstrated with access for guest users allowed.

Step 3: Second unpack of MethodSystems.pup (or custom site) on Machine B

In this step you add the application that supports Content Management Server 2001 when serving site content pages from this Content Connector Web server.

From the Microsoft Content Management Server\Server\Content Connector\CS2000\SitePackage, double-click the MethodSystems.pup file. The unpack window opens.

Step

Dialog box title

Action

1

Unpack

Select Custom Unpack. Click Next.

2

Unpack Method

Select Add an application in the package to an existing site. Click Next.

3

Site Name

Ensure the selected site name is MethodSystems or if this is a custom site, the custom name you chose when unpacking on Machine A, <MyCustomSite> should be visible. Click Next.

4

Select Applications

Uncheck MethodSystemsbizdesk (only the site application is unpacked on this machine). Click Next.

5

Select IIS Web Sites and Virtual Directories

Select an IIS Web site and virtual directory for each application.
1. Select the MethodSystems site application.
2. In the IIS virtual directory field, type your new site name (if this is a custom site), for example, <MyCustomSiteApplication>.

6

Unpacking

The site begins unpacking. This takes a few minutes.

7

Unpacking is Complete!

Click Finish.
Step 4: Updating the Commerce Server Manager on Machine A

The Business Desk application on Machine A launches the MSCMS 2001 Web Author to view and edit site pages. You must specify which server the Business Desk will use to launch content authoring operations.

  1. Click Start>Programs>Microsoft Commerce Server 2000>Commerce Server Manager.

  2. Expand Commerce Server Manager>Commerce Sites>Site Resources>Content Data.

  3. Right-click Properties. The Content Data Properties dialog box opens.

  4. From the Properties pane, select the Content Management Server for BizDesk.

  5. In the Selected Property Value pane, type the name of one of the servers in your cluster, for example the name of Machine B (or the shared DNS name or IP address). Read the property description at the bottom of this dialog box for more information.

The complete site is now available.

Step 5: Add additional Web servers (C, D, etc.)

The <MyCustomSiteApplication> application is now added to the Commerce Server site and running on Machine B. To add additional Web servers for this application, copy the application files on machines C, D, etc.

To add additional Web servers to the site application follow these procedures:

  1. Install Commerce Server Web Server, Content Management Server 2001, and Content Connector on each machine in the cluster.

  2. Go to wwwroot on machine B and find the directory where the site application was unpacked (for example, \Inetpub\wwwroot\MethodSystems or <MyCustomSiteApplication> if this is a custom site).

  3. Copy the MethodSystems or <MyCustomSiteApplication> to the wwwroot directory on the new Web server machine (C, D, etc.).

    In order to configure IIS virtual directories and applications for this machine, run SimulateUnpack.bat, which will launch Unpack.vbs with arguments. (The arguments in SimulateUnpack.bat were given to Unpack.vbs when the application was unpacked on Machine B.)

    Note These arguments are also appropriate on Machines C, D, etc. unless, for example, the wwwroot is on a different physical drive. If the arguments are not correct for machine C, D, etc. you can edit simulate unpack before running it. (To display more information about these arguments, double-click Unpack.vbs.)

  4. Once you verify the arguments, run SimulateUnpack.bat on the new Web server by double-clicking the file.

    The site application is now available on this Web server. Point your browser to the site application URL on this machine. Once the application is loaded, the name of this Web server is added to the site application in the Commerce Server Manager.

  5. Repeat these steps for each Web server machine in your configuration (for example, D, E, etc.).

Launching the Method Systems Business Desk

To launch the Method Systems Business Desk for the first time:

  1. Launch your browser and type the URL for the Business Desk https://<YourServer>/methodsystemsbizdesk. (In a multi-server configuration <Your Server> is Machine A.) This takes a few minutes. The Browse for Folder dialog box opens.

  2. Accept the default directory or select another directory to install the Business Desk.

  3. Select Start Business Desk from the status window. The following window appears.

Deleting a Content Connector Site

Note The following deletions are similar to what is in "Deleting a Site" in the Commerce Server 2000 Help. However, modifications have been made for Content Connector sites. Follow these steps when deleting Content Connector sites.

Deleting Content Connector site files, resources, and virtual directories

Deleting a site

  1. Click Start>Programs>Microsoft Commerce Server 2000>Commerce Server Manager.

  2. Expand Commerce Server Manager>Commerce Sites.

  3. Right-click the site to be deleted (for example, MethodSystems) and click Delete.

Deleting Global Resources

If the global resources used by this site are not used by any other site, you may want to delete them. There are three types of global resources used by the sample site (or custom site) that may be created when unpacking a site.

To delete these resources, from Commerce Server Manager\Global Resources, right-click and select Delete for the following:

  • Data Warehouse <number>

  • CS Authentication(<SiteName>)

  • Profiles(<ServerName>_<SiteName>_Commerce).

Deleting the databases used by the site

  1. Click Start>Programs>Microsoft SQL Server or Microsoft SQL Server 7.0>Enterprise Manager.

    Note Make sure SQL Server is running by checking if the icon in the Enterprise Manager window displays a green light. If it is not running, right-click the name of the SQL Server computer and click Start.

  2. Expand the nodes to the following path: \Microsoft SQL Servers\SQL Server Group\<SQL Server Name>\Databases.

  3. Right-click the database you want to delete and click All Tasks>Detach Database. The Detach Database window opens.

  4. In the Database status section, if the Connections using this database is more than 0, click Clear. Click Cancel (you must do this even if the Clear is unavailable because there are 0 connections).

  5. Right-click the database used by site (for example, MethodSystems) and click Delete.

  6. Repeat steps 3 to 5 for each database you want to delete.

Deleting the OLAP databases for the site

  1. Click Start>Programs>Microsoft SQL Server>Analysis Services>Analysis Manager.

  2. Expand the nodes to the following path: \Analysis Servers\SQL Server Name.

  3. Right-click the database you want to delete and click Delete.

  4. Click Yes to confirm the folder deletion for each database you want to delete.

  5. Repeat steps 3 and 4 for each database you want to delete.

Deleting Direct Mailer jobs

  1. Click Start>Programs>Microsoft SQL Server or Microsoft SQL Server 7.0>Enterprise Manager.

  2. Expand the nodes to the following path: \Microsoft SQL Servers\SQL Server Group\SQL Server Name\Management\SQL Server Agent\Jobs.

  3. From the right pane of the SQL Server Enterprise manager select the Direct Mailer job(s) you want to delete. Click Delete from the toolbar.

Deleting virtual directories

If you have a multiple server configuration you need to delete the following on all machines. However, depending how your machines are configured, not all files and virtual directories will be on all machines.

  1. Click Start>Administrative Tools>Internet Services Manager.

  2. Expand the nodes to the following path: \<computer name>\Default Web Site.

  3. Right-click the virtual directories (for example the applications of the site, MethodSystems and MethodSystemsbizdesk) and click Delete.

  4. From the Internet Services Manager, expand the nodes to the following path: \<computer name>\Default Web Site\NR\System\WBC\Customizable.

  5. Right-click the virtual directory Customizable and click Delete.

  6. From the Internet Services Manager expand the nodes to the following path: \<computer name>\Default Web Site\NR\ContentConnector\CS2000\SiteInterface.

  7. Right-click the virtual directory SiteInterface and click Delete.

Deleting site files

From Windows Explorer, go to the directory Inetpub\wwwroot where the site files are installed. Right-click and select Delete for the following files. (You may need to stop or restart the Web service to delete the <SiteName> folders.)

<SiteName> folder<SiteName> Business Desk foldercsapp.iniglobal.asa

Delete physical files used by the Content Data resource

From Microsoft Content Management Server\Server\ContentConnector\CS2000\SitePackage delete the sub-directory matching the site name, for example, MethodSystems.

Deleting content data

Delete the data in the order specified.

  1. From the MSCMS 2001 Site Builder, select the Channel to be deleted (for example, CS2000 Channel). From the toolbar, click Delete.

  2. Purge your deleted items folder.

  3. Repeat steps 1 and 2 for the CS2000 Folder, Template Gallery, and Resource Gallery.

If you were unable to delete all data, installing a new package will overwrite the data remaining on your system.

Uninstalling Content Connector

Note You must delete a Content Connector site before you uninstall Content Connector. If you uninstalled Content Connector first, reinstall it, remove the site, and then proceed with uninstalling Content Connector.

To uninstall Content Connector click Start>Settings>Control Panel>Add/Remove Programs and scroll to Content Connector. Click Remove.

Uninstall does not delete Content Connector sites. See "Deleting a Content Connector site" in this chapter for information.

Note If you reinstall Content Management Server 2001 you should uninstall and reinstall Content Connector following the instructions described in this manual.