CRNT-27093 - Updated camel app details

git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@61359 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b

1 files changed, 16 insertions, 84 deletions

diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
index 6cbc13a..6646b7e 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm
@@ -326,14 +326,17 @@ nor selected. The message names themselves are not filtered. The top level tree
 
 
 <h3 id="cam">Camel Route Application</h3>
+<p>Following properties of the comel route application need to be specified:</p>
+
 
 <h4>Route Definitions</h4>
-<p>The Camel Application Type allows you to specify arbitrary Camel Routes to 
+<p>Specify name and description. The Camel Application Type allows you to specify arbitrary Camel Routes to 
   be invoked from Activities in Process Models at runtime, like</p>
-<p><img src="images/camel-config-one.png">
+<p class="image"><img src="images/camel-config-one.png">
 <br> <strong>Figure:</strong> Simple Route - Example</p>
 <p>or more complex cases like</p>
-<p><img src="images/complex-route.png"></p>
+<p class="image"><img src="images/complex-route.png">
+<br> <strong>Figure:</strong> Complex Route - Example</p>
 <p>In all cases, you need to ensure that the Camel Components used in the Tags 
   are part of your Runtime Environment setup. By default, the following Camel 
   Components are available:</p>
@@ -361,28 +364,31 @@ nor selected. The message names themselves are not filtered. The top level tree
 <p>Detailed description of each component could be found in the <a href="http://camel.apache.org/components.html">Camel site</a>.</p>
 <p>Additional Camel Components can be added via Utility JARs as part of a <a href="managing-solutions.htm">Solution 
   Release</a> to a Runtime Environment.</p>
-<h2>Additional Bean Definitions</h2>
+<h4>Additional Bean Definitions</h4>
 <p>You may use references to Spring Beans in your routes. These Spring Beans are 
   either expected to be defined externally in your runtime environment or can 
   be defined in the <b>Additional Bean Specification</b> Text Area:</p>
-<h2><img src="images/route-with-spring-bean.png"></h2>
+<p class="image"><img src="images/route-with-spring-bean.png">
+<br> <strong>Figure:</strong> Bean Specification</p>
 <p>Hereby, the byte code of <b>com.siriussuper.order.OrderCache</b> is expected 
   to be available in your runtime deployment, e.g. by adding a Utility JAR file 
   with this byte code to your <a href="managing-solutions.htm">Solution Release</a>.</p>
-<h2>Symbolic &lt;from/&gt; Tag</h2>
+<h4>Symbolic &lt;from/&gt; Tag</h4>
 <p>Although @integration-productnameshort@ will add this tag automatically at 
   the beginning of the route, you may add an explicit <b>&lt;from uri=&quot;ipp:direct&quot;/&gt;</b> 
   tag for readability:</p>
-<p><img src="images/symbolic-from-tag.png"></p>
+<p class="image"><img src="images/symbolic-from-tag.png">
+<br> <strong>Figure:</strong> From Tag</p>
 <p>This corresponds with the use of a symbolic <b>&lt;from/&gt;</b> tag in the 
   <a href="camel-events.html">Camel Trigger</a>. </p>
-<h2>Request Only and Request/Response Mode</h2>
+<h4>Request Only and Request/Response Mode</h4>
 <p>With the <b>Direction</b> Select Input </p>
-<h2><img src="images/request-response-select.png"></h2>
+<p class="image"><img src="images/request-response-select.png">
+<br> <strong>Figure:</strong> Direction</p>
 <p>you may specify whether the Camel Application is only supposed to invoke a 
   Camel Route (<b>Request Only</b>) or also return the received Message Exchange 
   data back to further processing (<b>Request/Response</b>).</p>
-<h2>Payload Structure and Mapping</h2>
+<h4>Payload Structure and Mapping</h4>
 <p>The Camel Application Type exposes two In Java Access Points </p>
 <ul>
   <li><b>Header</b> (<b>java.util.Map</b>) and</li>
@@ -408,80 +414,6 @@ nor selected. The message names themselves are not filtered. The top level tree
 </ul>
 
 
-<!-- 
-<h2>Creating Applications</h2>
-<p>To create an application you can either:</p>
-<ul>
-    <li>In the toolbar palette of the <a href="model-views/views-diagrams.html">diagram</a>
-    select <strong>Application</strong> under <strong>Items</strong>. The application is
-    created by subsequently clicking on the diagram canvas and appears also in the <strong>Outline</strong>
-    view.</li>
-</ul>
-<p class="image"><img src="images/mg-create-application.png" alt=""><br />
-</p>
-<ul>
-    <li>Or in the <strong>Application</strong> section of the <a
-        href="model-views/views-outline.html">Outline view</a> area, choose <strong>New
-    Application</strong> from the pop-up menu. The created application will appear in the <strong>Outline</strong>
-    view and can be dragged to the diagram canvas.</li>
-</ul>
-<p>Next, open the application properties dialog by double-clicking on the
-applications symbol. Choose an ID and a name for the application.
-Please note that IDs containing
-hyphens, blanks or dots and IDs starting with digits are not supported.
-Using the Visibility Public option, you can also specify whether you want to import applications 
-by reference when referenced in another model. 
-     <p class="image"><img src="images/visibility.png"
-    alt="General Properties of an application"> <br>
-<strong>Figure:</strong> General Properties</p>
-   <p> For more information, please refer to <a href="mg-preferences.html#multipackage">
-   Multi Package Modeling Preferences</a> section of <a href="mg-preferences.html">Setting @productname@ Preferences</a> chapter. 
-Edit the
-application type specific properties. </p>
-
-
-<h2>Modifying Applications</h2>
-<p>To modify an application, double-click the application symbol in the <a
-    href="model-views/views-outline.html">Outline view</a> or in a <a
-    href="model-views/views-diagrams.html">diagram</a>. The properties dialog
-    opens where you can perform your changes.</p>
-<h3>Controlling</h3>
-<p>An application provides the following controlling properties:</p>
-<ul>
-    <li>Cost Center</li>
-    <li>Actual Cost Per Second</li>
-</ul>
-<p class="image"><img src="images/mg-appl-controlling.png" alt=""> <br>
-<strong>Figure:</strong> Controlling Properties of an Application</p>
-<h3>Simulation</h3>
-<p>In this section you can specify simulation configurations, as described detailed in the chapter
-<span class="showReference">
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/simulation-configurations.html">
-Simulation Configurations</a>
-</span><span class="hideReference">
-<strong>Simulation Configurations</strong></span>
-of the 
-<span class="showReference">
-<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.simulation/html/simulation/toc.html">
-Developer Simulation Guide</a>.
-</span><span class="hideReference">
-<strong>Developer Simulation Guide</strong> in the <strong>@productname@ Documentation</strong>.</span>
-)
-<h3>Effort Planning</h3>
-<p>In this section you can set the following Process Effort properties:</p>
-<p class="image"><img src="images/application-effort-planning-props.png" alt=""> <br>
-<strong>Figure:</strong> Effort Planning Properties of an Application</p>
-<p>Please refer to the chapter <a href="process-effort-calculation.html">Project Effort Calculation</a> for
-detailed information on this functionality.</p>
-
-<h2>Deleting Applications</h2>
-<p>To delete an application, use the option <strong>Delete </strong>in the
-application's pop-up menu in a diagram. In the <strong>Outline</strong> view, use the
-corresponding option <strong>Delete</strong>.</p>
-<p>To remove an application symbol from the diagram, choose the option <strong>Delete
-Symbol</strong> in the application's pop-up menu. After this operation the application will still
-be part of the model.</p> -->
-
 <script language="JavaScript" type="text/javascript">
 <!-- 
 writeFooter();