Administer > Manage WebSphere Commerce features > Enable Workspaces

Create an authoring server

Overview

The authoring server should be run on a separate system or machine partition from the production server.

See also: Enable Workspaces in the WebSphere Commerce development environment.

Procedure

1. Install WebSphere Commerce using the custom installation option of the installation wizard.

2. If you have a production server available:

   1. Verify you can connect from the authoring server node to the production database.

   2. Catalog the remote production database so that is accessible from the authoring server.

   3. Collect the following production server information...
      • Database name as cataloged on the authoring server.
      • Database user name (user ID)
      • Database user password
      • Fully qualified database server host name
      • Database server port

      You will also be asked to provide a name for the JDBC data source created for the production database, used by the quick publish function in workspaces.

   If you do not have a production server available, record the database information entered on the Database and Schema pages of the instance creation wizard. You will need this information in order to complete the Staging page of the Instance Creation wizard.

   When you have a production server available, you can update the authoring server with the production server information by following the instructions in Update the quick publish target.

3. Create a new WCS instance:

   1. Start the WebSphere Commerce Instance Creation wizard

   2. Complete the pages of the wizard.

   3. On the Staging page of the wizard, select...
      • Use staging server
      • Enable workspaces

      If you do not select these check boxes, the resulting instance will be a production WCS instance.

   When the instance creation process is complete, we will have an empty authoring server instance.

4. If a production server is available:

   1. Open the WebSphere Commerce configuration file in a text editor.

   2. Find the ManagedFileUpdateEARConfiguration tag.

      <ManagedFileUpdateEARConfiguration display="false">    
         
          <ContentManagedFileEARUpdate Implementation="com.ibm.commerce.filepublish.util.ContentManagedFileEARUpdateImpl" /> 
                
          <ContentManagedFileHandler Implementation="com.ibm.commerce.filepublish.util.ContentManagedFileHandlerImpl" /> 
                
          <ProductionServerInformation applicationName="WC_demo" /> 
                
          <ModuleInformation moduleName="Stores.war" />
          
          <EvaluationCriteria minNumOfFilesForUpdate="10" 
                              minSecFromLastUpload="3600" /> 
      
      </ManagedFileUpdateEARConfiguration>
      

   3. Update the ProductionServerInformation and ModuleInformation tags:

      ProductionserverInformation

      Specify the WebSphere Commerce application name, WC_enterprise_application, on the production server in the applicationName parameter.

      ModuleInformation

      Specify the module name for the store in the moduleName parameter. The usual name for the stores module name is Stores.war. This name is unlike to change unless you have extensive customization.

   4. Save the changes.

   5. Propagate your changes to the WebSphere Commerce configuration file.
      

5. Configure the authoring database and the production database for use with the staging utilities.
   

6. Synchronize the new, empty authoring server instance with the production server.
   

7. Optional: Enable e-mail notification in workspaces.

   Enable e-mail notification in workspaces allows WebSphere Commerce to sent e-mail automatically in the following situations:

   • Workspace Content Contributors will receive e-mail notification when a task they are assigned is part of a task group that has been activated.

   • Task Group Approvers will receive e-mail notification when a task group for which they are an approver is ready for approval.

   • Workspace Content Contributors will receive e-mail notification if a task group approval request is rejected and their assigned tasks are reactivated.

8. Create users and assign the users Workspace Manager, Workspace Content Contributor or Task Group Approver roles.
   

9. Stop and restart the authoring server instance.
   

+

Search Tips   |   Advanced Search