CLUSTERING: WHAT IS STORED WHERE

Clustering - What is stored where in UD6

UD6/CMtool driver is a direct replacement for whatever database is storing your Uniface Repository.

Uniface repository is always stored in a database - stating with Dbase III for Uniface 5 and 6, to SOLID for Uniface 7 and in Uniface 10 maybe you are storing the repository in SQLite. But UD6 stores your source code in easy to read XML files, in a 'directory tree'. This is a database, but the database is made up of readable text files. If you change the XML text file using a plain text editor, then you change the Uniface repository database instantly.

This is not an Import/Export format, and does not require any change to how you work within the IDF.

Here is the basic directory structure, by default most directories contain 1 file per Uniface object, however this can be altered. For more detail please see details further down this page.

sources

Container Directory

What is stored in each directory

Uniface sources are grouped together with like objects, and then 'split' into logical elements.

For example a Forms and Component Varaiables (registers) go together, and are divided up by 'form name'.

The following sections describe the two most common ways of clustering the Uniface sources, followed by a detailed description of the mapping between the Uniface Relational Repository model and the UD6 Directory structure. Most of these settings can be altered using the UD6 configuration files.

One file per object

Global objects such as messages, and include procs can be stored individually or as a single file per library.

This example shows one file per message:

sources

One file per library/language

Global objects such as messages, and include procs can be stored individually or as a single file per library.

This example shows one file per library:

sources

Mapping between repository model and UD6 Directory Structure

The UD6 configuration file JOINS is a text file that controls how entities are mapped to files. Customers can change this, however it is recommended you discuss your changes with the support team.

The one exception to this is the global objects: include procs, global procs, global variables/global registers, messages, keyboard translation tables etc. Prior to Uniface 10, these are all stored in one table: USOURCE, and so one UD6 rule applies to all records - however you can enable 'newglobals' setting to use a fixed alternative clustering for USOURCE. In Uniface 10 this works a bit differently since the clustering is primarily controlled by the JOINS configuration file.

NEWGLOBALS V2, NEWMSG

include procs	one file per include proc
global procs	one file per global proc
messages	one file per library & language
keyboard translation table	one file per keyboard translation table
device table	one file per device table
control panel	one file per control panel

NEWGLOBALS

include procs	one file per library
global procs	one file per proc
messages	one file per library per language
keyboard translation table	one file per keyboard translation table
device table	one file per device table
control panel	one file per control panel

Read more about Uniface Version Control

1. UD6 Overview
2. Basic Theory of Configuration Management
3. Configuration Management applied to Uniface
4. Comparison: VC-Link (PVCS-Uniface Bridge)
5. Comparison: Uniface 8 (SCCI Bridge)
7. NLS Support Overview
8. UD6 Option Pack
9. System Requirements
10 UD6 Article Links
11 Uniface 8 Migration
12 XMLGREP Search and Replace
13 UD6 Performance Optimisation
14 MAKE Build Management
15. UD6IDE: Eclipse editor for Uniface 6, 7, 8 and 9
16. theu.info - You in Uniface

$Revision$ $Date$ [go to top]