Creating a FileNet P8 domain

You create a FileNet P8 domain by using Enterprise Manager; a GCD is created automatically if one does not already exist. Thereafter, you can add additional servers to an existing FileNet P8 domain by running the installation program again on a server that is a member of the J2EE domain in which the FileNet P8 domain resides. See IBM FileNet P8 Platform Installation and Upgrade Guide for instructions on installing Content Engine.

GCD Security

The GCD is stored in a database, and contains a security descriptor that controls access to specific GCD objects. Access to the GCD table is a function of how access to the database is controlled.

See Help for Security for more information about the FileNet P8 domain's association with its authentication provider.

Backup and recovery considerations

If the database server hosting the GCD database is totally lost, the system administrator cannot reach the FileNet P8 domain; therefore, it is important to back up the GCD database. See Back up Content Engine for more information.

With Love,
Pravakar Kumar
http://pravakar115.blogspot.co.uk

Global Configuration Data

The heart of a FileNet P8 domain is its Global Configuration Data, or GCD, which defines Content Engine servers and resources that reside within the domain. Specifically, the GCD contains descriptive and location information for:

Sites: A site represents a geographical location where resources are well connected via a fast, reliable LAN. Object stores, storage areas, content cache areas, index areas, and virtual servers are all associated with an individual site. There is no functional limit to the number of sites a single FileNet P8 domain can contain. Sites are displayed in the Enterprise Manager domain node.

Virtual Servers: A virtual server is the logical service point that Content Engine clients interact with. You can map a virtual server to one or more server instances. When a virtual server contains multiple server instances, client requests are load-balanced across the set of server instances through the J2EE application server's clustering capabilities, or by using a hardware load balancer, providing scalability and high availability. In either case, applications accessing the virtual server are unaware of the number or type of server instances that reside behind it. There is no functional limit to the number of virtual servers a single FileNet P8 domain can contain. Virtual servers are displayed in the Enterprise Manager sites node.

Server Instance: A server instance is an individual J2EE application server instance. Multiple server instances, each running in its own Java™ Virtual Machine (JVM), can be hosted on a single physical server. (This is common when large multiprocessor servers are used.) Content Engine clients do not interact directly with a server instance; logically, clients always go through a virtual server. There is no functional limit to the number of server instances a single FileNet P8 domain can contain. Virtual servers and server instances are created in the GCD when you deploy the Content Engine software on an application server, but are not removed from the GCD when the Content Engine software is undeployed from an application server—users must delete virtual servers manually from Enterprise Manager. Server instances are displayed in the Enterprise Manager virtual servers node.

Object Stores: 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. There is no functional limit to the number of object stores that a single FileNet P8 domain can contain. Object stores are displayed in the Enterprise Manager object stores node.

Index Areas: An index area contains one or more indexes, which perform full-text searches against documents in an object store. There is no functional limit to the number of index areas that a single FileNet P8 domain can contain. Index areas are displayed in the Enterprise Manager sites node.

Storage Areas: Storage areas are containers for content storage, and can be configured for file storage, fixed storage, or database storage. There is no functional limit to the number of storage areas that a single FileNet P8 domain can contain. Storage areas are displayed in the Enterprise Manager sites node.

Content Cache Areas: A content cache is a disk area that contains copies of content recently accessed through a Content Engine server. Typically used in a geographically distributed environment, it enhances response time when retrieving content. There is no functional limit to the number of content cache areas that a single FileNet P8 domain can contain. Content cache areas are displayed in the Enterprise Manager sites node.

AddOns: After creating a new FileNet P8 domain, add-on features can be loaded into the GCD, making them available to any object store in the domain. See Add-on features for more information about the classes and properties added to the object store during this process. Add-on features are displayed in the Enterprise Manager domain node.

Marking Sets: By using markings, access to objects can be controlled based on specific property values. Marking sets are displayed in the Enterprise Manager domain node.

Fixed Content Devices: A fixed storage area is a file storage area with a connection to an independent software vendor's fixed content device providing additional storage capacity and security. The Fixed Content Device is an GCD entry representing the fixed content device. One or more fixed storage areas can share a single fixed content device. Fixed content devices are displayed in the Enterprise Manager domain node.

With Love,
Pravakar Kumar
http://pravakar115.blogspot.co.uk