SoaFaqWhatDoesCasaDo

Revision as of 16:14, 5 November 2009 by Admin (Talk | contribs)
(diff) ← Older revision | Current revision (diff) | Newer revision → (diff)

<< CompApp/CASA FAQ

What does the CASA editor do?

Contents



For complex SOA applications, the auto-generated service assembly from step 3 of the CompApp workflow may contain incomplete or incorrect configurations. To fix such problems, the user have to unzip the service assembly file and manually edit configuration files and/or add additional SE/BC service unit artifacts.

The Composite Application Service Assembly (CASA) editor was designed to simplify the user workflow that requires manual editing of the service assembly file (SA.zip). The CASA workflow shown in the following diagram allows the user to iterate steps 3 and 4 of the CompApp workflow to create a Build-Edit-Build loop.

File:Faq02.gif The CASA workflow

CASA Use Cases

Five most common use cases that require manual editing of service assembly were identified. These use cases are documented in File:CasaUISpec.pdf the CASA UI spec. The following is brief summary of these cases:

Case 1: Add missing concrete WSDL elements

A SU project, e.g., BPEL, can be developed using abstract WSDL elements. However to deploy such a project, the user has to add concrete WSDL elements specifying ports and bindings.

Case 2: Replace concrete WSDL elements

A service defined by concrete WSDL elements of a SU project can be replaced to provide the same service using a different BC, e.g., exposing a HTTP/SOAP service using a FILE binding/port instead.

Case 3: Correct auto-generated deployment configuration

The CASA editor can be used to change the auto-generated deployment configuration of a composite application. For example, auto-generated connections can be removed and new ones added using CASA.

Case 4: Connect to endpoints of an external service unit

A service assembly can have connections across its boundary to endpoints of external service units that deployed separately in another application. The external service unit may or may not be defined by a NetBeans SU project.

Case 5: Attach WS-* policy definitions

In a composite application, a WSDL port can be attached with WS-* and other policy definitions that add requirements and/or preferences to the web service provider and/or consumers.


References:

  • CASA UI spec
Not logged in. Log in, Register

By use of this website, you agree to the NetBeans Policies and Terms of Use. © 2012, Oracle Corporation and/or its affiliates. Sponsored by Oracle logo