Analítica WEB

The Content Manager Resource Manager does not only consist of the Web application that is running within WebSphere and serving import and retrieve requests. Four background services that can be started independently from the Web application also belong to the Resource Manager.

Figure 2-8 on page 33 shows the Resource Manager services and the data areas on which they are working. The upper half of the figure shows services related to VideoCharger, the lower half for non-streamed objects. Not shown is the replicator service that will typically work between two Resource Managers.

Figure 2-8 Resource Manager data areas and services

The four main services, purger, stager, migrator, and replicator, can be started separately from the Resource Manager Web application. On Windows, these four applications are Windows services and can be started and stopped using the Windows Services Control Panel, as shown in Figure 2-9 on page 34, or using the net start <name of service> command in batch operations.

Staging

Area Storage Area

(lbosdata) Tivoli Storage Manager Import Retrieve Migrator Purger Async. Recovery Video- Charger Multimedia Archive Migrator Stager Stream / Play U S E R

Figure 2-9 Resource Manager services on Windows

On UNIX, these services can be started using the script rc.cmrmproc -act start

and stopped using the rc.cmrmproc -act stop script provided by Content Manager, as shown in Example 2-4.

Example 2-4 Starting Resource Manager services on UNIX

root@cm44/etc# ./rc.cmrmproc -act start PROCACTION: start

2003-11-10 22:56:22,441 ICM0000: Licensed Materials - Property of IBM IBM Content Manager for Multiplatforms V8.2 (program number 5724-B19) (c ) Copyright IBM Corp. 1994, 2002, 2003. All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation

RMMigrator --> RMDB RMPurger --> RMDB RMReplica --> RMDB RMStager --> RMDB

# root@cm44/etc# ./rc.cmrmproc -act stop PROCACTION: stop

2003-11-10 23:06:00,483 ICM0000: Licensed Materials - Property of IBM IBM Content Manager for Multiplatforms V8.2 (program number 5724-B19) (c ) Copyright IBM Corp. 1994, 2002, 2003. All Rights Reserved. US Government Users Restricted Rights - Use, duplication or disclosure restricted by GSA ADP Schedule Contract with IBM Corporation

RMMigrator --> RMDB input: cm44 7500 shutdown sending shutdown to process client waiting for status info client got down

RMPurger --> RMDB

input: cm44 7501 shutdown sending shutdown to process client waiting for status info client got down

RMReplica --> RMDB input: cm44 7502 shutdown sending shutdown to process client waiting for status info client got down

RMStager --> RMDB

input: cm44 7503 shutdown sending shutdown to process client waiting for status info client got down

Purger

The job of the purger process is to maintain the staging area size. The staging area is used to cache objects from Tivoli Storage Manager and remote Resource Managers (for LAN cache). For example, when a client makes a request for a document that is stored in an optical jukebox managed by Tivoli Storage Manager, the document is first copied to the staging directory and then sent to the client. Any future requests for this particular document will be much faster, because the document would then be on the hard disk, and not on a slower optical platter.

When the staging area size reaches a preset upper limit, the purger will begin to remove files until it reaches a preset lower limit. For example, Figure 2-10 on page 36 depicts a 200 MB staging area, which has an upper threshold of 190 MB and a lower threshold of 10 MB. Whenever the staging area reaches 190 MB in size, the purger process will begin to selectively delete files from the staging directory, and will continue to do so until the directory reaches 10 MB in size.

Figure 2-10 Staging area thresholds

Figure 2-11 shows how to accomplish these setting in the Content Manager System Administration Client. To get this panel, click Resource Managers→ RMDB→ Staging Area.

Figure 2-11 Staging Area properties

Stager

The job of the stager process is to delete staged objects from a VideoCharger server. When using a Media Archive Server with VideoCharger, videos that are archived on the Media Archive Server cannot be directly streamed to clients. When a play request for an archived video is received, the video object must be

200 MB

190 MB

10 MB

0 MB

Upper Threshold

Lower Threshold

temporarily staged (or cached) to the VideoCharger server. When the

VideoCharger stager gets too full, the stager process will delete some, or all, of the staged objects.

Migrator

The job of the migrator is to move documents between storage classes and to remove deleted documents from the database. The migrator process is used to execute the rules set forth by the migration policies. If you forget to start the migrator process, documents will never be moved.

The second job of the migrator process is to remove objects from the Resource Manager server that have been marked for deletion by the asynchronous recovery utilities. When a client deletes a document, the database entries are immediately removed from the Library Server, but still remain on the Resource Manager (for performance reasons). The asynchronous recovery tools will mark the objects in the Resource Manager database that need to be removed. When the migrator starts, it will perform the deletion of these documents from the database. Therefore, even though you might not be planning to migrate

documents between storage classes, you should always ensure that the migrator process has been started so that deleted documents can be removed from the database tables.

Replicator

The replicator creates additional copies of documents stored to collections enabled for replication. When defining a collection, you can choose a copy destination on the same or a different Resource Manager. The replicator will copy these documents asynchronously, for example, to a secondary Resource Manager, as shown in Figure 2-12 on page 38.

The schedule and frequency used to run the replicator highly depends on the requirements. Frequent runs all over the day make sure that the secondary collections are up-to-date; however, they have a large impact on performance. A single run in off-peak hours reduces hardware and bandwidth requirements, but increases the risk of having not yet replicated documents unavailable.

Figure 2-12 Content Manager replication

Content Manager replication is not load balancing. As long as the primary Resource Manager is available, all import and retrieval operations will be managed by it. Only if the primary Resource Manager goes down does the Library Server monitor switch to secondary or other standby systems.

Asynchronous recovery utilities

The asynchronous recovery utilities consist of two programs used for document deletion and transaction reconciliation. These utilities are used to maintain and to restore the consistency between the Library Server and Resource Manager databases.

The document deletion utility will determine which documents have been deleted from the Library Server database and will then flag these documents in the Resource Manager databases for deletion. The migrator will actually perform the removal of database entries for deleted documents.

The transaction reconciliation utility is used to roll back any failed transaction and ensures that the Resource Manager database is in sync with the Library Server database.

These two utilities are automatically executed before the migrator performs any work. However, you do have the option of manually running these utilities yourself. Primary RM Secondary RM Col- lection Col- lection Replicator Import Retrieve Import failove_r Retrieve failover

To manually run these utilities on Windows, open a DB2 command window, using

db2cmd. To start the deletion reconciliation utility, run icmrmdel.bat (located by default in C:\Program Files\IBM\CM82\bin). To start the transaction reconciliation utility, run icmrmtx.bat (located by default in C:\Program Files\IBM\CM82\bin). To run these utilities on AIX, log on as the Resource Manager administrator (by default rmadmin). To start the deletion reconciliation utility, run icmrmdel.sh

located in /usr/lpp/icm/bin. To start the transaction reconciliation utility, run

icmrmtx.sh located in /usr/lpp/icm/bin.

We recommend that you run the asynchronous recovery utilities before

performing a backup of your system. This not only ensures your databases are in a consistent state, but also removes any database entries that represent deleted documents.