IBM Content Manager, Version 8.5.0.3

RMCONFIGURATION

Reserved for Content Manager EE resource manager configuration.

Table 1. RMCONFIGURATION
Column Name	Data Type	Attribute
PROPERTYNAME	VARCHAR(256)	NOT NULL
PROPERTYVALUE	VARCHAR(1536) FOR BIT DATA	NOT NULL
PROPERTYBINARY	VARCHAR(1536) DB2® ONLY RAW(1536) ORACLE ONLY	NULLABLE

Primary key: (PROPERTYNAME)
Indexes: None
Referential Constraints: None

Column Definitions

PROPERTYNAME: Name of the parameter. See Table 2 for the property names that are allowed.
PROPERTYVALUE: Value of the parameter if it can be represented as a String (including numbers).
PROPERTYBINARY: Value in binary format when it cannot be represented as a String.

Table 2. PROPERTYNAME parameters
Parameter	Description
`ALLOWED_LOGON_FAILURES`	An integer value, this value is the number of sequential logon failures allowed. After the allowed number is reached, all logons are denied. A value of -1 is the infinite case. The valid range is -1 to 32 767.
`ADMIN_PASSWORD_MINIMUM_LENGTH`	Allows configuring a minimum resource manager administration password length.
`ADMIN_PASSWORD_MAXIMUM_LENGTH`	Allows configuring a maximum resource manager administration password length.
`ADMIN_PASSWORD_MINIMUM_ALPHA_CHARACTERS`	`1` or `0` disables this check. Allows configuring a minimum number of required alphabetic characters for resource manager administration password from the following set: `ABCDEFGHIJKLMNOPQRSTUVWXYZ abcdefghijklmnopqrstuvwxyz`
`ADMIN_PASSWORD_MINIMUM_NUMERIC_CHARACTERS`	`1` or `0` disables this check. Allows configuring a minimum number of required numeric characters for resource manager administration password from the following set: `0123456789`
`ADMIN_PASSWORD_MINIMUM_OTHER_CHARACTERS`	`1` or `0` disables this check. Allows configuring a minimum number of required other characters for resource manager administration password from the following set: `!@#+.,?*_.`
`ADMIN_PASSWORD_MAXIMUM_REPEATED_CHARACTER`	Allows configuring a maximum number of repeated characters for resource manager administration password. `1` or `0` disables this check.
`ADMIN_PASSWORD_MINIMUM_DIFFERENT_CHAR ACTERS`	Allows configuring a minimum number of different characters for resource manager administration password. `1` or `0` disables this check.
`AUDITMODE`	The default is ASYNC.
`ADVERTISE_ACCEPT_RANGES`	Controls whether the server sets the Accept-ranges header for retrieve operations. If the value is `TRUE` then the Accept-ranges header is set. The default value is `FALSE`.
`BACKGROUND_LS_DELETE_PROCESS`	A long value that expresses the milliseconds since the time 00:00:00 Coordinated Universal Time (UTC) on January 1, 1970. This value is used to serialize processing for items pending deletion within the library server (items identified in library server ICMSTItemsToDelete table) from the resource manager server. When the delete cycle begins, this value is compared to the current time. If this value is smaller, then processing of pending deletions in the library server starts immediately. Otherwise, the delete cycle portion for library server items pending deletion ends. When delete processing for a batch of library server deletions occurs, the value is reset. See the BACKGROUND_LS_DELETE_TASK_DEFERTIME property for details. Recommendation: Do not alter this value unless directed by IBM® support.
`BACKGROUND_LS_DELETE_TASK_DEFERTIME`	A long value in milliseconds that specifies the maximum time allocated to a specific node or thread to process a batch of pending library server deletions. This value is used to calculate the value of the BACKGROUND_LS_DELETE_PROCESS. The values BACKGROUND_LS_DELETE_TASK_DEFERTIME and BACKGROUND_LS_DELETE_PROCESS are used specifically to serialize certain delete operations within the resource manager server. The default delay time is 900000 (15 minutes).
`BACKGROUND_RM_DELETE_PROCESS`	A long value that expresses the milliseconds since the time 00:00:00 Coordinated Universal Time (UTC) on January 1, 1970. This property controls the frequency in which the resource manager performs delete processing on objects marked for deletion ( OBJ_STATUS within RMOBJECTS table indicated pending deletion). When the delete cycle begins, this value is compared to the current time. If this value is smaller, processing of resource manager deletions is started immediately. Otherwise, the delete cycle portion for objects marked for deletion ends. See BACKGROUND_RM_DELETE_TASK_DEFERTIME for details. Recommendation: Do not alter this value unless directed by IBM support.
`BACKGROUND_RM_DELETE_TASK_DEFERTIME`	A long value in milliseconds that specifies the frequency in which the resource manager performs delete processing on objects marked for deletion ( OBJ_STATUS within RMOBJECTS table indicated pending deletion). This property value is added to current time to calculate the BACKGROUND_RM_DELETE_PROCESS value. During the normal delete cycle (see BACKGROUND_SERVICE_CYCLE), if no objects marked for deletion are found, then future delete operations for these delete candidates ( OBJ_STATUS within RMOBJECTS table indicated pending deletion) are deferred for the period specified. The default delay time is 18000000 (5 hours).
`BACKGROUND_SERVICE_CYCLE`	The default background service cycle time is expressed in minutes. When active, Asynchronous delete and Asynchronous reconciliation runs automatically in the background.
`BACKGROUND_SERVICE_BATCH_SIZE`	The default is 1000.
`BLOB_STORE_SIZE_ENFORCED`	Controls whether to use the new BLOB behavior or old BLOB behavior. By default this flag is set to `True` to use the new BLOB behavior. With the new behavior, for store orders, the entire data stream received by resource manager for an object is stored, there is no truncation or padding, and the size specified in the order must match with the actual size of the data stream received by resource manager. If a size mismatch is detected in the store order, a size mismatch error is returned. Also with the new behavior, for third-party store orders, the size specified in the order is not checked. The entire data stream received by resource manager for an object is stored, there is no truncation or padding. If the order states the size is 10K but the actual content in the stream is 10 bytes, the actual 10 byte object is stored. If the order says that the size is 10 bytes but the actual content in the stream is 10K, the actual 10K object is stored. For third-party store orders, the actual size of the object stored in resource manager is used for an objects metadata size instead of the size specified in the third-party store order. This flag can be set directly in the RMCONFIGURATION table or by using the Advanced Parameters tab of the web-based Resource Manager Administration program.
`CMCOMMON_LDAP`	Reference for installing the properties files on the resource manager.
`DEFAULT_EVENT_BATCH_SIZE`	The audit event batch size. The default is 750.
`DISABLE_SERVICE_CHECK_OUT_TIMEOUT`	Internal usage for the replication utility. Do not define or change unless directed by IBM Support personnel.
`DO_NOT_SUSPEND_VOLUME_ON_WRITE_IO_ERROR`	Allows configuration of volume suspend on I/O error behavior. `True` = IBM Content Manager Version 8.3 behavior. `False` = IBM Content Manager Version 8.4 behavior. `Last` allows suspend, but not on the last available volume.
`DO_NOT_SUSPEND_VOLUME_ON_THRESHOLD_FULL`	Allows configuration of volume suspend on I/O error behavior. `True` = IBM Content Manager Version 8.3 behavior. `False` = IBM Content Manager Version 8.4 behavior. `Last` allows suspend, but not on the last available volume.
`DSMI_DIR`	The fully qualified directory path for the Tivoli® Storage Manager client API.
`DSMI_LOG_PATH`	The fully qualified path of the error log directory for Tivoli Storage Manager.
`ECM_DASHBOARD_ENABLED`	Use to enable or disable System Dashboard for Enterprise Content Management.
`ENABLE_64BIT_TOKEN`	Controls which type of token is allowed by the resource manager. The default value is TRUE or 1 to enable the resource manager to use 64-bit encryption keys for the token. This setting also enables the content management system to use stronger 128-bit encryption keys if both the library server and resource manager are at Version 8.6 or later. If the library server and all resource managers in the system are Version 8.6 or later, then 128-bit encryption keys for the token are used. If the value is set to FALSE or 0, the resource manager must use the 128-bit or stronger encryption keys for the token from the AES-128 encryption standard or SHA-2 family encryption standard. Set this value to FALSE or 0 if your content management system is required to meet the 128-bit encryption key standards set by government or industry regulation. This setting ensures that no 64-bit encryption key for the token can be used.
`ENCRYPT_DATA_AT_REST`	Enables the resource manager to encrypt all object content when at rest. If set to TRUE, the resource manager encrypts incoming data. The default value is FALSE (does not encrypt incoming data).
`ENCRYPTIONKEY`	The key to generate the password.
`ENCRYPTIONKEY_DATA_AT_REST`	The key to generate the password.
`ENCRYPTIONKEY_STR`	The key to generate the password.
`ICMRM_LBOSAREA`	llbosdata data area.
`ICM_AGGR_BULK_OPEN`	Controls how aggregate migration processes source files for aggregate. If setting is set to `True`, all source files are opened before transfer to target storage, and then all source files are closed after transfer. This process might result in a significant number of file descriptors in use during aggregate migration operations. Setting this value to `false` (the default), results in each aggregate source file being opened, a transfer of contents to target aggregate, and the closing files one at a time. This process limits the number of file descriptors needed for aggregate migration operations.
`ICM_MAX_AGGR_BATCH_SIZE`	200 (default). The count limit on number of objects stored in aggregate. The default is 200.
`ICMRM_USER`	Prevents writing object files with two different owners, or being unable to access previously written object files. If set, the value is checked with the value from the Java™ system variable user.name. If it is different a stoppage error results. If not set, the value from the Java system variable user.name is used to set it.
`ICMRM_UMASK`	Controls file permissions at create time.
`ICM_VALIDATION_BATCH_SIZE`	Controls the number of items added to the temporary RMLSTIEMS validation table for a single database transaction. The default value is 50 items.
`ICM_VALIDATION_QUEUE_SIZE`	Controls the maximum number of worker threads that can be queued to the work manager. The default value is 50 threads.
`IO_BUFFER_SIZE`	Allows control of non Tivoli Storage Manager I/O buffers sizes, to balance memory and performance.
`KEY_MATERIAL`	Key for encrypting data at rest (JEKS keystore or obfuscated).
`LOGON_LOCKOUT_DURATION`	The integer value in minutes that the lock applies. 0 is the infinite case. The valid range is 0 to 32 767 minutes.
`LOGON_LOCKED`	True or False. This value is always set to False at startup.
`LDAP_SECURITY_CREDENTIALS`	The password reference for installing the properties files on the resource manager.
`LDAP_INITIAL_CONTEXT_FACTORY`	The reference for installing the properties files on the resource manager. The default is sun.com.jndi.ldap.
`LDAP_PROVIDER_URL`	The reference for installing the properties files on the resource manager. The default is http://localhost.
`LDAP_PORT`	The port number reference for installing the properties files on the resource manager.
`LDAP_REFERRAL`	The default set to ignore reference for installing the properties files on the resource manager.
`LDAP_ROOT_DN`	Reference for installing the properties files on the resource manager. 0= IBM, c= US.
`LDAP_SECURITY_AUTHENTICATION`	Reference for installing the properties files on the resource manager. The default is NONE.
`LDAP_SERVER_TYPE`	The LDAP server type reference for installing the properties files on the resource manager. The default is STANDARD_LDAP.
`LDAP_SEARCH_SCOPE`	Reference for installing the properties files on the resource manager. The default is SUBTREE_SCOPE.
`LDAP_SECURITY_PROTOCOL`	Reference for installing the properties files on the resource manager.
`LDAP_AUTHENTICATION_ATTRIBUTE`	Reference for installing the properties files on the resource manager. ON or OFF.
`LDAP_SECURITY_PRINCIPAL`	Reference for installing the properties files on the resource manager. The default is cn=root.
`RMBATCH_PROCESS_FREQ_SEC`	Audit event frequency. The default is 10800 seconds.
`MIGRATOR_LAST_STATE`	The default is stopped.
`MIGRATOR_TRANSACTION_TIMEOUT`	The migrator failed transaction retry timeout. The default is 900 seconds.
`PURGER_LAST_STATE`	The default is stopped.
`PURGER_TRANSACTION_TIMEOUT`	The purger failed transaction retry timeout. The default is 900 seconds.
`REPLICATOR_LAST_STATE`	The default is stopped.
`REPLICATOR_INTRANSACTION_TIMEOUT`	Internal usage for the replication utility. Do not define or change unless directed by IBM Support personnel.
`REPLICATOR_TRANSACTION_TIMEOUT`	The replicator failed transaction retry timeout. The default is 900 seconds.
`STAGER_LAST_STATE`	The default is stopped.
`STAGER_TRANSACTION_TIMEOUT`	The stager failed transaction retry timeout. The default is 900 seconds.
`STATIC_FILE_PERMISSION`	The default value 400 causes a new file to be read-only.
`SEQUENTIAL_LOGON_FAILURES`	The current count of sequential logon failures. This value is always set to zero at startup, and cannot be a negative value.
`TSM_ENABLE_FASTQUERYBACKUP`	Enables sending of the Tivoli Storage Manager option -fastquerybackup on Tivoli Storage Manager DSMInitEx calls. This setting might improve Tivoli Storage Manager performance with Tivoli Storage Manager 6.1 and later.
`TSM_CONNECTION_TIMEOUT`	The maximum idle time, in seconds, for a connection. A connection is closed if the idle time is exceeded. The default connection timeout is 180 seconds (3 minutes). This value controls the reduction of the pool number when activity is slow. If this value is not configured correctly, an error is not shown. Set this value so that it is less than the Tivoli Storage Manager session timeout value.
`TSM_MAX_POOLED_CONNECTIONS`	The default value is 50 Tivoli Storage Manager connections. The minimum value is 3. If the value exceeds 150, a warning is logged to the resource manager log file. The maximum allowed value is 32767. If you set a value that exceeds 32767, then it is ignored and the default value of 50 is used instead. You must set this value so that the number is less than the concurrent session limit that is set for the Tivoli Storage Manager server. Setting this value to a greater number than the concurrent session limit might result in errors in the clients for object storage and retrieval. Count all connections for this value, including multiple resource managers that share a single Tivoli Storage Manager server or other applications that also share this server. For example, if the resource manager is deployed in a WebSphere® Application Server cluster, then multiply the TSM_MAX_POOLED_CONNECTIONS value for a single resource manager by the number of cluster nodes and use that total as the value for TSM_MAX_POOLED_CONNECTIONS.
`TSM_MAX_WAIT_FOR_FREE_CONNECTION`	If this parameter is set to a positive value in milliseconds, then an error is shown if this value is exceeded while the resource manager is waiting for a connection. The default is -1 (no limit) and the maximum value allowed is 32767. If you set a value that exceeds 32767, then it is ignored and the default value of -1 is used instead.
`TSM_PARTIAL_RETRIEVE_DISABLED`	Disables Tivoli Storage Manager partial retrieve. You must set this value to `YES` if Tivoli Storage Manager contains any compressed objects. The default is `NO`, meaning that when Tivoli Storage Manager client compression and encryption are not used, then the Tivoli Storage Manager partial retrieve is used for aggregate object members.
`TSM_USE_QS`	Enables use of the Tivoli Storage Manager query session call to validate pooled Tivoli Storage Manager connections, instead of the query management class call.
`TSM_WAIT_FOR_FREE_CONNECTION`	The retry interval for getting Tivoli Storage Manager pooled connections. This value controls an internal wait time to ensure that a request does not remain on the queue indefinitely. This parameter enables the thread to check whether the value in TSM_MAX_WAIT_FOR_FREE_CONNECTION has been exceeded. The value is in milliseconds. The default value is 250 milliseconds. The maximum value is 32767. If you set a value that exceeds 32767, then it is ignored and the default value of 250 is used instead.
`USE_KEY_SIZE_BITS`	The size in bits for the key to encrypt data at rest (128 or 256). The default is 128.
`VAL_BEGIN_DATE`	Internal usage for validation utility.
`VAL_END_DATE`	Internal usage for validation utility.
`VAL_VOLUME_ID`	Internal usage for validation utility.
`VALIDATE_LSITEMS_COUNT`	Internal usage for validation utility.
`VALIDATE_LSITEMS_PROCESSED_COUNT`	Internal usage for validation utility.
`VALIDATE_LSITEMS_TOTALITEMS_COUNT`	Internal usage for validation utility.
`VALIDATE_STATUS`	Internal usage for validation utility.
`VALIDATE_TYPE`	Internal usage for validation utility.
`VALIDATE_VOLUME_STATUS`	Internal usage for validation utility.
`VALIDATOR_LAST_STATE`	Internal usage for the validation utility. This property is the last state of the validation utility.
`VALIDATION_REPORT_CONDITION_MESSAGE`	Internal usage for the validation utility.
`VALIDATION_REPORT_CURRENT_CONDITION`	Internal usage for the validation utility.
`VALIDATION_REPORT_CURRENT_EVENTTIME`	Internal usage for the validation utility. Represents the last time validation was run (epoch time in milliseconds).
`VALIDATION_XML_LOGPATH`	The path to the XML validation reports. This path must be set to generate XML formatted validation reports.
`icmrm.tsm.jni.trace`	Internal usage for control of JNI tracing. Do not change this value unless directed by IBM Software Support.

Note: TOKEN_REQUIRED reserved parameter is not supported. Token is always validated regardless of the value of this parameter.