Metamerge logo
Search

Advanced Search
*
*
*
* HOME DOCUMENTS & RESOURCES DOWNLOADS EARLY TECH ACCESS SUPPORT FAQ KNOWN ISSUES OLD VERSIONS
*

 

The Configuration File

The configuration file defines a server, and is a simple ASCII file. Your AssememblyLines, Connector Libraries, preferences etc. will be saved within it.

In the simplest case, you will have everything in one configuration file.  However, there are many situations where you would want to isolate parts of it:

  • Usernames and passwords in configured Connectors
  • Shared Components you want to reuse in several configuration files

Externalising fields like username and password

If the External Properties File is defined (you might need to restart the Admin Tool to make it active), an External Properties tab will be visible in the Configuration tab.

You can here define your own fields and give them values.  These values can be retrieved as dropdown values if you click on the label of a parameter field:  This is typically used to exclude some secret or site specific information from you configuration file. Check out Using External Properties section for more information on how to do this.

Note that External Properties have a key, but can have multi-line values.

Also note that the external properties are intended for externalising certain configuration parameters as username, password, filename etc..  If you want to save more general parameters and make them available for your AssemblyLine, see Load and Save Task parameters 

 

Export, Import and Include

Configuration Files, AssemblyLines, Connectors, EventHandler etc. can be exported in order to be reused in other configuration files.  Export, Import and Include is available from the File Menu.

Export does not export recursively, so if you want to export an AssemblyLine you have to export all it's components.

Import  copies the contents of the target file or url into the active configuration file:  Later change in the target will not be reflected in the configuration file.

Include makes a link to an url (or a plain file), and each time the Server (or the Admin Tool) is started, it is included when the configuration file is read.  The parameter is first assumed to be an URL, and if it is illegal a filename is assumed. Note that the Include will not be done before next time you read in the AssemblyLine. 

Note that the configuration file's system properties, external properties and Java Libraries  are not included.

Include has two parameters:  Include First (IF) and Overwrite Current (OC).  Include First means that the file is included before the master configuration is read in.  This means that the master configuration file will win name conflicts. Overwrite Current is the opposite:  The master file is read in first and might be overwritten by the include file(s).

When the master configuration file is read, it will always overwrite existing defined components.  Use IF false and OC true in order to overwrite the master configuration. 

The following table describes the possible combination of OC/IF

Value Meaning
Both false Read in all other IF files as well as the master configuration, include this file but skip already defined components
IF False

OC True

Read in all other IF files as well as the master configuration, include this file and overwrite already defined components
IF True

OC False

Read in this include file and then the rest of the master configuration file. Ignore elements in the master configuration that have already been defined.
Both True Read in this include file first, and overwrite existing components (relevant if other configuration file have been included as well).  Then read in the master, overwriting existing components.
 

 

*
  Metamerge Integrator version 4.6 ©Copyright Metamerge AS 2000-2002 Last edited 2002-06-10 contact us