[jboss-svn-commits] JBL Code SVN: r30600 - labs/jbosstm/workspace/whitingjr/trunk/performance.

[jboss-svn-commits at lists.jboss.org]

Author: whitingjr
Date: 2009-12-11 05:19:52 -0500 (Fri, 11 Dec 2009)
New Revision: 30600

Modified:
   labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt
Log:
Updated installation instructions.


Modified: labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt
===================================================================
--- labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt	2009-12-11 09:52:15 UTC (rev 30599)
+++ labs/jbosstm/workspace/whitingjr/trunk/performance/INSTALL.txt	2009-12-11 10:19:52 UTC (rev 30600)
@@ -7,12 +7,13 @@
 * Down load database client driver
 * Configure the database installation
 * Add vendor db library package.
+* Add method signatures for analysis.
 * Select command line options
 * Execute profiling for later comparrison.
 
-
     Each database driver is installed in a separate directory.
-   Create a directory (without spaces) for each database vendor.
+   Create a directory (without spaces) for the database vendor if it does not already
+   exist.
    ./libs/dbdrivers/<dbvendor>/
    Place the driver jar file in the. directory.
    
@@ -20,36 +21,36 @@
    and executing the profiling.
    
    Now configure the database connection details for the installation type.
-   Create a directory using the same <dbvendor> used in the previous step.
-   ./src/main/resources/properties/database/<dbvendor>/
-   Then copy the contents of the sample directory into the one just created.
-   for example
-   cp src/main/resources/properties/database/sample src/main/resources/properties/database/<dbvendor>/ 
+   You will find two properties files for each installation type. These allow multiple 
+   resources to be configured. Only two resources per vendor installation are supported.
    
    For each database vendor three types of installation are supported. Embedded,
-   co-located and remote. Rather than repeat vendor details for each installation
-   a common vendor properties file is used. This is used in addition to the installation 
-   property file.
-   common vendor properties
+   co-located and remote. The configuration details are repeated for each resource. 
+   This allows database by different vendors to be used concurrently. There is a  
+   common vendor properties file.
    ./src/main/resources/properties/database/<dbvendor>/db-profile.properties
-   and for a remote installation
-   src/main/resources/properties/database/<dbvendor>/database-locations/remote-db/db-installation.properties
+   each installation will have two files.
+   ./src/main/resources/properties/database/<dbvendor>/database-locations/<installation>/db-installation.properties
+   ./src/main/resources/properties/database/<dbvendor>/database-locations/<installation>/second-resource-installation.properties
+   By editing the 'db-vendor.method.xpaths.X' property you can select particular 
+   methods for summary information.
 
    Configuring the profiled classes for each vendor requires identifying the package name 
-   in the driver library. It is recommended you use a generic name to ensure most accurate
-   timings. for example, the MySQL driver package has two package domains
+   in the driver library. It is recommended you use a generic name to ensure most coverage
+   of the driver libraries. for example, the MySQL driver package has two package domains
    com.mysql and org.gjt
    This package is added to the 'db-vendor-profiling' property in the database 
    vendor common properties file. Multiple package names are supported using a comma
-   to separate each.
+   to separate each. Do not add a period and asterisk at the end. These are not required.
    
    Select an appropriate class for controlling the database during setup. Some vendors
    support sequences whereas others do not. If a class has not been provided then
    implement one using existing classes as guideline. You will need to
    extend org.jboss.jbossts.performance.persistence.vendor.AbstractVendorControl
+   The controlling of unique identities is handled by Hibernate. A technique for creating
+   identifiers independent of database vendor is used.
    
-
-    
-   
-   
-   
\ No newline at end of file
+   By editing this property you will control which methods have summary information generated.
+   ./build.properties - testcase.xpaths
+   This property is a csv. Notice between the class and method is a ':' colon. Use this 
+   instead of a period.