[savara-commits] savara SVN: r110 - tools/eclipse/trunk/docs/userguide/src/main/module.

Author: objectiser Date: 2009-12-05 19:15:35 -0500 (Sat, 05 Dec 2009) New Revision: 110 Modified: tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml Log: Updated Overlord to SAVARA references. Modified: tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml =================================================================== --- tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml 2009-12-06 00:00:41 UTC (rev 109) +++ tools/eclipse/trunk/docs/userguide/src/main/module/overview.xml 2009-12-06 00:15:35 UTC (rev 110) @@ -5,7 +5,7 @@ <title>Overview</title> <para> - The CDL component of the Overlord SOA governance project aims to leverage the concept of a choreography (or conversation) + The SAVARA project aims to leverage the concept of a choreography (or conversation) description to provide design-time and run-time governance of an SOA. </para> <para> @@ -19,13 +19,13 @@ orchestrated service domains. </para> <para> - This document will outline how the Choreography Description is being used as part of Project Overlord to provide SOA governance capabilities + This document will outline how the Choreography Description is being used as part of SAVARA to provide SOA governance capabilities for each phase of the SOA lifecycle. </para> <para> When a validated design has been approved by the users, it can be used to generate an initial skeleton of the implementation for each service. - The current version of Overlord enables a skeleton implementation to be generated as a JBossESB service configuration file, - using 'conversation aware' ESB actions. For more information on these, please see the “Conversational ESB User Guide”. + The current version of SAVARA enables a skeleton implementation to be generated as a WS-BPEL process or + JBossESB service configuration file (using 'conversation aware' ESB actions). </para> <section> @@ -110,7 +110,8 @@ <para> When a 'structured' implementation language has been used, such as WS-BPEL, jPDL or the new 'conversation aware' ESB actions, it will be possible to infer the behaviour of the service being implemented, to compare it against the choreography description. - Currently this has been implemented for the “conversation aware” ESB actions, and is demonstrated using the samples in this Overlord-CDL distribution. + Currently this has been implemented for the “conversation aware” ESB actions, and is demonstrated using + the samples in this SAVARA Runtime distribution. </para> <para> Detecting incorrectly implemented behaviour at the earliest possible time saves on downstream costs associated with finding and fixing errors. @@ -119,7 +120,7 @@ </para> <para> There are two other areas where a choreography description can be used as part of design-time governance, - that are not currently implemented in Overlord: + that are not currently implemented in SAVARA: </para> <itemizedlist> <listitem> @@ -152,7 +153,7 @@ The error can also be reported to a central management capability. </para> <para> - The CDL component of Overlord provides the ability to configure service validators to monitor the behaviour of individual services. + The SAVARA Validator provides the ability to configure service validators to monitor the behaviour of individual services. An enhanced version of the JBossESB trailblazer example has been included, with the appropriate validator configuration, to demonstrate this mechanism. </para> </section> @@ -181,25 +182,34 @@ <section> <title> First Steps </title> - <para>The first step will be to follow the instructions in the Getting Started Guide to install Overlord. </para> + <para>The first step will be to follow the instructions in the Getting Started Guide to install SAVARA. </para> <para> Once installed, the next step should be to try out the examples in the samples folder. The examples consistent of:</para> <itemizedlist> <listitem> Service Validation related examples <para> - The samples folder contains an enhanced version of the trailblazer example from the JBossESB, with the addition of a File Based Bank, and message content including a conversation id to enable the messages to be correlated with a specific session. + The samples folder contains an enhanced version of the trailblazer example from the + JBossESB, with the addition of a File Based Bank, and message content including a + conversation id to enable the messages to be correlated with a specific session. </para> </listitem> <listitem> Conversation aware ESB actions, with conformance checking against Choreography <para> - Two examples have been included, one simple example (purchasing) and the other more advanced (brokerage). Both relate to the business process of purchasing items. The second example introduces the concept of a broker to act on behalf of the customer, interacting with multiple potential suppliers. + Two examples have been included, one simple example (purchasing) and the other + more advanced (brokerage). Both relate to the business process of purchasing + items. The second example introduces the concept of a broker to act on behalf + of the customer, interacting with multiple potential suppliers. </para> <para> - These examples show how a service implementation (built using “conversation aware ESB actions” in this case), can be continuously checked for conformance against a choreography description. + These examples show how a service implementation (built using “conversation + aware ESB actions” in this case), can be continuously checked for conformance + against a choreography description. </para> <para> - The final step should be to review all of the documents in the docs folder to understand more about each capability, and then try using the techniques on your own project. + The final step should be to review all of the documents in the docs folder + to understand more about each capability, and then try using the techniques + on your own project. </para> </listitem> </itemizedlist>