Administrating Vaults and Stores

3DEXPERIENCE apps store objects in a database that can be organized in subsets called vaults. Separating the database in vaults avoids reaching the data capacity inherent to database tables. For example, data stored in two vaults are separated in different database tables.

This page discusses:

Vaults

By default, the 3DEXPERIENCE platform is delivered with a few vaults (for example eService Production).

The choice of the vault occurs when an object is created. It can depend on the following elements:

  • The type of the objects.
  • The collaborative space where the object is created.
  • The operation that leads to the creation of the object (for example to make the difference between a standard creation or a creation for archiving).
It cannot depend on the object itself (for example on some of its attributes).

In most cases, the strategy for a user may consist in creating different vaults for different collaborative spaces. It does not correspond to one vault per collaborative space but vaults are created, when scalability requires it, to separate data for different projects in different vaults.

Important:
  • The fact that you have data in two vaults does not isolate the data. It is possible to create data referencing a data in another vault, you can operate a query on data without restricting the query to one specific vault.
  • To create a vault, the administrator must use MQL. The syntax is the following: add vault NAME [ADD_ITEM {ADD_ITEM}];.
  • You cannot choose the vault of aggregated objects as the vault is determined by the object aggregator.

Stores

3DEXPERIENCE apps also store files associated to some particular objects. The files are also stored in different stores. A store is a logical partition that may lead to different physical implementations available in different geographies with mechanisms to synchronize the files. The reason for separating the files in different stores is mainly for confidentiality purposes.

Note: By default, the 3DEXPERIENCE comes with only one store (STORE).

To create a store, the administrator must use MQL. The syntax is the following: add store NAME [ADD_ITEM {ADD_ITEM}];.