From sacadmin Fri Apr 25 13:48:41 2008 Received: from sunmail5.uk.sun.com (sunmail5.UK.Sun.COM [129.156.85.165]) by sac.sfbay.sun.com (8.13.8+Sun/8.13.8) with ESMTP id m3PKmeUX005652 for ; Fri, 25 Apr 2008 13:48:41 -0700 (PDT) Received: from nwk-avmta-1.SFBay.Sun.COM (nwk-avmta-1.SFBay.Sun.COM [129.146.11.74]) by sunmail5.uk.sun.com (8.13.8+Sun/8.13.8/ENSMAIL,v2.2) with ESMTP id m3PKmXGL013689 for <@sunmail2sca.sfbay.sun.com:lsarc@sun.com>; Fri, 25 Apr 2008 21:48:39 +0100 (BST) Received: from pmxchannel-daemon.nwk-avmta-1.sfbay.Sun.COM by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) id <0JZW00B05F512V00@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:48:37 -0700 (PDT) Received: from sca-es-mail-1.sun.com ([192.18.43.132]) by nwk-avmta-1.sfbay.Sun.COM (Sun Java System Messaging Server 6.2-3.04 (built Jul 15 2005)) with ESMTP id <0JZW006EBF51NQE0@nwk-avmta-1.sfbay.Sun.COM> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:48:37 -0700 (PDT) Received: from fe-sfbay-10.sun.com ([192.18.43.129]) by sca-es-mail-1.sun.com (8.13.7+Sun/8.12.9) with ESMTP id m3PKmbf4027374 for ; Fri, 25 Apr 2008 13:48:37 -0700 (PDT) Received: from conversion-daemon.fe-sfbay-10.sun.com by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) id <0JZW00901EQZGG00@fe-sfbay-10.sun.com> (original mail from Terrence.Miller@Sun.COM) for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:48:37 -0700 (PDT) Received: from [129.146.86.55] by fe-sfbay-10.sun.com (Sun Java System Messaging Server 6.2-8.04 (built Feb 28 2007)) with ESMTPSA id <0JZW0049GF4QRRE0@fe-sfbay-10.sun.com> for lsarc@sun.com (ORCPT lsarc@sun.com); Fri, 25 Apr 2008 13:48:27 -0700 (PDT) Date: Fri, 25 Apr 2008 13:48:26 -0700 From: Terrence Miller Subject: SMF integration for Java DB in Solaris [LSARC/2008/278 FastTrack timeout 05/02/2008] Sender: Terrence.Miller@sun.com To: lsarc Cc: Lars.Heill@sun.com, Knut.Hatlen@sun.com, Oystein.Grovlen@sun.com Reply-to: Terrence.Miller@sun.com Message-id: <4812439A.2080904@Sun.COM> Organization: Sun Microsystems MIME-version: 1.0 Content-type: multipart/mixed; boundary="Boundary_(ID_t6V/QbPbxQ7+bGuLEYUCmw)" X-PMX-Version: 5.4.1.325704 User-Agent: Thunderbird 2.0.0.6 (X11/20070802) Status: RO Content-Length: 7824 This is a multi-part message in MIME format. --Boundary_(ID_t6V/QbPbxQ7+bGuLEYUCmw) Content-type: text/plain; format=flowed; charset=ISO-8859-1 Content-transfer-encoding: 8BIT Template Version: @(#)onepager.txt 1.29 04/11/15 SMI 1. Introduction 1.1. Project/Component Working Name: SMF integration for Java DB in Solaris 1.2. Name of Document Author/Supplier: Øystein Grøvlen, Oystein.Grovlen@sun.com 1.3. Date of This Document: 2008-04-09 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: DBPAC 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Heidi Bergh-Hoff, Senior Director Heidi.Bergh-Hoff@sun.com 1.4.4. The name of your business unit: Software (Database Group) 1.5. Email Aliases: 1.5.1. Responsible Manager: Geir.Hoydalsvik@sun.com 1.5.2. Responsible Engineer: Oystein.Grovlen@sun.com 1.5.3. Marketing Manager: 1.5.4. Interest List: Staale.Deraas@sun.com Lars.Heill@sun.com Knut.Hatlen@sun.com 2. Project Summary 2.1. Project Description: Java DB is Sun's branding of Apache Derby, an open source pure Java database under Apache. Java DB may both run as an embedded database in the same VM as the application or as a network server. In both cases, Java DB is accessed through JDBC. This project is for the inclusion of SMF for Java DB in Solaris. 2.2. Risks and Assumptions: None 3. Business Summary 3.1. Problem Area: Java DB in Solaris does not currently include SMF functionality. 3.2. Market/Requester: Solaris 3.3. Business Justification: SMF is the standard interface for administering services on Solaris. Since Java DB is installed by default in Nevada, users expect to be able to administer the Java DB Network Server the same way as they administer other services on Solaris. Therefore, we want the Solaris packages for Java DB to include basic SMF support that enables users to start/stop the network server with svcadm(1M), inspect the service status with svcs(1), and modify some configuration properties with svccfg(1M). 3.4. Competitive Analysis: N/A 3.5. Opportunity Window/Exposure: The target is to include SMF support in Java DB 10.4 scheduled for primo May 2008. 3.6. How will you know when you are done?: SMF for Java DB has been added in a separate package for the Java DB distribution on Solaris. 4. Technical Description: 4.1. Details: Implement an SMF manifest and script to allow Java DB to be integrated with the Solaris SMF facility. 4.2. Bug/RFE Number(s) 6649593 4.3. In Scope: SMF manifest and script 4.4. Out of Scope: N/A 4.5. Interfaces: The manifest and associated script will be delivered by a new package, SUNWjavadb-service. The following files and directories will be added: /var/svc/manifest/application/database/javadb.xml: Java DB service bundle which describes the service and its properties. /lib/svc/method/javadb: Script which starts and stops the network server. /var/lib/javadb/data: Default directory (known as derby.system.home) for the Java DB instance. This is where relative paths in database names are resolved from, and where the Java DB Network Server looks for configuration files. The following service configuration properties will be modifiable via svccfg(1M): javadb/lib: Location of Java DB jar files. Default: /opt/SUNWjavadb/lib javadb/data: Direcory used as derby.system.home. Default: /var/lib/javadb/data javadb/java: The java executable to start Java DB with. Default: /usr/bin/java javadb/java_args: Extra command line arguments for the java executable. Default: -server javadb/server_start_args: Command line arguments for the network server start command. Default: (empty) javadb/server_shutdown_args: Command line arguments for the network server shutdown command. Default: (empty) 4.6. Doc Impact: Users are expected to get the information they need from SMF man pages and the Java DB manifest file. 4.7. Admin/Config Impact: The SMF command svcadm may be used to start/stop/restart a Java DB netowrk server. 4.8. HA Impact: None 4.9. I18N/L10N Impact: None 4.10. Packaging & Delivery: The SMF manifest go into a new SUNWjavadb-service package. Sample pkgmap file content: : 1 29 1 i copyright 93 8259 1207141400 1 i depend 90 7017 1207141400 1 d none lib 0755 root sys 1 d none lib/svc 0755 root sys 1 d none lib/svc/method 0755 root sys 1 f none lib/svc/method/javadb 0555 root sys 2119 42112 1207138158 1 i pkginfo 471 37216 1207141400 1 d none var 0755 root sys 1 d none var/lib 0755 root other 1 d none var/lib/javadb 0755 nobody nobody 1 d none var/lib/javadb/data 0700 nobody nobody 1 d none var/svc 0755 root sys 1 d none var/svc/manifest 0755 root sys 1 d none var/svc/manifest/application 0755 root sys 1 d none var/svc/manifest/application/database 0755 root sys 1 f manifest var/svc/manifest/application/database/javadb.xml 0444 root sys 3585 37604 1207138158 4.11. Security Impact: None 4.12. Dependencies: None 5. Reference Documents: All information for this case is included in this document. (see LSARC/2008/277 for DB interfaces) 6. Resources and Schedule: 6.1. Projected Availability: May, 2008 6.2. Cost of Effort: Packaging: 2 person weeks 6.3. Cost of Capital Resources: None 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: Java DB 6.4.3. Type of CPT Review and Approval expected: FastTrack 6.4.4. Project Boundary Conditions: 6.4.5. Is this a necessary project for OEM agreements: No 6.4.6. Notes: 6.4.7. Target RTI Date/Release: May 2008 6.4.8. Target Code Design Review Date: 6.4.9. Update approval addition: N/A 6.5. ARC review type: FastTrack 7. Prototype Availability: 7.1. Prototype Availability: N/A 7.2. Prototype Cost: N/A --Boundary_(ID_t6V/QbPbxQ7+bGuLEYUCmw) Content-type: text/x-vcard; name=Terrence.Miller.vcf; charset=utf-8 Content-transfer-encoding: 7BIT Content-disposition: attachment; filename=Terrence.Miller.vcf begin:vcard fn:Terrence Miller n:Miller;Terrence adr:16 Network Circle;;UMPK-303;Menlo Park,;CA;94025;USA email;internet:terrence.miller@sun.com tel;work:650-786-9192 x-mozilla-html:FALSE version:2.1 end:vcard --Boundary_(ID_t6V/QbPbxQ7+bGuLEYUCmw)--