Disable WebSphere Commerce services

Disabling WebSphere Commerce services is performed by using an ANT target.

Do not disable the WebSphere Commerce services feature if you have configured the WebSphere Commerce with WebSphere Portal feature. To disable WebSphere Commerce services:

1. AIX|Linux|Solaris|I5/OS|Windows:

   For the WebSphere Commerce Server:

   1. If WebSphere Commerce is managed by WAS Deployment Manager (dmgr), start the deployment manager and all node agents. If WebSphere Commerce is not managed by WAS Deployment Manager (dmgr), start your WebSphere Commerce server.

   2. In the WC_installdir/bin directory, run this command:

      

      config_ant.bat -buildfile 
      WC_installdir/components/common/xml/disableFeature.xml 
      -DinstanceName=
      instance -DfeatureName=component-services
      -DdbUserPassword=
      db_password
      

      AIX|Linux|

      ./config_ant.sh -buildfile 
      WC_installdir/components/common/xml/disableFeature.xml
      -DinstanceName=
      instance 
      -DfeatureName=component-services -DdbUserPassword=
      db_password
      

      

      ./config_ant.sh -buildfile 
      WC_installdir/components/common/xml/disableFeature.xml
      -DinstanceName=
      instance 
      -DfeatureName=component-services -DdbUserPassword=
      db_password
      

      If the script runs successfully, you will see a BUILD SUCCESSFUL message in the command window where you ran the script. Otherwise, you will see a BUILD FAILED message.

2. For WebSphere Commerce Developer:

   1. Stop the Rational Application Developer and WebSphere Application Server servers.

   2. In the WCDE_installdir/bin directory, run this command:

      disableFeature.bat -DfeatureName=component-services
      

      If the script runs successfully, you will see a BUILD SUCCESSFUL message in the command window where you ran the script. Otherwise, you will see a BUILD FAILED message.

   3. Start WebSphere Commerce Developer.

   4. Start the WebSphere Commerce Test Server.

   5. Right-click the test server in the Servers view and select Publish.

   6. Wait for the application to finish publishing to complete and to restart.

   7. Verify that the application starts successfully.

   8. You can verify if the feature was successfully disabled by examining WCDE_installdir /logs/disableFeature.log. Near the bottom of the log, it clearly states whether the build failed or passed. If the build passed, then the feature was disabled successfully. Exceptions might occasionally be displayed after the BUILD SUCCESSFUL message. You can safely ignore these exceptions as long as it says the build is successful.

Related concepts

WebSphere Commerce services

Related tasks

Enabling WebSphere Commerce services