User Tools

Site Tools


Lure Property Files

Whenever Lure executes it firstly attempts to determine the appropriate Lure configuration and Lure connection property files to use.

These two files determine the runtime behaviour of the Lure program.

Lure run time properties are divided between these two property files as follows:

Lure Configuration File

The Lure configuration file contains properties that have to be common across all database environments on which the application is installed. Examples are which schemas to include and what folders and extensions to use for source files.

Lure Connection File

The Lure connection file contains properties that are specific to a particular database environment, i.e. the connection information for a database and what password(s) to use.

Lure Configuration File

For every Lure project there will always be only one configuration file with the following exact name:


The Lure configuration file is always located in the Lure root folder or in the Lure project folder (within Lure Stage). In fact, per definition a Lure root folder is a folder that contains a file with name main.lure-config.

All import and export operations act on the folder subtree within the Lure root folder, i.e. all exported or imported source code is stored within the root folder subtree.

Lure Connect File

Since a connect property file contains the information of how to connect to a specific database environment it follows that in general multiple connect files will be required per Lure project, one for each database environment. A Lure connect file has to have the extension lure-connect and has to be located in the Lure root folder (Lure project folder).

For example, to synchronize a Lure based database application between three environments, a development, QA and production environment, the following set of configuration files can be used:


Editing Lure Configuration Files

The best way to get started is to create a new Lure project within Lure Stage. The new project wizard will automatically create the connect and configuration files. To edit the files open either the connect or configuration file in the Lure Configuration Editor by selecting “Open” from the context menu.

See Getting Started.

Alternatively the Lure property files can be manually configured with any text editor. For this purpose two example property files can be found within the Lure installation folder in the “etc” subfolder. Copy these two files to your root/project folder and edit as required. The example property files contain detail descriptions of each property and how to configure it.

Locating property files at run time

Lure derives the location of the two property files and the root folder based on the file arguments passed to it. Using the first file argument as a starting point it searches up the parent folder path until it finds a folder that contains a file with name main.lure-config, identifying it as the root folder.

Lure expects the connect properties file(s) in the same (root) folder and will use any file with extension lure-connect. If more than one connect property file is used and present in the root folder (as in the example above) then additional information is required. Two options are available :

Option 1:

Use the --connect-file-name command line option when executing a Lure command (see Lure Command Line)

Option 2

Set the active connect file using the Lure command set-active-connect-file (see Lure Command Line). Once the active connect file is set, subsequent operations will use this connect file unless it is explictly overriden using the Option 1 approach, or until the active connect file is changed.

lure_property_files.txt · Last modified: 2013/07/29 18:27 by admin

Page Tools