Fraska Portal

Exploring the WebSphere Commerce world

Francesco Schettini

Francesco Schettini

Freelance e-Commerce Solution Architect focused on web development projects using technologies like WebSphere, SOLR, JEE and Eclipse RCP.

contacts:
blog: fschettini.com
linkedIn: es.linkedin.com/in/fschettini

WebSphere Commerce, Recommend products on search landing page

This article is focused on explain how to implement a personalized recommendation based on search keyword using the E-marketing Spot Title provided with FEP6.

In particular, the use case is the following:

  • recommend the products "Widescreen LCD monitor" and "Office chair" 
  • with an image and the text "Don't forget the importance of the ergonomics! Improve your workspace with our ergonomics products"
  • when the customer search the keyword "Laptop"

The result is the following:

 WebSphere Commerce Marketing e-spot title search landing page

Let's review the steps to get the above requirement ...

Posted by on in Marketing

The search rules are specific kind of marketing dialog activities where the scope is to change the search's results in order to focus the customer attention on desired products.

In few words the search rules allow modify the order of the results according to:

  • the keywords or phrase used by the customer;
  • some customer demographic characteristic.

They are pretty easy to understand and define; the Management Center Marketing Tool provides the Search Rules feature allows to define one or more rules.

Basically, we can define a personalization system for our search engine

Follow a use case explains how to define these kind of personalizations.

In the Management Center Catalog Tool you can find the Search Term Association Tool; it allows business users to influence the results- deriving from customer search requests- changing the meaning of the keywords used in the search queries.

In particular, Search Term Association Tool allows to set up Synonyms associations (#1 Synonyms) and Word Replacements (#2 Replacements).

In addition, it allows to use specific landing page instead of the classic results page (#3 Landing Page).

Further reporting features have been added to the Search Term Association Tool: Top Search Hits and Top Search Misses.

WebSphere Commerce Search Term Association Tool

 

In this post we will have a look to the Synonyms feature.

The upgrade to FEP6 brings some odd side effect on SOLR search indexes (tested with DB2).

In particular, the pre-process task is impacted; in fact, once the system is upgraded to the last Feature Pack the pre-process throwed the following exception:

SEVERE: Exception message: CWFDIH0002: An SQL exception was caught. The following error occurred: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=LASTUPDATE, DRIVER=4.12.55., stack trace: com.ibm.commerce.foundation.dataimport.exception.DataImportSystemException: CWFDIH0002: An SQL exception was caught. The following error occurred: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=LASTUPDATE, DRIVER=4.12.55.
    at com.ibm.commerce.foundation.dataimport.util.DataImportDatabaseHelper.setIndexingActionJ2SE(DataImportDatabaseHelper.java:258)
    at com.ibm.commerce.foundation.dataimport.preprocess.DataImportPreProcessorMain.main(DataImportPreProcessorMain.java:280)
Caused by: com.ibm.db2.jcc.am.SqlSyntaxErrorException: DB2 SQL Error: SQLCODE=-206, SQLSTATE=42703, SQLERRMC=LASTUPDATE, DRIVER=4.12.55
    at com.ibm.db2.jcc.am.hd.a(hd.java:676)
    at com.ibm.db2.jcc.am.hd.a(hd.java:60)
    at com.ibm.db2.jcc.am.hd.a(hd.java:127)
    at com.ibm.db2.jcc.am.mn.c(mn.java:2621)
    at com.ibm.db2.jcc.am.mn.d(mn.java:2609)
    at com.ibm.db2.jcc.am.mn.a(mn.java:2085)
    at com.ibm.db2.jcc.am.nn.a(nn.java:7054)
    at com.ibm.db2.jcc.t4.cb.g(cb.java:141)
    at com.ibm.db2.jcc.t4.cb.a(cb.java:41)
    at com.ibm.db2.jcc.t4.q.a(q.java:32)
    at com.ibm.db2.jcc.t4.rb.i(rb.java:135)
    at com.ibm.db2.jcc.am.mn.ib(mn.java:2055)
    at com.ibm.db2.jcc.am.nn.rc(nn.java:3219)
    at com.ibm.db2.jcc.am.nn.b(nn.java:4002)
    at com.ibm.db2.jcc.am.nn.fc(nn.java:769)
    at com.ibm.db2.jcc.am.nn.executeUpdate(nn.java:748)
    at com.ibm.commerce.foundation.dataimport.util.DataImportDatabaseHelper.setIndexingActionJ2SE(DataImportDatabaseHelper.java:251)
    ... 1 more

Installing Feature Pack 6 on my development environment (WCS 7 Developer Enterprise on Windows)- following IC instructions- I got the following issue with Installation Manager:

Specify a repository for package IBM WebSphere Commerce Developer Feature Pack 4.0.0.0.

WebSphere Commerce Feature Pack

Above error message seems to be a bit misleading since I'm installing FEP6 and it's claiming about FEP4 and FEP4 is not a requirement.

So, let's try to investigate this issue.

Most Popular Post

WebSphere Commerce, the SOLR extension index
Administration
Rate this blog entry:
4
WebSphere Commerce, Data Load and SOLR Delta Index
Data Load
Rate this blog entry:
0
WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5

Latest Blogs

WebSphere Commerce, CommandLevelAuthorizationCache
Cache
Rate this blog entry:
0
WebSphere Commerce v8, toolkit exception, ClassNotFound db2
Administration
Rate this blog entry:
1
WebSphere Commerce, ATP migration
Store
Rate this blog entry:
0
WebSphere Commerce, the curious life of a front-end catalog request
Core
Rate this blog entry:
5
WebSphere Commerce, Performance analysis of few European stores
Performance
Rate this blog entry:
0