WebSphere Commerce EnterpriseWebSphere Commerce Professional

Workspace managed assets

Managed assets are WebSphere Commerce components or resources that are enabled for workspaces and allow content to be written to separate workspace database schemas. Workspace Content Contributors can modify managed assets in the context of a workspace.

The following assets are not enabled for workspaces:
  • Price lists and rules
  • Catalog filters and contracts
  • Folders
  • Code assets, including JSP files.
  • Stores
WebSphere Commerce provides the following managed assets in Management Center:
Management Center tool Managed assets
Catalogs tool
  • Catalogs
  • Categories
  • Catalog entries
  • Attributes
  • Prices
  • Merchandising associations
  • Search term associations.
  • Introduced in Feature Pack 3SEO URL and keyword metadata
  • Feature Pack 5 or laterFacets
Marketing tool
  • e-Marketing Spots
  • Campaigns
  • Web activities, including experiments
  • Customer segments
Promotions tool
  • Promotions
Assets tool
  • Assets
Installments tool
  • Installment rules
Feature Pack 5 or laterPage Layout tool
  • Page layout assignments
Feature Pack 7 or laterCommerce Composer tool
  • Page layouts
  • Page layout assignments
  • SEO URL and keyword metadata for content pages
Feature Pack 5 or laterSearch indexing is enabled for workspaces. A separate search index is created for each allocated workspace to preview non-approved changes in a search-based navigation storefront in an authoring environment.
WebSphere Commerce provides the following managed assets in WebSphere Commerce Accelerator:
Managed assets WebSphere Commerce Accelerator
Product management
Merchandising management
Marketing management

Other assets such as contract assets, member management assets, store management assets, file assets such as JSP files or HTML files are not managed assets. You can work on only non-managed assets in the production-ready data.

If your planned site updates include a mix of managed assets, you want to update your site by using workspaces and non-managed assets. Ensure that your planned workflow handles any dependencies between the managed and non-managed assets.