Description | Represents a product extension to the core FileNet P8 Content Engine components. These extensions consist of properties and classes to support a specific feature. |
Deployment Mechanism | There is no automated mechanism for exporting and importing this type of object. Instead, re-create the AddOn in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | Before you import assets for your application, you must configure the AddOns in the destination object store exactly as they are configured in the source object store. This step ensures that the AddOns will work correctly and that you will be able to upgrade them in the future. |
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 |
Notes | None |
Description | Provides configuration information for the Content Federation Service (CFS) 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 |
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 |
Notes | None |
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 |
Notes | None |
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 |
Notes | None |
Description | Represents a logical collection of sites, virtual servers, server instances, object stores, content storage areas, index areas, and content cache storage areas, as well as the Content Engine services enabling these stores and the servers hosting them, for a single instance of Content 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 Engine objects. |
Description | Represents a connection to a third-party fixed content system that provides additional 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 |
Notes | None |
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 |
Notes | None |
Description | Provides configuration information for the IS 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 |
Notes | None |
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 provides defined in the application server that hosts Content Engine. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | None |
Description | Provides a collection of Marking objects that represent the possible values that can be applied to an object property. Each Marking objects 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, once it is assigned, who has access to the object it is assigned to. |
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 | Represents a set of services provided by Content Engine to access and manage documents and other objects. An object store resides 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 |
Notes | None |
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 Process Engine servers which makes it unnecessary to deploy the connection points. |
Description | Contains a number identifying 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 |
Notes | None |
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 |
Notes | None |
Description | Provides the location of the Rendition Engine server and information on 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 |
Notes | None |
Description | Represents an individual J2EE 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 | You do not need to deploy the server as it is created automatically by the Content Engine server at startup 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 |
Notes | None |
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 | 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, there is no need to deploy this object. By default, tracing is turned off, and in most situations should be left off for performance reasons unless you are performing diagnostics on a problem. |
Description | Provides configuration information for accessing and controlling a Verity server |
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 the logical service point with which Content 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. Instead, re-create the object in the destination environment. |
Dependencies | Not applicable |
Environment-specific data | Not applicable |
Notes | The virtual server is created automatically by the Content Engine server at startup. Therefore, you do not need to deploy the virtual server. |