Samples > Starter stores > Starter store enhancements > IBM Gift Center for the Madisons starter store > Get started
Enable WebSphere Commerce foundation
The WebSphere Commerce foundation feature adds new groups of services to the WebSphere Commerce Server.
Before you begin
- Log on as the non-root user.
- Verify the 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 WebSphere Application Server Deployment Manager (dmgr), start the WebSphere Application Server server1.
- Verify the test server is stopped and that Rational Application Developer is not running.
Verify the following WebSphere Commerce Feature Packs are installed:
- WebSphere Commerce Feature Pack 1
The enablement script adds new services and updates existing services required to support the WebSphere Commerce Version 7 Feature Pack 1 features.
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:
- 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
- If you are using a staging server, run the stagingprop utility before proceeding with feature enablement.
After stagingprop, check the STAGLOG database table and ensure all the records are marked as processed. That is, STAGLOG.STGPROCESSED=1. You should backup the STAGLOG table (export the table), and then clean up the STAGLOG table (delete from STAGLOG).
- 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:
- config_ant.bat -buildfile WC_INSTALL/components/common/xml/enableFeature.xml -DinstanceName=instance -DfeatureName=foundation -DdbUserPassword=db_password [-DdbaPassword=dba_password]
- ./config_ant.sh -buildfile WC_INSTALL/components/common/xml/enableFeature.xml -DinstanceName=instance -DfeatureName=foundation -DdbUserPassword=db_password [-DdbaPassword=dba_password]
- enableFeature.bat -DfeatureName=foundation [-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 the WC_INSTALL/instances/instance/logs/enablefoundation_timestamp.log file. For enablement details refer to log file:
- WC_INSTALL/instances/instance/logs/enablefoundation_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.
- Verify that the application starts successfully.
Access the following URL:
http://hostname:8007/webapp/wcs/component/member/services/MemberServices
It should render a page with the following information:
{http://www.ibm.com/xmlns/prod/commerce/9/member}MemberServices Hi there, this is a Web service!
- If the machine where you are installing the feature will be using staging tools or acting as a staging server:
- Backup the following base staging SQL files:
- WC_INSTALLschema/db_type/wcs.stage.trigger.sql
- WC_INSTALLschema/db_type/wcs.droptrigger.sql
- Append the contents of WC_INSTALL/components/component-services/schema/fep1/db_type/wcs.stage.trigger.component_name.sql to the end of WC_INSTALL/schema/db_type/wcs.stage.trigger.sql, where db_type is either db2 or oracle.
- Append the contents of WC_INSTALL/components/component-services/schema/fep1/db_type/wcs.stage.trigger.component_name.drop.sql to the end of WC_INSTALL/schema/db_type/wcs.droptrigger.sql, where db_type is either db2 or oracle.
- Append the contents of WCDE_INSTALL/components/component-services/schema/fep1/db_type/wcs.stage.trigger.component_name.sql to the end of WCDE_INSTALL/schema/db_type/wcs.stage.trigger.sql, where db_type is either db2 or oracle.
- Append the contents of WCDE_INSTALL/components/component-services/schema/db_type/wcs.stage.trigger.component_name.drop.sql to the end of WCDE_INSTALL/schema/db_type/wcs.droptrigger.sql, where db_type is either db2 or oracle.
After enabling the feature, there should be STAGLOG records captured in the Staging server. This STAGLOG record should be ignored. Since the STAGLOG is cleaned, either mark all the new STAGLOG records as processed, or delete them.
Staging is not supported in WebSphere Commerce Developer.
This step only needs to be performed once, even if you enable and disable the feature multiple times.
- If you are using a staging server, run the stagingcopy utility.
If you encounter problems with the staging copy complete the following steps:
- Change STMTHEAP to the maximum value. For example:
db2 update database configuration for db_schema using stmtheap 240000
- Change APPLHEAPZ to 3000. For example:
db2 update database configuration for db_schema using applheapsz 3000
- Disconnect all users from DB2.
- Stop and restart DB2.
- Run the stagingcopy utility.
Next topic: IBM Gift Center for Madisons: Publishing the sample add-on store archive