Enabling starter store enhancements

After you install the feature pack, you must enable the starter store enhancements feature to take advantage of the store features.

Deprecated featureTo use Madisons and Elite starter store enhancements, you must first enable the starter store enhancements feature.

After you enable the starter store enhancements feature, the following store archive (.sar) files are available for publishing:

Deprecated featureMayUJoy starter store (MayUJoy.sar)
Provides all the pages and features necessary for a functioning consumer direct online store for the Chinese market.
Deprecated featureBrazil starter store (Brazil.sar)
Provides all the pages and features necessary for a functioning consumer direct online store for the Brazilian market.
Deprecated featureMadisons starter store enhancements (MadisonsEnhancements.sar):
- Remote widgets store enhancements
- Digital wallet functionality
- Coshopping functionality
- Search integration
- Subscriptions and recurring orders
- Support for Management Center price lists and price rules
- Store pages that are tagged with the latest set of WebSphere Commerce analytics tags for IBM Digital Analytics, formerly known as Coremetrics Analytics
- e-Marketing Spots that support dynamic recommendations from IBM Product Recommendations, formerly known as Coremetrics Intelligent Offer
- Dynamic kit integration with Sterling Configurator
- Facebook integration
Deprecated featureElite starter store enhancements (EliteEnhancements.sar and EliteStorefrontAssetStore-FEP.sar):
- Search integration
- Store pages that are tagged with the latest set of WebSphere Commerce analytics tags for IBM Digital Analytics, formerly known as Coremetrics Analytics
- e-Marketing Spots that support dynamic recommendations from IBM Product Recommendations, formerly known as Coremetrics Intelligent Offer
- Dynamic kit integration with Sterling Configurator
Deprecated featureMadisons mobile enhancements (MadisonsMobileEnhancements.sar):
- Mobile starter stores for smartphone and tablet devices:
  - Mobile web starter stores
  - Mobile applications for Android and iOS
Aurora starter store (Aurora.sar):
- e-Marketing Spot and wish list feeds
- Click-to-edit function
- Advanced Search page
- Support for Dojo 1.8
- Hebrew language translation
- Tolerance for tablet devices
- Product-specific swatch images
Note: There are no enhancement store archive (.sar) files for the Aurora starter store. To obtain the latest Aurora store features for a specific feature pack, republish the Aurora.sar file after you install the feature pack and enable starter store enhancements.
Aurora mobile enhancements (AuroraMobile.sar):
- Mobile starter stores for smartphone and tablet devices:
  - Mobile web starter stores
  - Mobile applications that use IBM Worklight

Before you begin

Ensure that you are logged on as the WebSphere Commerce non-root user.
Ensure that you are logged on as a user that has *SECOFR authority.
Review the prerequisite steps in Enabling features.
Ensure that the test server is stopped and that Rational Application Developer is not running.
Ensure that your administrative server is started. For example:
- If WebSphere Commerce is managed by WebSphere Application Server Deployment Manager (dmgr), start the deployment manager and all node agents. Your cluster can also be started.
- If WebSphere Commerce is not managed by dmgr, start the WebSphere Application Server server1.
Determine how you are going to deploy the WebSphere Commerce search server:
In the standard configuration:
- Deploying the WebSphere Commerce search server locally in the standard configuration
- Deploying the WebSphere Commerce search server locally in the standard configuration
In the advanced configuration:
- Federating and clustering the WebSphere Commerce search server in the advanced configuration
- Deploying the WebSphere Commerce search server remotely in the advanced configuration

About this task

To support personalization in remote widgets and feeds, persistent sessions and personalization ID must be enabled. When you run the enablement script, the script checks the WebSphere Commerce configuration file for the current settings:

Current settings
	Enabled	Disabled
Persistent sessions	The script does not change the setting.	The script enables persistent sessions. The script sets the Cookie expiry (days) value to `-1`. As a result, sessions do not persist because the number of days is a negative number. To persist sessions, change the Cookie expiry (days) value to a positive number of days.
Personalization ID	The script does not change the setting.	The script enables personalization ID.

Procedure

Complete one of the following tasks:
- Log on as a WebSphere Commerce non-root user.
- Log on with a user ID that is a member of the Windows Administration group.
- Log on with a user profile that has *SECOFR authority.
Go to the following directory:
- WC_installdir/bin
- WCDE_installdir\bin
As the WebSphere Commerce non-root user, increase the file handle limit.
- Increase the file handle limit with the command: ulimit -n 8192
- As the root user grant USE authority to the non-root user. Switch to the non-root user and issue the command: ulimit -n 8192. You can also issue the command as the root user, then switch to the non-root user.
Run the enablement script. Running the starter store enhancements enablement script also enables the Management Center feature. That is, if the Management Center feature is disabled, it is enabled after you run the starter store enhancements enablement script.
- ```
config_ant.bat -buildfile WC_installdir/components/common/xml/enableFeature.xml 
-DinstanceName=instance_name -DfeatureName=store-enhancements -DdbUserPassword=db_password [-DdbaPassword=dba_password] 
[-DSolrWASAdminUser = solr_wasadminuser] [-DSolrWASAdminPassword = solr_wasadminpassword] 
[-Dscchost=HostForScheduledJobs] [search_server_config] 
[-DsearchPort=searchPort]
[-DpasswordFile=passwordFile]
```
- ```
./config_ant.sh -buildfile WC_installdir/components/common/xml/enableFeature.xml 
-DinstanceName=instance_name -DfeatureName=store-enhancements -DdbUserPassword=db_password 
[-DSolrWASAdminUser = solr_wasadminuser] [-DSolrWASAdminPassword = solr_wasadminpassword] 
[-Dscchost=HostForScheduledJobs] [search_server_config] 
[-DsearchPort=searchPort]
[-DpasswordFile=passwordFile]
```
- ```
./config_ant.sh -buildfile WC_installdir/components/common/xml/enableFeature.xml 
-DinstanceName=instance_name -DfeatureName=store-enhancements -DdbUserPassword=db_password [-DdbaPassword=dba_password] 
[-DSolrWASAdminUser = solr_wasadminuser] [-DSolrWASAdminPassword = solr_wasadminpassword] 
[-Dscchost=HostForScheduledJobs] [search_server_config] 
[-DsearchPort=searchPort]
[-DpasswordFile=passwordFile]
```
- ```
enableFeature.bat -DfeatureName=store-enhancements
```
Where:
instanceName

The name of the WebSphere Commerce instance with which you are working (for example, demo).

featureName

The name of the WebSphere Commerce feature to enable (for example, store-enhancements).

passwordFile

Optional: The full path to the password properties file. The properties file can contain encrypted passwords that might be required when running the utility. For example, you can store encrypted database administrator (dbaPassword) or database user (dbUserPassword) passwords. Passwords that are entered on the command line take precedence over the passwords that are in the password file. For more information, see Changing config_ant utility password properties file.

dbUserPassword

The password for the user who is connecting to the database.

dbaPassword

The dbaPassword is mandatory when you are enabling the feature on an Authoring server.

SolrWASAdminUser
The WebSphere Application Server administrator user ID for the Solr cell. This parameter is mandatory only if all three of the following conditions are met:

You enabled a previous version of Search from an earlier WebSphere Commerce feature pack

You enabled WebSphere Administration Server administrative security on the Search server

You are not specifying remoteSearchEngine=true
SolrWASAdminPassword
The WebSphere Application Server administrator password for the Solr cell. This parameter is mandatory only if all three of the following conditions are met:

You enabled a previous version of Search from an earlier WebSphere Commerce feature pack

You enabled WebSphere Administration Server administrative security on the Search server

You are not specifying remoteSearchEngine=true
scchost

The name of the host (server) on which the scheduled job runs. Use this parameter if your organization chooses to schedule jobs to run only on a specific host.
The WebSphere Commerce scheduler runs the RefreshRegistry command to ensure that the latest data from the CMDREG table is used by the WebSphere Commerce CommandRegistry. The job runs only if the CMDREG table was modified. It runs only once, shortly after enablement is completed. By default, this scheduled job run is set to run on any host. If you want to run on a specific host, use this parameter to define the specific host.
Note: The search server is deployed when the foundation feature is enabled.

remoteSearchEngine

Use this parameter with a value of true when you are deploying Solr search server on a remote machine.
Important: The remote web server is created under a different node than the local WebSphere Commerce server. If you are using the Deployment Manager (DMGR) to federate WebSphere Commerce, you must also federate the remote search server node that contains the web server definition.
The search_server_config options help automate updating the web server configuration for IBM HTTP Server. If you do not use this option, you must manually configure your web server after you run the enablement script, as described in the next step. When the search_server_config options are used, WebSphere Commerce search helps automate creating the web server configuration. This automation is achieved by passing in more configuration parameters when you run the enablement scripts.
Important: The automated web server configuration supports IBM HTTP Server (IHS) only. That is, it does not support or include steps for configuring non-IHS web servers such as IIS and SunOne. For other types of web servers, consult the documentation that is provided by the web server vendor to update the configuration.
This approach includes the following considerations:
- The WebSphere Commerce search web server's httpd.conf file is automatically created.
- You can set up a valid configuration where the WebSphere Commerce search and WebSphere Commerce web servers have separate configuration files. That is, you do not need to manually update the plugin-cfg.xml files.
- If preferred, you do not need to install another copy of IBM HTTP Server. The same installation can be shared with the WebSphere Commerce web server.
  A second IHS process is started to handle search HTTP requests that use the same IHS installation. A second process ensures that the configurations do not collide, while it eases configuration and maintenance.
Important: You can skip updating the web server configuration if you previously enabled the feature foundation and passed in the search_server_config parameters during the enablement. You can also skip the update if your Solr web server is already configured.
The following list shows the available parameters with brief explanations of each. Examples can be seen in the following task, along with more-detailed descriptions of each parameter and when it is needed and not needed:
- ../../com.ibm.commerce.component-services.doc/tasks/../../com.ibm.commerce.developer.doc/tasks/tsdsearchwebserver.html
The scripts validate the values that are provided for any mandatory parameters. If values for mandatory parameters are blank, the scripts do not proceed. The error message indicates which values must be specified. An example of such an error can be viewed in the following troubleshooting reference:
- Troubleshooting: Ant properties error occurs during feature enablement
Where search_server_config includes the following parameters that help automate updating the web server configuration for IBM HTTP Server:
searchPort

The WebSphere Application Server virtual host port number to listen on for the WebSphere Commerce search application.

The value must be a valid and available TCP port.

The default value is 3737.
If the script runs successfully in the runtime environment, a BUILD SUCCESSFUL message appears in the command window where you ran the script and in the WC_installdir/instances/instance_name/logs/enablestore-enhancements_timestamp.log file. For enablement details, see the WC_installdir/instances/instance_name/logs/enablestore-enhancements_timestamp.log file.
If the script runs successfully, the message enableFeature.bat completed is displayed in the command window. For enablement details, see the WCDE_installdir\logs\enableFeature.log file.
Configure the Web server for the Solr application
The following configuration options are available, depending on your web server and WebSphere Commerce Feature Pack version:
- WebSphere Commerce search deployment tasks include steps to manually update the web server configuration for IBM HTTP Server (IHS).
  This approach includes the following considerations:
  
  You created the WebSphere Commerce search web server httpd.conf file.
  
  A directive to listen on the search virtual host port is added.
  
  The web server plug-in is installed on the web server host.
- WebSphere Commerce search deployment tasks include steps to help automate updating the web server configuration when you use IBM HTTP Server (IHS). This automation is achieved by optionally passing in more configuration parameters when you are running the enablement scripts during the previous step. For more information, see the previous step.
- For configuring non-IHS web servers such as IIS and SunOne, consult the provided documentation to update the configuration.
Republish the application:
1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
  Note: The following warning message in the Problems view can be safely ignored:
```
The source path "/.apt_generated" cannot be resolved
```
2. Right click LOBTools and select OpenLaszlo Migration > Compare Customizations.
3. Rebuild any projects that need to be rebuilt in the workspace.
  For example:
  - Rebuild LOBTools. Right-click LOBTools, then select Build OpenLazlo Project
4. Start the WebSphere Commerce Test Server.
  Some errors are displayed in the console. These errors can be safely ignored.
5. In the Servers view, right-click the test server then click Publish.
6. Wait for the application to finish publishing and to restart. Ensure that no errors are displayed.
7. If you customized a previous version of Management Center, see Migrating Management Center to migrate those customizations to the latest Management Center version.

What to do next

If you completed this procedure as a part of migrating WebSphere Commerce search, then continue with the migration process:

Otherwise, review the following tasks:

If you are using the Madisons starter store, ensure that you publish the Madisons store archive after you install Feature Pack 1 or later. You might see a different store name for Madison starter store, depending on your version of the installed Feature Pack. If Feature Pack 1 is installed, the store name is Madisons.sar. If Feature Pack 2 or later is installed, the store name is Madisons-FEP.sar. When you install Fix Pack 1 or later, a new version of Madisons.sar is installed, containing the latest fixes and necessary extension points. The Brazil starter store, MayUJoy starter store, and Madisons starter store enhancements store archives do not function correctly with earlier versions of the Madisons starter store.I
If you are using the Aurora starter store, ensure that you republish the new Aurora.sar store archive or merge store JSP changes with your existing Aurora store. For more information about how to merge changes, see Enabling store-related interim fixes as a guideline.
You can choose to enable new Aurora starter store functions that are included in the Feature Pack. For more information, see
- Aurora starter store functions (Feature Packs 5 and 6)
- Aurora starter store functions (Feature Pack 7 and later)
If you are enabling starter store enhancements in the WebSphere Commerce development environment, the default configuration includes a Derby database with all base, non-feature pack, starter stores, including the Madisons starter store, pre-published. If you require a feature pack version of a starter store, publish the feature pack version by using a different store name. You can create a database without the pre-published stores or restore to a clean bootstrap Derby database. Then, you can publish the feature pack version of the starter store. Also, when you configure the WebSphere Commerce development environment you can select to a new bootstrap Derby database without the prepublished starter stores.
For more information about other features that you can enable, see First steps after enabling features.