summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2013-03-05 06:22:50 (EST)
committer Sven Rottstock2013-03-11 07:39:35 (EDT)
commit8af7fa0eb84d2e2418deeb4698855f8df9213a72 (patch)
treeb3dac6f5acd01c619c377eb9f42af9d19458f3e0
parentcfd52f3c725950b3bdba2ac64b6da56135739b8d (diff)
downloadorg.eclipse.stardust.documentation-8af7fa0eb84d2e2418deeb4698855f8df9213a72.zip
org.eclipse.stardust.documentation-8af7fa0eb84d2e2418deeb4698855f8df9213a72.tar.gz
org.eclipse.stardust.documentation-8af7fa0eb84d2e2418deeb4698855f8df9213a72.tar.bz2
CRNT-27092 - web service app details
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@63489 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.pngbin10274 -> 10837 bytes
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-application.htm4
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm49
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm8
4 files changed, 25 insertions, 36 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png
index 01ebe3d..17797fe 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/images/cr-app.png
Binary files differ
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 1a1d9a1..6d9af0f 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
@@ -37,7 +37,7 @@ more details on applications, refer to
<ul>
<li><a href="#mt">Message Transformation Application</a></li>
<li><a href=#cam>Camel Route Application</a></li>
- <li>Web Service Application</li>
+ <li><a href="#web">Web Service Application</a></li>
<li><a href="#mash">UI Mashup</a></li>
</ul></li>
@@ -364,7 +364,7 @@ Perform the following steps:</p>
<p class="image"><img src="images/search.png"
alt=""> <br>
<strong>Figure:</strong> Enter Search String</p>
- <li>Press <strong>Enter</strong>. The matching strings are searched and gets highlighted in yellow color.</li>
+ <li>Press <strong>Enter</strong>. The matching strings are searched and get highlighted in yellow color.</li>
<p class="image"><img src="images/search-string.png"
alt=""> <br>
<strong>Figure:</strong> Search Result</p>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
index 7423a91..dd84fa3 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-events.htm
@@ -52,12 +52,13 @@ Eclipse-based modeler do not display labels for the event. For more information,
<p class="image"><img src="images/create-statt-tool.png" alt=""> <br>
<strong>Figure:</strong> Create Start Event</p>
-<p>The Business Process Modeling perspective following types of start events:</p>
+<p>The Business Process Modeling perspective following types of events:</p>
<ul>
<li>None
<ul>
- <li><a href="#simpl">Manual Trigger</a>
- <li><a href="#scan">Scan Event</a></li>
+ <li><a href="#simpl">Start Event</a></li>
+ <li><a href="#simpl">Manual Trigger</a></li>
+
</ul>
</li>
<li> Camel Message Events
@@ -65,6 +66,7 @@ Eclipse-based modeler do not display labels for the event. For more information,
<li><a href="#file">File Event</a></li>
<li><a href="#mail">E-mail Event</a></li>
<li><a href="#msg">Message Event</a></li>
+ <li><a href="#scan">Scan Event</a></li>
<li><a href="#cam">Generic Camel Route Event</a></li>
</ul>
</li>
@@ -168,32 +170,14 @@ in the flyout menu.</p>
If specified, then it also gets displayed in the diagram.
</li>
<li>Description - Specify the description</li>
- <li>Event Class - By default <strong>None</strong> is selected. It means that
- user intervention is required to start the process. You can also select following options:
+ <li>Event Class - By default <strong>None</strong> is selected. You can also select following options:
<ul>
<li>Timer - Select this option to start a process instance at a specific time. </li>
<li>Message - Select this option to start a process instance based on the incoming message.
However, note that you need to specify <a href="#simpl">Implementation</a> for Timer and Message events.</li>
</ul></li>
<li>Interrupting</li>
-
-
- <!-- <li>Event Type - By default, <strong>Manual Process Start</strong> option is selected.
- It also contains following options:
- <ul>
- <li>Process Start via Scan - If you select this option, then the <strong>Scanned Document</strong>
- option is displayed. You need to select scanned document from the drop-down list.</li>
- <p class="image"><img src="images/scan.png" alt=""> <br>
- <strong>Figure:</strong> Scanned Document</p>
- <li>Process Start via Camel Endpoint - If the <b>Endpoint Type</b> is set to <b>Generic</b>, you may add an <b>Additional
- Route Specification</b> and <b>Additional Beans Specification</b>. The Generic endpoint type is supported.
- <p class="image"><img src="images/eve-camel-prop.png" alt=""> <br>
- <strong>Figure:</strong> Process Start via Camel Endpoint</p>
- </li>
- </ul>
-
- </li> -->
</ul></li>
@@ -201,8 +185,11 @@ in the flyout menu.</p>
<h3 id="simpl">Implementation</h3>
<p>This option is available only when you switch to <a href="model-views/pep-panels.html">Integrator</a> profile.
Using this option, you can specify implementing event to initiate the process.</p>
-<p>If you select the <strong>None</strong> option from the Event Class, then you need to specify <strong>Manual Trigger</strong>
-as a start event.</p>
+<p>If you select the <strong>None</strong> option from the Event Class, then the <strong>Manual Trigger</strong> option is
+selected, by default. It means that user intervention is required to start the process.
+You can also select the <strong>Please specify</strong> option from the <strong>Event Implementation</strong> drop-down
+to set the event as <strong>Start Event</strong>.
+</p>
<p>If you select the <strong>Message</strong> option from the Event Class, then the following implementing events are displayed.
</p>
@@ -317,7 +304,7 @@ its content is retrieved and mapped accordingly. To configure the file event, sp
<li>Parameters - Using this tab users can map the data received from the incoming exchange
to data defined in the process model. For example, map the content of the incoming message to a primitive data.
- <ul><li>
+ <ul>
<li>Name - By default, name is displayed as Message. This field is not editable.</li>
<li>Data Type - By default, Primitive is selected. This field is not editable.</li>
@@ -373,7 +360,7 @@ and passing all the information contained as input data.
<h3 id="msg">Message Event</h3>
<p>The message event is used to configure route to receive JMS messages from a JMS broker. To configure the message
event, you need to provide the following details.</p>
-<h5>Adding Bean</h5>
+<h4>Adding Bean</h4>
<p>You need to specify following bean details to the <a href="#defcam">default-camel-context.xml</a> file.
</p>
@@ -385,7 +372,7 @@ event, you need to provide the following details.</p>
&lt;/property&gt;
&lt;/bean&gt;
</pre>
-<h5>Downloading activemq Jars</h5>
+<h4>Downloading activemq Jars</h4>
<p>Based on your JMS server, you need to download the activemq client jars. If you have RAD setup, then
downloaded jars should be copied to <tt>ipp-portal/lib</tt> folder </p>
@@ -444,7 +431,9 @@ to allow process instances to be started manually and via Infinity Process Platf
<ol>
<li>Scanned Document - You can select the scanned document of the same model or other model.
- The drop-down list displays the defined <strong>Document</strong> data type of the current model as well as other models.
+ The drop-down list displays the defined <strong>Document</strong> data type of the current model as well as other models.
+ If the Process Supports Attachment option is enabled, then the <strong>Process Attachment</strong> option would
+ also be displayed in the drop-down list.
</li>
<li>Metadata Structure - This field displays the metadata associated with the document, if any.</li>
</ol>
@@ -542,12 +531,12 @@ to allow process instances to be started manually and via Infinity Process Platf
<li>Name - Specify name of the end event</li>
<li>Description - Specify the description</li>
</ul>
-
+<!--
<h3>Implementation</h3>
<p>This option is available only when you switch to <a href="model-views/pep-panels.html">Integrator</a> profile.
Using this option,
you can select the application which is implementing the logic for the task.</p>
-
+ -->
<h3>Comments - End Event</h3>
<p>To add comments for events, perform the following steps:</p>
<ol>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
index 40dc171..583b64f 100644
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
+++ b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/pep-struct-type.htm
@@ -221,14 +221,14 @@ To refer the structure type:
Document Repository</a></span>
<!-- link from inside Portal Documentation jar -->
<span class="hideReference"> of the
- <a href="../../execution-clients/admin-portal/views/admin-portal-repository.html">
+ <a href="../execution-clients/admin-portal/views/admin-portal-repository.html">
Document Repository</a></span>
<span class="showReference">
<a href="PLUGINS_ROOT/org.eclipse.stardust.docs.enduser/html/handbooks/execution-clients/admin-portal/admin-portal.html">
- </a></span>
+ Administration perspective</a></span>
<!-- link from inside Portal Documentation jar -->
<span class="hideReference">
- <a href="../../execution-clients/admin-portal/admin-portal.html">Administration perspective</a></span>
+ <a href="../execution-clients/admin-portal/admin-portal.html">Administration perspective</a></span>
view, create a folder named <tt>schemas</tt>, then upload <tt>mySchema.xsd</tt>
to the newly created folder.
</li>
@@ -236,7 +236,7 @@ To refer the structure type:
<li>If the external xsd is referenced, for example, <tt>/mySchema.xsd</tt> in XPDL file then directly upload <tt>mySchema.xsd</tt> to
the <tt>root</tt> of the document repository. Alternatively, make a jar containing <tt>mySchema.xsd</tt> and add
the jar to the model classpath.</li>
- </ul>
+</ul>
<p>Note that these external structured types are read-only.</p>