If the databases of the Libary Server and Resource Manager are installed in different DB2 instances, but on the same server host, you should catalog the Library Server database within the instance of the Resource Manager, to enable the Resource Manager to access the Library Server database. The Resource Manager needs to access the Libary Server database to validate any security tokens, the Library Server creates when people import or retreive any documents from the Resource Manager.

In the next procedure, the following texts need to be updated to your own situation:

• instance_name_resource_manager -> Name of the instance of the Resource Manager.
• hostname -> The short hostname of your server.
• resource_manager_database -> The name of the Resource Manager database.
• resource_manager_instance_owner -> The owner/userid of the Resource Manager instance.
• library_server_database -> The name of the Library Server database.
• instance_name_library_server -> Name of the instance of the Library Server.
• library_server_instance_owner -> The owner/userid of the Library Server instance.

• Log in as the database instance owner of the Resource Manager.
• Open or create the sqllib/profile.env file and add the following lines, to enable TCP/IP communication and the automatic restart:

  DB2ENVLIST='EXTSHM'
  DB2COMM='tcpip'
  DB2AUTOSTART='TRUE'

• Open or create the sqllib/userprofile file and add the following lines:

  ICMROOT=/usr/lpp/icm
  ICMDLL=/home/db2fenc1
  ICMCOMP=/usr/vacpp/bin
  CMCOMMON=/usr/lpp/cmb/cmgmt
  EXTSHM=ON
  PATH=$PATH:$ICMROOT/bin/DB2
  LIBPATH=$ICMROOT/lib:$ICMROOT/inso:$LIBPATH
  export ICMROOT ICMDLL ICMCOMP CMCOMMON EXTSHM PATH LIBPATH

• Log off.
• Log in as the database instance owner of the Library Server.
• Open or create the sqllib/profile.env file and add the following lines, to enable TCP/IP communication and the automatic restart:

  DB2ENVLIST='LIBPATH IMCROOT ICMDLL ICMCOMP EXTSHM CMCOMMON'
  DB2COMM='tcpip'
  DB2AUTOSTART='TRUE'

• Open or create the sqllib/userprofile file and add the following lines:

  ICMROOT=/usr/lpp/icm
  ICMDLL=/home/db2fenc1
  ICMCOMP=/usr/vacpp/bin
  CMCOMMON=/usr/lpp/cmb/cmgmt
  EXTSHM=ON
  PATH=$PATH:$ICMROOT/bin/DB
  LIBPATH=$ICMROOT/lib:$ICMROOT/inso:$LIBPATH
  export ICMROOT ICMDLL ICMCOMP CMCOMMON EXTSHM PATH LIBPATH

• Catalog the Resource Manager database instance:

  db2 catalog local node instance_name instance instance_name system ostype aix

• Refresh the database directory cache:

  db2 terminate

• Catalog the Resource Manager database in the system database directory:

  db2 catalog db resource_manager_database at node instance_name_resource_manager

• Refresh the database directory cache:

  db2 terminate

• Try to connect to the Resource Manager database:

  db2 connect to resource_manager_database user resource_manager_instance_owner

• Disconnect the connection:

  db2 terminate

• Log off.

In the same way as the Library Server connects to the Resource Manager database, the Resource Manager needs access to the Library Server database.
Perform te following steps on the Resource Manager machine with the Resource Manager instance owner:

• Log in as the Resource Manager instance owner.
• Catalog the Resource Manager database instance:

  db2 catalog local node instance_name_resource_manager instance instance_name_resource_manager system ostype aix

• Catalog the Library Server database in the system database directory:

  db2 catalog db library_server_database at node instance_name_library_server

• Refresh the database directory cache:

  db2 terminate

• Try to connect to the Library Server database:

  db2 connect to library_server-database user library_serveR_instance_owner

• Disconnect the connection:

  db2 terminate

• Log off.
• Log in as the Library Server instance owner.

• db2 catalog tcpip node CMCDB2 remote hostname server db2c_library_server_instance

• Log off.
• Log in as the Resource Manager instance owner.

• db2 catalog tcpip node CMCDB2 remote hostname server db2c_resource_manager_instance

• Log off.
• Log in as root and modify /etc/services:

  db2c_library_server_instance 50000/tcp
  db2c_resource_manager_instance 50001/tcp

Check if you can find both databases. Log in as the resource manager instance owner. Run:

db2 list database directory

Then connect to both databases.

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

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

Check for the entries LOGRETAIN and USEREXIT. If both of them are set to OFF (which is the default), then the database uses circular logging. If they are set to RECOVERY and ON respectively, then archival logging is used.

Archival logging is necessary if you wish to be able to roll forward all transactions after a restore of the database.

Getting help on error codes:

# db2 ? SQL0964c

If you wish to know more on error code SQL0964c.

Listing tables in other schema

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

Describing a table

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

View the database manager configuration

# db2 get dbm config

Content Manager DB2 tips

• 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.

DB2 database check:

# ps -ef | grep db2loggw

This command shows you the (log writer processes of the) DB2 databases that are active. To show the DB2 instance list:

# su - db2inst1 -c db2 list active databases
# su - db2inst1 -c db2ilist

Check if the db2agents and db2sysc are active via ps -ef. If one of these are not functioning, the database will not be active.

Check connectivity to DB2 database:

# su - db2inst1
# db2 connect to [database-instance] user [user-name] using [password]
db2 list tables
db2 list applications
db2 connect reset

IBM HTTP Server check:

Check the HTTP process using:

# ps -ef | grep httpserver

Startup a web browser to http://[server]/ and to https://[server]/.

Check the eClient:

# ps -ef | grep eClient_Server

WebSphere check:

Start a browser to http://[server]:9090/admin and login with ID wasadmin or icmadmin. Start a command window, go to the WebSphere directory (WebSphere/AppServer/bin) and run:

# serverstatus -all

Individual WebSphere applications can be stopped with stopserver icmrm (if you would like to stop the Resource Manager) and startserver icmrm (server1 is the default WebSphere server).

Check the Resource Manager

Start a browser to http://[server]/icmrm/ICMResourceManager. If you get output about a NULL request, it's fine.

Other checks:

http://[server]/icmrm/snoop should output information of the Snoop Servlet.
https://[server]/icmrm/ICMRMAdminServlet should show RM diagnostic data (You'll probably have to logon with the rmadmin userid).

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

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

For DB2 Universal database (version 5):

# su - db2inst1 -c db2level

For IBM Content Manager (version 8):

# /usr/lpp/icm/bin/cmlevel

Content Manager eClient (version 8):

# /opt/IBM/CMeClient/cmlevel

EIP:

# /usr/lpp/cmb/bin/cmlevel

Java:

# java -version

All other software, on AIX use:

# lslpp -l

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

Related links:

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

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.

Forrester conducted a research of various Enterprise Content Management suites in June and July 2005. They concluded that IBM Content Manager, together with Documentum, is one of the market leaders in its field: "IBM and EMC are clear ECM suite leaders. IBM and EMC have both been in the ECM market for the longest time and have ECM strategies that align with IT's needs." - The Forrester Wave, Enterprise Content Management Suites, Q3 2005 - October 7, 2005.

IBM Content Manager consists of the following parts:

Library Server

Is actually built upon a DB2 (or Oracle, but mostly DB2) database for the index of the digitized content. It is where you define the information that you store in your library. All user access for digitized content is validated by the library server. The library server also maintains referential integrity between the indexing information in the database and the objects themselves. There is at least one library server in an ICM implementation.

Resource Managers

Resource managers are the repositories that contain the digitized content and manage the storage and retrieval of objects. The resource manager provides hierarchical storage management (HSM) when used in conjunction with TSM / IBM Spectrum Protect. There is at least one and usually more resource managers in an ICM implementation. The Resource Manager is also built upon a DB2 database and is actually the index to the resources (= files) on a filesystem.

Mid-tier server

Functions as a broker that mediates communications between the client (web browser) and the library server. This is implemented via IBM WebSphere Application Server.

Clients

Users access the content via the eClient in a Web Browser, with JavaServer Pages (JSP), servlets and a viewer applet that runs on IBM WebSphere Application Server. Also a normal (fat) Windows client, and an administrative client is available.


A standalone configuration of IBM Content Manager
The latest version of IBM Content Manager and OnDemand is version 8.3. Version 9 of IBM Content Manager will presumably combine the two products of ICM and OnDemand into 1 product (but this is only a rumour up till now). Version 8.3 from OnDemand is the same as version 7.1.2.