System Configuration Diagram

  Tablespace sizes were increased to support the Injection rate.
  Scripts to create the DB are included in the FDA.
  Table and index initrans were modified.
  The M_INVENTORY, M_WORKORDER and M_PARTS tables were horizontally partitioned.
  Automatic segment space management was used for all tablespaces.
  System managed undo was used.
  Table locks were disabled during the run using disable_locks.sh script.

   The load program was not modified.

  The following Beans were deployed in READ_COMMITTED mode as per the
  benchmark requirement:
  Mfg      - AssemblyEnt, BomEnt, ComponentEnt, LargeOrderEnt, PartEnt
  Orders   - ItemEnt
  Supplier - SupplierCompEnt, SupplierEnt
  
  All other beans were deployed using pessimistic locking mode such that all
  selects including finders are issued with a FOR UPDATE clause in select
  statement:
  Corp     - CustomerEnt, CustomerInventoryEnt
  Mfg      - InventoryEnt, WorkOrderEnt
  Orders   - OrderEnt, OrderLineEnt
  Supplier - POEnt, POLineEnt, SComponentEnt
  Util     - SequenceEnt
  
  The ItemEnt bean was cached for 20 minute intervals by setting:
  read-only to true, and
  time-to-live to 1200000 (ms)
  in orders-toplink-ejb-jar.xml deployment descriptor.

  Data and redo logs were written to RAID 1 volume to provide durability.
  The application servers have pair of mirrored disks (using ZFS) to provide
  durability for server logs and JMS persistence filestore.

  A 80 min run at Injection Rate of 440 increased storage by 1.1 GB. This
  extrapolates to 19.8 GB for 24 hours. The system is configured with 730 GB of durable storage.

  Oracle Application Server 10g uses pass-by-value as required by the EJB
  specification.

Supplier  Description                                   Product #          Qty
--------  -------------------------------------------   ----------------   ---
                              BILL OF MATERIALS
--------------------------------------------------------------------------------


Supplier        Description                                     Product No.             Qty
--------        ----------------------------------------        ------------------      ---
Sun             Sun Fire T2000, 1x1.2 GHz T1, 32 GB             T20Z108B-32GA2D         2
Sun             Solaris 10 6/06 Media KIT                       SOLZ9-10EC9A7M          2
Sun             SunSpectrum Upgrade: 3Y GOLD, 24x7              W9D-T2000-8-24-3G       2
Sun             QLogic QLA2342-SUN PCI/PCI-X                    375-3363                1
Sun             17" Entry Color Monitor                         X7147A                  1
Sun             PS/2 Keyboard & Mouse                           320-1261                1
Netgear         24 port Gigabit ethernet switch                 GS624T                  1
Sun             73-GB 10000 RPM 2.5 inch SAS Disk Drive         XRA-SS2CD-73G10KZ       2
Sun             Sun StorEdge 3510, 12 x 146GB, 1 RAID
                                                    SE3510-12X146/15K-1RAID-AC-RR       1
Sun             SunSpectum Upgrade: 3Y GOLD, 24x7               W9D-SE3510-24-3G        1
Oracle          Oracle Database 10g Release 2 Enterprise Edition, 
                Partitioning, Per Processor         
                (v10.2)						             		2*	     
Oracle          Oracle Database Server Support Package for 3 years
                (Incident Server Support) 24x7x4                               		1
Oracle          Oracle Application Server 10g Release 10.1.3.2, 
                Java Edition, Per Processor       		                        2*
 	        (v10.1)
Oracle          Oracle Application Server Support Package for 3 years	     		1	
	        (Incident Server Support) 24x7x4 

(*2 = 0.25 * 8)  Explanation:  For a Sun UltraSPARC T1 processors with 4, 
6 or 8 cores at 1.0 gigahertz or 8 cores at 1.2 gigahertz for only those 
servers specified on the Sun Server Table which can be accessed at
http://oracle.com/contracts, shall be determined by multiplying the total 
number of cores by a factor of .25.

  The xerces implementation version 2.6.2 from xml.apache.org was used as it
  comes packaged with Oracle Application Server 10g.
  
  The driver used the following jndi.properties:
  java.naming.factory.initial=com.evermind.server.rmi.RMIInitialContextFactory
  java.naming.provider.url=ormi://MT:23791/SPECjAppServer
  java.naming.security.principal=oc4jadmin
  java.naming.security.credentials=welcome
  oracle.j2ee.rmi.loadBalance=lookup

The only errors in the driver error logs are the application errors
generated by this benchmark.

On the database, incremental checkpointing ensured that no buffer will
remain dirty (in the cache) for more than the allowed time.

Oracle Application Server 10g Release 10.1.3.2 implements Recoverable Last
Resource Commit (RLRC) optimization where one and only one SinglePhaseResource
participates in a global transaction with one or more XAResources. This is
accomplished by emulating an XAResource to represent the 1PC resource. The
transaction manager takes the following steps when it receives a request to commit
a global transaction that includes one emulated XAResource:
1. It invokes a prepare call on each of the 2PC resources.
2. If all of the 2PC resources are successfully prepared, then commit (one-phase)
is called and the commit record is written to the commit-log, on the emulated XA
resource (database) as part of the local transaction.
3. If the 1PC on the emulated XA resource completes successfully, then the
transaction manager calls commit on each of the 2PC resources.
or:
If the 1PC on the emulated XA resource fails, then the transaction manager queries
the commit-log for transaction outcome. If the record exists, 2PC resources are
committed, otherwise 2PC Resources are aborted.
Transaction outcome after a single point of failure is guaranteed by the presence of
the commit-record in the commit log, indicating a successful transaction completion;
while a missing commit-record signifies abort. The commit record is deleted lazily
after the global transaction has committed.

In conjunction with the RLRC implementation, the log-file location specified in the
transaction-manager.xml identifies the location where  the participating resource
managers are recorded. The commit record table name associated with an instance is
specified in the commit-record-table-name attribute, in the Connection-Factory
element of data-sources.xml.