Enabling the Management Center
The Management Center is enabled by default in WebSphere Commerce version 7. If you do not have a feature pack installed, you can disable the Management Center for a specific instance, but once disabled, it cannot be enabled again for that instance. If you disable the Management Center for a specific instance, you must re-create an instance to re-enable it.
Once you install a WebSphere Commerce Feature Pack, you must follow these steps to enable the Management Center feature for the Feature Pack you installed. The Management Center feature that is delivered in a Feature Pack can be successfully re-enabled if you disabled it.
Before you begin
- Review the minimum Hardware prerequisites for installing WebSphere Commerce.
- Ensure that your system meets all of the prerequisites for the feature pack.
- Review the prerequisite steps in Enabling features.
- 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. Optionally, 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.
- Ensure that the test server is stopped and that Rational Application Developer is not running.
- Back up your database:
- Backup overview.
- See the database vendor's user manual for information about backup and restore procedures.
- See the database vendor's user manual for information about backup and restore procedures.
- 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.
- Issue the following SQL statement and make
note of the number of the latest record in the STAGLOG table in the staging
database
SELECT MAX(STGRFNBR) FROM STAGLOG
- Optional: It is recommended that you run the stagingprop utility:
- Determine how you are going to deploy the WebSphere Commerce search
server:In the standard configuration:In the advanced configuration: