Disabling starter store enhancements

You can disable the starter store enhancements by running the disablement script.

Procedure

Disabling the starter store enhancements.
1. Start the server or cluster that manages your WebSphere Commerce instance, if it is not already started.
2. In the WC_installdir/bin directory, run this command:
  - ```
  config_ant.bat -buildfile WC_installdir/components/common/xml/disableFeature.xml 
  -DinstanceName=instance_name -DfeatureName=store-enhancements -DdbUserPassword=db_password 
  [-Dscchost= HostForScheduledJobs]
  [-DpasswordFile=passwordFile]
```
- Ensure that you are logged on as the WebSphere Commerce non-root user.
```
  ./config_ant.sh -buildfile WC_installdir/components/common/xml/disableFeature.xml
  -DinstanceName=instance_name -DfeatureName=store-enhancements -DdbUserPassword=db_password 
  [-Dscchost= HostForScheduledJobs]
  [-DpasswordFile=passwordFile]
```
- Ensure that you are logged on as a user with *SECOFR authority
```
  config_ant.sh -buildfile WC_installdir/components/common/xml/disableFeature.xml
  -DinstanceName=instance_name -DfeatureName=store-enhancements -DdbUserPassword=db_password
  [-Dscchost= HostForScheduledJobs]
  [-DpasswordFile=passwordFile]
```
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.
3. Wait for the message BUILD SUCCESSFUL.
  Note: During the execution of the config_ant command, the following message might be seen:
```
Warning: Could not find file 
WC_profiledir/properties/soap.client.props.yourOriginalFile
to copy
```
  This error can be safely ignored.
1. Stop the Rational Application Developer and WebSphere Application Server servers.
2. In the WCDE_installdir/bin directory, run this command:
```
disableFeature.bat -DfeatureName=store-enhancements
```
Verify that the store-enhancements feature is disabled.
1. 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 a BUILD FAILED message is displayed. See the following log file: WC_installdir/instances/instance_name/logs/disablestore-enhancements_timestamp.log
2. To verify that the feature was successfully disabled examine the WCDE_installdir /logs/disableFeature.log file. Near the bottom of the log, look for a BUILD SUCCESSFUL message. If the build passed, then the feature was disabled successfully. Occasionally, there are exceptions that are logged after the BUILD SUCCESSFUL message. You can safely ignore these exceptions.
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 restarting.