Performance Tuning for Content Manager

132 Performance Tuning for Content Manager

Server to find and request access to data. When the Library Server authorizes

the access, it sends a key (a token) related to the asset directly back to the client,

unlike previous Content Manager implementations. The client then passes the

key (token) to the Resource Manager to request the resource object (Figure 5-1).

Figure 5-1 Data flow triangle

5.7.2 Physical locations

One aspect of scalability and performance that has a major impact on design is

the support for multiple Resource Managers in the same system. Additional

Resource Managers can spread the I/O and network load involved in storage and

retrievals. If installed at physically remote sites, this can mask wide area network

delays.

The Resource Managers can be located next to users to potentially reduce the

network traffic and delays associated with moving a relatively large amount of

data across a wide area network. A customer with multiple sites can run a single

Content Manager system with a central Library Server for a single point of control

and have distributed Resource Managers at each location. Users can store and

retrieve their data to and from their local server. All data is available to all

authorized users throughout the system, but the frequently accessed data is

located on a nearby server.

Web Application

Server

Resource

Manager

Database

Library

Server

System

Administration

Client

search

token

token

object