Database Management

About the estos MetaDirectory Database

The estos MetaDirectory has an additional abstraction layer between the individual data stems created by replicators and the LDAP database. LDAP systems provide data in a tree structure. The introduced abstraction layer makes it possible to merge databases in the LDAP tree under one node. User groups can thus be offered data masters that are composed of different source databases.

Parts of the LDAP tree are architecturally fixed and cannot be modified. This concerns the nodes:

• dc=configuration
  Saves LDAP-specific configuration settings such as the LDAP schema
• dc=meta
  All locally generated databases will be automatically connected to this node.
  Databases from replicators that are not running locally will not be automatically connected to the LDAP tree.
• dc=phonebooks
  All activated phone directories will be automatically connected to this database node.
• dc=web
  All locally generated databases and all activated phonebooks will be automatically connected to this node.

Additional LDAP nodes are created automatically during the initial installation:

• dc=phone
  This database node is available for connecting LDAP-enabled terminals. Use the advanced LDAP node settings to configure the connection to an LDAP-enabled phone.

When an import replicator is executed for the first time, two subnodes are created for the corresponding data source, which contain the imported datasets. One node bears the name of the replicator and contains (after replication) the contact data available in the data source. The second sub-node has the name of the replicator - extended by the abbreviation "deleted_Items" and contains "deleted" records, i.e. records that have already been replicated once but were no longer present in the data source during a subsequent replication. The subnodes for deleted records are not displayed in the database management of the estos MetaDirectory Administrator.

Database management in estos MetaDirectory Administrator

In the estos MetaDirectory Administrator, you can manage the LDAP tree under "Database Management". On the left side the LDAP database structure is shown, on the right side on top all available datasets, below a short dataset information about the currently selected dataset.

LDAP database structure

All database nodes are displayed with the databases mounted in each case. Nodes that cannot be manipulated are displayed in light gray. Nodes can be added, removed and edited via the buttons as well as via a context menu. Datasets can be added or removed by drag and drop from the list of available datasets or with the buttons to the right of the LDAP tree. If you want to mount a dataset multiple times, hold down the control key while dragging and dropping.

This list shows next to all available datasets the type and a short status information. An icon on the left side shows if the dataset has already been mounted manually:

• Database not in use
• Database used once
• Database used multiple times

Database Information
The list displays the most important information about the currently selected dataset from the dataset list or LDAP tree. At a glance you can see how many contacts are stored, added, modified or deleted during the last replication. Additional status information is provided for troubleshooting and analysis.

Advanced LDAP Node Settings
The advanced LDAP node settings can be opened via the context menu or the "Properties" button. Information about the extended LDAP node settings.

Operations for Available Databases

Create a New Database
The replicator belonging to this data source will be started by selecting this feature.

	Locally created datasets are automatically mounted under the LDAP node dc=meta.
	Phonebooks are not searched in VirtualListView and PagedResults requests to the server. The corresponding phonebook connections do not support such extensions.