Home
User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
Integrating
Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
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
IBM Digital Analytics, formerly known as Coremetrics Analytics integration with Web 2.0 starter stores
The WebSphere Commerce Web 2.0 starter stores use Rich Internet Application (RIA) technologies such as Ajax (Asynchronous JavaScript and XML) and Dojo widgets. With these technologies certain customer interactions with store page content do not result in a full page refresh. IBM Digital Analytics, formerly known as Coremetrics Analytics provides a framework to track these intrapage interactions, in addition to interactions that result in a full-page refresh. This framework ensures that IBM Digital Analytics collects accurate analytics data about how customers are using your Web 2.0 store.
Customizing IBM Digital Analytics events for Web 2.0 starter stores
You can customize events for IBM Digital Analytics, formerly known as Coremetrics Analytics for Web 2.0 starter stores in three different ways.
Sending additional data to IBM Digital Analytics for a IBM Digital Analytics event
Each of the predefined events for IBM Digital Analytics, formerly known as Coremetrics Analytics supports a set of parameters to provide the analytics data that IBM Digital Analytics requires. You can add custom parameters to the JSON object if required. Any custom parameters are appended to the end of the IBM Digital Analytics data tag.

User Guide
The information contained in this section applies to WebSphere Commerce Version 8. The documentation also applies to all subsequent releases and modifications until otherwise indicated in a newer section.WebSphere Commerce is a single, unified e-commerce platform that offers the ability to do business directly with consumers (B2C), directly with businesses (B2B), and indirectly through channel partners (indirect business models). WebSphere Commerce is designed to be a customizable, scalable, and high availability solution that is built to leverage open standards. It provides easy-to-use tools for business users to centrally manage a cross-channel strategy. Business users can create and manage precision marketing campaigns, promotions, catalog, and merchandising across all sales channels.
- Planning
  Creating a custom implementation of a WebSphere Commerce store requires a significant amount of planning. From gathering client needs, to deploying the live solution, much work is needed to successfully deploy a custom client store. Use the resources in here to help you plan every phase of store creation.
- Installing
  Review the following sections for information about installing the WebSphere Commerce product, associated maintenance, and WebSphere Commerce enhancements.
- Migrating
  Before you migrate to WebSphere Commerce Version 8.0, review this information to help plan and execute your migration.
- Deploying
  The topics in this section describe how to publish stores to either a test or production environment, and how to deploy customized code.
- Operating
- Integrating
  Topics in the Integrating category highlight the tasks that are commonly performed for using WebSphere Commerce in combination with other products.
  - Integrating with back-end systems and external applications
    External systems integration is a key feature of the WebSphere Commerce solution. In WebSphere Commerce business logic is enabled for integration and built-in adapters and interfaces are provided for common integration points. Additionally, the WebSphere Commerce integration solution leverages integration standards by using various IBM connectivity solutions.
  - IBM Watson Campaign Automation integration
    You can integrate IBM Watson Campaign Automation with WebSphere Commerce so that transactional emails are sent by IBM Watson Campaign Automation.
  - Sterling Order Management integration
    The integration between WebSphere Commerce and Sterling Order Management combines the industry-leading front-end capabilities of WebSphere Commerce with the proven, back-end order and inventory management features of Sterling Order Management.
  - IBM MQ
    WebSphere Commerce provides a listener for IBM MQ for inbound requests, and an adapter for IBM MQ for outbound requests, to integrate back-end, and external systems with WebSphere Commerce.
  - Content management integration
    You can integrate WebSphere Commerce with an external content management system through a punch-out window from Management Center and through the web feed utility. You can integrate WebSphere Commerce with IBM Web Content Manager to provide Management Center users the ability to associate IBM Web Content Manager content with WebSphere Commerce objects.
  - Mobile applications that use IBM Worklight
    IBM Worklight is a mobile application platform that you can use to develop cross-platform hybrid applications for the Aurora starter store.
  - Facebook integration
    Facebook integration relies on several Facebook plugins to add the Connect to Facebook, Like, and Send buttons to the Aurora starter store.
  - 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.
    - Analytics tag library for IBM WebSphere Commerce
      The basis for the WebSphere Commerce analytics framework is a JSP-based tag library. By adding WebSphere Commerce analytics tags to your store pages, you can communicate information about site usage to an 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
      - IBM Digital Analytics JavaScript library types: standard and custom
        There are two different JavaScript libraries for IBM Digital Analytics, formerly known as Coremetrics Analytics: the standard IBM Digital Analytics library and the custom IBM Digital Analytics library. It is important to understand which type your site is using because the implementation details differ.
      - CDFGenerator utility
        For proper product and content classification, IBM Digital Analytics, formerly known as Coremetrics Analytics requires a Category Definition File (CDF). When you run the CDFGenerator utility, it generates a CSV file in the IBM Digital Analytics defined CDF format. The CDFGenerator is the command-line utility that generates the product data as a CSV file.
      - Auto tagging utility
        The Auto tagging utility automates the process of tagging the store JSP files with analytics tags. This utility makes tagging the site much easier and also reduces the implementation time. With this utility, the JSP files are only tagged with the tag named pageview and not any other tag. This utility scans the WebSphere Commerce web pages and adds the tags. The utility also creates backup copies of the JSP files that it updates to facilitate removing the changes.
      - Sample biConfig.xml file for IBM Digital Analytics
        The following biConfig.xml sample file represents the default version included with IBM Digital Analytics, formerly known as Coremetrics Analytics.
      - Storing category information in cookies for analytics reporting
        You can configure your site to store category information in cookies to pass to an analytics provider. The configuration steps involve adding a <useCookies> element to your biConfig.xml configuration file, and adding a <cm:setCategoryCookie/> tag to certain store pages.
      - Configuring single sign-on between Management Center and IBM Digital Analytics
        Make the integration between Management Center and IBM Digital Analytics, formerly known as Coremetrics Analytics seamless for business users by configuring single sign-on. When single sign-on is in place, business users do not need to log on to IBM Digital Analytics separately when they launch the IBM Digital Analytics dashboard or view IBM Digital Analytics reports from Management Center.
      - Using the output tag to configure the placement of IBM Digital Analytics JavaScript snippets
        In store JSP pages, the output tag (<cm:output/>) acts as a marker for the location to write JavaScript snippets for IBM Digital Analytics, formerly known as Coremetrics Analytics each time the page is rendered.
      - Creating self-signed certificates for testing IBM Digital Analytics for IBM WebSphere Commerce
        Use a self-signed or third-party certificate for testing IBM Digital Analytics, formerly known as Coremetrics Analytics in a staging or test environment.
      - IBM Digital Analytics, formerly known as Coremetrics Analytics integration with Web 2.0 starter stores
        The WebSphere Commerce Web 2.0 starter stores use Rich Internet Application (RIA) technologies such as Ajax (Asynchronous JavaScript and XML) and Dojo widgets. With these technologies certain customer interactions with store page content do not result in a full page refresh. IBM Digital Analytics, formerly known as Coremetrics Analytics provides a framework to track these intrapage interactions, in addition to interactions that result in a full-page refresh. This framework ensures that IBM Digital Analytics collects accurate analytics data about how customers are using your Web 2.0 store.
        List of analytics tags in starter store pages
        The Aurora starter store is already tagged with the full set of WebSphere Commerce analytics tags so that you do not have to add the tags yourself. By understanding which pages include tags by default, you can plan the implementation of additional tagging more effectively.
        Customer interactions that trigger IBM Digital Analytics events in Web 2.0 starter stores
        In Web 2.0 starter stores, customers can interact with intrapage content that does not result in a full page refresh. For example, a customer can drag products into their mini shopping cart, or their wish list, or use the Product Fast Finder to narrow down search results. For these intrapage interactions, WebSphere Commerce starter store pages generate events to provide analytics data to IBM Digital Analytics, formerly known as Coremetrics Analytics.
        IBM Digital Analytics events
        The event listener for IBM Digital Analytics, formerly known as Coremetrics Analytics is a JavaScript object that is incorporated into the store JSP file. The IBM Digital Analytics event listener detects IBM Digital Analytics events and calls the appropriate IBM Digital Analytics tag functions. The tag functions forward the analytics data to IBM Digital Analytics.
        Customizing IBM Digital Analytics events for Web 2.0 starter stores
        You can customize events for IBM Digital Analytics, formerly known as Coremetrics Analytics for Web 2.0 starter stores in three different ways.
        Sending additional data to IBM Digital Analytics for a IBM Digital Analytics event
        Each of the predefined events for IBM Digital Analytics, formerly known as Coremetrics Analytics supports a set of parameters to provide the analytics data that IBM Digital Analytics requires. You can add custom parameters to the JSON object if required. Any custom parameters are appended to the end of the IBM Digital Analytics data tag.
        Customizing the IBM Digital Analytics event listener
        You can use the Dojo object-oriented programming infrastructure to add custom business logic to the existing event listeners for IBM Digital Analytics, formerly known as Coremetrics Analytics. If you want to continue to use IBM Digital Analytics as an analytics provider, but implement and listen for a new type of event, you can create a Dojo object that extends from wc.analytics.CoremetricsEventListener.
        Collecting analytics data about intrapage interactions
        If you use an analytics vendor other than IBM Digital Analytics, formerly known as Coremetrics Analytics, you can customize the framework that tracks intrapage interactions in starter stores to work with the alternative analytics vendor.
      - IBM Digital Analytics reports for WebSphere Commerce
        IBM Digital Analytics, formerly known as Coremetrics Analytics offers a set of five analytics reports designed specifically for WebSphere Commerce. The reports display marketing metrics that are gathered from your site by the WebSphere Commerce analytics tags. These reports are available to WebSphere Commerce sites that are integrated with IBM Digital Analytics. You can view the reports in the IBM Digital Analytics application in an intuitive, visual format, along with other IBM Digital Analytics reports.
      - IBM Digital Analytics based customer segments
        With the push of a button, marketing managers can export any profile segments that are defined in IBM Digital Analytics, formerly known as Coremetrics Analytics as WebSphere Commerce customer segments. These customer segments are viewable in Management Center. Marketing managers can use these IBM Digital Analytics based customer segments as targets for marketing activities and promotions, just as they would use customer segments that are created in WebSphere Commerce.
      - Configuring default values for an analytics provider
        You can configure default values for an analytics provider configuration to apply the default values to all stores that are associated with the analytics provider. By setting site-level default values, you can quickly configure multiple stores to use the same analytics provider settings. You can also override the default values for an individual store.
      - Using a reload file to test the analytics integration configuration
        In your development environment, you can create and use a reload file to quickly test adjustments to the configuration between WebSphere Commerce and an analytics provider. When this file is in same directory as your biConfig.xml configuration file, your system can locate the file and begin reloading the biConfig.xml file to apply any changes to your analytics configuration. This reloading behavior can help you test changes and complete your analytics configuration quicker.
    - Integrating a store with an external analytics system (other than IBM Digital Analytics)
      To meet your analytics requirements, you can integrate a WebSphere Commerce store with any web-based analytics system that uses a JavaScript based tagging mechanism. For this purpose, WebSphere Commerce provides an extensible JSP-based tag library framework for analytics.
    - Integrating a store with multiple analytics providers
      WebSphere Commerce provides you with the option to use multiple analytics providers for one store, allowing for greater data collection and accuracy of shopper activity. As a result, you can compare and analyze multiple sets of data from different analytics providers.
  - IBM Product Recommendations and WebSphere Commerce
    IBM Product Recommendations is an IBM Digital Analytics solution that you can subscribe to that automatically generates personalized product recommendations on the storefront. The recommendations are based on the browsing, shopping, and purchasing behavior of individual customers. If your site is integrated with IBM Digital Analytics, you can display recommendations from IBM Product Recommendations on your store pages.
  - IBM Marketing Center integration
    You can integrate Management Center with IBM Marketing Center, a cloud-based, all-in-one solution that combines customer analytics with real-time marketing. To integrate with IBM Marketing Center, you must configure the WebSphere Commerce biConfig.xml file to enable the integration. You can also configure single-sign on between Management Center and IBM Marketing Center.
  - IBM Digital Data Exchange integration
    To simplify the process of collecting and sending customer shopping behavior data to analytics providers, integrate WebSphere Commerce with IBM Digital Data Exchange (DDX). IBM Digital Data Exchange (DDX) is offered as part of the IBM Digital Analytics solution.
  - Administering IBM Enterprise Marketing Management
    If your site is integrated with IBM Enterprise Marketing Management applications, such IBM Digital Analytics, IBM Product Recommendations, or IBM Marketing Center, you can administer the application features that your site uses. For example, you can administer IBM Digital Analytics based customer segments and import recommendations for IBM Product Recommendations.
  - IBM Dynamic Pricing
    Dynamic Pricing 16.4 is a cloud-based pricing system that analyzes real-time market data to provide suggestions on how merchandisers can react to competitor pricing and shifts in market conditions. Data can be fed to Dynamic Pricing from multiple sources, including WebSphere Commerce. You can configure WebSphere Commerce to export pricing data to Dynamic Pricing for pricing analysis and adjustment. The adjusted pricing data can then be imported from Dynamic Pricing to WebSphere Commerce, so the prices can be propagated to your live store front.
  - Universal Behavior Exchange (UBX) integration
    You can integrate Universal Behavior Exchange (UBX) with WebSphere Commerce so that you can import and export WebSphere Commerce customer segments as UBX audiences between third-party applications.
  - Watson Content Hub integration
    You can integrate Watson Content Hub with WebSphere Commerce, so that you can manage content in Watson Content Hub and then use the content in the Management Center Catalogs tool.
  - Integrating IBM WebSphere ILOG JRules BRMS with WebSphere Commerce for pricing
    IBM WebSphere ILOG JRules BRMS is a business rule management system that allows developers to easily build and deploy rule-based applications that automate fine-grained, variable decisions used by business systems. You can use WebSphere ILOG JRules to build pricing rulesets, and then reference those rulesets from WebSphere Commerce price rules you create in Management Center.
- Administering
- Tutorials
  WebSphere Commerce provides many tutorials to help you customize and understand your WebSphere Commerce instance and stores.
- Samples
- Developing
  The topics in the Developing section describe tasks performed by an application developer.
- Compliance
  The following section describes how you can leverage WebSphere Commerce features and functionality to help your site be compliant with different privacy and security standards.
- Securing
  These topics describe the security features of WebSphere Commerce and how to configure these features.
- Performance
- Troubleshooting

Sending additional data to IBM Digital Analytics for a IBM Digital Analytics event

Each of the predefined events for IBM Digital Analytics, formerly known as Coremetrics Analytics supports a set of parameters to provide the analytics data that IBM Digital Analytics requires. You can add custom parameters to the JSON object if required. Any custom parameters are appended to the end of the IBM Digital Analytics data tag.

Example

Consider a IBM Digital Analytics page view event with the following JSON object:


  { pagename: "Coffee Makers",
     referralURL: "http://www.google.ca",
     category: "Catalog" }

Because only the pagename and category parameters are known to the IBM Digital Analytics event listener, the following IBM Digital Analytics data tag is generated (the null values represent the known, but unspecified search parameters):


  cmCreatePageviewTag("Coffee Makers", "Catalog", null, 
     null, "http://www.google.ca")

Each IBM Digital Analytics event corresponds to a view, and each view corresponds to a view JSP file in the WC_eardir/Stores.war/ directory.


IBM Digital Analytics event	View	JSP
IBM Digital Analytics page view event	AnalyticsPageView	AnalyticsPageView.jsp
IBM Digital Analytics product view event	AnalyticsProductView	AnalyticsProductView.jsp
IBM Digital Analytics cart view event	AnalyticsShopcartView	AnalyticsShopcartView.jsp
IBM Digital Analytics registration view event	AnalyticsRegistrationView	AnalyticsRegistrationView.jsp
IBM Digital Analytics element event	AnalyticsElementView	AnalyticsElementView.jsp

Each view generates the analytics data in JSON format for the corresponding IBM Digital Analytics event. The JSP file that creates the JSON object is made up of two parts:

The view JSP file, which generates the core data that IBM Digital Analytics requires.
The extension view JSP file fragment, which generates additional custom data.

For example, the AnalyticsElementView.jsp file includes the AnalyticsElementViewExtension.jspf file in the WC_eardir/Stores.war/AuroraESite directory. To customize the view JSP file, update the extension file.