Sample biConfig.xml file for IBM Digital Analytics: Feature Pack 3 and later implementations

The default sample biConfig.xml file that WebSphere Commerce provides is in the following directory:

• WC_installdir/components/store-enhancements/samples/Coremetrics/xml
• WCDE_installdir\components\store-enhancements\samples\Coremetrics\xml

Your updated biConfig.xml file must be deployed to the following directory so that IBM Digital Analytics can reference it:

• WC_eardir/xml/config/bi
• WCDE_installdir\workspace\WC\xml\config\bi

When you are updating the biConfig.xml file in your development environment, you can use a reload file to help you quickly test configuration changes. By using this reload file, you do not need to continually restart your server to apply configuration changes from the biConfig.xml file. For more information, see Using a reload file to test the analytics integration configuration.

For more information about configuring the settings for the biConfig.xml file for use with IBM Digital Analytics, see Configuring the store to communicate with IBM Digital Analytics(biConfig.xml).

<?xml version="1.0" encoding="UTF-8"?>

<!--
 =================================================================
  Licensed Materials - Property of IBM

  WebSphere Commerce

  (C) Copyright IBM Corp. 2010, 2013 All Rights Reserved.

  US Government Users Restricted Rights - Use, duplication or
  disclosure restricted by GSA ADP Schedule Contract with
  IBM Corp.
 =================================================================
-->
<BIConfiguration>
1  <ssoKey></ssoKey>
2  <biproviders>
3    <biprovider name="coremetrics">
      <options><attribute name="useDDX" value="false"/></options>
      <header>
        <![CDATA[<script type="text/JavaScript">
        <!--
        ]]>
      </header>
      <footer>
        <![CDATA[
        //-->
        </script>]]>
      </footer>
    </biprovider>
  </biproviders>
  
4  <stores>
5    <store storeId="10101" 
      biprovider="coremetrics" enabled="true" debug="true" 
      marketingCenterEnabled="true"
      useHostedCMHLibraries="true" useEmailForCustomerId="false" 
      segmentExportMode="append" >
      <useCookies>true</useCookies>
      <clientid>69999999</clientid>
      <url>https://welcome.coremetrics.com/analyticswebapp/analytics.jsp</url>
      <marketingCenterUrl>https://mc.coremetrics.com/mcwebapp/welcome.do</marketingCenterUrl>
      <includeShipAdjustInProductPrice>true</includeShipAdjustInProductPrice>
      <options><attribute name="useDDX" value="false"/></options>
      <output section="header">
        <![CDATA[
        <script type="text/javascript" src="//libs.coremetrics.com/eluminate.js"></script> 
        <script type="text/javascript"> 
        cmSetupNormalization("krypto-_-krypto");
        
        // send data to production system 
        //cmSetClientID("99999999",true,"data.coremetrics.com","thesite.com"); 
        
        // send data to test system 
        cmSetClientID("69999999",false,"testdata.coremetrics.com","thesite.com"); 
        </script> 				
        ]]>
      </output>
    </store>
  </stores>
</BIConfiguration>   

1 Identifies a secret key for single sign-on to your analytics provider for Management Center users. Single sign-on is enabled only for an integration between IBM Digital Analytics and Management Center.

2 Begins the analytics provider configuration section. Within this element, you can include multiple <biprovider> element. Each <biprovider> element, includes the configuration settings for an individual analytics provider.

Within the <biprovider> element, default values can be set for each configuration setting. These values apply to every store that is associated with the identified analytics provider. For more information, see Configuring default values for an analytics provider.

4 Begins the store level configuration section. Within this element, you can include multiple <store> elements. Each <store> element, can include the configuration settings for one or more stores.