1. Introduction 1.1. Project/Component Working Name: Sun GlassFish Communication Server 1.0 (project SailFin) 1.2. Name of Document Author/Supplier: Sreeram Duvur, Binod P.G 1.3. Date of This Document: August 29, 2008 1.3.1. Date this project was conceived: July, 2007 1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: Web and Application Platform PAC (WAP PAC) 1.4.2. The ARC(s) you expect to review your project: LSARC 1.4.3. The Director/VP who is "Sponsoring" this project: Thomas Kincaid 1.4.4. The name of your business unit: Software Infrastructure 1.5. Email Aliases: 1.5.1. Responsible Manager: Murthy Narayanan 1.5.2. Responsible Engineer: sreeram.duvur@sun.com, prasad.subramanian@sun.com 1.5.3. Marketing Manager: satish.hemachandran@sun.com 1.5.4. Interest List: as-telco@sun.com 2. Project Summary 2.1. Project Description: Sun GlassFish Communication Server is a specialization of Sun GlassFish Enterprise Server (aka Sun Java System Application Server) for the Telecom market. It adds SIP Servlets API capabilities to the Java EE 5 standards that are already supported. Developed jointly with Ericsson AB as Project SailFin, it will be made available to Carriers and Enterprises that are interested in deploying mission critical SIP enabled services. It will implement support for SIP Servlets 1.1 specification defined in JSR-289. Since the project mostly reuses existing GlassFish administration and clustering infrastructure, only the new SIP container functionality and some enhancements to SIP load balancing, security and related administrative aspects are discussed in the submitted material. Since this is a layering on top of GlassFish, this is presented as a fast track, addressing only incremental additions 2.2. Risks and Assumptions: * Existing OEM agreements and customer demand require that the product pass comptability tests and ship to customers in CY08. * Must meet stringent horizontal scalability and robustness demands of the telecom market. 3. Business Summary 3.1. Problem Area: Addresses the need for a high performance SIP application server that also provides all the power of Java EE 5 to deploy new subscriber services. 3.2. Market/Requester: Network Equipment Providers and Carriers who create and deploy services for the mobile and fixed line markets. 3.3. Business Justification: Java and SIP Servlets are surprisingly deeply penetrated in the service creation markets. Carriers demand high-end performance, scalability and availability and are looking to establish long-term OEM and supplier relations with infrastructure software players. They are attracted to Java EE and JSR-289 (SIP Servlets API 1.1) because it enables new class of applications that use web services and data access to be developed and composed much more easily. 3.4. Competitive Analysis: Project SailFin is the first and most popular SIP Application Server to be developed in open source. It has drawn the interest of many customers including Ericsson which is a co-developer and consumer, and 40% market reach. The acquisition of BEA WebLogic by Oracle has resulted in the elimination of Oracle Comunications and Mobility Server. IBM Websphere 6.1 includes support for SIP Servlets 1.0 (JSR-116) RedHat/JBoss is working on adding SIP Servlets Support. 3.5. Opportunity Window/Exposure: Customer interest and business commitments require that the product be delivered in CY08. 3.6. How will you know when you are done?: The initial delivery of the product will be deemed complete when it passes the compatibility test suites required by JSR 116 and 289. It must also pass the longevity and system tests that have been agreed upon by Sun and OEM customers. 4. Technical Description: 4.1. Details: See attached PDF document (sailfin_umbrella.pdf) that describes the project components. 4.2. Bug/RFE Number(s): Not Applicable 4.3. In Scope: 4.3.1 OS Platform Support The primary OS platforms being supported by the project include: * Windows XP and Vista on x64 (Developer Only) * Mac OS X on x64 ( Developer Only) * SuSE Linux 10 on X64 * RedHat Linux 4 on X64 * Solaris 10 on SPARC and x64 4.4. Out of Scope: Not Applicable 4.5. Interfaces: Exported Interfaces +-------------------------------------------------------------------------------------------+ | Name |Classification|Specified in |Comments | +-------------------------------------------------------------------------------------------+ | JSR-116 |Standard |http://jcp.org/en/jsr/detail?id=116 | | +-------------------------------------------------------------------------------------------+ | JSR-289 |Standard |http://jcp.org/en/jsr/detail?id=289 | | +-------------------------------------------------------------------------------------------+ | sun-domain_1_4.dtd |Committed |Section 5.1 in attachment | | +-------------------------------------------------------------------------------------------+ | sun-sip_1_1.dtd |Committed |Section 5.1 in attachment | | +-------------------------------------------------------------------------------------------+ | sun-converged-loadbalancer_1_0.dtd |Committed |Section 5.1in attachment| | +-------------------------------------------------------------------------------------------+ | Admin CLI |Committed |Section 5.2 and 5.3 in attachment | | +-------------------------------------------------------------------------------------------+ Imported Interfacs This project imports and exports all the exported interfaces of WSARC 2006/586 GlassFish v2 or SJSAS 9.1. See http://sac.eng/arc/WSARC/2006/586/ 4.6. Doc Impact: 4.6.1. End User Documentation See attached PDF document that describes the project documentation set. * man pages are provided as part of the asadmin tool * Online help is provided as part of the GUI UIRB reviews are scheduled for administrative interfaces. 4.6.2. Distribution Documentation Administration and Deployment documents will guide administrators. 4.6.3. Developer Documentation SIP Servlet and Converged Application Deveopment will be described in Developer Guide. 4.7. Admin/Config Impact: See PDF attached for Inception. 4.8. HA Impact: See PDF attached for contains an overview of session data replication, converged load balancer and deployment topology. 4.9. I18N/L10N Impact: Will be internationalized. Localizations based on customer demand. 4.10. Packaging & Delivery: 4.10.1 Overall Filesystem Layout Layout is identical to what is already approved for Sun Java System Application Server. Jar/Zip based distribution and installer will be provided. 4.11. Security Impact: Adds TLS support for SIP protocol, support for Digest Authentication and support for Proxy-Asserted-Identity 4.12. Dependencies: Sun Java System Application Server 9.1.x 5. Reference Documents: WSARC 2006/586 GlassFish v2 or SJSAS 9.1: http://sac.eng/arc/WSARC/2006/586/ See project detail document locations in submitted materials. 6. Resources and Schedule: 6.1. Projected Availability: Production quality release in Sep 08 and an update in Dec 08. 6.2. Cost of Effort: Roughly 25 resources for 1.5 years. 6.3. Cost of Capital Resources: Addressed via existing resources. 6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: Not applicable. 6.4.3. Type of CPT Review and Approval expected: Not applicable. 6.4.4. Project Boundary Conditions: Not applicable. 6.4.5. Is this a necessary project for OEM agreements: Yes. 6.4.6. Notes: Not applicable. 6.4.7. Target RTI Date/Release: Not applicable. 6.4.8. Target Code Design Review Date: Reviews have been occurring throughout the development process. 6.4.9. Update approval addition: Not applicable. 6.5. ARC review type: Fast Track Since this is a layering on top of GlassFish, this is presented as a fast track, addressing only incremental additions 6.6. ARC Exposure: Open 6.6.1. Rationale: Not applicable. 7. Prototype Availability: Open Source developement builds are visible at http://sailfin.dev.java.net