Configuring the Settings in Database Mode

Store Settings in the Database and/or the Local Save Image

This section explains how to store settings in the database and/or the local save image.

Select the Start > All Programs > MyProduct > Tools > Environment Editor V6R2012 command.

The Environment Editor appears.
Without selecting a variable, right-click on the variable list to see the contextual commands, then select the New Variable command.
In the Variable Editor dialog box, enter the variable name DSYSettingDir, enter a value, for example E:\users\MySettingsStoredinDB then click OK, save your changes and exit the Environment Editor.
Start a V6 session and log onto a security context.
For example:
```
VPLMDesigner.MyCompany.Standard
```
where Standard is the project name.
Because the Local Save mechanism is activated, selecting the Local Save command stores your settings in the local save image on your disk.
Exit the V6 session.
You will be prompted to either propagate your changes to the database, or save your session in a local save image. Propagating to the database stores your settings to the server and deletes the settings in the local save image. The settings in the server are now your reference settings. Saving your session in a local save image means that your reference settings are not on the server, but on your disk. The local save image contains a typical settings cache structure illustrated in What Is Settings in Database Mode?.
Note that the directory E:\users\MySettingsStoredinDB is empty: the Local Save mechanism has not yet been deactivated.
Start a new V6 session.
You will be prompted to retrieve your local save image (if you created one) containing your settings. If you do not, the settings in your local save image are deleted.

Store Settings in the Database and/or the Local Cache

This section explains how to store settings in the database and/or the local cache.

Select the Start > All Programs > MyProduct > Tools > Environment Editor V6R2012 command.

The Environment Editor appears.
Without selecting a variable, right-click on the variable list to see the contextual commands, then select the New Variable command.
To deactivate the Local Save mechanism, in the Variable Editor dialog box, enter the variable name PLM_DeactivateLocalSave, enter the value TRUE then click OK, save your changes and exit the Environment Editor.
Start a V6 session and log onto a security context.
For example:
```
VPLMDesigner.MyCompany.Standard
```
where Standard is the project name. This time, the Local Save mechanism has been deactivated and will not be available.
Exit the V6 session.
You will be prompted to propagate your changes to the database. Propagating to the database stores your settings to the server and keeps a copy in the local cache. The settings in the server are now your reference settings.

Note that the directory E:\users\MySettingsStoredinDB is no longer empty. It contains a typical settings cache structure illustrated in What Is Settings in Database Mode?.
The user settings are located in:
E:\users\MySettingsStoredinDB\Standard\usr.
The directory created to contain administration settings later:
E:\users\MySettingsStoredinDB\Standard\Adm
is empty.
Start a new V6 session and log onto a different security context.
For example:
```
VPLMDesigner.MyCompany.Engineering
```
where Engineering is the project name.

The user settings are located in:
E:\users\MySettingsStoredinDB\Engineering\usr.
The file .lastEnv contains the name of the most recently used project : Engineering.
To test that the settings have been stored on the server, start a new V6 session, select Tools > Options..., specify a few settings, then exit your session. Delete the contents of the local cache directory, then start a new V6 session.
The settings are retrieved from the server again and the contents of the local cache are updated.