Enabling features

After you install a WebSphere Commerce feature pack, you can enable any of the included features to enhance your WebSphere Commerce instance.

Before you begin

Each WebSphere Commerce feature pack contains features that you can enable.
In the runtime environment, to enable the features included in the WebSphere Commerce feature pack, you must have a WebSphere Commerce instance created.
In a staging environment, ensure that you run the stagingprop utility before you enable features.
In a staging environment, both the staging and production servers must satisfy the following condition:
- The WebSphere Commerce application and the WebSphere Commerce database are at the same feature pack level.
Back up your database. Refer to your database user manual for information on backup and restore procedures.
It is recommended that you use the latest DB2 fix pack available for your DB2 version.
There are issues that are related to database schema creation when you use DB2 V9.7 Fix Pack 5 or later. See: Database schema creation might fail on DB2 V9.7 Fix Pack 5 (or later) when you install or upgrade from a WebSphere Commerce version older than V7.0.0.6
Important: If you plan to use DB2 Version 9.7 database, you must change the development database type before you enable features.
If you have custom table spaces, you must ensure that the SQL files that rely on the table spaces are modified to reference the names of your custom table spaces.
Depending on the feature pack level you have installed, modify one or more of the following files:
- WC_installdir/components/foundation/schema/fep1/db2/wcs.schema.foundation.sql
- WC_installdir/components/foundation/schema/fep2/db2/wcs.schema.foundation.sql
- WC_installdir/components/foundation/schema/fep3/db2/wcs.schema.foundation.sql
- WC_installdir/components/foundation/schema/fep4/db2/wcs.schema.foundation.sql
- WC_installdir/components/location-services/schema/fep4/db2/wcs.schema.location-services.sql
- WC_installdir/components/foundation/schema/fep5/db2/wcs.schema.foundation.sql
- WC_installdir/components/foundation/schema/fep6/db2/wcs.schema.foundation.sql
- WC_installdir/components/foundation/schema/fep7/db2/wcs.schema.foundation.sql
- WC_installdir/components/foundation/schema/fep8/db2/wcs.schema.foundation.sql
In each applicable SQL file, you must change any table space references so that they point to your custom table spaces. Feature packs are cumulative, so if you are on a later feature pack, files for lower-level feature packs will already be present on your system and will need to be modified.
Ensure that you have all of your changes checked into software configuration management (SCM).
Disconnect SVN before feature enablement. It can be re-enabled after feature enablement is complete.
Ensure that Windows Indexing and Windows Search services are disabled. If these services are enabled they can prevent the clean-up of working directories, which can cause feature disablement to fail.
Install a WebSphere Commerce feature pack.

About this task

If you enable a high-level feature, lower-level features are enabled automatically. The following table shows the dependencies between the features.


Functional area	When you enable this feature...	These dependent features are automatically enabled
Location-based services	location-services	management-center foundation
Store enhancements Includes: Remote widgets Coshopping functionality Search integration Subscriptions and recurring orders Price rules and price lists IBM Product Recommendations, formerly known as Coremetrics Intelligent Offer Dynamic kit integration with Sterling Configurator Search engine optimization (SEO)	store-enhancements	management-center foundation
Content versioning	content-version	management-center foundation
Management Center	management-center	foundation
WebSphere Commerce foundation	foundation

Procedure

Enable one or more features:

Note: Any features that are enabled before you run the setdbtype command must be re-enabled.