Disabling the Management Center

If you no longer want to use Management Center to manage your catalogs, promotions, and marketing, you can disable the feature. Note that if you disable Management Center, some objects that you created or updated using Management Center might not work properly in WebSphere Commerce Accelerator.

The Management Center feature is a prerequisite for the Store enhancement and Content versioning features. You cannot disable Management Center if these features are enabled. First, disable each of these features, then disable the Management Center feature.

Before you begin

Before you disable the Management Center, complete the following prerequisites:

Ensure that your administrative server is started. For example:
- If WebSphere Commerce is not managed by WebSphere Application Server Deployment Manager (dmgr), start the WebSphere Application Server server1.
- 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.
Ensure your test server is stopped and WebSphere Commerce Developer is closed.

Procedure

Ensure that you are logged on as a WebSphere Commerce non-root user.
Ensure you log on with a user profile that has *SECOFR authority.
Navigate to the following directory:
- WC_installdir/bin
- WCDE_installdir\bin
Run the script to disable the Management Center:
- ```
config_ant.bat -buildfile WC_installdir/components/common/xml/disableFeature.xml 
-DinstanceName=instance_name -DfeatureName=management-center -DdbUserPassword=db_password
[-DpasswordFile=passwordFile]
```
  [-Dscchost= HostForScheduledJobs]
- ```
./config_ant.sh -buildfile WC_installdir/components/common/xml/disableFeature.xml 
-DinstanceName=instance_name -DfeatureName=management-center -DdbUserPassword=db_password 
[-Dscchost= HostForScheduledJobs]
[-DpasswordFile=passwordFile]
```
- disableFeature.bat -DfeatureName=management-center
Where:

instanceName

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

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.

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.
If the script runs successfully in the runtime environment, you see a BUILD SUCCESSFUL message in the command window where you ran the script. Otherwise, you will see a BUILD FAILED message. Refer to the following log file:
- WC_installdir/instances/instance_name/logs/disablemanagement-center_timestamp.log
If the script runs successfully in the development toolkit, you will see a disableFeature.bat completed message in the command window where you ran the script. Otherwise, you will see a disableFeature.bat FAILED message. Refer to the following log file:
- WCDE_installdir\logs\disableFeature.log
Republish the application:
1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
2. Start the WebSphere Commerce Test Server.
3. Right-click the test server in the Servers view and select Publish.
4. Wait for the application to finish publishing and to restart.