About the database

Model data is maintained in a centralised multi-user database. Local working copies of parts of this data are then made available in each user's working directory. Simulation results are stored in the remote results root.

The general structure of the database is:

• the database contains one or more Model groups
• Model groups can contain other Model groups, version controlled items, and data groups
• Data groups can contain other data groups of the same type and database items of the correct type for the group

Some database items are version controlled items. These provide a safe and structured way of creating successive versions to test potential changes, or going back to a previous version and branching to explore other what if scenarios. Other model data, such as themes or switch controllers, is stored in Data Groups.

Groups can be embedded within groups to provide structured storage. Item names can be up to 80 characters long, and must not be blank. Names can contain spaces.

The names of version controlled items must be unique within a database. All other names must be unique within that type and its parent. For example, two data groups of different types within a Model Group can have the same name, but two groups of the same type must have different names.

For information on how to import, update, create, open, rename, or delete a database item, see the Working with database items topic.

Each database has a version number. For example, a database created with version 2023.0 of the software will have a database version of 2023.0. You can choose which version of the database is to be used when you create a database. This can be useful if you collaborate with other users who do not work with the same version of IWLive Pro Operator Client as you.

Notes:

• If you work with a database that is older than the version of the software you are using, for example, database version 2023.0 with software version 2023.1, you may not be able to access all the new features that are available in the newer version of IWLive Pro Operator Client. The availability of a new feature depends on whether or not it requires database tables and fields, such as object properties or a database item, that are only available in the newer version of the database.

• You can update an older version of a database to a newer one. This lets you access all the features available in the newer version of the software. However, the updated database cannot be used, by you or any other user, in an older version of the software.

The version number of the currently selected database is displayed in the Explorer window.

The working directory is a directory where working copies of files are stored. Data for each database is stored in a sub-directory of the working directory, with the name of the sub-directory being the Unique Database Identifier for the database.

The data stored in the working directory is made up of local results files and other temporary working files.

Automatic clean up of unneeded files in the working directory will be carried out by default. You can turn automatic clean-up off, and you can manually clean up the working directory: see Cleaning the working directory.

The remote results root is a directory where simulation results are stored. The remote files root is used as the default data source file base for live data. The location of these roots is specified for each database: see Setting the remote results and files roots.

The configuration root is a directory where the configuration (IWO) file for an Oracle database is stored. If a configuration root is not defined, the IWO file will be stored under the working directory.

IWLive Pro Operator Client maintains a link between the database and the working directory via the IWO file. The file is created when the database is first opened.

To set the configuration root, see Setting the configuration root.