WebSphere Commerce Developer

Enabling Workspaces in the WebSphere Commerce development environment

The development environment is not meant to be an authoring environment. Support is provided in the environment for customization purposes only. For example, to test changes to the content management functionality. The ability to propagate changes is not available. If you want to change the content management workspaces, you cannot publish the changes out to another database.

Before you begin

Before you enable workspaces in the WebSphere Commerce development environment, ensure that:
  1. WebSphere Commerce Developer is installed and configured.
  2. The development environment is configured to use DB2 Universal Database or Oracle database. Workspaces do not work with Apache Derby.
  3. The Search authoring environment is deployed only in the embedded configuration. For more information, see Deploying WebSphere Commerce Search.
  4. Change history is enabled in your development environment. Complete the following steps to enable it:
    1. Go to the WCDE_installdir/workspace/WC/xml/config/wc-server.xml.
    2. Open wc-server.xml and find <WorkspaceChangeHistoryEnabled enable="false"/>.
    3. Edit the settings to the following values: <WorkspaceChangeHistoryEnabled enable="true"/>.
    4. Save and close the file. Then, restart the server.


  1. Exit the development environment.
  2. Review wc-server.xml and make sure that the following parameter is set to true.
    <component enabled="true" name="WorkspaceTaskList"/>
  3. Issue the following command:
    WCDE_installdir/bin/enableContentManagement.bat number_of_workspaces addWorkspace
    Used when enabling workspaces in the WebSphere Commerce development environment for the first time.

    Enter the maximum number of workspaces you want on the authoring server. Ensure that the number of workspaces that are allocated is sufficient to handle the number of concurrent workspace activities that might occur.

    The maximum number of workspaces is the maximum number of simultaneous activities that require data isolation. Multiple stores that are managed by the same organization can share a workspace. For instance, to work on two future events simultaneously and provide regular updates and a data-isolated area in which to complete emergency fixes, you need four workspaces per organization.

    The maximum number of workspaces specifies the number of database schemas that are allocated for workspaces. The number of allocated database schemas remains fixed. If a Workspace Manager creates more workspaces than the number of workspace database schemas available, task groups in workspaces without an available database schema cannot be activated until another workspace is completed or canceled.

    For more information, see Workspaces data model.

    Used when workspaces is already enabled in the WebSphere Commerce development environment.

    Enter the number of additional workspaces to create.

    If you encounter errors when you run the utility, review the enableContentManagement.log file for more detailed troubleshooting information. This file can be located within the following directory:
    • WCDE_installdir\logs
  4. Enable the WebSphere Commerce search index.
    Run the setupSearchIndex utility with the following workspace-specific parameters specified:
    • dbauser
    • dbauserpwd
    • createAll
    For more information, see Setting up the search index.
  5. Optional: Enable email notification in workspaces.