Depending on the type of asset, you can re-create AddOns, re-create the object, or manually add Global configuration data assets.
Description | Represents a product extension to the core Content Platform Engine components. These extensions consist of properties and classes to support a specific feature. |
---|---|
Deployment Mechanism | ![]() ![]() |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides configuration information for the events dispatcher. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Auditing is the process of capturing specific content information
when a specific event occurs and storing the captured results in the
audit log. The CmAuditingConfiguration object is one component of the audit disposition process, which identifies and deletes entries in the audit log that are ready for deletion. The CmAuditingConfiguration interface is also known as the audit disposition thread. It is a background process that works with the CmAuditDispositionPolicy interface and the CmAuditProcessingBookmark interface to identify and delete record from the audit log. |
---|---|
Deployment Mechanism | FileNet® P8 does not have a tool that deploys auditing objects. Therefore, you must manually add auditing objects into the destination environment. Importing converted objects |
Dependencies | Deployment of an audit configuration object does not have any dependencies on other objects. |
Environment-specific data | Deployment of an audit configuration object does not have any environment-specific requirements. |
Description | Provides configuration information for Content Federation Service replication. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | None |
Description | Provides a local storage area for frequently accessed documents that are accessible over a LAN. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides configuration information for a content cache area. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides configuration information about the content storage parameters for a server or group of servers. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Represents a logical collection of sites, virtual servers, server instances, object stores, content storage areas, index areas, and content cache storage areas, and the Content Platform Engine services that enable these stores and the servers that host them, for a single instance of Content Platform Engine. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | You must create the domain in the destination environment before you can import Content Platform Engine objects. |
Description | Represents a connection to a third-party fixed content system that provides extra storage capacity and security. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Controls access to the Global Configuration Data (GCD). |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | IBM® Content Search Services is a
search engine that both reads and writes object index information
so that searches can be based on:
The CmTextSearchConfiguration (IBM Content Search Services configuration) object contains configuration information about Content Platform Engine server dispatcher and worker threads, which control the processing of IBM Content Search Services content indexing requests. |
---|---|
Deployment Mechanism | FileNet P8 does not have a tool that deploys IBM Content Search Services objects. Therefore, you must manually add IBM Content Search Services objects into the destination environment. Importing converted objects |
Dependencies | Deployment of an IBM Content Search Services configuration object is not dependent upon any other objects. |
Environment-specific data | Deployment of an IBM Content Search Services configuration
object is dependent upon the following environment-specific data.
|
Description | IBM Content Search Services is a
search engine that both reads and writes object index information
so that searches can be based on:
The CmTextSearchServer (IBM Content Search Services server) object contains the connection and configuration information for an IBM Content Search Services server. The CmTextSearchServer (IBM Content Search Services server) object is stored in the GCD and is associated with a particular site. Therefore, a CmTextSearchServer (IBM Content Search Services server) can be used only by object stores that are within the same site. |
---|---|
Deployment Mechanism | FileNet P8 does not have a tool that deploys IBM Content Search Services objects. Therefore, you must manually add IBM Content Search Services objects into the destination environment. Importing converted objects |
Dependencies | Deployment of an IBM Content Search Services server
object is dependent upon the following objects:
|
Environment-specific data | Deployment of an IBM Content Search Services server
object is dependent upon the following environment-specific data.
|
Description | Provides configuration information for the Image Services document import agent. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides configuration information that is used to access LDAP repositories. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, you configure the LDAP directory when you first install FileNet P8 software on the destination system. This configuration must align with the authentication provider defined in the application server that hosts Content Platform Engine. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides a collection of Marking objects that represent the possible values that can be applied to an object property. Each Marking object contains a set of access permissions that define who can assign that specific value to an object property, who can modify or remove that specific value, and, after it is assigned, who has access to the object it is assigned to. |
---|---|
Deployment Mechanism | You can use FileNet Deployment Manager to import and export marking sets. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Represents a set of services that are provided by Content Platform Engine to access and manage documents and other objects. Object stores are in a FileNet P8 domain, which can contain many object stores. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Identifies a specific isolated region in the workflow database. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | Typically, each environment has its own dedicated servers, which make it unnecessary to deploy the connection points. |
Description | Contains a number that identifies a specific isolated region. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides configuration information for publishing. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Provides the location of the Rendition Engine server and information about how to communicate to it. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Represents an individual Java™ Platform, Enterprise Edition (Java EE) application server instance. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | It is not necessary to deploy the server as it is created automatically by the Content Platform Engine server at start time. |
Description | Defines configuration options for all server caches that do not have object store-specific characteristics. The options apply to the following caches: code module cache, GCD cache, marking set cache, metadata cache, subject cache, and user token cache. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Represents a geographical location where resources are well-connected by a fast, reliable LAN. Object stores, storage areas, content cache areas, index areas, and virtual servers are all associated with an individual site. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | An administrator must create the site to match the geographical environment. |
Description | Contains configuration settings for SMTP services. The email sweep action handler that is included in the email services extensions add-on and any workflow system, if no SMTP server is locally specified, use the information that is stored in a CmSMTPConfiguration object. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this configuration. Instead, re-create the configuration in the destination domain. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | Represents global configuration values for the sweep framework. Sweeps are run as background threads on the Content Platform Engine. A Sweep Configuration object can be assigned to objects of the server hierarchy, such as: Domain, Site, VirtualServer, and ServerInstance. The first object that is encountered by the current server is the active instance. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this configuration. Instead, re-create the configuration in the destination domain. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Description | The CmTimeslot (time slot) object contains a schedule for a
text indexing or for an audit disposition background task. This object
has both start and duration information. You add CmTimeslot objects to a CmTimeslot List, which you set on a CmTextSearchConfiguration or a CmAuditingConfiguration object. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this configuration. Instead, re-create the configuration in the destination domain. |
Dependencies | Deployment of a time slot object is dependent upon the following
objects:
|
Environment-specific data | Deployment of a time slot object is not dependent upon any environment-specific data. |
Description | The CmTimeslotList (time slot list) object
contains a schedule for a text indexing or for an audit disposition
background task. This object has both start and duration information. You add CmTimeslot objects to a CmTimeslotList, which you set on a CmTextSearchConfiguration or a CmAuditingConfiguration object. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing time slot lists. Instead, re-create the list in the destination domain. |
Dependencies | Deployment of a time slot object is dependent upon the following
objects:
|
Environment-specific data | Deployment of a time slot list object is not dependent upon any environment-specific data. |
Description | Provides configuration information for trace logging. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | Typically, it is not necessary to deploy this object. By default, tracing is turned off, and in most situations, tracing is left off for performance reasons unless you are performing diagnostics on a problem. |
Description | Provides the logical service point with which Content Platform Engine clients interact. A virtual server can map to a single independent server instance or to a set of server instances. |
---|---|
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | The virtual server is created automatically by the Content Platform Engine server when the server is started. Therefore, it is not necessary to deploy the virtual server. |