Maintenance architecture

You need to plan for the tasks that maintain the health and integrity of your web content system. Your technical architect and database architect need to define what maintenance procedures are required for your system, and when and how often they need to be run.

Backup and restore strategies

Document backup and restore strategies for all the software and repositories in your web content system. This approach includes documenting procedures to back up and restore:
  • Data repositories
  • Themes
  • Portlets
  • Page structures
  • Configuration settings
  • Custom application

Applying updates

The process and timing of software updates are defined in the maintenance architecture. This document not only applies to Web Content Manager and HCL DX Portal, but to all software products in your web content system.

For example, you would document procedures to install fix packs for Web Content Manager regularly.

Running maintenance tools

You document the process and timing of running each maintenance tool. This documentation not only applies to Web Content Manager and HCL DX Portal, but to all software products in your web content system.

For example, you would document when and how often to run maintenance tools, such as the member fixer task, and when to clear item and version histories to maintain server performance.