Install > Installing WebSphere Commerce feature packs > Enable features
Enable starter store enhancements
To use and develop in the MayUJoy and Brazil starter stores, and to use Madisons starter store enhancements, first enable the starter store enhancements feature.
- The MayUJoy starter store provides pages and features a consumer direct online store for the China market.
- The Brazil starter store provides pages and features necessary for a consumer direct online store for the Brazilian market.
- The Madisons starter store enhancements include remote widgets and digital wallet functionality.
Before you begin
- Install WebSphere Commerce Feature Pack 1
- Log on as the non-root user.
- Verify the test server is stopped and that Rational Application Developer is not running.
- Verify the administrative server is started. For example:
- If WebSphere Commerce is managed by WAS Deployment Manager (dmgr), start the deployment manager and all node agents. Your cluster can also be started.
- If WebSphere Commerce is not managed by WAS Deployment Manager (dmgr), start the WebSphere Application Server server1.
Personalization
To support personalization in remote widgets and feeds, enable...
When you run the enablement script, the script checks the WebSphere Commerce configuration file for the current settings:
- If persistent sessions are already enabled, the script does not change the settings. If persistent sessions are disabled, the script enables persistent sessions but sets the Cookie expiry (days) value to -1. As a result, sessions will not actually be persisted because the number of days is a negative number. You can change the Cookie expiry (days) value to a positive number of days at any time so that sessions are persisted.
- If personalization ID is already enabled, the script does not change this setting. If personalization ID is disabled, 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.
- Navigate to the following directory:
- WC_INSTALL/bin
- WCDE_INSTALL\bin
- Free enough disk space on the system to accommodate a backup of the WebSphere Commerce v5.6.1 or 6.0 database.
- As the WebSphere Commerce non-root user, increase the file handle limit...
ulimit -n 8192
Run the WCIM migration wizard or wcim_ant script in the same command window that you ran the ulimit command in. The ulimit setting is lost (and we will need to re-run this step) if you close this command window.
- 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 currently disabled, it is enabled after running the starter store enhancements enablement script.
- config_ant.bat -buildfile WC_INSTALL/components/common/xml/enableFeature.xml -DinstanceName=instance -DfeatureName=store-enhancements -DdbUserPassword=db_password [-DdbaPassword=dba_password]
- ./config_ant.sh -buildfile WC_INSTALL/components/common/xml/enableFeature.xml -DinstanceName=instance -DfeatureName=store-enhancements -DdbUserPassword=db_password [-DdbaPassword=dba_password]
- enableFeature.bat -DfeatureName=store-enhancements [-DdbaPassword=dba_password]
The dba_password is required only if you are enabling the feature on an Author server.
- 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...
WC_INSTALL/instances/instance/logs/enablestore-enhancements_timestamp.logFor enablement details refer to log file:
- WC_INSTALL/instances/instance/logs/enablestore-enhancements_timestamp.log
If the script runs successfully in the development toolkit, you see an enableFeature.bat completed message in the command window where you ran the script. For enablement details refer to log file:
- WCDE_INSTALL\logs\enableFeature.log
If the server is configured with an LDAP server, restart the WebSphere Commerce Server after verifying a successful enablement.
- Republish the application:
- Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
- Start the WebSphere Commerce Test Server. Some errors are displayed in the console, these errors can be safely ignored.
- Right-click the test server in the Servers view and select Publish.
- Wait for the application to finish publishing and to restart. Ensure that no errors are displayed.
- Publish the Madisons starter store.
Ensure that you publish the Madisons.sar store archive after installing WebSphere Commerce v7 Fix Pack 1 or later. When you install WebSphere Commerce v7 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.
What to do next
After running the enablement script, you can perform one of the following tasks:
- Publish the MayUJoy starter store
- Publish the Brazil starter store
- Publish the Madisons enhancements store archive
Related tasks
Disable starter store enhancements