IBM FileNet P8, Version 5.2.1            

FileNet P8 domain structure

The FileNet® P8 domain contains the entities that represent the Content Platform Engine physical resources (such as object stores) as well as the Content Platform Engine servers that provide access to those resources.

Although there is no limit to the number of entities a single FileNet P8 domain can contain, there are practical and performance issues to be considered. These issues, if applicable, are discussed in the help topics that are related to each entity.
Site
A site is a geographical location where resources are connected through a local area network. Object stores, storage areas, content cache areas, index areas, and virtual servers are associated with an individual site. As virtual servers, server instances, and other resources are added to the domain, they are assigned to the default site, unless a different site is explicitly specified. A user with system administrator privileges can change the site that is used as the default.
Virtual server
A virtual server is the logical service point that Content Platform Engine clients interact with. Virtual server objects are created dynamically during system initialization and startup that is based on the configured topology of the Java™ EE application server. (The topology is the physical or logical mapping of the location of networking components or nodes within a network.) A virtual server can contain one or more server instances. Applications accessing the virtual server are unaware of the number or type of server instances that reside behind the virtual server.
Server instance
A Content Platform Engine server instance is an individual Java Platform, Enterprise Edition (Java EE) application server instance. Multiple server instances, each running in their own Java virtual machine (JVM), can be hosted on a single physical server. (Multiple server instances are a common configuration when large multiprocessor servers are used.) Content Platform Engine clients do not interact directly with a server instance; logically, clients always go through a virtual server. Virtual servers and server instances are created in the global configuration database when you deploy the Content Platform Engine software on an application server, but are not removed from the global configuration database when the Content Platform Engine software is removed from an application server.
Database connection
A database connection combines the connection information to the database, that is the JNDI XA data source and the JNDI non-XA data source and the site information. The connection information is used during the creation of other objects like object stores and isolated regions.
Object store
An object store is a repository for storing objects (such as documents, folders, and business objects) and the metadata that defines the classes and properties of objects.
Index area
An index area is a container for one or more indexes, which are used to perform full-text searches against documents in an object store.
Storage area
A storage area is a container for content storage, and can be configured for file storage, fixed storage, or database storage.
Fixed content device
A fixed content device is an external (non-FileNet P8) storage device from an independent software vendor. This device can be associated with a FileNet P8 fixed storage area.
Content cache area
A content cache is a disk area that contains copies of content recently accessed through a Content Platform Engine server. Typically used in a geographically distributed environment, it enhances response time when retrieving content.
Add-on feature
An add-on feature is a module that contains custom metadata and data that support extensions to core Content Platform Engine features. See Add-on features for more information about the classes and properties added to the object store during this process.
Marking set
A marking set provides a way to define a level of security on objects in addition to the normal FileNet P8 security model. By using markings, access to objects can be controlled based on specific property values.


Last updated: October 2015
aem_domain_structure.htm

© Copyright IBM Corporation 2015.