Upgrading smarttarget_conf.xml file
The smarttarget_conf.xml file has changed in SmartTarget 2014 SP1. Use the configuration_upgrade.jar to migrate the file and then manually configure the <TimeZoneOffset> element and <Analytics> section for Experiments.
Procedure
- Back up your
smarttarget_conf.xmlconfiguration file—for example, create a copy of the file calledsmarttarget_conf_old.xml. - Open a command prompt.
- Access the SmartTarget installation media.
- Access the
Migration\directory. - Run the
configuration_upgrade.jarusing the following command:
wherejava -jar configuration_upgrade.jar "/filepath/smarttarget_conf.xml"filepathspecifies the location to yoursmarttarget_conf.xmlfile.A
smarttarget_conf.xml.upgradedfile is created containing old settings migrated to a new file. - Open
smarttarget_conf.xml.upgradedin a text editor and check the migrated settings. - If you are upgrading from SmartTarget 2011 SP3, SP2, or SP1:
- In the
<IndexServer>element, change the<Location>setting as this has changed (SmartTarget deployment now makes use of the Fredhopper Deployment Agent):The following is an example of oldsmarttarget_conf.xmlsetting:<Location>c:/fredhopper/instance01/FAS/data/xml/incoming/batch/</Location>The following is an example of the newsmarttarget_conf.xmlsetting:<Location>c:/fredhopper/indexer/data/fas-xml-incremental/catalog01</Location> - In the
<Regions>element, add the names (case-sensitive) of your Page Regions. For example:<Regions> <Region>Header</Region> <Region>Footer</Region> <Region>Sidebar</Region> <Region>Inset 1</Region> <Region>Inset 2</Region> </Regions>Note: In previous versions of SmartTarget, you needed to add the ID values of the SmartTarget page regions to a custom field in the Business Manager.
- In the
- Set the
<TimeZoneOffset>element and in the<Analytics>section enter details of your Google Analytics account:<TimeZoneOffset>0</TimeZoneOffset> <!-- Analytics --> <Analytics implementationClass="com.tridion.smarttarget.analytics.google.GoogleAnalyticsManager" timeoutMilliseconds="5000" trackingRedirectUrl="/redirect/"> <ServiceAccountEmailAddress/> <PrivatekeyPath/> <AccountId/> <TrackingId/> <ViewId/> <CustomDimensions> <ExperimentId>dimension1</ExperimentId> <PublicationTargetId>dimension2</PublicationTargetId> <PublicationId>dimension3</PublicationId> <PageId>dimension4</PageId> <Region>dimension5</Region> <ComponentId>dimension6</ComponentId> <ComponentTemplateId>dimension7</ComponentTemplateId> <ChosenVariant>dimension8</ChosenVariant> </CustomDimensions> </Analytics>TheNote: For more information, see Setting up Analytics.<Analytics>element has the following properties:Property Description implementationClassThe class that implements the analytics provider. trackingRedirectUrlA relative URL to your Web site redirects folder, by default "/redirect/".timeoutMillisecondsThe time in milliseconds to wait to retrieve the Experiment from the analytics provider before timing out. The<Analytics>element has the following child elements:ServiceAccountEmailAddress- The email account created when you created a Project in the Google Console Developer.
PrivatekeyPath-
The path to the location of the P12 key generated when you created a Project in the Google Console Developer, for
C:/Google/MyProject RS-8235a2fedac7.p12. AccountId- The Account ID created when you set up Google Analytics.
TrackingId- The Tracking ID created when you set up Google Analytics.
ViewId- The View ID created when you set up Google Analytics.
CustomDimensions-
The custom dimensions created when you set up Google Analytics to bring Content Manager data into the platform:
Element Value ExperimentIddimension1PublicationTargetIddimension2PublicationIddimension3PageIddimension4Regiondimension5ComponentIddimension6ComponentTemplateIddimension7ChosenVariantdimension8
- Save your
smarttarget_conf.xml.upgradedfile assmarttarget_conf.xml. - In the
<SmartTarget><TimeZoneOffset>section of thesmarttarget_conf.xmlconfiguration file, enter the offset:<TimeZoneOffset>0</TimeZoneOffset>For example:<TimeZoneOffset>Description -7The Content Manager system is in a time zone 7 hours earlier than the Content Delivery system. -7:45The Content Manager system is in a time zone 7 hours and 45 minutes earlier than the Content Delivery system. +5The Content Manager system is in a time zone 5 hours later than the Content Delivery system. +5:30The Content Manager system is in a time zone 5 hours and 30 minutes later than the Content Delivery system. - Save
smarttarget_conf.xml. - Copy
smarttarget_conf.xmlto the following locations:Application using smarttarget_confFile path Content Delivery server %TRIDION_HOME%\config .NET Web application (Presentation Server) bin\config Java Web application (Presentation Server) WEB_INF/classes SmartTarget Deployment Web service bin\config Content Delivery Web service (for each Fredhopper system) bin\config or WEB_INF/classes