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
HCL Commerce development environment,
ensure that:
- Change history is enabled in your development environment. Complete the
following steps to enable it:
- Go to the
WCDE_installdir/workspace/WC/xml/config/wc-server.xml.
- Open wc-server.xml and find
<WorkspaceChangeHistoryEnabled
enable="false"/>
.
- Edit the settings to the following values:
<WorkspaceChangeHistoryEnabled
enable="true"/>
.
- Save and close the file. Then, restart the server.
- Be sure you have a staging database loaded. For more information see,
Loading the HCL Commerce Developer database
schema.
Procedure
-
Exit the development environment.
-
Issue the following command:
WCDE_installdir/bin/enableContentManagement.bat number_of_workspaces addWorkspace
Where:
- number_of_workspaces
- Use the number_of_workspaces parameter if you are enabling workspaces in
the HCL Commerce development environment for the first time.
Enter the maximum number of
workspaces you want on the authoring environment. 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.
- addWorkspace
- Use the addWorkspace parameter if workspaces is already enabled in the
HCL Commerce development environment.
- Specify 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:
-
Enable the HCL 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.
-
Start the test
server.
Add the JVM argument, WorkspaceTaskListEnabled
, which is needed for workspaces
to function in Version 9.0.0.1.
-
Open the
Administration console, and go to . server is the name of your server, and the default value is
server1.
-
In the Generic JVM argument field of the
Configuration tab, add the following string.
-DWorkspaceTaskListEnabled=true
-
Save your changes to the master configuration.
-
Restart the test
server.
- Optional:
Enable email notification in workspaces.