Application Configuration Import and Export Targets

The application configuration information for the Cúram web client is stored as a series of XML and properties files in the server source directory. It is merged and loaded into the database at build time from where it is read by the client tier at run time.

The rules for merging are as follows:

• Files in the clientapps directory take precedence over files in the tab directory, regardless of component order. E.g: if a file named CaseHome.nav exists in the clientapps directory of any component of the application, then any files named CaseHome.nav which exist in the tab directory of any component are ignored.
• Files in the clientapps directory are selected (not merged) based on the component order. E.g: if a file name CaseHome.nav exists in the clientapps directory of components Custom1 and Custom2, and Custom1 is ahead of Custom2 in the component order, then the version of CaseHome.nav from Custom1 is used and the version from Custom2 is ignored.
• Files in the tab directory are merged according to the component order - provided that a corresponding file in a clientapps directory does not exist. E.g: if a file named SearchTab.nav exists in the tab directory of components CustomA and CustomB, but not in the clientapps directory of any component, then the contents of the two files are merged together.
  Note: Note that only OOTB Cúram components may use the tab directory to store application configuration files; this directory may not be used by custom components. Custom components may use only the clientapps directory for application configuration files.

One target controls the import and export of application configuration to and from the database:

inserttabconfiguration

Merges application configuration files from disk and inserts the data into the database. The default action of this target is to insert the application configuration data onto the database but it can also be used to:

• Merge the application configuration files and write the merged files to a directory on disk.

  If property dir.tab.merge is set then it denotes a directory into which the application configuration files from the various components of your application will be merged. In this mode, nothing is written to the database. E.g: build inserttabconfiguration -Ddir.tab.merge=C:/EJBServer/tabExtract

• Extract the application configuration data from the database and write it to a directory on disk.

  If property dir.tab.extract is set then it denotes a directory into which the application configuration data from the database will be extracted. In this mode the application configuration data is read from the database and nothing is written to the database. E.g: build inserttabconfiguration -Ddir.tab.extract=C:/EJBServer/tabExtract