summaryrefslogtreecommitdiffstats
diff options
context:
space:
mode:
authorVrishali Doke2012-08-30 06:38:40 (EDT)
committer Stephan Born2012-08-30 06:38:40 (EDT)
commit174be0d760148928d46ea3d588b34497037cd1b2 (patch)
tree9969c0d97c02063354fd917a954d047ab91e2792
parent7ef46ca198f975ceb48f08774bddaafd6322aea0 (diff)
downloadorg.eclipse.stardust.documentation-174be0d760148928d46ea3d588b34497037cd1b2.zip
org.eclipse.stardust.documentation-174be0d760148928d46ea3d588b34497037cd1b2.tar.gz
org.eclipse.stardust.documentation-174be0d760148928d46ea3d588b34497037cd1b2.tar.bz2
CRNT-25597 - Pepper guide structure
git-svn-id: http://emeafrazerg/svn/ipp/product/trunk/stardust/documentation@58797 8100b5e0-4d52-466c-ae9c-bdeccbdeaf6b
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-commit.html114
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-control.html185
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-editing.html269
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-introduction.html90
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-locking.html181
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-preface.html44
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-revert.html86
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-update.html77
-rw-r--r--org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-vcs-view.html72
9 files changed, 0 insertions, 1118 deletions
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-commit.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-commit.html
deleted file mode 100644
index c3d67c7..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-commit.html
+++ /dev/null
@@ -1,114 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Committing Changes</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Reverting Changes","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-locking.html","con-revert.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-<h1>Committing Changes</h1>
-<p>In case a model element is locked and has local changes, these changes
-can be committed to the subversion repository.</p>
-<ul>
- <li><a href="#steps">The Commit Process</a></li>
- <li><a href="#commit">Committing Model Element Changes</a></li>
- <li><a href="#dialog">The Commit Changes Dialog</a></li>
- <li><a href="#conflict">Conflicting IDs On Model Element Commit</a></li>
-<!-- <li><a href="#merge">Merging Changes</a></li>-->
-</ul>
-<h2 id="steps">The Commit Process</h2>
-<p>During a commit, the following steps will be performed
-automatically:</p>
-<ul>
- <li>Potential collisions (e.g. two datas with same IDs) are checked
- for, to ensure that the commit does not introduce inconsistencies. In case
- of inconsistencies, try to resolve them as described in the section
- <a href="#conflict">Conflicting IDs on Model Element Commit</a>.</li>
- <li>It will be checked that locks obtained were not released by the
- administrator.</li>
- <li>Remote changes are merged into the local model to all model
- elements that are not locked.</li>
- <li>The changes are committed and lock files are created for new
- elements.</li>
- <li>Locks will be released if not requested otherwise.</li>
-</ul>
-<h2 id="commit">Committing Model Element Changes</h2>
-<p>All model element nodes in the model Outline view representing lockable
-elements provide the option <strong>Commit Changes</strong>. To commit a change
-for an element, right-click its node in the Outline view and select <strong>Commit
-Changes</strong>.</p>
-
-<p class="image"><img src="images/commit-element-changes.png"
- alt="Committing Model Element Changes."><br>
-<strong>Figure:</strong> Committing Model Element Changes.</p>
-<p>Please note that the model has to be saved before this operation. Otherwise
-a warning dialog opens.</p>
-<p class="image"><img src="images/save-model-warning.png"
- alt="Save Warning"><br>
-<strong>Figure:</strong> Warning indicating to save Model first.</p>
-
-<h2 id="dialog">The Commit Changes Dialog</h2>
-<p>After selecting the option to commit, a <strong>Commit Changes Dialog</strong> opens,
-where you can select the changes on model elements you like to commit. It displays
-all changed and thus locked model elements and new elements with
-checkboxes to select for committing. A checkbox <strong>Keep Lock</strong>
-is provided to choose if the locks of the selected elements
-should be kept after the commit.</p>
-<p class="image"><img src="images
-/commit-dialog-model.png" alt="Commit Changes Dialog"><br>
-<strong>Figure:</strong> The Commit Changes Dialog.</p>
-<p>Overlay icons indicate the sort of changes on elements.
-The pen icon indicates changes on an element that already existed:</p>
-<p class="image"><img src="images/pen-icon.png" alt=""><br>
-<strong>Figure:</strong> Changed Model Element.</p>
-<p>The plus icon indicates that an element has been added to the model:</p>
-<p class="image"><img src="images/plus-icon.png" alt=""><br>
-<strong>Figure:</strong> Added Model Element.</p>
-<p>The cross icon indicates that an existing element has been deleted from
-the model:</p>
-<p class="image"><img src="images/cross-icon.png" alt=""><br>
-<strong>Figure:</strong> Deleted Model Element.</p>
-<p>Also an entry field for a commit comment is provided. A commit comment
-is obligatory, otherwise the <strong>OK</strong> button is not enabled. Please
-enter at least 10 characters.</p>
-
-<p>After the <strong>OK</strong> button is selected, all selected changes will be
-merged with the model file in the repository. Committing a changed element increments
- the counter of the element lock file. To cancel the commit select <strong>Cancel</strong>.</p>
-<h3 id="commitAll">Committing All Changes in a Model</h3>
-<p>To commit all changes in a model, select the
-<strong>All Elements</strong> entry. All elements pertaining to the
-model and having changes will be selected for committing. </p>
-<p class="image"><img src="images/commit-all-changes.png" alt=""><br>
-<strong>Figure:</strong> Commit all Changed Elements in a Model.</p>
-<h2 id="conflict">Conflicting IDs On Model Element Commit</h2>
-<p>Conflicts on IDs might occur during a commit of model elements, for example
-if a commit results in having two elements with the same ID in the repository.
-In that case a dialog opens to indicate that a duplicate ID or name exists and to
-offer to change them directly in appropriate entry fields:</p>
-<p class="image"><img src="images/merge-dupl-id.png" alt="Conflict Dialog"><br>
-<strong>Figure:</strong> Dialog to change ID or Name.</p>
-<p>After giving the element a new ID and closing this dialog,
- the commit process continues.</p>
-
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-control.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-control.html
deleted file mode 100644
index f112180..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-control.html
+++ /dev/null
@@ -1,185 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Concurrency Control</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Locking and Unlocking Elements","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-introduction.html","con-locking.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-<h1>Concurrency Control</h1>
-<ul>
- <li><a href="#requirements">Preparing for Concurrency Control</a></li>
- <li><a href="#adding">Adding Concurrency Control to Process Models</a></li>
- <li><a href="#prefs">Setting Concurrency Preferences</a></li>
- <li><a href="#disconnect">Disconnecting From Concurrency Control</a></li>
- <li><a href="#lockFiles">Lock Files</a></li>
-<!-- <li><a href="#offline">Working Offline</a></li> -->
- <!-- <li><a href="#consistency">Maintaining Model Consistency</a></li>-->
- <li><a href="#upgrade">Upgrading Models</a></li>
-</ul>
-
-<h2 id="requirements">Preparing for Concurrency Control</h2>
-<p>The Concurrency Control functionality is only available in case you have a
-project with a connection to a Subversion repository and your model is shared
-with this connection.
-To work with a shared project you either have to check out an existing project
-from the repository or share a local project with the repository.</p>
-
-<h3>Subversion Connection</h3>
-<p>You need an Subversion (SVN) repository added to your workspace to work in concurrency
-mode. To add an existing
-Subversion repository to your workspace:</p>
-<ol>
- <li>Select <strong>Windows &gt; Open Perspective &gt; Other &gt; SVN Repository Exploring</strong>.</li>
- <li>Click the <strong>Add SVN Repository</strong> icon.</li>
- <li>In the upcoming dialog enter the URL of your repository location.</li>
- <li>Select <strong>Finish</strong>.</li>
-</ol>
-<p>For detailed information on adding an SVN connection, please refer to
-the <strong>Subclipse - Subversion Eclipse Plugin</strong> documentation
-(Workbench User Guide &gt; Getting started &gt; Team SVN tutorial &gt;
-Creating a new Repository Location).</p>
-<h3 id="share">Sharing a Project</h3>
-<p>In case you want to use a local project for concurrency mode, you have to share this project
-with an SVN repository. To share a project:</p>
-<ol>
- <li>Right-click your project in the Package Explorer.</li>
- <li>Select <strong>Team &gt; Share Project</strong>.
-<p class="image"><img src="images/share-project.png" alt=""><br>
-<strong>Figure:</strong></p></li>
- <li>Select <strong>SVN</strong> as repository plug-in.
- <p class="image"><img src="images/share-project-svn.png" alt=""></p></li>
- <li>Click <strong>Next</strong>.</li>
- <li>Create a new repository location or use an existing repository location.</li>
- <li>In the latter case browse to the existing location.</li>
-</ol>
-<p class="image"><img src="images/share-project-rep.png" alt=""></p>
-<p>For detailed information on sharing a project, please refer to
-the <strong>Subclipse - Subversion Eclipse Plugin</strong> documentation
-(Workbench User Guide &gt; Getting started &gt; Team SVN tutorial
-&gt; Connect an Existing Project with SVN).</p>
-<h3 id="checkout">Checking out existing Projects</h3>
-<p>To check out an existing project:</p>
-<ol>
- <li>Switch to the <strong>SVN Repositories</strong> perspective.</li>
- <li>Go to the location of your project.</li>
- <li>Select the project and choose <strong>Checkout</strong>.</li>
-</ol>
-<p>For detailed information on checking out existing projects from the repository,
- please refer to the <strong>Subclipse - Subversion Eclipse Plugin</strong> documentation
-(Workbench User Guide &gt; Getting started &gt; Team SVN tutorial &gt; Checkout).</p>
-<h3 id="checkout">Checking out Models from the Repository</h3>
-<p>In case a new model has been checked in by another user, you can
-check out this model and its lock files from the repository.
-Synchronizing your project with the repository indicates if new models
-have been added. For detailed information on synchronizing with a repository,
-please refer to the <strong>Subclipse - Subversion Eclipse Plugin</strong>
-documentation (Reference &gt; Team Menu &gt; Team Synchronizing Perspective ).</p>
-
-<p class="note"><strong>Note</strong><br>
-Please make sure that you use the latest version of a model element for
-concurrency control, otherwise it might lead to inconsistencies.</p>
-<h2 id="adding">Adding Concurrency Control to Process Models</h2>
-<p>To add concurrency control to a model, right-click the model in the Outline view
-and select <strong>Add Concurrency Management</strong>. With this action a
-commit to the repository is invoked automatically.</p>
-<p class="image"><img src="images/add-concurrency.png"
- alt="Adding Concurrency Control"><br>
-<strong>Figure:</strong> Add Concurrency Control.</p>
-<p>If the model is in <a href="con-introduction.html#version">version management mode</a>,
-the necessary lock files are created and the model state is switched to
-concurrency mode. In case the model is in <a href="con-introduction.html#local">local
-file mode</a>, the model file is checked into the subversion repository.</p>
-<p>In case a model has been shared before and changes are performed
-in local mode, it is not possible to share this model again. You have
-to check out a clean copy of the model from the repository and repeat the
-changes. An according warning message is opening to inform you about these
-necessary steps:</p>
-<p class="image"><img src="images/share-operation-warning.png"
- alt="Sharing Warning Message"><br>
-<strong>Figure:</strong> Warning Message for already Shared Model.</p>
-<h2 id="prefs">Setting Concurrency Preferences</h2>
-<p>You can set the following preferences for handling the Concurrency
-Management Control:</p>
-<ul>
- <li>enable and enter a rate for a refresh job to periodically refresh
- informations from the repository. Please note that the value must be an
- Integer between 30 and 7200 (seconds).</li>
- <li>enable and set a retry rate in seconds in case of connection failure.
- Please note that the value must be an
- Integer between 30 and 7200 (seconds).</li>
-</ul>
-<p>To set these preferences, open the <strong>Preferences</strong> dialog:</p>
-<ol>
- <li>Select <strong>Window &gt; Preferences</strong>.</li>
- <li><span>Expand the <strong>@productname@</strong> entry in the left
- pane and select <strong>Concurrency Management Preferences</strong>.</span></li>
- <li><span>Now you can set your preferences.</span></li>
-</ol>
-<p class="image"><img src="images/preferences.png" alt="Concurrency Preferences"><br>
-<strong>Figure:</strong> Concurrency Management Preferences.</p>
-<h2 id="disconnect">Disconnecting From Concurrency Control</h2>
-<p>To exit the <strong>Concurrency Management Mode</strong>, right-click the
-model in the Outline view and select <strong>Disconnect From Concurrency Management</strong>:</p>
-<p class="image"><img src="images/disconnect.png"
- alt="Disconnect From Cocurrency Control"><br>
-<strong>Figure:</strong> Disconnect From Concurrency Control.</p>
-<p>The following steps are performed automatically during a disconnect to
-ensure that the disconnect is not called by several users simultaneously or one
-after another:</p>
-<ul>
- <li>locking and updating the XPDL</li>
- <li>removing lock folder and all collaboration extended attributes</li>
- <li>saving and committing the XPDL file</li>
- <li>locking the folder</li>
- <li>unlocking the XPDL file</li>
-</ul>
-<h2 id="lockFiles">Lock Files</h2>
-<p>For all separately lockable model elements, lock files are created in a
-model specific directory inside the same project. All lock files are added and
-committed to the version control system, when the <strong>Concurrency Management Mode</strong>
-is switched on. To be able
-to track changes, lock files are modified and committed upon changes of these
-model elements. A number that will be incremented on
-each commit of a changes of an element is stored in the according lock files.</p>
-
-<h3>Lock File Naming</h3>
-<p>The names of lock files look are composed as follows:</p>
-<pre>&lt;project_root&gt;/.MODEL_&lt;GUID&gt;/&lt;element_type&gt;/&lt;element_type&gt;__&lt;element_uuid&gt;.lck</pre>
-<p>Whereby:</p>
-<ul>
- <li>MODEL_&lt;GUID&gt; is a GUID generated on entering the concurrency mode and saved in the model extended attributes</li>
- <li>element_type corresponds the EMF specific name feature, for example: <tt>processDefinition__ProcessDefinition_1.lck</tt></li>
- <li>element UUID, this number is saved with the element in its extended attributes and does not change, e.g. on element renaming.</li>
-</ul>
-<!-- <h2 id="offline">Working Offline</h2>
-<p>You can work offline on process models. Locked model elements can be modified without server connectivity.</p>-->
-
-<h2 id="upgrade">Ugrading Models</h2>
-<p>Upgrading a model requires a lock on all model elements as obtained by the
-<strong>Lock All for Editing</strong> option. Please refer to section
-<a href="con-locking.html#lockAll">Locking all Lockable Elements</a> of chapter
-<a href="con-locking.html">Locking and Unlocking Elements</a> for information on this
-option. For a model upgrade, the lock on all
-model elements is obtained implicitely.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-editing.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-editing.html
deleted file mode 100644
index 4003b23..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-editing.html
+++ /dev/null
@@ -1,269 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Working with Model Elements in Concurrency Mode</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Watching Collaborative Modeling Activities","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-update.html","con-vcs-view.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-<h1>Working with Model Elements in Concurrency Mode</h1>
-<ul>
- <li><a href="#import">Importing Model Elements</a></li>
- <li><a href="#process">Editing Process Definitions</a></li>
- <li><a href="#diagrams">Editing Diagrams</a></li>
- <li><a href="#property">Editing Mode in Property Dialogs</a></li>
- <li><a href="#copy">Cut, Copy and Paste Operations</a></li>
- <li><a href="#direct">Renaming Model Elements</a></li>
- <li><a href="#creating">Creating New Elements</a></li>
- <li><a href="#delete">Deleting Elements</a></li>
-<!-- <li><a href="#changes">Model Element Changes Indication</a></li>-->
- <li><a href="#state">Model Element State Indication</a></li>
- <li><a href="#external">External Model Information Resources</a></li>
-</ul>
-<h2 id="import">Importing Model Elements</h2>
-<p>The import of model elements is only possible, if a global lock is
-set. This can be achieved by the <strong>Lock All For Editing</strong>
-option. Please refer to the section <a href="con-locking.html#lockAll">
-Locking all Lockable Elements</a> of the chapter <a href="con-locking.html">Locking
-and Unlocking Elements</a> for detailed information on this option.</p>
-<p>In case you try to import model elements without owning a global lock on
-the target model, the following error message requesting to obtain a global lock
-first is displayed:</p>
-<p class="image"><img src="images/import-lock-warning.png" alt="Error Message"><br>
-<strong>Figure:</strong> Message Dialog to indicate the required Lock.</p>
-<h2 id="process">Editing Process Definitions</h2>
-<p>If a process definition is not locked for editing, no
-elements pertaining to process definitions like activities, triggers,
-transitions or data paths, can be added, removed or edited in this
-process definition.</p>
-<h2 id="diagrams">Editing Diagrams</h2>
-<h3>Editing Process Diagrams</h3>
-<p>Process diagrams are not editable, if the parent process definition
-is not locked. You can open them in read-only mode, which means:</p>
-<ul>
- <li>Symbols cannot be moved.</li>
- <li>No symbols can be added, deleted, cut, copied or pasted.</li>
- <li>No drag and drop from the Outline view is possible.</li>
- <li>Options from the toolbar palette cannot be used.</li>
- <li>Model elements pertaining to the process definition cannot be renamed.</li>
-</ul>
-<p>A diagram in locked state might contain model elements like participants, applications
-or data, that can be changed independently. In case these elements are locked for editing,
-they can be edited from within the diagram, like opening the property dialog,
-renaming and deleting, but their symbols have the same restrictions as all
-element symbols in a non-editable diagram.</p>
-
-<p>In case you try to edit a model element pertaining to the process definition or
-another element, which is not in locked state, a message dialog opens to notify that
-the element has to be locked first:</p>
-<p class="image"><img src="images/diagram-element-lock-warning.png" alt="Lock First Warning"><br>
-<strong>Figure:</strong> Message Dialog requesting Lock on Element.</p>
-
-<h3>Editing Model Diagrams</h3>
-<p>In case a model diagram is not locked for editing, you can open it
-in read-only mode, as described for process diagrams.</p>
-<p>The behavior of the contained symbols pertaining to model elements is the
-same as described for process diagrams.</p>
-<h2 id="property">Editing Mode in Property Dialogs</h2>
-<p>Property dialogs of model elements of a model in <strong>Concurrency
-Management Mode</strong> are displaying all control fields in read-only mode. To edit
-content, a button <strong>Lock for Editing</strong> is provided at the bottom of the
-dialog. Clicking this button will lock the corresponding model element or, if
-the model element to be edited is only part of a lockable element, its
-containing element.</p>
-<p class="image"><img src="images/lock-for-editing-props.png"
-alt="Property Dialog Example"><br>
-<strong>Figure:</strong> Property Dialog in read-only Mode.</p>
-<p>In case the lock attempt fails, an according error dialog opens and all
-controls stay in readonly mode.</p>
-<p class="image"><a href="images/lock-problem-props_orgSize.png" target="_blank">
-<img src="images/lock-problem-props.png" alt="Error Dialog"></a><br>
-<strong>Figure:</strong> Error Dialog</p>
-<!-- is removed from properties dialog (temporarily?)
-<p>To unlock the model element, select the <strong>Revert Changes</strong> button in
-the lower right corner of the property dialog. This option will revert
-your changes, unlock the model element and set the entry fields
-to read-only state. Please refer to the chapter
-<a href="con-revert.html">Reverting Changes</a> for detailed information
-on reverting changes.</p>
-
-<p class="image"><img src="images/revert-changes-button-props.png" alt="Revert"><br>
-<strong>Figure:</strong> Revert Changes.</p>-->
-<p>Property dialogs of elements pertaining to a process definition are
-not editable if the parent process definition is not locked.</p>
-<h2 id="copy">Cut, Copy and Paste Operations</h2>
-<p>In case model elements are copied to a model in concurrency mode, the new
-elements will be displayed as newly added elements in the Outline view
-and provided to be committed in the commit dialog. In case a diagram or
-process definition, where a copied element should
-be pasted, is not locked, a warning dialog opens to indicate that
-the target element has to be locked first.</p>
-
-<p class="image"><img src="images/paste-warning.png" alt="Paste Warning"><br>
-<strong>Figure:</strong> Message Dialog requesting Lock.</p>
-
-<h2 id="direct">Renaming Model Elements</h2>
-<p>Direct editing of symbol names, like using the <strong>F2</strong> short
-key or a mouse click on the name, requires a lock for editing on the according element or
-a lock on the according process definition accordingly.
-Otherwise a message dialog opens to inform that a lock has to be achieved
-before.</p>
-<p class="image"><img src="images/lock-element-first.png" alt=" Dialog"><br>
-<strong>Figure:</strong> Lock Failed Dialog</p>
-
-<h2 id="creating">Creating New Elements</h2>
-<p>If new lockable model elements are created, their according lock file will not be
-created and submitted immediately, this is done on commit. New elements pertaining to
-a parent node, for example a process definition, can only be created, if the parent node
-is locked for editing.</p>
-<p>For all lockable element, the newly created
-element is indicated as new with an overlay icon displaying a plus sign
-in the right upper corner of the element icon:</p>
-<p class="image"><img src="images/plus-icon.png" alt=""><br>
-<strong>Figure:</strong> Icon indicating an added model element.</p>
-<h2 id="delete">Deleting Elements</h2>
-<p>A confirmation dialog open when deleting a lockable element:</p>
-<p class="image"><img src="images/delete-confirm.png"
- alt="Deletion Confirmation Dialog"><br>
-<strong>Figure:</strong> Deletion Confirmation Dialog</p>
-<p>To delete any element a lock must be obtained before the user can delete
-the element. Deleting activities or other elements pertaining to a process
-definition, requires a lock of the according process definition. In that case a
-dialog opens to indicate that a lock is needed:</p>
-<p class="image"><img src="images/delete-lock-first.png" alt="Error Dialog"><br>
-<strong>Figure:</strong> Dialog indicating required Lock.</p>
-<h3>Deleting Elements having Symbols in a Diagram</h3>
-<p>In case an element is deleted having symbols in a diagram, that is
-locked for editing, the symbols are also deleted. If the according diagram is not
-locked for editing, the symbols are not deleted, but replaced with undefined
-symbols.</p>
-<p class="image"><img src="images/undefined-element.png"
- alt="Undefined Model Element"><br>
-<strong>Figure:</strong> Deleted Element replaced by an undefined Element.</p>
-<h3>Indication to other Users</h3>
-<p>In case a user deletes a lockable model element and commits this change,
-this is indicated in the appropriate model element in the Outline
-view to other users by an overlay icon representing a cross.</p>
-<p class="image"><img src="images/cross-remotely-icon.png"
- alt="Model Element deleted remotely."><br>
-<strong>Figure:</strong> Model Element deleted remotely.</p>
-<!--<h2 id="changes">Model Element Changes Indication</h2>
-<p>In the Outline view, changes on model elements are indicated via
-an overlay icon in the right upper corner on the model element icon.
-These indicate the following sort of changes:</p>
-<ul>
- <li><a href="#localChange">Local and Remote Changes</a></li>
- <li><a href="#added">Added Element</a></li>
- <li><a href="#deleted">Deleted Element</a></li>
-</ul>
-<h3 id="localChange">Local and Remote Changes</h3>
-<p>In case a model element has local or remote changes that are not committed yet, an
-overlay icon showing a pen is displayed in the right upper corner of the element
-icon in the Outline view:</p>
-<p class="image"><img src="images/pen-icon.png" alt=""><br>
-<strong>Figure:</strong> Icon indicating local changes.</p>
-<p>You can differ if the changes are local or remote by the overlay icon
-in the lower right corner indicating the model element state, which is
-described in section <a href="#state">Model Element State Indication</a>.
-Thus, a barrel icon or a locked sign icon combined with the pen icon indicates
-that the model element has been changed by another user. In that case, an
-update might be useful. For example:</p>
-<p class="image"><img src="images/pen-barrel-icon.png" alt=""><br>
-<strong>Figure:</strong> Icon indicating remote changes.</p>
-<p>Whereas the checkmark icon combined with the pen icon indicates local changes
-that are not committed yet.</p>
-<h3 id="added">Added Element</h3>
-<p>In case a model element is locally added and not committed yet, or
-a model element is added remotely, an
-overlay icon displaying a plus sign is displayed in the right upper corner of
-the element icon:</p>
-<p class="image"><img src="images/plus-icon.png" alt=""><br>
-<strong>Figure:</strong> Icon indicating an added model element.</p>
-<p>You can differ if the element is added locally or remotely by the overlay icon
-in the lower right corner indicating the model element state, which is
-described in section <a href="#state">Model Element State Indication</a>.
-Thus, a barrel icon or a locked sign icon combined with the plus icon indicates
-that the model element has been deleted by another user. In that case, an
-update might be useful.</p>
-<p>Whereas the checkmark icon combined with the plus icon indicates
-that the element is locally added and not committed yet.</p>
-<h3 id="deleted">Deleted Element</h3>
-<p>In case a model element is deleted from the repository by another
-user, an overlay icon displaying a cross sign is displayed in the right upper corner of
-the element icon:</p>
-<p class="image"><img src="images/cross-remotely-icon.png" alt=""><br>
-<strong>Figure:</strong> Icon indicating a remotely deleted model element.</p>
-<p>You can differ if the element is deleted locally or remotely by the overlay icon
-in the lower right corner indicating the model element state, which is
-described in section <a href="#state">Model Element State Indication</a>.
-Thus, a barrel icon or a locked sign icon combined with the cross icon indicates
-that the model element has been deleted by another user. In that case, an
-update might be useful.</p>
-<p>Whereas the checkmark icon combined with the cross icon indicates
-that the element is locally deleted.</p>-->
-
-
-<h2 id="state">Model Element State Indication</h2>
-<p>In the Outline view, the lock state of model elements are indicated in
-the lower right corner of the model elements icon. The following states are
-possible:</p>
-<ul>
- <li><a href="#shared">Shared Mode</a></li>
- <li><a href="#locked">Locked State</a></li>
- <li><a href="#lockedUser">Locked by another User</a></li>
-</ul>
-<h3 id="shared">Shared Mode</h3>
-<p>In case a model element is shared with the repository, but not
-locked, the following overlay icon indicates this state:</p>
-<p class="image"><img src="images/barrel-icon.png" alt=""><br>
-<strong>Figure:</strong> Shared Mode</p>
-<h3 id="locked">Locked State</h3>
-<p>In case a model element is locked for editing, a checkmark icon
-indicates that state:</p>
-<p class="image"><img src="images/checkmark-icon.png" alt=""><br>
-<strong>Figure:</strong> Locked State</p>
-<h3 id="lockedUser">Locked by another User</h3>
-<p>In case a model element is locked by another user, the following
-icon is indicating this state:</p>
-<p class="image"><img src="images/locked-other-user-icon.png" alt=""><br>
-<strong>Figure:</strong> Locked by another User</p>
-<p>Additionally the name of the user who locked this element is
-added to the right side of the model element name, e.g.:</p>
-<p class="image"><img src="images/locked-by-user.png" alt=""><br>
-<strong>Figure:</strong> Name of the User who locked the Element.</p>
-<h2 id="external">External Model Information Resources</h2>
-<p>In case an already existing model element is imported from an external
-model resource, the original version will be replaced. A confirmation dialog
-opens, where you can choose to replace the existing element or to
-reuse the element in the model:</p>
-<p class="image"><img src="images/external-model-overwrite.png" alt=""><br>
-<strong>Figure:</strong> Replacement Dialog</p>
-
-<p>The corresponding
-model elements have to be locked for editing before this action.
-Otherwise, an according error message requesting to lock the model
-elements before the import is displayed.</p>
-<p>Please refer to the chapter
-<a href="../mg-registry.html">External Model Resources</a> for
-general information on working with external model resources.</p>
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-introduction.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-introduction.html
deleted file mode 100644
index 5f4fbc6..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-introduction.html
+++ /dev/null
@@ -1,90 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Introduction</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Concurrency Control","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "","con-control.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-<h1>Introduction</h1>
-<p>@productname@ supports concurrent work on process models
-stored in a central repository.</p>
-<ul>
- <li><a href="#modes">Collaborative Modeling Modes</a></li>
- <li><a href="#concept">Concurrency Management Mode Locking Concept</a></li>
- <li><a href="#vcs">Version Control System Support</a></li>
- <li><a href="#scope">Scope</a></li>
-</ul>
-<h2 id="modes">Collaborative Modeling Modes</h2>
-<p>You may work on a @productname@ model file in three different modes:</p>
-<ul>
- <li><a href="#local">Local File Mode</a></li>
- <li><a href="#version">Version Management Mode</a></li>
- <li><a href="#con">Concurrency Management Mode</a></li>
-</ul>
-<p>In a modeling environment, a model always knows about its state regarding the
-above modes and behaves differently depending on this state, for example concerning
-editing.</p>
-<h3 id="local">Local File Mode</h3>
-<p>Working in <strong>Local File Mode</strong> means working on a plain XPDL file.</p>
-<h3 id="version">Version Management Mode</h3>
-<p>When working in <strong>Version Management Mode</strong>, the XPDL file is
-checked into SVN and managed as any other programming artefact. The following diagram
-illustrates the structure of a development project in
-<strong>Version Management Mode</strong>:</p>
-<p class="image"><img src="images/version-control-mode.png"
- alt="Diagram - Version Management Mode"><br>
-<strong>Figure:</strong> Development Project Structure in Version Management Mode.</p>
-<h3 id="con">Concurrency Management Mode</h3>
-<p>When working in <strong>Concurrency Management Mode</strong>, the XPDL file is
-checked into SVN and concurrent modeling is managed via auxiliary lock files. The following
-diagram illustrates the structure of a development project in
-<strong>Concurrency Management Mode</strong>:</p>
-<p class="image"><img src="images/collaborative-modeling-mode.png"
- alt="Diagram - Concurrency Management Mode"><br>
-<strong>Figure:</strong> Development Project Structure in Concurrency Management Mode</p>
-
-<h2 id="concept">Concurrency Management Mode Locking Concept</h2>
-<p>The <strong>Concurrency Management Mode</strong> adds the concept of locking
-specific model elements for update in addition to the regular version management.
-Obtaining a lock enables the lock owner to update a model element and write these changes back.</p>
-
-<h2 id="vcs">Version Control System Support</h2>
-<p>@productname@ supports the open source version
-control system <a href="http://subversion.tigris.org/">Subversion</a> for
-concurrency control. To support Subversion (up to version 1.5.x) as
-repository, the <a href="http://subclipse.tigris.org/">Subclipse</a> 1.6.5
-version control system plugins are supplied in the @productname@
-repository.</p>
-
-<p>The plug-ins should be listed in your Eclipse
-plug-in details after restarting Eclipse with the <tt>-clean</tt> option as
-the following screenshot indicates:</p>
-
-<p class="image"><img src="images/svn-plugins.png"
- alt="SVN Plugins"><br>
-<strong>Figure:</strong> Installed Subversion Plugins</p>
-
-<h2 id="scope">Scope</h2>
-<p>Please note that the concurrency mode only changes user operations in the modeling environment.
-The @productname@ Portals and command line utilities are not affected.</p>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-locking.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-locking.html
deleted file mode 100644
index f0376f9..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-locking.html
+++ /dev/null
@@ -1,181 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Locking and Unlocking Elements</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Committing Changes","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-control.html","con-commit.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-<h1>Locking and Unlocking Elements</h1>
-<p>In the <strong>Concurrency Management Mode</strong> specific model
-elements can be locked for editing. Obtaining a lock enables the lock owner to
-perform changes on a model element and write these changes back.</p>
-
-<ul>
- <li><a href="#separat">Separately Lockable Model Elements</a></li>
- <li><a href="#editOption">Locking Elements for Editing</a></li>
- <li><a href="#lockAll">Locking all Lockable Elements</a></li>
- <li><a href="#release">Releasing Locks</a></li>
- <li><a href="#force">Force Unlock on Existing Foreign Locks</a></li>
- <li><a href="#problem">Lock Failed Error - Item is out of date</a></li>
-</ul>
-<h2 id="separat">Separately Lockable Model Elements</h2>
-<p>The following elements of a process model can be locked separately:</p>
-<ul>
- <li>the model itself</li>
- <li>structured type definitions</li>
- <li>process definitions</li>
- <li>model diagrams</li>
- <li>data</li>
- <li>applications</li>
- <li>participants</li>
- <li>link types</li>
-</ul>
-
-<h2 id="editOption">Locking Elements for Editing</h2>
-<p>Before an element can be locked, it will be checked, if remote changes exist. In
-that case, the element has to be updated first. Please refer to the chapter
-<a href="con-update.html">Updating Model and Model Elements</a> for detailed
-information on updating elements. Newly created model elements
-have no locks per default. According lock files are created during a commit.</p>
-<p>All nodes in the model Outline view representing lockable elements as listed in
-the section
-<a href="#separat">Separately Lockable Model Elements</a>,
-provide the <strong>Lock for Editing</strong> option in their context-menu. This option is
-enabled if the model element is not already locked. To lock an
-element, right-click the according node in the Outline view and select
-<strong>Lock for Editing</strong>.</p>
-<p class="image"><img src="images/edit-element.png" alt="Select Edit."><br>
-<strong>Figure:</strong> Lock Element for Editing.</p>
-<p>In cases changes have been performed on this model element and committed
-meanwhile by another user,
-a warning dialog opens, indicating that an update is necessary first:</p>
-<p class="image"><img src="images/update-first.png" alt="Update First Dialog"><br>
-<strong>Figure:</strong> Warning Dialog for updating first.</p>
-<p>If a model element is locked for editing, this is indicated via an overlay icon
-presenting a checkmark, in the right
-lower corner of the element icon in the Outline view.</p>
-<p class="image"><img src="images/edit-icon.png" alt="Edit Icon"><br>
-<strong>Figure:</strong> Icon to indicate Edit Mode for a Process Definition.</p>
-<p>Please note that locking the model itself will not lock all lockable
-model elements implicitely. Please refer to
-the section <a href="#lockAll">Locking all Lockable Elements</a> in case you want
-to lock all lockable elements in a model.</p>
-<h2 id="lockAll">Locking all Lockable Elements</h2>
-<p>Locking a model itself will not lock all lockable
-model elements implicitely. It only locks model specific properties. In case
-you like to lock all lockable elements in a model, right-click
-the model in the Outline view and choose the
-option <strong>Lock All For Editing</strong>.</p>
-<p class="image"><img src="images/lock-all-for-editing.png" alt="Lock All"><br>
-<strong>Figure:</strong> Lock All for Editing Option.</p>
-<p class="note"><strong>Note:</strong>
-Model upgrades require a lock on all model elements. For model upgrade, the lock
-on all model elements is obtained implicitely.</p>
-
-<h3 id="implUpdate">Implicit Update Operations Requiring A Global Lock</h3>
-<p>The following actions require all model elements to be locked:</p>
-<ul>
- <li>modifying oranizational hierarchies in model diagrams</li>
- <li>model upgrades</li>
-</ul>
-<h2 id="release">Releasing Locks</h2>
-<h3 id="implicit">Implicit Lock Release</h3>
-<p>Locks are implicitely released if changes on a model element are committed and the option
-<strong>Keep Locks</strong> is disabled in the commit dialog.
-Please refer to the section <a href="con-commit.html#dialog">The Commit Dialog</a>
-of the chapter <a href="con-commit.html">Committing Changes</a> for
-information on this option.</p>
-<h3 id="explicit">Explicit Lock Release</h3>
-<p>Locked elements can be unlocked explicitly without committing,
-in case you like to revert your local changes.
-In this case right-click the according node
-in the Outline view and select <strong>Revert Changes</strong>.
-Please refer to the chapter <a href="con-revert.html">Reverting Changes</a>
-for detailed information.</p>
-
-<h2 id="force">Force Unlock on Existing Foreign Locks</h2>
-<p>In case a foreign lock is not released by a user, it can be explicitly
-released by a user, who has the permission to force unlocks. By default, all
-users have the permission to force unlocks. To change this behavior, administrators
-have the option to prohibit the permission for specific users. Please refer to
-section <a href="#prohibit">Prohibiting Force Unlock for Specific Users</a>
-for details.</p>
-<p>Having the permission, you can force unlocking
-existing foreign locks to other users by
-selecting <strong>Force Unlock All</strong> in the model
-context-menu in the Outline view:</p>
-<p class="image"><img src="images/force-unlock-all.png"
-alt="Force Unlock All"><br>
-<strong>Figure:</strong> Force Unlock All</p>
-<p>The following dialog opens before the unlock
-is performed to confirm the unlock and give you information about the option:</p>
-<p class="image"><img src="images/force-unlock-warning.png"
-alt="Force Unlock Warning"><br>
-<strong>Figure:</strong> Force Unlock Warning</p>
-<p>After selecting <strong>OK</strong>, another dialog opens where you can
-explicitly select the
-model elements, where an unlock on all foreign locks should be performed on:</p>
-<p class="image"><img src="images/force-unlock-dialog.png"
-alt="Force Unlock Dialog"><br>
-<strong>Figure:</strong> Force Unlock Dialog</p>
-<p>In case a force unlock operation is tried from a user not having the
-permission to, an according error message opens.</p>
-<!--<p class="image"><img src="images/unlock-error-dialog.png"
-alt="Force Unlock Error Dialog"><br>
-<strong>Figure:</strong> Force Unlock Error Dialog</p>-->
-
-<h3 id="prohibit">Prohibiting Force Unlock for Specific Users</h3>
-<p>By default, all users have the permission to perform an unlock all. Administrators
-have the possibility to prohibit force unlock for specific users by creating
-SVN hooks. Thus it can be decided when lock creation and lock
-releases are allowed to happen. This can be performed via SVN repository hooks.
-In case you are an administrator and like to use this functionality, please refer to the
-<a href="http://svnbook.red-bean.com/nightly/en/svn-book.html#svn.reposadmin.create.hooks">
-Implementing Repository Hooks</a> section of the SVN documentation
-for detailed information on creating hooks.</p>
-<p>The <tt>pre-lock</tt> and <tt>pre-unlock</tt> hooks allow administrators to
-decide when lock creation and lock releases are allowed to happen.
-Depending on whether or not a lock already exists, these two hooks can
-decide whether or not to allow a certain user to break or steal a lock.
-The <tt>post-lock</tt> and <tt>post-unlock</tt> hooks are also available, and can be used to
-send email after locking actions.</p>
-<h2 id="problem">Lock Failed Error - Item is out of date</h2>
-<p>When trying to lock an element, it might happen that you get an exception
-indicating that the item is out of date, as in the following screenshot:</p>
-<p class="image"><a href="images/lock-problem_orgSize.png" target="_blank">
-<img src="images/lock-problem.png" alt="Lock Error"></a><br>
-<strong>Figure:</strong> Lock Failed Message</p>
-<p>The lock file might be out of date,
-if another user just released a lock on this element and the refresh
-job is not running during your locking process.
-As a workaround, you can either:</p>
-<ul>
- <li>close and reopen your model, or</li>
- <li>set another refresh rate in the
- <strong>Concurrency Management Preferences</strong>.<br>Please refer to the
- section <a href="con-control.html#prefs">Setting Concurrency Preferences</a>
- of the chapter <a href="con-control.html">Concurrency Control</a> for detailed
- information on setting concurrency preferences.</li>
-</ul>
-<p>However, after the lock folder is refreshed, locking is working without problems again.</p>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-preface.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-preface.html
deleted file mode 100644
index 6a21beb..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-preface.html
+++ /dev/null
@@ -1,44 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Collaborative Modeling</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-editing.html","",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide");
- -->
-</script>
-<h1>Collaborative Modeling</h1>
-<p>@productname@ provides you with the option to work in <strong>Concurrency Management Mode</strong>,
-where model files are checked into a subversion repository and concurrent modeling is managed
-via auxiliary lock files.</p>
-<h2>Content</h2>
-<ul>
- <li><a href="con-introduction.html">Introduction</a></li>
- <li><a href="con-control.html">Concurrency Control</a></li>
- <li><a href="con-locking.html">Locking and Unlocking Model Elements</a></li>
- <li><a href="con-commit.html">Committing Changes</a></li>
- <li><a href="con-revert.html">Reverting Changes</a></li>
- <li><a href="con-update.html">Updating Model and Model Elements</a></li>
- <li><a href="con-editing.html">Working with Model Elements in Concurrency Mode</a></li>
-<!-- <li><a href="con-update-elements.html">Updating Elements</a></li>-->
- <li><a href="con-vcs-view.html">Watching Collaborative Modeling Activities</a></li>
-<!-- <li><a href="con-tracking.html">Tracking Version History</a></li> -->
-</ul>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-revert.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-revert.html
deleted file mode 100644
index 900d40c..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-revert.html
+++ /dev/null
@@ -1,86 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Reverting Changes</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Updating Model and Model Elements","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-commit.html","con-update.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-
-<h1>Reverting Changes</h1>
-<p>If changes are not yet committed to the repository server, they can be reverted by
-updating the local version against the server version and releasing the lock.</p>
-<ul>
- <li><a href="#revert">Reverting Changes Option</a></li>
- <li><a href="#dialog">Reverting Changes Dialog</a></li>
-</ul>
-<h2 id="revert">Reverting Changes Option</h2>
-<p>In case a model element has changes that are not yet committed,
-you can revert those changes. Right-click the model in the Outline view and choose
-<strong>Revert Changes</strong>.</p>
-<p class="image"><img src="images/revert-changes.png"
- alt="Revert Changes"><br>
-<strong>Figure:</strong> Select Revert Changes</p>
-<p>The reverting option now unlocks the model element and reverts its local changes. In case no local changes
-exist, the element is unlocked only.
-Please note that the model has to be saved before this operation. Otherwise
-a warning dialog opens.</p>
-<p class="image"><img src="images/save-model-warning.png"
- alt="Save Warning"><br>
-<strong>Figure:</strong> Warning indicating to save Model first.</p>
-<!-- Does not make sense??: If the model element is locked by another user, the unlocking
-process fails and the following warning dialog opens:</p>-->
-<p>The <strong>Revert Changes</strong> option
-is only available for model elements, if these are locked. It is always available
-for a model, but in case no model elements are locked, the Revert dialog does
-not open and the following message dialog pops up instead:</p>
-<p class="image"><img src="images/no-locks-hold.png"
- alt="No Locks Hold"><br>
-<strong>Figure:</strong> Warning indicating that no elements are locked for editing.</p>
-<h2 id="dialog">Reverting Changes Dialog</h2>
-<p>After selecting the <strong>Revert Changes</strong> option,
-a dialog opens, showing all locked elements. Here the changes
-on elements that should be reverted can be selected.</p>
-<p class="image"><img src="images/revert-changes-dialog.png"
- alt="Revert Changes Dialog"><br>
-<strong>Figure:</strong> The Revert Changes Dialog.</p>
-<p>Diagrams containing model elements with reverted changes, are updated
-automatically.</p>
-<p>Overlay icons indicate the sort of changes on elements.
-The pen icon indicates changes on an element that already existed:</p>
-<p class="image"><img src="images/pen-icon.png" alt=""><br>
-<strong>Figure:</strong> Changed Model Element.</p>
-<p>The plus icon indicates that an element has been added to the model:</p>
-<p class="image"><img src="images/plus-icon.png" alt=""><br>
-<strong>Figure:</strong> Added Model Element.</p>
-<p>The cross icon indicates that an existing element has been deleted from
-the model:</p>
-<p class="image"><img src="images/cross-icon.png" alt=""><br>
-<strong>Figure:</strong> Deleted Model Element.</p>
-<!--same as revert changes for elements
-<h2 id="revertAll">Reverting All Changes</h2>
-<p>To revert all changes in a model, right-click the model in the Outline view and
-select the <strong>Revert Changes</strong> option:</p>
-<p class="image"><img src="images/revert-all-changes.png" alt="Reverting all Changes"><br>
-<strong>Figure:</strong> Reverting all Changes in a Process Model.</p>-->
-
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-update.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-update.html
deleted file mode 100644
index 056b6c0..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-update.html
+++ /dev/null
@@ -1,77 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Updating Model and Model Elements</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
- writeNavigation("Working with Model Elements in Concurrency Mode","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-revert.html","con-editing.html",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-
-<h1>Updating Model and Model Elements</h1>
-<p>If model element changes exist on the repository server, you should perform an update
-on your model or model elements.</p>
-<ul>
- <li><a href="#update">Model Element Update Option</a></li>
- <li><a href="#updateModel">Model Update Option</a></li>
- <li><a href="#dialog">Update Dialog</a></li>
- <li><a href="#conflict">Conflicting IDs On Model Element Update</a></li>
-</ul>
-<p>Please note that an update operation only updates committed changes,
-it does not refresh the lock state of model elements.</p>
-
-<h2 id="update">Model Element Update Option</h2>
-<p>To update your model elements with existing changes
-on the repository server, right-click the model element
-in the Outline view and choose <strong>Update</strong>. Please
-note that this option is only available in case the element
-is in shared state and not locked for editing.</p>
-<p class="image"><img src="images/update-element.png"
- alt="Update"><br>
-<strong>Figure:</strong> Updating a Model Element.</p>
-<p>Please note that the model has to be saved before this operation. Otherwise
-a warning dialog opens.</p>
-<p class="image"><img src="images/save-first-warning.png"
- alt=""><br>
-<strong>Figure:</strong> Warning</p>
-<h2 id="updateModel">Model Update Option</h2>
-<p>The update option is always available for a process model,
-but in the update dialog only those elements are displayed,
-which are in shared mode and thus not locked for editing.</p>
-<h2 id="dialog">Update Dialog</h2>
-<p>After selecting the <strong>Update</strong> option,
-a dialog opens, showing all elements with changes that have been performed
-remotely and have been committed to the repository. Via the checkboxes
-the changes on elements that should be updated can be selected explicitly.</p>
-<p class="image"><img src="images/update-model-dialog.png"
- alt="Update Dialog"><br>
-<strong>Figure:</strong> The Update Dialog.</p>
-<p>Diagrams containing model elements with updated changes, are updated
-automatically.</p>
-<h3 id="conflict">Conflicting IDs On Model Element Update</h3>
-<p>Conflicts on IDs might occur during an update of model element, e.g.
-if an update results in having two elements with the same ID.
-These elements will be treated as different elements then with
-an error indicating the duplicate ID.</p>
-<p class="image"><img src="images/duplicate-error.png"
- alt="Duplicate Error"><br>
-<strong>Figure:</strong> Error indicating duplicate ID.</p>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>
diff --git a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-vcs-view.html b/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-vcs-view.html
deleted file mode 100644
index 1f189d8..0000000
--- a/org.eclipse.stardust.docs.analyst/html/handbooks/modelling_analyst/concurrency/con-vcs-view.html
+++ /dev/null
@@ -1,72 +0,0 @@
-<!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.01//EN" "http://www.w3.org/TR/html4/strict.dtd">
-<html>
-<head>
-<meta http-equiv="Content-Type" content="text/html; charset=ISO-8859-1">
-<meta http-equiv="Content-Style-Type" content="text/css">
-<link rel="STYLESHEET" href="../../../styles/carnot.css" charset="ISO-8859-1"
- type="text/css">
-<title>Watching Collaborative Modeling Activities</title>
-<script language="JavaScript" src="../../../styles/naviLine.js"
- type="text/javascript"></script>
-</head>
-<body>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeNavigation("","PLUGINS_ROOT/org.eclipse.stardust.docs.dev/html/toc.html",
- "con-editing.html","",
- "../../../toc.html","Business Analyst Handbooks",
- "../mg-preface.htm","The Modeling Guide",
- "con-preface.html","Collaborative Modeling");
- -->
-</script>
-<h1>Watching Collaborative Modeling Activities</h1>
-<p>To watch collaborative modeling activities, @productname@
-provides the <strong>Collaborative Modeling Feed View</strong>.</p>
-<h2>The @productname@ Collaborative Modeling Feed View</h2>
-<p>To open the <strong>Collaborative Modeling Feed View</strong>:</p>
-<ol>
- <li>In the main menu select <strong>Window &gt; Show Views
- &gt; Other....</strong>.</li>
- <li>In the <strong>@productname@</strong> category select
- <strong>Collaborative Modeling Feed</strong>.</li>
-</ol>
-<p class="image"><img src="images/open-feed-view.png"
- alt="Open the Collaborative Modeling Feed View"><br>
-<strong>Figure:</strong> Open the Collaborative Modeling Feed View</p>
-
-<!--
-# Model Element - Model Element Name (Model Element ID)
-
--->
-<p>The view provides the following information:</p>
-<ul>
- <li><strong>Revision</strong> - the revision number.</li>
- <li><strong>Date</strong> - timestamp of the event.</li>
- <li><strong>Author</strong> - name of the user who invoked the event.</li>
- <li><strong>Event</strong> - provides information about obtained locks, released locks, updates and commits.</li>
- <li><strong>Comment</strong> - comment on the event, e.g. added during a commit.</li>
-</ul>
-<p class="image"><img src="images/collaborative-view.png" alt="Collaborative Modeling Feed View"><br>
-<strong>Figure:</strong> The Collaborative Modeling Feed View</p>
-<h3>Updating the View</h3>
-<p>In the upper right corner, a refresh button is provided to update the table
-and also refresh the entries in the Outline view, e.g. to indicate if meanwhile
-another user has locked or changed an element.</p>
-<p class="image"><img src="images/collaborative-view-refresh.png" alt="Update the View"><br>
-<strong>Figure:</strong> Update the View</p>
-<h3>Sorting</h3>
-<p>By default, the entries in the table are sorted by the revision number in descending order.
-You can determine to sort by another column by clicking in its header. Clicking again reverses
-the sorting order. The column by which values the table is ordered is indicated by an arrow pointing
-down for descending order and pointing up for ascending order.</p>
-<p class="image"><img src="images/collaborative-view-sorted.png" alt="Sorted View"><br>
-<strong>Figure:</strong> Collaborative Modeling Feed View Sorted by Event Entries.</p>
-<p>The <strong>Author</strong>, the <strong>Event</strong> and the <strong>Comment</strong>
-columns are sorted alphabetically.</p>
-<script language="JavaScript" type="text/javascript">
-<!--
-writeFooter();
--->
-</script>
-</body>
-</html>