This topic alphabetically lists the properties that apply to the SnapLockFixedContentDevice class.
ClassDescription
object containing the fixed description (immutable metadata) of
the class from which this object is instantiated.
Settability of this property is read-only for most users. For users who have been
granted privileged write access (AccessRight.PRIVILEGED_WRITE
), this property is
settable only on create. After initial object creation, this property is read-only for all users.
Settability of this property is read-only for most users. For users who have been
granted privileged write access (AccessRight.PRIVILEGED_WRITE
), this property is
settable only on create. After initial object creation, this property is read-only for all users.
Settability of this property is read-only for most users. For users who have been granted privileged
write access (AccessRight.PRIVILEGED_WRITE
), this property is read/write. (The read/write access for those
users can only change if a change is made to the ACL on the object store that controls who has privileged write access to objects in that
object store).
FixedStorageArea
objects only.)The text is not locale-specific to the retrieving user except for the following classes:
DirectoryStructure
class has constants defined for the directory
structure type settings.
Valid settings are:
DIRECTORY_STRUCTURE_SMALL
(default setting): Specifies a small
directory structure. Small structures consist of two levels of directories
with 23 nodes at each level (total of 529 directories at the 2nd level).
Content is stored only at the 2nd level. DIRECTORY_STRUCTURE_LARGE
: Specifies a large directory structure.
Large structures extend the small structure with a third level of 23 nodes,
for a total of 12,167 directories at the 3rd level. Content is stored only at the 3rd level. null
(non-accessible content cache): For the ContentCacheArea
object, this property returns null
when the server cannot physically access the
content cache area and has not previously done so, and the CacheStatus property
setting is Closed
. Note that, although a null
value can be returned,
you cannot set this property to null
. For the ContentCacheArea
object, the directory organization of the
cache permits different servers to work on different directories, and thus allows
cache pruning to be scalable across multiple servers. All of the directories in the
cache contain roughly the same amount of recently added content (as a result of the
cache randomly selecting a directory for new content, and of pruning roughly
the same amount of content from each directory). Pruning, consequently, can occur
independently for each directory and yet still achieve the cache-wide result of
deleting the least frequently requested content.
Name
property of the object's class.
For CmAuditProcessingBookmark
and AuditDefinition
objects, this property is intended to identify client applications
that process the audit log.
For CmAuditProcessingBookmark
objects, this property, in support of the audit disposition feature, identifies the client that created the object.
For AuditDefinition
objects, this property identifies a set of audit definitions for a given client or client functionality.
For CmAuditProcessingBookmark
and AuditDefinition
objects, it is recommended that you set this property.
Specify a unique value to distinguish one client application from another.
Note, however, that the server does not prevent identical display names across multiple
CmAuditProcessingBookmark
or AuditDefinition
objects. Therefore, the client application is responsible for enforcing uniqueness.
For User
and Group
classes, the Id property takes the value of the
Security Identifier (SID) rather than the 128-bit GUID. The string representation of the
SID is in this example format: S-1-5-21-1559522492-2815155736-3711640725-55269
.
When Active Directory is used as the directory service for IBM FileNet P8, calls to
User.get_Id()
and Group.get_Id()
always return the current SID for the
principal, even if this user or group has only historical SIDs populating the Active
Directory server.
For a given property representation, the Id property has the following characteristics:
PropertyDescription.get_Id()
is equal to PropertyTemplate.get_Id()
, which is equal to PropertyDefinition.get_PrimaryId()
.PropertyDefinition.get_Id()
is not equal to PropertyDefinition.get_PrimaryId()
.PropertyDefinition.get_Id()
is not equal to PropertyDescription.get_Id()
.
For a newly created document object, you can override the Id property of its associated VersionSeries
object
before you save or check in the document for the first time.
com.filenet.engine.content.fcprovider.centera.CenteraFCP
com.filenet.engine.content.fcprovider.is.ImageServicesFCP
com.filenet.engine.content.fcprovider.fsb.SnaplockFCP
Settability of this property is read-only for most users. For users who have been granted privileged
write access (AccessRight.PRIVILEGED_WRITE
), this property is read/write. (The read/write access for those
users could only change if a change is made to the ACL on the object store that controls who has privileged write access to objects in that
object store).
For CmTextSearchIndexArea
objects, the root directory is used by IBM® Content Search Services servers
to store IBM Content Search Services indexes within a given index area. All the IBM Content Search Services
servers that belong to the same object store site that contains the index area must be given read and write
permissions to this directory. If the root directory that you specify does not exist on your machine, the server will create one.
If you assign an affinity group to an index area, only the IBM Content Search Services servers assigned to that affinity group need to have read and write permissions to the root directory of the index area; it is not necessary to assign permissions to the other servers in the site. When an index area is assigned to an affinity group, it is recommended that you use a root directory that is local for all the IBM Content Search Services servers in the affinity group. Doing so can improve performance because input/output operations are faster for local disks.
SiteSettings
objects associated with a fixed content device. Site settings provide
site-specific, configuration value overrides. For each fixed content device type with settings that can be
overridden, a corresponding subclass of SiteSettings
is defined with properties that, if populated,
will override the corresponding properties of the same name on the fixed content device object.
For an EMC Centera fixed content device, this property allows the PoolAddress property to be different, depending
on the site in which the Content Engine server is running. If the Content Engine server is running in a site
that does not correspond to one of the SiteSetting
objects, then the PoolAddress property on the
CenteraFixedContentDevice
object is used as the default.
For a FileNet Image Services fixed content device, this property allows the CSMCache property to be different
depending on the site in which the Content Engine server is running. If the Content Engine server is running
in a site that does not correspond to one of the SiteSetting
objects, then the CSMCache property
on the IMFixedContentDevice
object is used as the default.
For a NetApp SnapLock fixed content device, there are currently no properties that may be customized for a site.