How to determine the type of DB2 database logging is used (circular or archival):

# su - db2inst1 -c db2 get database configuration for [database]

# db2 ? SQL0964c

db2> list tables for schema s1
db2> list tables for all

db2> select tabschema, tabname from syscat.tables
db2> describe table [schema-name].[table-name]

# db2 get dbm config

• Give each Content Manager database a different name; don't leave them at default (for example ICMNLSDB). This will cause problems when doing federated searches across multiple content manager systems.
• Do not use the database catalog function on the client for naming databases, this is not supported within ICM.
• Use UTF-8 databases (not ISO8859-1) because it supports the Euro symbol. UTF-8 databases have a negative performance impact, limited to an increase of 50% of the database size, compared to single-byte (ISO8559-1) encoded databases.
• Keep the DB2 databases and the Content Manager system on the same server. Basically because the Library Server is not more than a bunch of stored procedures in the database itself. Also, because it eases the backup, which will be far more difficult to create consistently across multiple systems.
• Keep the number of WAS (WebSphere) threads equal to the number of DB2 database connections. Having more WAS threads than available database connections, will cause problems in Content Manager.

When installing service packs, keep the versions of the eClient_Server and Content Manager itself at the same level; Content Manager is very picky about this.

This is a quick procedure for configuring the system admin client for ICM on your Windows desktop, with the Library Server on a different AIX (or other OS) host system:

First make sure, both the DB2 run-time Client and Content Manager for Multiplatforms software are installed on your desktop. There is no need to install a library server and/or resource manager during ICM installation.

Use the Server Configuration Utility, to configure the server to connect to:

Server type: Content Manager
Server name: [the name of your library server, usually ICMNLSDB]
Schema name: ICMADMIN
Host name: [The (FQDN) hostname of the server where the db2 database is active]
Operating System: [The operating system on which the db2 database is active]
Port number: [check your host system and lookup the port for db2c_db2inst1, usually 50000]
Remote database name: [Usually ICMNLSDB]
Nodename: [the short hostname]
Security options: Server authentication (leave all other fields blank)

Problem: When the Icmrmvolval validation utility finds documents in de Resource Manager database, but not on your file system. You need to find out which document this is about. Icmrmvol reports item ID's that cannot be found on your filesystem, but do exist in the Resource Manager database.

Run the Icmrmvolval utility:

# ./icmrmvolval.sh -f [directory]

A1001001A04D28A95704H07197

db2 => connect to ICMNLSDB user ICMADMIN
select sourceitemid from icmstri001001 where targetitemid = 'A1001001A04D28A95704H07197'

SOURCEITEMID
--------------------------
A1001001A04D28A95704F54278

select componenttypeid from icmstitems001001 where itemid = 'A1001001A04D28A95704F54278'

COMPONENTTYPEID
---------------
1007

select * from icmut01007001
where itemid = 'A2001001A04J03C02629E64804'

select a.componenttypeid, a.itemid from icmstitems001001 a, icmstri001001 b
where a.itemid = b.sourceitemid and b.targetitemid = 'A1001001A04D28A95704H07197'

COMPONENTTYPEID ITEMID
--------------- --------------------------
1007            A1001001A04D28A95704F54278

select a.componenttypeid, a.itemid from icmstitems001001 a, icmstri001001 b, tempitems c where a.itemid = b.sourceitemid and b.targetitemid = c.ritemid

select * from icmut01007001 where itemid in (select a.itemid from icmstitems001001 a, icmstri001001 b, tempitems c where a.itemid = b.sourceitemid and b.targetitemid = c.ritemid)

IBM (DB2) Content Manager Version is a product available for Microsoft Windows, AIX, Sun Solaris and Linux. The former name of IBM Content Manager was Visual Info. Actually, the Content Manager portfolio from IBM is much larger, than this single product. Basically, there are 2 products, the first one called IBM Content Manager, and the second one IBM Content Manager OnDemand. Besides these two, there are a lot of additional tools and products.

ICM is a system for the management of business content, or Enterprise Content Management (ECM). It handles all types of digitized content, based on access via browsers, similar to Documentum. In other words: ICM is a system which allows storage of digitized documents, which can be retrieved via a web browser. Content Manager OnDemand is specifically used for storing spooled output and usually replaces the older Microfiche.

In general, most organizations have well-developed information systems in place for storing, sorting and retrieving text-based data records (business or structured data). These same organizations however, usually do not have the same type of data storage and retrieval systems in place for the large and growing mass of digital media (unstructured or semi-unstructured data).

The concept of Enterprise Content Management is to bring under the control of one system a platform independent integrated solution for storing and managing large quantities of multimedia content as well as the traditional relational database data. This allows database management facilities such as referential integrity, transactional integrity, robustness and archival and retrieval to be utilized to manage the full range of data objects within the modern enterprise.

Data stored by IBM Content Manager can be categorized as follows:

• Operational content: Scanned images (often in TIFF format - Tag Image File Format), Facsimiles, Computer generated output.
• Workgroup documents: Word processors (like MS Word, WordPerfect, Adobe FrameMaker, Lotus), Spreadsheets (MS Excel and Lotus 1-2-3), Presentation graphics.
• Media Assets: Audio and Video (MPEG).
• Web Content: HTML, graphics, business content.

A standalone configuration of IBM Content Manager

A number of external links, related to IBM Content Manager:

Official IBM sites:

• DB2 Information Management on IBM.com
• Content Manager Home on IBM.com
• Information Integrator for Content (II4C) or Enterprise Information Portal (EIP)
• Content Manager OnDemand for Multiplatforms on IBM.com
• DB2 Content Manager for Multiplatforms - Support
• DB2 Universal Database for Linux, UNIX and Windows - Support
• Content Manager Backup/Recovery and High Availability Redbook
• DB2 Product Family
• DB2 fixes
• DB2 Information Management Training
• DB2 Information Center
• The DB2 Memory Model
• Everything you wanted to know about DB2 Universal Database processes
• An Overview of Transactional Logging in DB2 Universal Database
• IBM FTP Site for On Demand
• IBM Content Manager User newsgroup
• Content Manager 8.3 announcement

• Docspro
• DB2 Magazine
• International DB2 Users Groups (IDUG)

For Websphere Application Server: versionInfo.sh (default in the subdir bin of the WebSphere installation directory:

# /usr/WebSphere/AppServer/bin/versionInfo.sh

# su - db2inst1 -c db2level

# /usr/lpp/icm/bin/cmlevel

# /opt/IBM/CMeClient/cmlevel

# /usr/lpp/cmb/bin/cmlevel

# java -version

# lslpp -l

ICM is a complex system. It uses several different parts: DB2 database, WebSphere, HTTP Server, ICM software and of course the operating system. This usually leads to confusion about who's administering the system.

Usually the DBA or the storage administrator will be made responsible for the ICM system. The DBA, because ICM is in the DB2 portfolio of IBM. The storage administrator, because ICM usually stores large amounts of data and requires a difficult backup methodology.

But in the end, it doesn't matter much, as long as there is a team responsible for the ICM system at whole, who knows the different parts of the system, and how they work together. And knows who to contact if a problem is very specific to a certain part of the ICM system, like database, or backup.

Test access to the IBM HTTP Server by accessing the following URLs:

• http://server.name.com
• https://server.name.com

• http://server.name.com:8008

• http://server.name.com:9090/admin

• http://server.name.com/snoop
• http://server.name.com/icmrm/snoop
• https://server.name.com/icmrm/SnoopServlet
• http://server.name.com:9080/snoop
• https://server.name.com:9443/snoop
• http://server.name.com:9081/icmrm/snoop
• https://server.name.com:9444/icmrm/snoop

• http://server.name.com/icmrm/ICMResourceManager
• https://server.name.com:9444/icmrm/ICMResourceManager
• https://server.name.com:9444/icmrm/ICMRMAdminServlet
  (log in with your "rmadmin" user and password)
• https://server.name.com/icmrm/ICMRMAdminServlet/sms
• http://server.name.com/icmrm/UTFTestServlet
• https://server.name.com/icmrm/UTFTestServlet

• Import a document into the NOINDEX document type.
• Do a basic search on the NOINDEX document type and find your imported document.
• Double click the document to display it (if not already displayed).
• Close the Windows client.

• For version 8.2: http://server.name.com/eClient82/IDMInit
• For version 8.3: http://server.name.com:9083/eclient/IDMInit
• Log in.
• Do a search on the NOINDEX item type.
• Find and display the imported document.
  (if no document displays, check if you installed and configured XVFB)

• Log in.
• Click on Resource Managers.
• Click on the plus (+) sign for Resource Managers.
• Click on the resource manager that is shown.
• If you have no error, SSL communication to the Resource Manager is working properly.

• Open DB2 Command Window
• Run "C:\Program Files\IBM\cmgmt\cmbdbcat81" AIX CAT DBP001 KL101234 INSTP001 KL101234.FQDN.COM 50000

• db2 => list node directory (check node)
• db2 => uncatalog node INSTP001
• db2 => list database directory (check db)
• db2 => uncatalog database KL101234

• db2 => connect to KL101234 user icmadmin using icmadmin
• db2 => list tables

• Add to file: C:\Program Files\ibm\CMgmt\cmbds.ini:
  FEDSERVER=KL101234
  FEDSERVERREPTYPE=DB2
  FEDSCHEMA=ICMADMIN
  FEDSSO=FALSE
  FEDDBAUTH=SERVER
  FEDREMOTE=TRUE
  FEDHOSTNAME=kl101234.fqdn.com
  FEDPORT=50000
  FEDREMOTEDB=DBP001
  FEDNODENAME=kl101234
  FEDOSTYPE=AIX
  
• Add to file: C:\Program Files\ibm\CMgmt\cmbicmsrvs.ini:
  ICMSERVER=KL101234
  ICMSERVERREPTYPE=DB2
  ICMSCHEMA=ICMADMIN
  ICMSSO=FALSE
  ICMDBAUTH=SERVER
  ICMREMOTE=FALSE
  ICMHOSTNAME=
  ICMPORT=
  ICMREMOTEDB=
  ICMNODENAME=
  ICMOSTYPE=
  
  
• Now you can startup the IBM Content Manager Windows client and system administration client and login.