Enabling Manual sequencing and featured image features for Commerce Insights
To manually change either the sequence of your products or the featured image in Commerce Insights, you must take steps to enable these options before you can use them.
For more information about Manual product sequencing see, Changing the product sequencing with Manual sequencing. For more information about featured images, see Changing a featured image during product sequencing.
Before you begin
- For development environments that are using Db2 or Oracle databases, you
must create a staging trigger before you do this procedure. For Db2 databases, use the following SQL files:
- WCDE_installdir\schema\db2\wcs.stage.sequence.sql
- WCDE_installdir\schema\db2\wcs.stage.trigger.sql
db2 connect to db_name user db_user using db_password db2 -tvf WCDE_installdir\schema\db2\wcs.stage.sequence.sql db2 -td# -vf WCDE_installdir\schema\db2\wcs.stage.trigger.sql
For Oracle databases, use the following SQL files:- WCDE_installdir\schema\oracle\wcs.stage.sequence.sql
- WCDE_installdir\schema\oracle\wcs.stage.trigger.sql
About this task
Procedure
-
In your WebSphere Commerce development environment, configure the
EnableProductDisplayConfiguration search property in your custom catalog
component configuration file (wc-component.xml) on the Search EAR.
-
Update the Search index schema on your runtime environment.
- Optional:
Enable the feature in the Features.xml file.
Note: This step is necessary only if you previously disabled the enhancement to enable product sequencing and featured image options. If you have not disabled this enhancement, continue with Step 4.
-
Restart the search server for the changes to take effect.
For more information about restarting the search server, see Starting and stopping WebSphere Commerce Search.
What to do next
When the product display configuration for product sequencing and featured images is enabled, increase the Solr JVM maximum heap space by 15 MB category. For more information about increasing the Solr JVM maximum heap, see WebSphere Commerce Search performance tuning.