How to configure Commerce Server 2007 to analyze log files from a Web site that is not based on Commerce Server 2007

This article describes how to configure Microsoft Commerce Server 2007 to analyze log files from a Web site that is not based on Commerce Server 2007. The only requirement is that the log files must be in W3C log file format.

For the purposes of this article, the Web server log files are from a fictitious Web site and a fictitious Web server. This fictitious Web server is running Microsoft Internet Information Services (IIS) version 6.0. The URL of this fictitious Web site is http://noncswebsite.microsoft.com. The Web site uses Microsoft SQL Server 2000.

In IIS, the fictitious Web site is named "My Custom Web Site." The NetBIOS name of the server is MyNonCS2K7Srv. The IP address of the server is 192.168.5.5. This fictitious Web site logs daily.

To analyze log files, follow these steps:

1. Install Commerce Server 2007 by the following recommended installation instructions. To view the instructions, visit the following Microsoft Web site:
   http://go.microsoft.com/fwlink/?LinkID=57268
2. Unpack the Dw.pup solution file.
3. Click Custom unpack, and then click Next.
4. Click Create a new site, and then click Next.
5. In the Site name box, type NonCSAnalysis, and then click Next.
6. On the Select Resources screen, determine whether Data Warehouse is in the Resources to unpack list.
   • If Data Warehouse is not in the Resources to unpack list, click Data Warehouse in the Available resources list, click Add, and then click Next.
   • If Data Warehouse is in the Resources to unpack list, click Data Warehouse, and then click Next.
7. On the Global Resource Pointers screen, accept the default global resource pointer, and then click Next.
8. On the Database Connection Strings screen, modify the database connection information as appropriate, and then click Next. For example, specify a database and a computer that is running Microsoft SQL Server.
9. On the Select Applications screen, click Next.
10. Configure the server properties. To do this, on the Data Warehouse screen, change the name in the Data Warehouse box to NonCSAnalysisDW, and then click Next. Alternatively, in the Analysis Server Properties area, you can accept the default option.
11. In the Commerce Serve Site Packager dialog box, click OK.
12. After the package is finished, in the Commerce Serve Site Packager dialog box, click Finish.
13. Open the Commerce Server Manager Microsoft Management Console (MMC).
14. Under the Commerce Server Manager snap-in, expand Commerce Sites, expand NonCSAnalysis, and then expand Applications.
15. Right-click Applications, click New, and then click Add Non-Commerce Application.
16. On the General tab, type MyCustomWebSite in the Application Name box.
17. In the Nonsecure host name box, type noncswebsite.microsoft.com.
18. In the IIS application path box, type / to analyze the whole site.
19. Click the Web Servers tab, and then type My Custom Web Site in the IIS Web site box.
20. In the Local domain box, type microsoft.com, and then click OK.
21. In the Non-Commerce applications and Web servers dialog box, click noncswebsite.microsoft.com. Right-click noncswebsite.microsoft.com/MyCustomWebSite, click New, and then click Add Non-Commerce Web Server.
22. In the Server name box, type MyNonCS2K7Srv. In the IP address box, type 192.168.5.5. In the TCP port box, type 80. Leave the Host header name box blank.
    
    Note For Transmission Control Protocol (TCP) and Secure Sockets Layer (SSL) ports, type the correct information based on the configuration of the Web server that the logs are coming from.
23. On the Log Files tab, click the appropriate log file period based on the configuration of the Web server that the logs are coming from. For the example in this article, click Daily. This setting directly affects the way that the DTS tasks search for log files.
24. In the Log file directory, type the path where you want to store the log files. The path must be a local path.
25. Open the SQL Enterprise Manager (MMC), expand Microsoft SQL Servers, expand SQL Server Group, and then expand the name of the server.
26. Right-click Data Transformation Services, and then click New Package.
27. On the Task menu, click Configuration synchronization (Commerce Server). The Properties dialog box for the Synchronize Data Warehouse task appears.
28. In the Site name list, click NonCSAnalysis.
    
    Note You must run the Configuration Synchronization task on each recently created data warehouse. You must also run the Configuration Synchronization task after you make any changes to the Commerce site configuration.
29. On the Task menu, click Web server log import (Commerce Server). The Properties dialog box for for the Import Web Server Logs task appears.
30. In the Site name list, click NonCSAnalysis.
31. Click the Log File Location tab, and then click noncswebsite.microsoft.com in the Application list.
32. Modify the log file path as required. This path must be the path of a folder that is located on a local drive or on a mapped network drive that contains W3C log files.
33. Click Log Files, and then select all the log files that you want to import.
    
    Note If you do not see any log files, either the log file path is incorrect, or the log file period is not set correctly. Log files cannot be imported while IIS is writing to the log files.
34. In the Import Web Server Logs dialog box, click OK.
35. On the Task menu, click Report Preparation (Commerce Server). The Properties dialog box for the Import Web Server Logs task appears.
36. In the Operation properties list, click NonCSAnalysisDW.
37. Under Processing Mode, select Full, and then click OK.
38. Hold down the CTRL key, and then click both Web server log import and Report Preparation.
39. On the Workflow menu, click On Success.
40. Start the DTS package. To do this, on the Package menu, click Execute.
41. After the DTS package has finished running, use Report Manager to view reports for the Web site.