Template Version: %Z%%M% %I% %E% SMI



1. Introduction
   1.1. Project/Component Working Name:
	Berkeley Database 4.5.20

   1.2. Name of Document Author/Supplier:
	Karen Langford 
	
   1.3. Date of This Document:
	05/24/2007

   1.4. Name of Major Document Customer(s)/Consumer(s):
	1.4.1. The PAC or CPT you expect to review your project: NA
	1.4.2. The ARC(s) you expect to review your project:
	1.4.3. The Director/VP who is "Sponsoring" this project: 
               William Franklin
	1.4.4. The name of your business unit: Database Technology Group

   1.5. Email Aliases:
    	1.5.1. Responsible Manager: Masood.Mortazavi@sun.com
    	1.5.2. Responsible Engineer: Karen.Langford@sun.com
    	1.5.3. Marketing Manager: Rebecca.Hansen@sun.com
	1.5.4. Interest List: NA

2. Project Summary
   2.1. Project Description:

	Currently, the Berkeley Database (BDB) ships within a number of Sun products. 
	This ARC case is to establish BDB 4.5.20, the latest version of the Berkeley 
	Database, as an accepted database technology for product use within Sun, 
	including Solaris, and the Sun Java Enterprise System.

 	We are also looking for guidance on the correct way to uniquely name BDB's
	packages and installpath so that more than one version of BDB can exist on 
	the same platform.
 
   2.2. Risks and Assumptions:

 	Many products currently use prior versions of Berkeley DB. 
        These products may not be able to upgrade immediately to this new version of 
	Berkeley DB.  


3. Business Summary
   3.1. Problem Area:
	There are at least 20 Sun products that currently use Berkeley DB today. 
	We anticipate they will want to upgrade to this new release within the
	year.

   3.2. Market/Requester:
	There is no specific market.  The requester is the Database Technology 
	Group, with the support of the various Berkeley DB users (in particular 
	the NICP Software group).

   3.3. Business Justification:
	Allows our products to use the latest of Berkeley BDB technology which is
	centerally managed by DBTG.

   3.4. Competitive Analysis:
	This case does not change the competetive landscape in any real way; it 
	is a version update.

   3.5. Opportunity Window/Exposure:
	There is no real window that will close on us here, but the sooner we make 
	this version available to product groups the sooner they can move to this 
	new version.
  
   3.6. How will you know when you are done?:
	When DBTG makes an ARC approved BDB binaries available for use.

4. Technical Description:
    4.1. Details:
	Berkeley DB is a C-based, record-level database package.  It allows very 
	fast, vertically scalable, transactional access to persistent data.  
	It is already in heavy use within Sun; in particular it is the underlying 
	data store for Sun Java Directory Service.

	For more information on the new features of BDB 4.5.20 please see 

	if.4.5.20.html in the case directory

    4.2. Bug/RFE Number(s):
	NA
    
    4.3. In Scope:
	NA

    4.4. Out of Scope:
	NA
    
    4.5. Interfaces:
	The Berkeley Database is a third party product and according to our 
	licensing agreement the interfaces cannot be made available directly to 
	the customer. This has not changed. Any redistribution of the libraries

        must include the original Sleepycat/Oracle license agreement.
    
    4.6. Doc Impact:
	None.
    
    4.7. Admin/Config Impact:
	NA
    
    4.8. HA Impact:
	New in the Berkeley DB Release 4.5 is the non-stop upgrade feature - which 
	enables a replicated BDB system to be upgraded without downtime. Also new is
	the replication framework feature - which provides a pre-built and supported 
	set of functions for quickly building replicated or highly available systems.
 
    4.9. I18N/L10N Impact:
	NA
    
    4.10. Packaging & Delivery:
	For Solaris and Nevada: 
	Cluster id: SUNWCbdb
	Metaclusters: SUNWCXall, SUNWCall, SUNWCprog, SUNWCuser, SUNWreq
	Cluster name: BerkeleyDB-Base 4.2.52
	Packages: SUNWbdb, SUNWbdbj
	We will add packages for the new release.
    
    4.11. Security Impact:
	NA
    
    4.12. Dependencies:
	Solaris and Nevada
	Access Manager
	Directory Server
	Messaging Server
	Message Queue
	Mail Server
	Calendar Server
	Evolution
	PHP
	Flexline 600 & Virtual Storage Manager ( StorageTek )
	Identity Server
	Instant Messaging
	Mars Keystone
	Niagra / Rock SP
	N1 Sun Cluster
	N1 Grid
	Portal Server
	NSS
	Open Office
	OPL 
	StarOffice
	WPSync
	Sendmail
	Solaris SNMP Agent
	CDE Tooltalk
	Solaris Encryption Framework
	SJS Web Server

5. Reference Documents:
	Please see the docs folder under inception.materials.

6. Resources and Schedule:
   6.1. Projected Availability:
	September 1, solely based on time required to garner ARC approval.

   6.2. Cost of Effort:
	Estimated at 3 person months.	

   6.3. Cost of Capital Resources:
	Negligble.

   6.4. Product Approval Committee requested information:
   	6.4.1. Consolidation or Component Name: Software

	6.4.3. Type of CPT Review and Approval expected: Standard

        6.4.4. Project Boundary Conditions:
		- Must be delivered as Solaris packages, Linux RPMs, 
		Windows zip, and HP depots.
		- Must be delivered in time for next edition of Sun 
		Java Enterprise System.

	6.4.5. Is this a necessary project for OEM agreements: No

	6.4.6. Notes: NA

	6.4.7. Target RTI Date/Release:	September 1, 2007.

	6.4.8. Target Code Design Review Date:
		There will be no code review, this is 3rd-party code.

	6.4.9. Update approval addition: No additions.

   6.5. ARC review type: Standard
 
7. Prototype Availability:
   7.1. Prototype Availability:	Berkeley DB 4.5.20 is available today.

   7.2. Prototype Cost:	None