Distribution includes:
lib:
  - Include all these jars in the consumer app's lib directory and add them to the build path.
  - The war should include all these jar under 'WEB-INF\lib' 
  - If deployed under JBOSS, DO NOT inlcude jta.jar within the war.
  - Note: When running unit tests outside the container, one may have to include app server
  related jars.

metadatamanager.jar
 - Include this in the lib folder of the web app project. 
 - This should be present along with other dependent jars under 'WEB-INF\lib' in the war
   
dbscript:
 - Use this script to create tables and sequences required for metadata manager
 - Configure the values specific to your database in createDB.prop	  

WebContent:
 web.xml
 	- Contains configuration for invoking initialization of metadata beans via spring.
 	- Data source reference include.
 Context.xml (sample)
 	- Required if running under Tomcat and defines the data source definition.
 jboss-web.xml (sample)
 	- Required if running under JBOSS and defines the data source definition.
 	(Assuming that the data source is defined in *-ds.xml file.)
 	
Dependent Libraries.txt:
	File which lists all dependent jar's version.
 	
licenses:
   Includes all license files.
   
Configuration:
1. If using JTA include 'MetadataManagerDB_JTA_Context.xml' in contextConfigLocation property of web.xml. Else use 'MetadataManagerDBContext.xml'
2. Configure DataSource.xml if jndi name is other than 'java:/comp/env/jdbc/metadataDB' or using explicit connection parameters.
3. Configure web.xml to load the 2 spring file and data source.
4. Configure appropriate web-app related file (e.g. Context.xml for Tomcat and jboss-web.xml for JBOSS) to configure Data source.
5. Metadata Manager jar requires log4j.xml to be configured by the app using it.
6. Ensure that the driver jar (e.g. ojdbc14.jar) is in the app server's classpath and NOT in the war file.
   Use it only at compile time. DONT include it in the war.