Difference between revisions of "ars.cfg"

ars.cfg (view source)

Revision as of 18:54, 2 November 2017

523 bytes added , 18:54, 2 November 2017

→‎CMOD Database Configuration

Jderrick

Bureaucrats, Administrators

1,126

edits

@@ Line 117: / Line 117: @@
 == CMOD Database Configuration ==
+{| class="mw-collapsible mw-collapsed wikitable"
+! Sample Content Manager OnDemand Database Configuration &nbsp;
+|-
+|
    #
    # Number of Database SubServers (Library Server Only)
@@ Line 125: / Line 128: @@
    #
    ARS_NUM_DBSRVR=4
-;ARS_NUM_DBSRVR
-: The ARS_NUM_DBSRVR parameter specifies the number of 'subservers' or database connections to create to the database.  In larger systems, increasing this number may have performance benefits, at the expense of using additional RAM.
-: Increasing ARS_NUM_DBSRVR number too high may result in poor performance if not enough RAM is available.
-: Setting ARS_NUM_DBSRVR to 0 (zero) on large systems may cause performance issues during spikes in activity, as each new connection to CMOD creates a new Subserver, which may consume all available RAM.
    #
@@ Line 135: / Line 133: @@
    #
    ARS_DB_ENGINE=DB2
-; ARS_DB_ENGINE
-: Specifies the database engine to be used, usually DB2 or Oracle.
    #
@@ Line 146: / Line 141: @@
    #
    ARS_DB_IMPORT=0
-; ARS_DB_IMPORT
-: In the early days of CMOD, when storage space was prohibitively expensive, OnDemand had the ability to 'archive' infrequently used database tables in the same way that it archived data to TSM.  As storage prices have fallen and data compression in database engines has become common, this method of reducing the use of disk space has become essentially obsolete.  [https://www.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.installmp.doc/dodax012.htm v9.5]
    #
@@ Line 155: / Line 147: @@
    #
    ARS_DB_PARTITION=
-;ARS_DB_PARTITION
-: If your database engine supports partitioning, change this parameter to 1 on the library server.  Application Groups which should support partitioning must have a field defined to hold the partition data.
-: This configuration parameter is only intended for the very largest of CMOD servers holding hundreds of billions of documents, and serving tens of thousands concurrent users.
-[https://www.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.installmp.doc/dodax013.htm v9.5]
    ########################################
@@ Line 165: / Line 152: @@
    ########################################
    DB2INSTANCE=archive
+|}
+;ARS_NUM_DBSRVR
+: The ARS_NUM_DBSRVR parameter specifies the number of 'subservers' or database connections to create to the database.  In larger systems, increasing this number may have performance benefits, at the expense of using additional RAM.
+: Increasing ARS_NUM_DBSRVR number too high may result in poor performance if not enough RAM is available.
+: Setting ARS_NUM_DBSRVR to 0 (zero) on large systems may cause performance issues during spikes in activity, as each new connection to CMOD creates a new Subserver, which may consume all available RAM.
+; ARS_DB_ENGINE
+: Specifies the database engine to be used, usually DB2 or Oracle.
+; ARS_DB_IMPORT
+: In the early days of CMOD, when storage space was prohibitively expensive, OnDemand had the ability to 'archive' infrequently used database tables in the same way that it archived data to TSM.  As storage prices have fallen and data compression in database engines has become common, this method of reducing the use of disk space has become essentially obsolete.  [https://www.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.installmp.doc/dodax012.htm v9.5]
+;ARS_DB_PARTITION
+: If your database engine supports partitioning, change this parameter to 1 on the library server.  Application Groups which should support partitioning must have a field defined to hold the partition data.
+: This configuration parameter is only intended for the very largest of CMOD servers holding hundreds of billions of documents, and serving tens of thousands concurrent users.
+[https://www.ibm.com/support/knowledgecenter/SSEPCD_9.5.0/com.ibm.ondemand.installmp.doc/dodax013.htm v9.5]
 ;DB2INSTANCE
 : Specifies the name of the database to use for storing document metadata.
 === CMOD Database Creation ===
-These parameters should be defined before issuing the [[arsdb]] command with the -c, -r, or -t options.
+{| class="mw-collapsible mw-collapsed wikitable"
+! Sample Content Manager OnDemand Database Creation Parameters &nbsp;
+|-
+|
    #
    # These parameters used only during database creation
@@ Line 179: / Line 185: @@
    ARS_DB2_LOGFILE_SIZE=1000
    ARS_DB2_LOG_NUMBER=40
+|}
+These parameters should be defined before issuing the [[arsdb]] command with the -c, -r, or -t options.
 ;ARS_DB2_DATABASE_PATH
@@ Line 199: / Line 208: @@
 : The number of logs multiplied by the log file size parameter above determines how large your primary log filesystem should be, and how large your archive filesystem should be.
+{| class="mw-collapsible mw-collapsed wikitable"
+! Sample Content Manager OnDemand DB2 TSM Configuration Parameters &nbsp;
+|-
+|
    #
    # DB2/TSM Parameters
    #
    ARS_DB2_TSM_CONFIG=/opt/tivoli/tsm/client/api/bin/dsm.opt.db2
+|}
 ;ARS_DB2_TSM_CONFIG
 : This is the configuration file for Tivoli Storage Manager used by DB2 for transaction log archiving and automatic backup & restores.
+{| class="mw-collapsible mw-collapsed wikitable"
+! Sample Content Manager OnDemand DB2 TSM Configuration Parameters &nbsp;
+|-
+|
    ###########################################
    # ORACLE Parameters (Library Server Only) #
    ###########################################
    ARS_ORACLE_HOME=/oracle
+|}
 ;ARS_ORACLE_HOME
 : Points CMOD to the directory where oracle is installed.