Vaults and Stores

You can create vaults to store simulation objects and metadata.

Vaults are containers that determine where simulation objects and metadata are stored in the 3DSpace database. Vaults do not store files. You can use multiple vaults to balance loads and organize information in the database. End users must select a vault when saving certain Process Composer entities, so the vaults should be defined in such a way that is meaningful to end users; for example, a vault may contain only data that pertain to a particular product.

For details about creating and configuring vaults, see the following topic in the ENOVIA Studio Modeling Platform MQL Guide:

Configuration and Development > 3DEXPERIENCE Open > Common Tools > MQL | Building the System Basics > Vaults

The physical files associated with simulation documents are saved in directories. These directories are defined by stores, which are database objects that point to a particular file system path/directory.

For complete information about creating, modifying, and configuring stores, see the following topic in the ENOVIA Studio Modeling Platform MQL Guide:

Configuration and Development > 3DEXPERIENCE Open > Common Tools > MQL | Building the System Basics > Stores

The default store directory used by Process Composer is

collaboration_server_dir\Apps\STORE\

You typically should reconfigure the default store path used for Process Composer files. For details about how to move the store directory or create a new store for Process Composer, see the ENOVIA Studio Modeling Platform MQL Guide.

When defining new stores for Process Composer, you must create captured stores.