Maintenance architecture

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

Backup and restore strategies

You should document backup and restore strategies for all the software and repositories in the web content system. This approach includes documenting procedures to back-up and restore:

• Data repositories

• Themes

• Portlets

• Page structures

• Configuration settings

• Custom application

Apply updates

The process and timing of software updates are defined in the maintenance architecture. This not only applies to Web Content Manager and WebSphere Portal, but to all software products in the web content system. For example, we would document procedures to install cumulative fixes for Web Content Manager on a regular basis.

Running maintenance tools

We document the process and timing of running each maintenance tool. This documentation not only applies to Web Content Manager and WebSphere Portal, but to all software products in the web content system. For example, we 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.

Parent: Create a design document

Related:

Maintain web content