Performance Tuning for Content Manager

12 Performance Tuning for Content Manager

time when working with large documents. eClient also supports the same type of

search capabilities as a Windows client.

Portal client

Portal client is an extensive and customizable front end to Content Manager. It is

composed of Content Manager Portlets, a Web-based application, running on

the WebSphere Portal environment.

Content Manager Portlets consists of two portlets, the Main portlet and the

Viewer portlet. The

Main portlet provides a single portlet-based functional

replacement for the current Content Manager eClient. When deployed alone, the

Main portlet will display documents in new browser windows for viewing.

Optionally, the

Viewer portlet can be deployed on the same portal page as the

Main portlet to provide document-viewing capability with a unified layout in an

integrated fashion, instead of in separate browser windows. Click-2-Action (C2A)

is also supported by the Viewer portlet. Other portlets, including the Main portlet,

can communicate to the Viewer portlet using C2A to have documents displayed

in the Viewer portlet.

Portlets are free. They are available from the WebSphere Portlet Catalog:

http://catalog.lotus.com/wps/portal/workplace?NavCode=1WP1000O6

Creating your own client

You can create custom Content Manager client applications using client APIs and

user exit routines that are part of the Content Manager connectors. These

connectors come with Content Manager Information Integrator for Content. You

can use these APIs to:

 Access information in the Library Server and Resource Manager.

 Customize document processing.

 Design your own data model.

1.2.4 Content Manager component communication

When the Content Manager system is installed and running, the client application

accesses the Library Server through an SQL request (such as create, retrieve,

update, or delete). The Library Server, which contains metadata, processes the

request by looking up, in its content index, where the data resides. The Library

Server then gives the client a security token and a locator within the Resource

Manager where the information can be found. The information is then returned to

the client. The client uses the security token and locator to access the Resource

Manager. The Resource Manager accepts the security token and returns the

information to the client through HTTP.