Introduced in Feature Pack 1

Disabling WebSphere Commerce foundation

You can disable WebSphere Commerce foundation by running the disablement script.

About this task

  • Introduced in Feature Pack 1When foundation is enabled, component-specific rows are extracted from the existing CMDREG table and saved to a file. They are extracted during enablement, immediately before updates are applied to the CMDREG table. When foundation is disabled, the data is restored from that backup file so that the table is restored to its pre-enablement state.
    In some cases, there may be multiple backup files. For example, this can occur in the following circumstances:
    • if you have switched databases
    • If you have enabled foundation multiple times
    • If you have enabled multiple versions of the foundation feature
    When there are multiple backup files, the disablement process uses the latest backup file to do the restore. If this happens, you might find that the proper data is not contained in the latest backup. You can examine the other backup files to locate and manually restore the data required.


  • For IBM i OS operating systemSolarisLinuxAIXWindowsIn the runtime environment:
    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:
      • Windows
        config_ant.bat -buildfile WC_installdir/components/common/xml/disableFeature.xml 
        -DinstanceName=instance_name -DfeatureName=foundation -DdbUserPassword=db_password
        Feature Pack 5[-Dscchost=HostForScheduledJobs]
        WebSphere Commerce Version or laterFeature Pack 8[-DpasswordFile=passwordFile]
      • For IBM i OS operating systemSolarisLinuxAIX (Ensure that you are logged on as the WebSphere Commerce non-root user)
        ./ -buildfile WC_installdir/components/common/xml/disableFeature.xml
        -DinstanceName=instance_name -DfeatureName=foundation -DdbUserPassword=db_password
        Feature Pack 5[-Dscchost=HostForScheduledJobs]
        WebSphere Commerce Version or laterFeature Pack 8[-DpasswordFile=passwordFile]
      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 or laterFeature Pack 8passwordFile
      WebSphere Commerce Version 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.

      Wait for the message BUILD SUCCESSFUL to be displayed.

      Note: The config_ant command might generate the following message:
      Warning: Could not find file WC_profiledir/properties/soap.client.props.yourOriginalFile to copy
      This error can be safely ignored.
    3. Verify that the feature was disabled successfully.
      See the following log file:
      • WC_installdir/instances/instance_name/logs/disablefoundation_timestamp.log
    4. Optional: Feature Pack 7 or later You can clean up and remove the WebSphere Application Server profile and WebSphere Application Server server that WebSphere Commerce foundation feature enablement created. You should not complete the following steps if you have other applications using that profile.

      If you choose to remove the profile, the following steps will remove the server (solrServer), any other servers that might exist in the profile, related WebSphere Application Server configuration information, and all of the applications installed on those servers:

      1. Ensure that all of the WebSphere Application Server servers that belong to the profile are stopped. For more information, see Starting and stopping quick reference.
      2. Use the tools provided by WebSphere Application Server to delete the WebSphere Application Server profile that WebSphere Commerce created. The profile name is instance_name_solr.
        To remove your WebSphere Application Server profile, see one of the following topics:
      3. Remove the WebSphere Application Server profile service from the Services panel. Run the following commands from a command prompt:
        cd WAS_installdir/bin
        WASService.exe -remove WC_instance_name_solr
      4. Optional: Delete or rename the WebSphere Application Server profile directory from your file system. You must perform this step if you plan to enable the foundation feature again.
        The directory to remove or rename is:
        • WAS_installdir\profiles\instance_name_solr
  • WebSphere Commerce DeveloperIn a WebSphere Commerce Developer environment:
    1. Stop the Rational Application Developer and WebSphere Application Server servers.
    2. In the WCDE_installdir/bin directory, run this command:
      disableFeature.bat -DfeatureName=foundation
    3. Verify that the feature was disabled successfully.
      See the following log files:
      • WCDE_installdir/logs/disablefoundation_timestamp.log
      • WCDE_installdir/logs/disableFeature.log
      Near the bottom of the disableFeature.log, it will clearly state whether the build failed or passed. If the build passed, then the feature was disabled successfully. There can occasionally be exceptions that are displayed after the BUILD SUCCESSFUL message. You can safely ignore these exceptions if it says that the build is successful. If the build fails, for more information, see Troubleshooting: WebSphere Commerce configuration issues
    4. Republish the application:
      1. Open WebSphere Commerce Developer and switch to the Enterprise Explorer view.
      2. Right-click LOBTools and select one of the following options:
        • Feature Pack 4Feature Pack 2Feature Pack 3Feature Pack 1OpenLaszlo Migration > Compare Customizations
        • Feature Pack 5 or laterOpenLaszlo Migration > Launch Migration Tool
      3. Rebuild any projects that are required to be rebuilt in the workspace. For example:

        Rebuild LOBTools. Select LOBTools > Build OpenLazlo Project

      4. Start the WebSphere Commerce Test Server. Some errors are displayed in the console, these errors can be safely ignored.
      5. In the Servers view, right-click the test server then click Publish.

        Wait for the application to finish publishing and to restart. Ensure that no errors are displayed.

    5. Feature Pack 7 or later Remove the search application from the test server:
      1. In the Servers view, right click the test server and select Add and Remove.
      2. In the Add and Remove window, select Search and click Remove.
      3. Click Finish.