Enabling WebSphere Commerce foundation
The WebSphere Commerce foundation feature adds new groups of services to the WebSphere Commerce Server.
The enablement script adds new services and updates the existing services that are required to support feature pack features.
Enabling WebSphere Commerce foundation enables WebSphere Commerce search by default. WebSphere Commerce search is a core runtime component in WebSphere Commerce, with many features tightly integrated with the search component. For more information about WebSphere Commerce search dependencies, see Integrating WebSphere Commerce with third-party search engines.
If you are using a self-signed certificate (dummy certificate) in the staging
or author environment, you might encounter SSL handshake exceptions. These might occur in the store
preview after you apply Fix Pack 9. The exceptions occur only if you apply Fix Pack 9 using one of
the following methods:
- You first applied Fix Pack 9, then created an instance, and then enabled foundation on Feature Pack 7 or earlier
- You first created an instance, then applied Fix Pack 9, and then enabled foundation on Feature Pack 8
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.
- Ensure that you apply the interim fix for APAR JR50445. You must apply this interim fix before feature enablement can successfully complete.
- 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 WebSphere Application Server Deployment manager (dmgr), start the WebSphere Application Server server1.
- Review the prerequisite steps in Enabling features.
- Ensure that the test server is stopped and that Rational Application Developer is not running.
- If you use a staging server, you must ensure that your production server and
staging server stay synchronized. To keep them in sync, you must perform the following steps before
you enable the feature on the staging server:
- Optional: It is recommended that you run the stagingprop utility:To ensure that stagingprop is run successfully:
- Check the stagingprop log file.
- Check the STAGLOG table in the staging database and confirm that no unprocessed records exist. An unprocessed STAGLOG record is a record in which the STGPROCESSED column has a value of 0.
- Stop all activities on the staging server. Any data changes on the staging server are not captured or propagated from this point until feature enablement is completed.
- Optional: It is recommended that you run the stagingprop utility:
- Determine how you are going to deploy the WebSphere Commerce search server:
Procedure
What to do next
- Migrating WebSphere Commerce search from Feature Pack 7 to Feature Pack 8
- Migrating WebSphere Commerce search from Feature Pack 2, 3, 4, 5, or 6 to Feature Pack 7 or later
- Migrating WebSphere Commerce search from Feature Pack 2, 3, 4, or 5 to Feature Pack 6