Home
User Guide
The information contained in this section applies to IBM WebSphere Commerce Version 7.0.0.9 and Feautre Pack 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in new editions.
Developing
The topics in the Developing section describe tasks performed by an application developer.
Presentation layer
WebSphere Commerce uses Java Server Pages (JSP) to implement the view layer of the Model-View-Controller (MVC) design pattern. The view layer is in charge of retrieving data from the database through the use of data beans and formatting it to meet the display requirements. The view layers determines whether the request is sent to a browser or streamed out as XML. JSP files present a clean separation between data content and presentation.
Analytics for IBM WebSphere Commerce
WebSphere Commerce provides a framework that you can configure to integrate your store with an external Web analytics solution. This framework includes a tag library that you can use in store page JSP files to provide appropriate analytics information to the external analytics system.
Integrating a store with IBM Digital Analytics for WebSphere Commerce
WebSphere Commerce provides a framework and tools to simplify the process of setting up your site to use IBM Digital Analytics, formerly known as Coremetrics Analytics. IBM Digital Analytics is an industry leading hosted web analytics solution. The framework is implemented as a tag library designed to act as an intermediary layer between WebSphere Commerce and IBM Digital Analytics. The tools include an auto tagging utility to place analytics tags in your store pages. The tools also include a utility to generate a file that contains your catalog hierarchy for IBM Digital Analytics. This solution can significantly reduce the time that is required to deploy web analytics
Task flow: Implementing IBM Digital Analytics for IBM WebSphere Commerce
This task flow leads you step-by-step through the process of configuring a store to communicate with IBM Digital Analytics, formerly known as Coremetrics Analytics. This task flow shows how to add the analytics tags to your store pages.
Running the auto tagging utility
You can run the auto tagging utility to automate the process of tagging store JSP files with the page view tag (<cm:pageview />). You must add other analytics tags manually, such as the order tag (<cm:order />) tag and the shopping cart tag (<cm:cart>).

Running the auto tagging utility

You can run the auto tagging utility to automate the process of tagging store JSP files with the page view tag (<cm:pageview />). You must add other analytics tags manually, such as the order tag (<cm:order />) tag and the shopping cart tag (<cm:cart>).

Feature Pack 3 The auto tagging utility also adds the <cm:output /> tag to the <head> element of all your store pages. This ensures that the JavaScript snippets for IBM Digital Analytics, formerly known as Coremetrics Analytics defined in the <output> element of your biConfig.xml file are written to each HTML page.

About this task

The Madisons and Elite starter stores are already pretagged for IBM Digital Analytics. If your store is built from one of these starter stores, you do not need to run the auto tagging utility unless you have added custom pages to the store. If you are not sure, you can search your JSP files for occurrences of <cm:.

Procedure

Go to the following directory:
- WC_installdir/bin
- WCDE_installdir/bin
Run the command line utility.
View the JSP files to verify the pages are tagged with the <cm:pageview /> tag.