System Configuration Diagram

  Tablespace sizes were increased to support the Injection rate.
  Scripts to create the DB are included in the FDA.

  The load program was not modified

  The following beans: PartEnt, ComponentEnt, AssemblyEnt, BomEnt and
  LargeOrderEnt in the Manufacturing Domain, ItemEnt in the Orders Domain,
  and SupplierCompEnt and SupplierEnt in the Supplier Domain were
  accessed using READ_COMMITTED which is Cursor Stability (CS) for DB2.
  The remaining beans were accessed using
  translates to DB2 isolation level of Read Stability (RS)
  
  The ItemEnt bean was cached for 20 minute intervals by setting
  concurrency-strategy to ReadOnly and
  read-timeout-seconds to 1200
  in bea-orders.xml deployment descriptor.

  To ensure database durability, RAID 1 (mirror disks)
  was used for the database files and logs on
  the three Sun StorEdge 3510 arrays.
  
  Each application server has a pair of mirrored disks (using onboard
  controller) to provide durability for all the
  server logs and filestore for JMS persistence.

  An 80 minute run at an injection rate of 4000 increased storage by 4234 MB
  This extrapolates to 74 GB of storage for a 24 hour run.
  The database is configured with 4380 GB of storage.
  Each Sun StorEdge 3510 FC Array was configured as a single RAID 1
  logical drive.

  BEA WebLogic 9.2 uses pass-by-value as required by the EJB Specification.

Supplier  Description                                Product No.          Qty
--------  ----------------------------------------   ------------------   ---
Sun       Sun Blade 8000 Chassis                     A81-AZ                1
Sun       20-port GbE Network Express Module         X5040A-Z              2
Sun       Sun Fire X8400, 4x2.6 GHz 885, 32 GB       X5063A-Z             10
Sun       73GB 10K RPM 2.5" SAS Disk                 XRB-SS2CD-73G1-KZ    20
Sun       Solaris 10 6/06  DVD KIT                   SOLZ9-10EC9A7M        1
Sun       Americas Domestic NEMA L6-20P Power cord   X5044A-Z              6
Sun       SunSpectrum Upgrade: 3YGOLD, 24x7          W9D-A81-24-3G         1

Sun       Sun Fire E6900 1.5GHz Bundle               SYS6900B-4-1500       1
Sun       Unibrd: 4 USIV+ @ 1.5 GHz w/32GB           US4BRD-484-1500       5
Sun	  D240 Media Tray			     540-4523		   1
Sun       PCI I/O Assembly SF Midrange Servers       4051A                 1
Sun       Sun GigaSwift Network Adapter              X4150A-2              8
Sun       Sun StorEdge 2 GB Dual FC Adaptor          SG-PCI2FC-QF2-Z       2
Sun       Sun StorEdge Dual GB/Dual SCSI             X4422A-2              2
Sun	  AC Power Cable Option			     X3800A                1
Sun       Solaris 10 1/06 Media KIT                  SOLZ9-10BC9A7M        1
Sun       SF E6900 O/S Upgrade: 3YGOLD, 24x7         W9D-E69-24-3G         1
Sun       SF USIV+ BD OS UPG 3YR GOLD, 24x7          W9D-S4BDPLUS-24-3G    6

Sun       Sun StorEdge 3510, 12 x 146GB, 1 RAID      XTA3510R01A1R1752     2
Sun       Sun StorEdge 3510, 12 x 73GB, 1 RAID       XTA3510R01A1R876      1
Sun       SunSpectum Upgrade: 3Y GOLD, 24x7          W9D-SE3510-24-3G      3

Sun	  Sun Fire X2100 	 		     A75-LFZ1-H-1GB-FA8    1
Sun	  DVD-ROM Drive				     X8082A-Z		   1
Sun	  Localized Power Cord 			     X311L	           1
Sun       17" Entry Color Monitor                    X7201A                1
Sun       USB Keyboard                               320-1271              1
Sun       USB Mouse                                  320-2632              1
Sun       SunSpectrum Upgrade: 3YGOLD, 24x7          W9D-A75-24-3G         1

BEA       BEA WebLogic Server 9.2 License,  Advantage Edition             40 
BEA       3-year 24x7x4 Support for WebLogic Server                       40

IBM       DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR  D518GLL            48
          LIC+SW MAINT 12 MO
IBM       DB2 UDB ENTERPRISE SERVER EDITION PROCESSOR  E00BILL            96
          SW MAINT RNWL 1 ANNIV

  The submission used round-robin DNS for load-balance of
  all network requests. The DNS server was hosted
  on the database server.
  
  This submission used the xerces implementation 2.6.2 provided
  with WebLogic 9.2

The only errors in the driver log files were those that are normally generated
by this benchmark.

DB2 uses "Soft" checkpoint to ensure that no updates remain unflushed for
longer than the allowed time.

When DB2 UDB Server changes a database table with an update, insert, or delete
operation, the change is initially made in memory, not on disk. When there is
not enough space in the memory buffer to read in or write additional data
pages, DB2 UDB Server will make space by flushing some modified pages to disk.
Modified pages are also written to disk as part of the "Soft" checkpoint to
ensure that no updates remain unflushed for longer than the allowed time.
Before a change is made to the database, it is first recorded in the
transaction log. This ensures that the database can be recovered completely
in the event of a failure. Using the transaction log, transactions that
started but did not complete prior to a failure can be undone, and
transactions recorded as complete in the transaction log but not yet written
to disk can be redone.

DB2 UDB uses a write-ahead-logging protocol to guarantee recovery. This
protocol uses "Soft" checkpoint to write least-recently-used database
to disk independent of transaction commit. However, enough log information to
redo/undo the change to a database pages is committed to disk before the
database page itself is written. This protocol therefore renders checkpoint
unnecessary for DB2 UDB.