Data Storage
By default, Web Content Management uses Cloudscape as a data repository. WCM data can also be saved within a JDBC database. Large sites should be stored via DB2 or Oracle persistency, whcih will improve performance and reliability.
You can use different data storage options in different environment. For example, use DB2 persistency with an Authoring application, but use a Cloudscape repository on the Staging and Delivery applications.
Two WCM applications cannot share a single data repository. Separate data repositories must be created for each WCM application.
When first creating a new WCM application, it is better to copy an existing WCM data repository database to a new server, enable your new WCM application to use the new data repository, and then enable Syndication rather than trying to Syndicate an entire Site's data. be using the same type of database to be able to do this.
- The Repository Configuration Task.
By default, WCM uses Cloudscape as a data repository. The WCM Repository configuration task updates the WCM configuration to use a different JDBC data repository such as DB2.
- WCM Parameters in wpconfig.properties.
The Web Content Management section of...
/PortalServer/config/ wpconfig.properties...contains settings that are used by WCM configuration tasks.
- Data Repository Settings.
When configuring WCM to use a Data Repository edit the WCM section of the wpconfig.properties file. Default settings for each supported Data Repository are listed in this file and can be used as the basis for configuring a Data Repository.
- Resource Storage Settings.
External files can be imported into WCM. Like WCM data, these resources can be stored in different repositories.
Parent topic: Configuration.
IBM Workplace WCM - V5.1.0.1
IBM is a trademark of the IBM Corporation in the United States, other countries, or both.