The Fixed Content Devices General property page identifies general information about fixed content devices configured for the P8 domain, including configuration parameters.
See FileNet P8 Content Federation Services for Image Services Guidelines for more information about these values.
Attribute Name | Attribute Value |
IS User Name | String The CFS-IS Administrative User account that administers CFS for IS. This user name must already exist on the Image Services server. Enter up to 40 alphanumeric characters without spaces. The following characters are valid: " ' # [ ] ! < > ? * " |
IS Password/Confirm Password | String The password for the CFS-IS Administrative User, up to eight alphanumeric characters. |
IS Domain Name | String The Image Services domain name as defined in the Image Services Configuration Database (CDB). This value is stored as one part of the Service name configuration parameter in the fixed content device. Enter up to 20 alphanumeric characters. The <domain> portion of a two- or three-part NCH name of the associated Image Management System (IMS). NCH names are case-sensitive. NCH three-part names use form: <object>:<domain>:<organization>. The object name must be 1 to 40 bytes (bytes, not characters). If present, it always has the value of DefaultIMS. The domain name must be 1 to 20 bytes. |
IS Organization | String In most cases, this value is "FileNet." This value is stored as another part of the Service name configuration parameter in the fixed content device. Enter up to 20 alphanumeric characters. The <organization> portion of a two- or three-part NCH name of the associated Image Management System (IMS). NCH names are case-sensitive. NCH three-part names use the form: <object>:<domain>:<organization>. The object name must be 1 to 40 bytes (bytes, not characters). If present, it always has the value of DefaultIMS. The organization name must be 1 to 20 bytes. |
Timeout Seconds | Integer Timeout in seconds for retrieving content from IMS. If no timeout is desired, enter 0. |
CSM Cache | String Colon-separated three-part name of a local CSM cache. The names use the form: page_cache<n>:<domain>:<organization>. There must be no more than one local CSM cache name for a given value of <domain>:<organization>. Example: For domain "ntvaga" and organization "CompanyName," the names use the form page_cache<n>:ntvaga:CompanyName, where <n> is an unsigned decimal integer greater than or equal to 2. The default CSM cache on the document server is page cache number 1: for example, page_cache1:ntvaga:CompanyName. |
Attribute Name | Attribute Value |
Pool Address |
String PEA files control access of a client application to the Centera system. They map a given application to a Virtual Storage Pool. Using Virtual Storage Pools is a best practice recommended by EMC to separate storage from multiple applications, and for replication purposes. FileNet provides:
P8 Content Engine does not require a specific PEA file. By default, it uses the "anonymous" profile if none is specified. However, it does support passing a PEA file reference as part of the Centera connection string. The PEA file is generated using the Centera administration tool with the following settings and transferred to the Content Engine server: A PEA file example: Or, if the file is shared by more than 1 computer, the filename is a shared path name: 10.10.16.1,10.10.16.2?\\myhost\centera\my.pea An advanced technique is to write the XML (see About Centera > Pool Address Site Mapping XML Data for an example) to a UNICODE file (prefix the XML with sitemap), then set the Centera connection string to the file name (with ‘file:’ prefix). FileNet recommends placing the file in the P8 domain GCD share, since it's already shared and accessible from all Content Engine service computers in the P8 domain, has proper security settings, and should be part of regular system backups. For example, if the file ‘Map_Centera.xml’ is copied to the GCD share, set the connection string to ‘file:\\server\FNCE_server$\Map_Centera.xml’. |
Concurrent Readers |
Integer |
Max Reader Semaphore Wait Time | Used with the Maximum Reader Threads configuration value. If the maximum number of reader threads are currently busy reading from Centera, the new thread waits the duration of Max Reader Semaphore Wait Time (MRSWT) for a slot to open up (so it can perform a Centera read). If the full time expires, the thread fails the read request. |
Default Retention Pass Through | Boolean |
Never Delete Clips Or Content |
Boolean Note that referrals can still be deleted from the store (as well as content for reservations and annotations). Set this flag to 1 to run Centera in a write-once/delete-never mode, and still delete documents from the object store. |
BLOb Write Collision Avoidance Flag | Integer Used by the provider when creating Centera content, the value is combined with FP_OPTION_CLIENT_CALCID_STREAMING to form the options parameter of FPTag_BlobWrite. There are three possible [decimal] values:
|
BLOb Read Ahead Size | Integer A maximum buffer size, used by the provider to determine if the entire content BLOb should be read with a single call to FPTag_BlobRead. If the content size is less than or equal to the parameter value, the entire BLOb is read using a single call (a buffer of content size must be allocated), and the data is passed back using the callers 'stream' as requested. If the content size is greater than the parameter value, FPTag_BlobReadPartial reads only the data of the size requested by the caller (no buffer is created). |
Embedded Data Threshold |
Integer Note that this limit is per content element. The overall size of embedded data can exceed this limit if multiple content elements are embedded in a single Clip (up to the maximum size of the C-Clip). |
Audited Delete Prefix | String A prefix string to use with Centera audited delete. If the string is blank, audited delete is not invoked (FPClip_Delete is used). If the string is not blank, the string is not used as the prefix of the delete reason passed to FPClip_AuditedDelete (the document ID GUID is appended to the prefix string to form the complete delete reason text). |
Buffer Size | Integer |
Timeout | Integer TCP/IP connection timeout in milliseconds. The default value is 120000 ms (2 minutes). The maximum value is 600000 ms (10 minutes). |
Enable Multicluster Failover | Boolean When set to TRUE (1), multicluster failover is enabled; by default, the option is TRUE (1). To turn multicluster failover off for all capabilities, specify FALSE (0). |
Default Collision Avoidance | Binary To enable collision avoidance at pool level, set this option to TRUE (1); the default is FALSE (0). If you enable this option, the SDK uses an additional BLOb discriminator for read and write operations of C-Clips and BLObs. (BLOb Write Collision Avoidance Flag is used in tag write and only applies to BLObs.) |
Prefetch Size | Integer Helps determine the BLOb size. The default size is 32 KB. The maximum size is 1 MB. |
Maximum Connections | Integer The maximum number of sockets the SDK allocates for your application. Sockets communicate with the Centera clusters managed in each pool object. The default value is 100. The maximum value is 999. |
Retry Count | Integer The number of times an operation retries before reporting failure to the client application. The default value is 6. If the first execution of the function fails, the system retries the function six times. In total, the function executes seven times. The maximum value is 99. |
Retry Sleep | Integer The time to wait before the failed API function call retries, in milliseconds. The maximum value is 100000 ms. If no retry sleep has been defined, the SDK uses an exponential back-off scheme. The sleep time increases after each retry, starting at 1 second, and doubles after each retry |
Cluster Nonavailable Time | Integer The time in seconds that a cluster is marked as not available before retrying with a probe. Other clusters in the pool are used while the cluster is unavailable. The default value is 600 (10 minutes). The minimum is 0. The maximum is 36000 (10 hours). |
Open Strategy | Integer
|
Multicluster Read Strategy | Integer Choices are:
|
Multicluster Write Strategy | Integer Choices are:
|
Multicluster Delete Strategy | Integer Choices are:
|
Multicluster Exists Strategy | Integer Choices are:
|
Multicluster Query Strategy | Integer Choices are:
|
Attribute Name | Attribute Value |
Root Directory Path |
String |
Directory Structure |
Boolean
|
SnapLock User Name | String Username to connect to remote SnapLock device. |
SnapLock Password | String Password to connect to remote SnapLock device. |
Confirm Password | String Password to connect to remote SnapLock device. |
Device Address | String IP Address or host name of SnapLock device. |
Device Root Directory | String Used in SnapLock only, the absolute path on the SnapLock device starting from the volume name. In the example /snap_vol/v16, snap_vol is the volume name. Use this path for delete: setRetentionPeriod ONTAPI |