SolarisLinuxWindowsAIXFor IBM i OS operating systemIntroduced in Feature Pack 2

Disabling content versioning in Management Center

If you no longer want to manage versions of your objects, you can disable the content versioning feature by running the disablement script.

Before you begin

  • WebSphere Commerce DeveloperEnsure that the test server is stopped and that Rational Application Developer is not running.
  • SolarisLinuxAIXEnsure 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.

Procedure

  1. Complete one of the following tasks:
    • SolarisLinuxAIXLog on as a WebSphere Commerce non-root user (for example, wasuser).
    • For IBM i OS operating systemLog on with a user profile that has *SECOFR authority.
    • WindowsLog on with a user ID that is a member of the Windows Administration group.
  2. Navigate to the following directory:
    • WC_installdir/bin
    • WebSphere Commerce DeveloperWCDE_installdir\bin
  3. Run the disablement script:
    Running the disablement script disables the content versioning feature.
    • Windows
      config_ant.bat -buildfile WC_installdir/components/common/xml/disableFeature.xml 
      -DinstanceName=instance_name -DfeatureName=content-version -DdbUserPassword=db_password
      Feature Pack 5 or later[-Dscchost=HostForScheduledJobs]
      WebSphere Commerce Version 7.0.0.9 or laterFeature Pack 8[-DpasswordFile=passwordFile]
    • SolarisLinuxAIX
      ./config_ant.sh -buildfile WC_installdir/components/common/xml/disableFeature.xml
      -DinstanceName=instance_name -DfeatureName=content-version -DdbUserPassword=db_password
      Feature Pack 5 or later[-Dscchost=HostForScheduledJobs]
      WebSphere Commerce Version 7.0.0.9 or laterFeature Pack 8[-DpasswordFile=passwordFile]
    • WebSphere Commerce Developer
      disableFeature.bat -DfeatureName=content-version
    Where:
    instanceName
    The name of the WebSphere Commerce instance with which you are working (for example, demo).
    Feature Pack 5 or laterscchost
    Feature Pack 5 or laterThe 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.

    WebSphere Commerce Version 7.0.0.9 or laterFeature Pack 8passwordFile
    WebSphere Commerce Version 7.0.0.9 or laterFeature Pack 8Optional: 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.
    • instance_name is the name of the WebSphere Commerce instance.
    • Feature Pack 5 or laterHostForScheduledJobs is the host name. Use this if your organization chooses to schedule jobs to run only on a specific host.
    Note: During the execution of the config_ant command, the following message may be seen:
    
    Warning: Could not find file 
    WC_profiledir/properties/soap.client.props.yourOriginalFile to copy
    
    This error can be safely ignored.
  4. Verify the content versioning feature has been disabled.
    • SolarisLinuxWindowsAIXIf 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/disablecontent-version_timestamp.log.
    • WebSphere Commerce DeveloperYou can verify if the feature was successfully disabled by examining WCDE_installdir\logs\disableFeature.log. Near the bottom of the log, it will clearly state whether the build fails or is successful. Note that there might occasionally be exceptions displayed after the BUILD SUCCESSFUL message. You can safely ignore these exceptions as long as it says the build is successful.
    • WebSphere Commerce DeveloperYou can also examine WCDE_installdir\logs\disablecontent-version_timestamp.log.

Results

After you disable the content versioning feature, the database that contains version-specific data is not automatically deleted along with the table aliases introduced into the WebSphere Commerce schema. If this feature will not be re-enabled for this instance, you can manually drop the table aliases and the version schema (by default, VCW_instance_name). However, the version schema and tables are not re-created when this feature is re-enabled. The SQL statements used for version database schema and all tables created during feature enablement are contained in the SQL log file:
  • WC_installdir/instances/instance_name/logs/Create_version_db_<instance_name>.sql.log
  • WebSphere Commerce DeveloperWCDE_installdir\logs\Create_version_db_demo.sql.log