A store is used to divide the database for improved performance. An object’s policy determines the store that is used for its files by default. A file store provides:
Multiple file stores are possible at different locations. For example, two or more file stores could contain CAD drawings. These stores might be located on the same host or on different hosts. An object's policy determines the store that is used for its files. A lock feature enables you to lock a store from the user for all write activities. Business objects with a policy using a locked store cannot have files checked in (written), but files can be checked out (read). This is useful when a store becomes obsolete. Stores are unlocked by default. For information on replacing a store with a new store, see Implications of Changing Stores. The system has few restrictions on the characters that can be used in the names of checked-in files. For more information, see About Administrative Object Names. Ingested stores may also be distributed via a copy or a link. Additionally, captured stores can be replicated with the system administrator either manually or programmatically updating all locations periodically. |