Enabling WebSphere Commerce services

The WebSphere Commerce services feature adds four new groups of services to the WebSphere Commerce Server. To enable these services:

  1. Install the component-services feature that corresponds to the Feature Pack that you are using:

    • Feature Pack 2

    • Feature Pack 3

    • Feature Pack 3.0.1

  2. 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, start your WAS.

  3. To enable or disable features in WebSphere Commerce Developer which run on Cloudscape, the WebSphere Commerce Test Server must be stopped. The test server does not need to be stopped if WebSphere Commerce Developer is running on another database, such as DB2.

  4. Navigate to the following directory:

  5. Run the following script:

    • Windows:

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

    • AIX|Linux|Solaris:

      (Ensure that you are logged on as the WebSphere Commerce non-root user)

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

    • I5/OS|

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

    • enableFeature.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.

  6. Republish the application.

    1. Start Rational Application Developer.

    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.

  7. Verify that the application starts successfully.

    Access the following URL:

    http://localhost:8007/webapp/wcs/component/member/services/MemberServices

    It should render a page with the following information:

    {http://www.ibm.com/xmlns/prod/commerce/9/member}MemberServices
    Hi there, this is a Web service!
    

  8. Optional: You can also verify if the feature was successfully enabled by examining WCDE_installdir /logs/enableFeature.log. Near the bottom of the log, it clearly states whether the build failed or passed. If the build passed, then the feature was successfully enabled.

  9. If the machine where you are installing the feature will be using staging tools or acting as a staging server:

    1. Append the contents of WC_installdir/components/component-services/schema/db_type/component-services.stage.triggerFrom1.0.0.0.sql to the end of WC_installdir/schema/db_type/wcs.stage.trigger.sql, where db_type is either db2 or oracle.

    2. Append the contents of WC_installdir/components/component-services/schema/db_type/component-services.droptrigger.sql to the end of WC_installdir/schema/db_type/wcs.droptrigger.sql, where db_type is either db2 or oracle.

    3. Append the contents of WCDE_installdir/components/component-services/schema/db_type/component-services.stage.triggerFrom1.0.0.0.sql to the end of WCDE_installdir/schema/db_type/wcs.stage.trigger.sql, where db_type is either db2 or oracle.

    4. Append the contents of WCDE_installdir/components/component-services/schema/db_type/component-services.droptrigger.sql to the end of WCDE_installdir/schema/db_type/wcs.droptrigger.sql, where db_type is either db2 or oracle.

    This step only needs to be performed once, even if you enable and disable the feature multiple times.

Related concepts

WebSphere Commerce services

Related tasks

Install the Design Pattern Toolkit and the ComponentProjects design pattern
Disable WebSphere Commerce services