IBM Support

Considerations when using a remote database configuration with Content Manager OnDemand

Release Notes


Abstract

IBM® Content Manager OnDemand is designed to be a tightly coupled database application where both the Content Manager OnDemand server and the database server run on the same system. The Content Manager OnDemand server is a lightweight front-end to the database and therefore utilizing a remote database can result in under-utilized resources (such as CPU and memory) where the Content Manager OnDemand server is running.

Although not preferred, it is possible to run the Content Manager OnDemand server against a remote database server. However, in the remote database server scenario, you might not be able to leverage certain functions that Content Manager OnDemand offers.

Content

When using a remote database configuration with Content Manager OnDemand:
  1. ARSDB command restrictions for Db2 and Microsoft SQL Server:
    • Creating the Content Manager OnDemand database (by using the -c parameter) cannot be used. You must manually create the database. After the database has been created, the ARSDB -rtv command should be used to create the Content Manager OnDemand system tables and indexes.
    • Starting, stopping, and/or activating the database (by using the -g, -h, -k parameters) cannot be used.
    • Backing up the database (by using the -y, -Y, -X, -z, -Z parameters) cannot be used.
       
  2. With the tablespace (Db2, Oracle) or filegroup (Microsoft SQL Server) option, Content Manager OnDemand is unable to create tablespaces or file groups:
    • When choosing the following option for the application group database storage: System Managed Space Table Space - SMS (Db2), Use Tablespace (Oracle), or Use File groups (Microsoft SQL Server), Content Manager OnDemand looks for the directory, based on the ars.dbfs file that has the most available space to create the tablespace or file group. However, when the database server is remote, it is possible for Content Manager OnDemand to analyze the available file systems on the remote server using NFS. The Content Manager OnDemand tablespace creation user exit can also be used. See the arscsxit.h file (in the installation directory) for information on the tablespace creation user exit.
    • For Db2 with remote database configuration, the best storage management is the Automatic Storage Table Space where Db2 controls the storage space. This option was added to the Content Management OnDemand support for Multiplatforms in V9.
  3. ARSTBLSP command restrictions:
    • Copy tables into their own table space (by using the -a 0 parameter) cannot be used.

[{"Line of Business":{"code":"LOB45","label":"Automation"},"Business Unit":{"code":"BU053","label":"Cloud & Data Platform"},"Product":{"code":"SSEPCD","label":"Content Manager OnDemand for Multiplatforms"},"ARM Category":[{"code":"a8m0z0000001gP1AAI","label":"technote"}],"ARM Case Number":"","Platform":[{"code":"PF002","label":"AIX"},{"code":"PF016","label":"Linux"},{"code":"PF033","label":"Windows"}],"Version":"10.1.0;10.5.0"}]

Document Information

Modified date:
09 August 2021

UID

swg27019582

Page Feedback