Reminder no meeting today. However the project team is looking for an owner for this case (and intern). They would like to get a quick review.
Any volunteers? Thanks, -- mark Linda Schneider wrote: > Template Version: @(#)onepager.txt 1.35 07/11/07 SMI > Copyright 2007 Sun Microsystems > > 1. Introduction > 1.1. Project/Component Working Name: > OpenMQ/SGMQ 4.4 (Crane) > > 1.2. Name of Document Author/Supplier: > linda.schneider at sun.com > > 1.3. Date of This Document: > 07/06/09 > > 1.3.1. Date this project was conceived: > 12/01/08 > > 1.4. Name of Major Document Customer(s)/Consumer(s): > 1.4.1. The PAC or CPT you expect to review your project: 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: > Anil.Gaur at sun.com > > 1.4.4. The name of your business unit: > Application Platform > > 1.5. Email Aliases: > 1.5.1. Responsible Manager: edward.bratt at sun.com > 1.5.2. Responsible Engineer: linda.schneider at sun.com > 1.5.3. Marketing Manager: > > 1.5.4. Interest List: > > 2. Project Summary > 2.1. Project Description: > > This is a minor feature release for the Sun Glassfish Message Queue > (was > Sun Java System Message Queue). SGMQ is a Message Oriented Middleware > product that facilitates asynchronous communication between > applications > and implements the JMS 1.1 specification. It is shipped standalone, > as the > messaging provider in Glassfish and within other Sun products. > > Changes added to this release include a JMS Bridge (to talk to other > providers), > modifications to support Glassfish v3, support for the STOMP protocol, > packaging changes to support IPS and other minor RFEs. > > 2.2. Risks and Assumptions: > > Risks: > Incompatible changes are being made (for performance) to our > persistence store. To mitigate the risk, a copy of the > old data will be left when the store is migrated and the faster > store configuration may be turned off. > > New contracted APIs (both on management and for packaging) will > be added for Glassfish V3 which must be maintained going > forward. > > IPS packaging support is being added and will be the default > packages > for most customers. There will be no automatic migration of data > when the customer upgrades. All new customers will be > expected to > use the new packages (although we will continue to provide SVR4 > and RPM packages for 2 more releases for existing customers) > > 3. Business Summary > > The primary drivers of this product is integration with users of > WebSphere MQ (was MQSeries) and changes to support glassfish > functionality. > > 3.1. Problem Area: > > The changes for Crane address: > > * Improved performance.` > > * the ability for products using MQ to communicate with other > similar products: > - the bridge supports talking with other providers > - Stomp support allows customers to use the Stomp protocol to > talk to mq > > * Install and upgrade issues: > - Previous editions of MQ have used native packaging which > required root access. This removes that restriction and > also allows for Update Center 2.X support. > > 3.2. Market/Requester: > * Specific customers requesting Websphere MQ integration > * Support for integration with Oracle AS and Weblogic servers. > * External requests via user aliases for STOMP support. > * Glassfish V3 requirements. > > 3.3. Business Justification: > > 3.4. Competitive Analysis: > > 3.5. Opportunity Window/Exposure: > > 3.6. How will you know when you are done?: > > The product will be done when the meets the traditional feature, > performance, stability and test goals. > > 4. Technical Description: > 4.1. Details: > > No changes to the product will rely on new 3rd party > open source products. > > All code will be developed in house by sun engineers. > > Websites with specific (one-pager) information for the > major features is listed in section 5 (references) below. > > The major features are: > > - support for a JMS bridge. > This feature allows MQ to exchange messages with other > JMS providers such as Websphere MQ. > > - STOMP protocol support. > This feature allows Stomp clients (a public API) to > act as clients of an MQ broker. > > - V3 support: > This is limited to support for lazy loading, a set of > packaging changes and IPS packages specific to MQ, > and additional locations for finding java, etc. > > - Support for IPS: > Creation of new IPS packages for the standalone product > and special IPS packages required for GF (because they > do not follow the filesystem specification) > > - UMS improvements: > Minor enhancements for an existing feature to add > monitoring and management functionality > > - In-process broker: > An API allowing standalone clients to embed the > MQ server inside their executable. > > - JMS Performance work: > Optimization of internal code. Will change how > data is stored on disk in some scenarios. > > - Installer Changes: > Creation of an installer to install IPS (vs zip) > packages. > > - Minor changes to allow Glassfish to configure > some APIs (will require a contract from glassfish) > > > 4.2. Bug/RFE Number(s): > > Outside of the changes above, multiple bugs and RFEs are changed in > this release which can > be located through qerying bugster or issue tracker: > > Current count: > 52 RFEs (most are minor) > 125 bugs in bugster (+ issue tracker bugs) > > 4.3. In Scope: > None > > 4.4. Out of Scope: > > We will not provide migration scripts for customers moving from > SVR5/RPM packages to IPS. (although we will provide manual > migration steps). > > 4.5. Interfaces: > > The full list of interfaces will be documented in the 20 questions > document and/or fast track information which will be submitted to > the ARC. > > Expected changes to Imported Interfaces: > > * Addition/use of an api from Glassfish to support Lazy loading > (Classfication will be: Contract private) > > * Import of Grizzly. > Classification is: public (?? - I think) > > > Expected changes to Exported interfaces are: > > * modifications to the file store. > > Note: these modifications will not be compatible however we > will provide properties to turn off use of these enhancements > and will keep pre-upgrade data around if a client must revert. > > (Classification: committed private ) > > * Modfications (Additions) to the CLI of most executables > > (Classification: Committed) > > * Modification to the file system layout to support the > standalone layout (which matches the current JES > Specifications) > as well as the one required for integration into glassfish > > (Classification is: Committed) > > * Modifications (minor additions) to the UMS protocol > > (Classification: committed) > > * New Interface: IPS packages > > (Classification will be: committed) > > * Addition of new broker configuration properties > > (Classfication: Uncomitted) > > * Modification of the output of various commands > > (Classification: Uncomitted) > > * Modification to the log file output > > (Classification: Uncomitted) > > * Modification to the JMX api > (Classification: committed) > > * New admin executable: imqbridgemgr > (Classification: committed) > > > 4.6. Doc Impact: > We will be updating all documents for this release (both because of > these changes and because of the name change) > > 4.7. Admin/Config Impact: > > This will affect all CLIs and the JMX client. It will not > affect the GUI. > > 4.8. HA Impact: > > Does not affect the current HA infrastructure. > > 4.9. I18N/L10N Impact: > Yes, new Localized strings will be needed for added for the new > features. > Documentation will need to be localized. > > 4.10. Packaging & Delivery: > > Solaris: > This version of MQ will not be placed in Solaris 10 or > earlier. > > A version of MQ is updated (with glassfish) into > OpenSolaris which > is packaged identically to older releases (it is based on the > SVR4 layout) > > General: > MQ will now be providing IPS packages (which will be the > default > for most customers) > > SVR4/RPM packages are being deprecated and will be > supplied for > 2 more releases. > > No automatic upgrade is being provided for the transition > from > SVR4 to IPS packages. The command (will be documented in > the release notes) to do this is: > > (Solaris version) > cp -r /var/imq/instances <mq home>/var > > > 4.11. Security Impact: > This release does not change use of any security APIs, > java policy changes and does not add any new ports or > other connection points. > > 4.12. Dependencies: > > New private contract Dependencies: > > - Glassfish Lazy loading API (will require contract) > > > Other Dependencies: > > - a list of all dependencies (build, test, etc) can be found at: > (INTERNAL SITE) > > http://mq.sfbay.sun.com/Wiki.jsp?page=CraneEncumbrance > > > - The following itemize ONLY runtime dependencies ( 2 new > items): > > - EXTERNAL 3rd Party Dependencies > * NSS/NSPR (used by C library) > * Appach Commons Codec > > - INTERNAL Dependencies: > * (NEW) Grizzly v1.9.19 > * JAXM > * JMX API > * JNDI Provider Implementation (JNDI FS) > * Java Help > * J2SE > * Open Installer Framework > * Sysnet Registration > * AS Registration Module (Note: have existing contract > from 4.3) > * AS Registration Module > * (New) Update Center Toolkit > > > 5. Reference Documents: > Content Page: (Internal) > http://mq.sfbay.sun.com/Wiki.jsp?page=MQCraneFeatures > Content Page: (External) https://mq.dev.java.net/4.4.html > > These pages list one pagers for all features. > > 6. Resources and Schedule: > 6.1. Projected Availability: > CYQ4 or CYQ4 2009 > > 6.2. Cost of Effort: > approx 10 man years (all pieces of the product) > > 6.3. Cost of Capital Resources: > no additional captial expenditures are required > > 6.4. Product Approval Committee requested information: > 6.4.1. Consolidation or Component Name: Web and Application > Platform Suites (WAP) > 6.4.3. Type of CPT Review and Approval expected: > FastTrack > > Interface changes are fairly minimal and this release > contains only a small number of features) however its > possible a Standard review will be required based on > largest component (the jms bridge) > > 6.4.4. Project Boundary Conditions: > Boundary conditions are in the MQ 4.4 phase 2 presentation. > This information is not available externally. > > 6.4.5. Is this a necessary project for OEM agreements: > No. > > 6.4.6. Notes: > // See dependencies section above. > > 6.4.7. Target RTI Date/Release: > > This release will not be integrated into Solaris 10 at this time. > > MQ will be integrated into OpenSolaris as part of glassfish, > however > that integration will be handled and ARC'ed by that team. > > MQ does plan to integration independently into the last > OpenSolaris > release of CY2009 provided it accepts IPS style packages. We will > file for a separate review at that time. > > Internal products (outside of glassfish) will pick up the bits > post-FCS > > Planned Dates for glassfish integration is found at (internal > link): > http://mq.sfbay.sun.com/Wiki.jsp?page=CraneSchedule > > 6.4.8. Target Code Design Review Date: > Design review has already happened. > Selected code reviews for bugs are on-going and will be > completed > by late August. > > 6.4.9. Update approval addition: > > N/A - this does not apply to solaris > > 6.5. ARC review type: FastTrack > Again: see comment above, I need help to determine if the > bridge changes are too large for a fast-track > > 6.6. ARC Exposure: > Open > > Project is part of an open source project (OpenMQ) > Project is also part of Glassfish. > > 6.6.1. Rationale: > NA - this project is open source. > > 7. Prototype Availability: > 7.1. Prototype Availability: > Main features are available in the July 15th builf (build 11-1) > > 7.2. Prototype Cost: > 3 man years (to cover testing, documentation and bug fixing) > > -- <http://www.sun.com> * Mark A. Carlson * Sr. Architect *Systems Group* Phone x69559 / 303-223-6139 Email Mark.Carlson at Sun.COM
