Performance Tuning for Content Manager

Chapter 5. Designing and configuring for performance 121

Upcoming chapters cover tuning the configuration parameters for the database,

WebSphere, and TSM. First, we should consider configuration and design

options in the Resource Manager that can affect performance. As in the case of

the Library Server, you use the system administration client or the administration

APIs to set and change configuration parameters, turn functions on or off, and

define storage to the system.

5.6.1 Resource Manager properties

To reach the Resource Manager properties, open the system administration

client. From the left-side pane, expand the Library Server (ICMNLSDB) Æ

Resource Managers → the Resource Manager database (RMDB). Right-click

the Resource Manager database to select Properties to open the Resource

Manager Properties window. Right-click the Resource Manager database to

select the Staging area to open the Staging Area panel.

Properties

In the Resource Manager Properties panel, you can set the details stored in the

Library Server about the Resource Manager, including communications details,

logon details, token duration, the LAN cache switch, and a disable switch.

The Library Server and the system administration client use this connection

information to make connections to the Resource Manager. The connection

information includes host name, user ID, password, protocols, port numbers, and

access data used to log on.

Token duration

Token duration

specifies how long the security token, provided to a client to

access a document on this Resource Manager, will remain valid. The default is

48 hours. A client application may continue to access the resource object without

reference to the Library Server for the period that the token remains valid. If your

application frequently re-reads the same item on the Resource Manager, you can

store the item’s URL and go directly to the Resource Manager for the item for as

long as the token remains valid.

LAN cache

LAN cache

enables objects to be retrieved from the user’s default Resource

Manager if a copy is cached there. The user’s default Resource Manager should

be the physically closest Resource Manager or the Resource Manager with the

Note: The Resource Manager uses its own database connection pooling

methods, not the standard WebSphere database connections.