The following files are required by the application and should be present in the 'org.jaffa.config' package. They are packaged in the 'jaffa.jar' distributable. To customize a configuration paramter, modify a copy of the file and ensure that the copy appears in the classpath before jaffa.jar

• framework.properties - has all the configuration settings for the application. This provides the location of the other configuration files. It has various settings for configuring the Persistence and Presentation layers. Additionally, there are settings for configuring the Dynamic Rules Engine and Security. There are a host of other miscellaneous settings too.

• dtd.properties - is used for mapping the Public Ids specified in the DTDs to the DTDs stored locally. This eliminates the need to validate XML by connecting to the outside world for accessing the appropriate DTDs.

• locale.properties - lists the layout/parse formats for DateOnly, DateTime, Integer, Decimal and Currency fields. These formats are used for internationalization

The following are some of the other configuration files required by an application

• business-functions.xml - lists the business-functions for the application. This is used for providing role-based access to components executing certain business-function(s). This should always be present in the ‘resources’ package.

• roles.xml - lists the the different roles and the business-functions available to each role. It supports the chaining of roles. This is used for providing role-based access to components executing certain business-function(s). Its location is specified by the framework.properties setting ‘framework.security.policy.url’. The default location is the ‘resources’ package.

• components.xml - lists the components for the application. It also lists the business-functions required for a component. This is used for providing role-based access to components executing certain business-function(s). Its location is specified by the framework.properties setting ‘framework.ComponentsFile’. The default location is the ‘resources’ package.

• validators.xml - lists the different validators available for the Dynamic Rules Engine. Its location is specified by the framework.properties setting ‘framework.rules.validators.url.list’. The default location is the ‘resources’ package.

• core-rules.xml - lists the core set of validation rules for an application. This file is used by the Dynamic Rules Engine. Its location is specified by the framework.properties setting ‘framework.rules.core-rules.url’. The default location is the ‘resources’ package.

• [variant]-rules.xml - lists the variant set of validation rules. There can zero or one such file for each variant. This file is used by the Dynamic Rules Engine. Its location is specified by the framework.properties setting ‘framework.rules.variations.directory’

• log4j.xml - is used by Log4J for configuring application logging. This file will only be used if specified by the framework.properties setting ‘framework.Log4JConfig’. The setting should also provide the location of the file.

• init.xml - is used by the JDBC Engine for providing the database information. It also provides location for the mapping files of the domain objects. Its location is specified by the framework.properties setting ‘framework.persistence.jdbcengine.init’