Import/Export Properties

Every environment has a set of properties. It is possible to export all the parameters to a file and import these into another environment enabling you to.

The scope of the import/export is both the Database connection details and the parameters.

Exporting the properties will create a file <environment>.properties.

Database properties entries are preceded by “db.”

Environment properties are preceded by “env.”

Sqlplus module properties are preceded by “sqlplus.”

You can manually update this file. When adding parameters don’t forget these prefixes.

Importing a properties file is done by browsing to a file and select it.

The following rules apply:

  • New entries in the file are added to the environment.
  • Entries are case sensitive. “PARALLEL” and “parallel” are not the same.
  • Existing entries without a value are updated with the value in the file.
  • Existing entries with a value are ignored and remain intact.    
  • After importing the screen will show an overview of the imported Database and Environment parameters, the current value and the import status of it.

     When manually defining path settings in a properties file you need to escape backslashes and colons. c\:\\temp is a valid definition in the settings import file.

Rename Environment

Access the environment by clicking the name of it.

You can rename the Environment at any time by selecting this option from the Menu pane under SETTINGS and entering a new unique name.  

Remove Environment

Access the environment by clicking the name of it.

In the Menu pane click “Remove environment” from the SETTINGS group.

You cannot remove an environment while an application is running. Wait until the run has finished before removing the environment.
When removing an environment the RUNTIME metadata is cleared. It will not perform an uninstall of the applications and therefor you may still have the application tables and data in your database. To have a cleaned database either uninstall application before removing a project or clean the database manually afterwards.