InfoSphere Enterprise Records, Version 4.5.1.3+              

InfoSphere Enterprise Records object stores

An IBM® InfoSphere™ Enterprise Records object store can act as a File plan object store, a record object store, or a combination of the two.

An object store can have more than one file plan and the object store can be configured with only one default plan at a time. The default can be changed by the Application Engine Administrator at any time. For more information on setting the default file plan, see the IBM FileNet® P8 Version 5.0 Information Center Working with documents > Working with records > File plans > How to... > Set the default file plan.

An IBM FileNet P8 object store is a repository of objects and a suite of accompanying storage and retrieval services.

For InfoSphere Enterprise Records, an object store can be any of the following:
File plan object store (FPOS)
A FPOS contains a file plan, which is a hierarchy of record management objects needed to classify records.
Records object store (ROS)
A ROS contains documents that you can declare as records.
Combined FPOS and ROS
A combined FPOS and ROS contains both the file plan and documents.
For best performance, use a database store as the content store for the FPOS.
Important: Do not use periods in the FPOS name. You will not be able to declare a record if a period is included in the object store name. For more information, see the IBM FileNet P8 Information Center topic Working with documents > Working with records > Records > How to... > Declare a record. The object store acting as the FPOS can use one or more ROSs in the same IBM FileNet P8 domain for records declaration.

In a production environment, optimize security by ensuring that only a limited number of Application Engine or Workplace XT users have access to the entities that make up your file plan in the FPOS.

You can choose between using a database store or file store as the content storage area, based on the anticipated size of objects. Content Engine retrieves small objects such as records objects (less than 1 MB in size) quicker from a database store. Record objects contain a reference to the documents and their content. Carefully plan which groups should be allowed to administer the object store (object store administrators) and which groups need general access rights to create, delete, or modify content. Setting security using groups helps create a more manageable environment.

Important: When creating a new FPOS, make sure you add the users and groups you assign Records Administrator privileges to in the FPOS to the object store administrators group.
Executing queries or running the Disposition Sweep process for a file plan that has a large number of record categories or record folders returns large data sets and can therefore result in errors if the database timeout is not set appropriately. For more information about timeouts configuration, see the following topics:


Feedback

Last updated: November 2010


© Copyright IBM Corporation 2010.
This information center is powered by Eclipse technology. (http://www.eclipse.org)