Database information

Use to specify advanced database information.

Maximum Rows

Verify the value in the Maximum Rows field. IBM recommends that you accept the default value.

Multiple loads per database table

Each time that you load a report into the application group, Content Manager OnDemand adds the index records to the database table that is currently open. When the open database table reaches the Maximum Rows value, Content Manager OnDemand closes it and opens a new table. Choose this database organization when the reports in the application group are part of a logical sequence of information that contain a unique identifier, such as an invoice number. Multiple loads per database table is the recommended option.

Single table for all loads

This option is available for Content Manager OnDemand for z/OS and Content Manager OnDemand for IBM® i. Click the Single table for all loads checkbox if you want to create one database table for each application group. This option is most frequently used when you load a small amount of data. If you select this option, the Maximum Rows field in this window is removed.

Single load per database table

Each time that you load a report into an existing application group, Content Manager OnDemand stores the index records for the report in a new database table. Content Manager OnDemand uses the Maximum Rows value to determine the amount of space to allocate for the table. Choose this database organization when the reports in the application group are not necessarily related, such as daily status reports.

Note: This option is no longer supported.

Create Tablespace Type

For Content Manager OnDemand for Multiplatforms and z/OS servers with Db2, specify whether application group data is stored in table spaces. Choose from one of the following options:

Automatic Storage (only Multiplatforms servers)
SMS (Multiplatforms and z/OS servers)
None (Multiplatforms and z/OS servers)

Use Tablespace

For Content Manager OnDemand for Multiplatforms servers with Oracle, select this option to store application group data in table spaces.

Before application group data can be stored in tablespaces, you must configure the system to use tablespaces by identifying file systems on one or more storage volumes. For UNIX servers, the file systems are added to the ARS.DBFS configuration file. For Windows servers, the file systems are added using the Configurator. Content Manager OnDemand looks for the file system that has the most available space to create the tablespace.

If the database server is remote, Content Manager OnDemand cannot analyze the available file systems on the remote server. As a result, the Content Manager OnDemand tablespace creation user exit named arsutbl.c must be created and used if Use Tablespace is selected. See the arscsxit.h file, located in the installation directory, for information on the tablespace creation user exit.

Use Filegroups

For Content Manager OnDemand for Multiplatforms servers with Microsoft SQL Server, select this option to store application group data in filegroups.

Before application group data can be stored in filegroups, you must configure the system to use filegroups by identifying file systems on one or more storage volumes. The file systems are added using the Configurator. Content Manager OnDemand looks for the file system that has the most available space to create the filegroup.

If the database server is remote, Content Manager OnDemand cannot analyze the available file systems on the remote server. As a result, the Content Manager OnDemand tablespace creation user exit named arsutbl.c must be created and used if Use Filegroups is selected. See the arscsxit.h file, located in the installation directory, for information on the tablespace creation user exit.

Compress Table/Tablespace

For databases that support compression, select this checkbox to make Content Manager OnDemand compress the tables or table spaces. If the database does not support compression, Content Manager OnDemand ignores this setting.

Annotation

Determines whether Content Manager OnDemand maintains a database field for annotation status. Choose Yes or No. Yes is the recommended option.

Document Activity Tracking

Select the activities for which you want to record the last date the activity was done for the application group. You can view these dates in the application group list.

Database Name

Specifies the name of this database. New application group data tables will be created in the specified database. Previously created application data tables will remain in the database in which they were originally created. The database name can be up to 8 bytes, and cannot contain spaces. This is an optional field, and is available on z/OS only.

Interoperate with FileNet P8 Platform

To use Content Federation Services (CFS-CMOD), ensure that you enable this feature on the server first. If you do not enable the feature on the server, your selection to enable the feature in an application group is ignored.

To enable Content Federation Services on AIX, Linux, IBM i, and z/OS, modify the ARS.CFG file and add this line: ARS_SUPPORT_CFSOD=1

To enable Content Federation Services on Windows, use the Windows configurator.

Select Yes or No to specify whether you want to use Content Federation Services (CFS-CMOD).

Federate documents automatically

If you select this checkbox, all of the loaded metadata is also federated into FileNet. If you do not select this checkbox, you need to specify the loaded metadata by using a Content Manager OnDemand client if you want to federate them into FileNet.

Enable Enterprise Records to declare records automatically

Do not enable Enterprise Records if your documents are stored exclusively in a cache-only storage node. Documents that are stored in cache could be expired even if they are declared as records in Enterprise Records. On IBM i servers, this means that the migration policy specified in the application group definition to which the documents belong must have at least one migration policy level with a media type other than Expire, so that the Archived Storage Manager (ASM) manages the data.

If you select this checkbox, Content Manager OnDemand assumes that any documents that are federated into FileNet are declared as records to Enterprise Records. If you do not select this checkbox, then the documents that are federated into FileNet are not declared as records in Enterprise Records.

Enhanced Retention Management

To use the Enhanced Retention Management feature, ensure that you enable the feature on the server first. If you do not enable the feature on the server, your selection to enable the feature in an application group is ignored.

To enable Enhanced Retention Management on AIX, Linux, IBM i, and z/OS, modify the ars.cfg file and add this line: ARS_SUPPORT_HOLD=1

To enable Enhanced Retention Management on Windows, use the Windows configurator.

Do not enable Enhanced Retention Management if your documents are stored exclusively in a cache-only storage node. If the Life of Data and Indexes value has been reached, documents that are stored in cache could be expired by Content Manager OnDemand even if there is a hold placed on a document. On IBM i servers, this means that the migration policy specified in the application group definition to which the documents belong must have at least one migration policy level with a media type other than Expire, so that the Archived Storage Manager (ASM) manages the data.

Select Yes or No to specify whether you want to use enhanced retention management for this application group. Select the Implied hold checkbox to lock down the content as soon as the data is loaded. You can select implied hold for new application groups only, because an implied hold applies to all data within the application group and you must select it before you load any data.

Query using parameter markers

Select this checkbox to use parameter markers. Clear this checkbox to turn off the parameter markers when you perform database queries.

Full Text Index

To use Full Text Index, the application group expiration type must be LOAD.

Yes

If you select this checkbox, you must specify a server name.

Full Text Index documents automatically: If you select this checkbox, all data loaded into the Content Manager OnDemand server is run through the full text indexer.
Server Name: Specify the Full Text Index (FTI) server name using the following format:server_name,port_number. For server_name, enter the address of your FTI server; for example, domain.example.com. For port_number, enter the port number used by the FTI server to listen for requests.

No

Select this checkbox if you do not want to run the data through the full text indexer.

Encryption

Specifies whether Content Manager OnDemand encrypts the physical documents at rest that belong to this application group. Physical documents at rest generally refers to document data that is located in persistent storage such as disk or tape.

Yes: Select this checkbox if you want to encrypt the documents in this application group.
No: Select this checkbox if you do not want to encrypt the documents in this application group. The default is No.

Create/Use new style date/time field types in place of existing old style date/time field types

Select this checkbox if you want Content Manager OnDemand to apply the new style introduced in Content Manager OnDemand Version 9.0 to Date, Date/Time, or Date/Time (TZ) fields that were created prior to Content Manager Content Manager OnDemand Version 9.0 (known as old style).

The new style for Date, Date/Time, or Date/Time (TZ) fields increases the range of dates. After you update the application group to use the new style, you cannot do the following tasks:

Create Date, Date/Time, or Date/Time (TZ) fields with the old style
Access data in the application groups with Content Manager OnDemand clients older than Version 9