Not logged in | Login
CASA One Pager
1.2. Name of Document Author/Supplier: Tientien Li
1.3. Date of This Document: 11/15/06, 03/26/07 (update)
1.4. Name of Major Document Customer(s)/Consumer(s): 1.4.1. The PAC or CPT you expect to review your project: SOA/BI PAC 1.4.2. The ARC(s) you expect to review your project: WSARC 1.4.3. The Director/VP "Sponsoring" this project: Jerry.Waldorf@sun.com 1.4.4. The name of your business unit: SOA Business Integration
1.5. Email Aliases: 1.5.1. Responsible Manager: Venkat.Chellasamy@sun.com 1.5.2. Responsible Engineer: Tientien.Li@sun.com 1.5.3. Marketing Manager: Kevin.Schmidt@sun.com 1.5.4. Interest List: firstname.lastname@example.org
2. Project Summary 2.1. Project Description: The Composite Application Service Assembly (CASA) editor is a Netbeans module for editing the deployment configuration of JBI Service Assembly. The connection between service unit endpoints within the application can be edited and new connections can be created using the CASA editor.
2.2. Risks and Assumptions: The beta version of Netbeans visual library 2.0 will be used to implement the graphic of CASA editor. The FCS date of this library is scheduled post the CASA release date. 3. Business Summary 3.1. Problem Area: The composite application project introduced in Netbeans Enterprise Pack 5.5 allows cooperating JBI module components, e.g., BPEL, XSLT, and Java EE projects to be assembled into a composite application. The initial version of the project system auto-generate necessary deployment configuration parameters based on the best guess of inter-connection data obtained from its component projects.
For most of the simple projects, the auto-generation process works and generates correct deployment configuration. However, for more complex scenarios, the build process creates incomplete deployment configuration. Manual editing is often required to modify and/or
supply additional connection information needed for deployment.
The CASA editor is designed to support the following deployment configuration editing scenarios:
* Adding/modifying concrete WSDL elements such as service endpoints * Adding/removing service connections between service units * Connecting to endpoints of external service units
3.2. Market/Requester: Enterprise Developers looking to utilize SOA tooling provided by
Netbeans Enterprise Pack for composite application development. 3.3. Business Justification: The CASA editor ranks high in terms of priority in our development plan. It will not only solve key problems we had in the tooling, but also promote a better composite application development methodology. With the CASA editor, the user is free to develop business logics using abstract WSDLs independent of deployment artifacts. Deployment specific information can be added in later using the CASA editor.
3.4. Competitive Analysis: IBM WebSphere Integration Developer 6 and Oracle SOA Suite are using the composite application technology similar to that provided in our current Java CAPS 5.x products. The JBI based SOA framework for composite application development provided in Netbeans Enterprise Pack utilizes our next generation technology with many advanced features.
3.5. Opportunity Window/Exposure: CY2007
3.6. How will you know when you are done?: We have developed use cases from example projects collected from users that require manual editing of deployment configurations. We are done when all these examples can be successfully completed in CASA.
4. Technical Description: 4.1. Details: The CASA editor is a Netbeans module associated with the composite application project. The user can open the project to edit its deployment configuration. 4.1.1. Open CompApp project configuration
Once opened, CASA loads service assembly configuration files, creates a design-time in-memory model, and opens associated editors. It also checks JBI binding component plug-ins installed in the IDE. For each plug-in, a palette item linking to the associated binding component type is added. 4.1.2. Add/remove JBI module projects
The user can add/remove JBI module component (SU) projects to the composite application. External service unit can also be added using CASA palette. 4.1.3. Add/remove connections
The user can add/remove connections between endpoints within the composite application. Connections to/from external service unit can also be added in CASA.
4.1.4. Add/remove concreate WSDL elements
To add a new WSDL service endpoint, the user select the palette item and drag-n-drop it on to the graph editor. An empty wsdl service port element will be created. Once the port is connected to an endpoint with known wsdl portType, the associated binding element will be created and populated with specific default extensibility elements of the selected binding component type. 4.1.5. Edit concreate WSDL element attributes
Concrete wsdl elements can be modified using their property sheets and associated property editors. CASA utilizes the editing functions provided by the WSDL editor to edit wsdl and extensibility elements and their attributes. 4.1.6. Attatch WS policy definitions to WSDL port
In addition, WS-policy definitions, e.g., security, and reliable messaging, can be attached to wsdl service ports using pre-defined profiles provided by Netbeans WSIT plug-in. The user can use editor GUI to customize policy parameters. 4.1.7. Attach aspect service units to connection
The user can attach JBI aspect service units to connections between endpoints within the composite application. The aspect project data will be generated base on usages within the application.
At the end of the editing session, the editor module saves the model content into files and generates an updated deployment configuration descriptor to reflect changes made by the user.
4.2. Bug/RFE Number(s): Netbeans Issue #89502 http://www.netbeans.org/issues/show_bug.cgi?id=89502
4.3. In Scope: // Aspects that are in scope of this proposal if not obvious from above
4.4. Out of Scope: // Aspects that are out of scope if not obvious from above.
4.5. Interfaces: Modification to the following interfaces may be required:
1) Netbeans JBI Binding Component extension plug-in module defines its binding component type and associated extensibility element definitions in module layer.xml file. Additional items may be needed to support CASA. We are working with the binding component team to expand this interface.
2) Netbeans Web Services Interoperability Technologies (WSIT) plug-in module defines a set of predefined WS-policy profiles. We are working with the WSIT team to expand the interface to allow WSIT plug-in be utilized in CASA for attaching WS-policy profiles to composite application deployment configurations.
4.6. Doc Impact: This is a new component and will need a new set of documents
including: tutorials, user guide, and sample applications.
4.7. Admin/Config Impact: No Admin/Config impact expected to the Netbeans Enterprise Pack
4.8. HA Impact: N/A
4.9. I18N/L10N Impact: Yes, the CASA editor will confirm to all Sun and Netbeans software I18N/L10N requirements
4.10. Packaging & Delivery: The CASA editor will be packaged as a Netbeans module included in the Enterprise Pack 5.5.1 release.
4.11. Security Impact: The CASA editor uses WSIT plug-in to attach security related WS-policy profiles to deployment configuration. The editor does not use any security related API. 4.12. Dependencies: In addition to core Netbeans modules, the CASA editor has dependencies on following: - XML modules including XAM, and WSDL - WSDL editor - WSIT plug-in - Visual Library - JBI Binding Component plug-in modules
5. Reference Documents: i-team wiki page has project plans, resources, and contact information http://jupiter.czech.sun.com/wiki/view/Jet/CASAi-team
alaska wiki page has technical and development information. http://alaska.stc.com:10000/alaska/Wiki.jsp?page=CASAEditor
6. Resources and Schedule: 6.1. Projected Availability: Beta on 2/26/07 FCS on 4/23/07
6.2. Cost of Effort: The complete list of engineers, docs and QA for each project is listed in the i-team wiki. 6.3. Cost of Capital Resources: N/A
6.4. Product Approval Committee requested information: 6.4.1. Consolidation or Component Name: CASA Editor 6.4.3. Type of CPT Review and Approval expected: Standard 6.4.4. Project Boundary Conditions: TBD 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: Feb' 07 6.4.8. Target Code Design Review Date: Feb' 07 6.4.9. Update approval addition: N/A
6.5. ARC review type: Standard
7. Prototype Availability: 7.1. Prototype Availability: N/A
7.2. Prototype Cost: N/A