Changes between Version 21 and Version 22 of technicalGuideAndManual

Timestamp:

11/20/13 12:54:51 (11 years ago)

Author:

bartek

Comment:

--

technicalGuideAndManual

@@ -1 +1 @@
 {{{
 #!html 
-<div xml:lang="en" class="article" title="QCG Notification v. 3.0 Technical Guide and Manual"><div class="titlepage"><div><div><h2 class="title"><a id="idp192"></a><span class="emphasis"><em>QCG Notification</em></span> v. 3.0 Technical Guide and
+<div xml:lang="en" class="article" title="QCG-Notification v. 3.2 Technical Guide and Manual"><div class="titlepage"><div><div><h2 class="title"><a id="idp192"></a><span class="emphasis"><em>QCG-Notification</em></span> v. 3.2 Technical Guide and
     Manual</h2></div><div><div class="authorgroup">
       <div class="author"><h3 class="author"><span class="firstname">Bartosz</span> <span class="surname">Bosak</span></h3><code class="email">&lt;<a class="email" href="mailto:bbosak@man.poznan.pl">bbosak@man.poznan.pl</a>&gt;</code></div>
 
       <div class="author"><h3 class="author"><span class="firstname">Krzysztof</span> <span class="surname">Kurowski</span></h3><code class="email">&lt;<a class="email" href="mailto:krzysztof.kurowski@man.poznan.pl">krzysztof.kurowski@man.poznan.pl</a>&gt;</code></div>
-    </div></div><div><p xml:lang="en" class="releaseinfo">3.0.3</p></div><div><p class="copyright">Copyright © 2008-2013 Poznan Supercomputing and Networking Center</p></div></div><hr></hr></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="sect1"><a href="#idp32960">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp35648">Motivations</a></span></dt><dt><span class="sect2"><a href="#idp8704">Purpose of the Document</a></span></dt><dt><span class="sect2"><a href="#idp38656">Status</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp33088">Terminology and WS-Notification Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp41856">WS-Notification Concept</a></span></dt><dt><span class="sect2"><a href="#idp136496">UML-style Diagrams</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp168048">User Guide for a Publisher, Subscriber and
-    NotificationConsumer<span class="emphasis"><em> </em></span></a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp169120">Prefixes and Namespaces</a></span></dt><dt><span class="sect2"><a href="#idp188752">Interaction with <span class="emphasis"><em>QCG Notification</em></span></a></span></dt><dt><span class="sect2"><a href="#ted">Topics, TopicExpressions and Dialects</a></span></dt><dt><span class="sect2"><a href="#idp217984">Extensions</a></span></dt><dt><span class="sect2"><a href="#idp238384">Methods Description</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp656832">Administration Guide of <span class="emphasis"><em>QCG
-    Notification</em></span></a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp659488">Prerequisites</a></span></dt><dt><span class="sect2"><a href="#idp665136">Building</a></span></dt><dt><span class="sect2"><a href="#idp680896">Creating database for <span class="emphasis"><em>QCG Notification</em></span> - the
-      PostgreSQL example</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp702064">Configuration of <span class="emphasis"><em>QCG Notification</em></span></a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp703168">Configuration File: <code class="filename">qcg-ntfd.xml</code></a></span></dt><dt><span class="sect2"><a href="#moduleoptions">Module configuration</a></span></dt><dt><span class="sect2"><a href="#idp870048">WS-Topics management</a></span></dt><dt><span class="sect2"><a href="#idp875936">Starting <span class="emphasis"><em>QCG Notification</em></span></a></span></dt><dt><span class="sect2"><a href="#idp881408">Stopping <span class="emphasis"><em>QCG Notification</em></span></a></span></dt></dl></dd></dl></div>
+    </div></div><div><p xml:lang="en" class="releaseinfo">3.2.0</p></div><div><p class="copyright">Copyright © 2008-2013 Poznan Supercomputing and Networking Center</p></div></div><hr></hr></div><div class="toc"><p><strong>Table of Contents</strong></p><dl><dt><span class="sect1"><a href="#idp4160">Introduction</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp35072">Motivations</a></span></dt><dt><span class="sect2"><a href="#idp18432">Purpose of the Document</a></span></dt><dt><span class="sect2"><a href="#idp40112">Status</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp41056">Terminology and WS-Notification Concept</a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp42464">WS-Notification Concept</a></span></dt><dt><span class="sect2"><a href="#idp137520">UML-style Diagrams</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp170464">User Guide for a Publisher, Subscriber and
+    NotificationConsumer<span class="emphasis"><em> </em></span></a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp171776">Prefixes and Namespaces</a></span></dt><dt><span class="sect2"><a href="#idp194432">Interaction with <span class="emphasis"><em>QCG-Notification</em></span></a></span></dt><dt><span class="sect2"><a href="#ted">Topics, TopicExpressions and Dialects</a></span></dt><dt><span class="sect2"><a href="#idp225600">Extensions</a></span></dt><dt><span class="sect2"><a href="#idp246832">Methods Description</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp247088">Administration Guide of
+    <span class="emphasis"><em>QCG-Notification</em></span></a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp674032">Prerequisites</a></span></dt><dt><span class="sect2"><a href="#idp679536">Building</a></span></dt><dt><span class="sect2"><a href="#idp695296">Creating database for <span class="emphasis"><em>QCG-Notification</em></span> - the
+      PostgreSQL example</a></span></dt></dl></dd><dt><span class="sect1"><a href="#idp716544">Configuration of <span class="emphasis"><em>QCG-Notification</em></span></a></span></dt><dd><dl><dt><span class="sect2"><a href="#idp717776">Configuration File: <code class="filename">qcg-ntfd.xml</code></a></span></dt><dt><span class="sect2"><a href="#moduleoptions">Module configuration</a></span></dt><dt><span class="sect2"><a href="#idp883872">WS-Topics management</a></span></dt><dt><span class="sect2"><a href="#idp889392">Starting <span class="emphasis"><em>QCG-Notification</em></span></a></span></dt><dt><span class="sect2"><a href="#idp894960">Stopping <span class="emphasis"><em>QCG-Notification</em></span></a></span></dt></dl></dd></dl></div>
   
 
-  <div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title"><a id="idp32960"></a>Introduction</h2></div></div></div>
+  <div class="sect1" title="Introduction"><div class="titlepage"><div><div><h2 class="title"><a id="idp4160"></a>Introduction</h2></div></div></div>
     
 
-    <p><span class="bold"><strong>QCG Notification</strong></span> is a reference
+    <p><span class="bold"><strong>QCG-Notification</strong></span> is a reference
     implementation of a set of industry Web Service specifications (<a class="link" href="#WS-Notification"><a class="ulink" href="http://www.oasis-open.org/committees/tc_home.php?wg_abbrev=wsn">WS-Notification
     OASIS standard)</a></a> for message push/pull-style notification,
@@ -28 +28 @@
     subscriptions.).</p>
 
-    <div class="sect2" title="Motivations"><div class="titlepage"><div><div><h3 class="title"><a id="idp35648"></a>Motivations</h3></div></div></div>
+    <div class="sect2" title="Motivations"><div class="titlepage"><div><div><h3 class="title"><a id="idp35072"></a>Motivations</h3></div></div></div>
       
 
@@ -53 +53 @@
     </div>
 
-    <div class="sect2" title="Purpose of the Document"><div class="titlepage"><div><div><h3 class="title"><a id="idp8704"></a>Purpose of the Document</h3></div></div></div>
+    <div class="sect2" title="Purpose of the Document"><div class="titlepage"><div><div><h3 class="title"><a id="idp18432"></a>Purpose of the Document</h3></div></div></div>
       
 
       <p>The main goal of this document is to define a set of initial use
-      cases, scenarios and specify software requirements for <span class="emphasis"><em>QCG
-      Notification</em></span>, its programming application interface,
-      functional units and the integration with both internal and external
-      modules.</p>
+      cases, scenarios and specify software requirements for
+      <span class="emphasis"><em>QCG-Notification</em></span>, its programming application
+      interface, functional units and the integration with both internal and
+      external modules.</p>
 
       <p>The document is aimed at software architects and programmers who
       will be developing software components based on this document. Many
-      requirements and <span class="emphasis"><em>QCG Notification </em></span>concept itself
+      requirements and <span class="emphasis"><em>QCG-Notification </em></span>concept itself
       might be interesting for developers and end users of any Web
       Services.</p>
@@ -72 +72 @@
     </div>
 
-    <div class="sect2" title="Status"><div class="titlepage"><div><div><h3 class="title"><a id="idp38656"></a>Status</h3></div></div></div>
+    <div class="sect2" title="Status"><div class="titlepage"><div><div><h3 class="title"><a id="idp40112"></a>Status</h3></div></div></div>
       
 
@@ -80 +80 @@
   </div>
 
-  <div class="sect1" title="Terminology and WS-Notification Concept"><div class="titlepage"><div><div><h2 class="title"><a id="idp33088"></a>Terminology and WS-Notification Concept</h2></div></div></div>
+  <div class="sect1" title="Terminology and WS-Notification Concept"><div class="titlepage"><div><div><h2 class="title"><a id="idp41056"></a>Terminology and WS-Notification Concept</h2></div></div></div>
     
 
     <p>The aim of this section is to capture high-level functionality of
-    <span class="emphasis"><em>QCG Notification</em></span> and/or interaction without providing
+    <span class="emphasis"><em>QCG-Notification</em></span> and/or interaction without providing
     excessive implementation or technical details of the system.</p>
 
-    <div class="sect2" title="WS-Notification Concept"><div class="titlepage"><div><div><h3 class="title"><a id="idp41856"></a>WS-Notification Concept</h3></div></div></div>
+    <div class="sect2" title="WS-Notification Concept"><div class="titlepage"><div><div><h3 class="title"><a id="idp42464"></a>WS-Notification Concept</h3></div></div></div>
       
 
-      <div class="sect3" title="WS-Notification Fundamentals"><div class="titlepage"><div><div><h4 class="title"><a id="idp42800"></a>WS-Notification Fundamentals</h4></div></div></div>
+      <div class="sect3" title="WS-Notification Fundamentals"><div class="titlepage"><div><div><h4 class="title"><a id="idp43408"></a>WS-Notification Fundamentals</h4></div></div></div>
         
 
@@ -134 +134 @@
       </div>
 
-      <div class="sect3" title="WS-BaseNotification"><div class="titlepage"><div><div><h4 class="title"><a id="idp54576"></a>WS-BaseNotification</h4></div></div></div>
+      <div class="sect3" title="WS-BaseNotification"><div class="titlepage"><div><div><h4 class="title"><a id="idp55184"></a>WS-BaseNotification</h4></div></div></div>
         
 
@@ -190 +190 @@
       </div>
 
-      <div class="sect3" title="WS-BrokeredNotification"><div class="titlepage"><div><div><h4 class="title"><a id="idp73792"></a>WS-BrokeredNotification</h4></div></div></div>
+      <div class="sect3" title="WS-BrokeredNotification"><div class="titlepage"><div><div><h4 class="title"><a id="idp74496"></a>WS-BrokeredNotification</h4></div></div></div>
         
 
@@ -200 +200 @@
         flow where NotificationBroker is present.</p>
 
-        <div class="figure"><a id="idp75776"></a><p class="title"><strong>Figure 2. Web Services BrokeredNotification entities - QCG
-            Notification entities</strong></p><div class="figure-contents">
+        <div class="figure"><a id="idp76368"></a><p class="title"><strong>Figure 2. Web Services BrokeredNotification entities -
+            QCG-Notification entities</strong></p><div class="figure-contents">
             
 
-            <div class="mediaobject" style="text-align: center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_brokeredentities.png" style="text-align: middle" width="324" alt="Web Services BrokeredNotification entities - QCG Notification entities"></img></div>
+            <div class="mediaobject" style="text-align: center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/smn_brokeredentities.png" style="text-align: middle" width="324" alt="Web Services BrokeredNotification entities - QCG-Notification entities"></img></div>
           </div></div><p><br class="figure-break"></br>Note, that there are some important enlargements and
         modifications in the WS-BrokeredNotificatison terminology. Below the
@@ -274 +274 @@
       </div>
 
-      <div class="sect3" title="WS-Topics"><div class="titlepage"><div><div><h4 class="title"><a id="idp98784"></a>WS-Topics</h4></div></div></div>
+      <div class="sect3" title="WS-Topics"><div class="titlepage"><div><div><h4 class="title"><a id="idp99424"></a>WS-Topics</h4></div></div></div>
         
 
@@ -301 +301 @@
             </dd></dl></div>
 
-        <div class="figure"><a id="idp110368"></a><p class="title"><strong>Figure 3. Example Topic Namespace</strong></p><div class="figure-contents">
+        <div class="figure"><a id="idp111056"></a><p class="title"><strong>Figure 3. Example Topic Namespace</strong></p><div class="figure-contents">
           
 
@@ -308 +308 @@
       </div>
 
-      <div class="sect3" title="Base of QCG Notification"><div class="titlepage"><div><div><h4 class="title"><a id="idp113248"></a>Base of <span class="emphasis"><em>QCG Notification</em></span></h4></div></div></div>
-        
-
-        <p><span class="emphasis"><em>QCG Notification</em></span> is a reference
+      <div class="sect3" title="Base of QCG-Notification"><div class="titlepage"><div><div><h4 class="title"><a id="idp112832"></a>Base of <span class="emphasis"><em>QCG-Notification</em></span></h4></div></div></div>
+        
+
+        <p><span class="emphasis"><em>QCG-Notification</em></span> is a reference
         implementation of WS-BaseNotification, WS-BrokeredNotification and
         WS-Topics OASIS industry standards. As a consistent and highly
@@ -319 +319 @@
         scale Web Service based systems, SOA environments and it acts as a
         core component in QCG Service Bus. To meet security requirements,
-        <span class="emphasis"><em>QCG Notification</em></span> (or <span class="emphasis"><em>QCG Notification
+        <span class="emphasis"><em>QCG-Notification</em></span> (or <span class="emphasis"><em>QCG-Notification
         Provider</em></span>) exposes well defined Web Service and programming
         interfaces over QCG security mechanisms for dynamic notification,
@@ -327 +327 @@
         Publisher, Subscriber or Consumer.</p>
 
-        <p>A flexible plug-in architecture of <span class="emphasis"><em>QCG Notification
+        <p>A flexible plug-in architecture of <span class="emphasis"><em>QCG-Notification
         </em></span>enables using different communication protocols for
         messages transmission. Currently messages can be transported between
-        <span class="emphasis"><em>QCG Notification</em></span> and third party entities not
+        <span class="emphasis"><em>QCG-Notification</em></span> and third party entities not
         only through HTTP protocol, but also through XMPP (jabber) as well as
         SMTP (e-mail) protocols. It is possible to variously mix channels of
@@ -338 +338 @@
 
         <p>Below we present a set of Web Service notification use cases
-        demonstrating capabilities offered by <span class="emphasis"><em>QCG
-        Notification</em></span>.</p>
+        demonstrating capabilities offered by
+        <span class="emphasis"><em>QCG-Notification</em></span>.</p>
 
         <div class="figure"><a id="notificationConsumers"></a><p class="title"><strong>Figure 4. Notification with multiple Publishers and multiple
@@ -349 +349 @@
 
         <p>The <a class="link" href="#notificationConsumers" title="Figure 4. Notification with multiple Publishers and multiple NotificationConsumers">diagram 4</a> shows
-        one of the basic notification flows supported by <span class="emphasis"><em>QCG
-        Notification</em></span>. Depending on records, Notifications produced
-        by a Publisher and received by the <span class="emphasis"><em>QCG
-        Notification</em></span> may or may not be dispatched to concrete
-        NotificationConsumer. Note, that Subscriptions represent relationships
-        between Topics and NotificationConsumers in this scenario. Before any
-        Notification is delivered to a NotificationConsumer, a Subscriber has
-        to send first a SubscribeRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span> in which all parameters of a Subscription are
-        specified. Main parameters of a SubscribeRequest message are
-        ConsumerReference and TopicExpression defined according to the
-        specific Dialect type. On the other hand, before a Publisher starts
-        sending Notifications it may be obligated to register himself in
-        <span class="emphasis"><em>QCG Notification</em></span>. The diagram below shows a
+        one of the basic notification flows supported by
+        <span class="emphasis"><em>QCG-Notification</em></span>. Depending on records,
+        Notifications produced by a Publisher and received by the
+        <span class="emphasis"><em>QCG-Notification</em></span> may or may not be dispatched to
+        concrete NotificationConsumer. Note, that Subscriptions represent
+        relationships between Topics and NotificationConsumers in this
+        scenario. Before any Notification is delivered to a
+        NotificationConsumer, a Subscriber has to send first a
+        SubscribeRequest message to <span class="emphasis"><em>QCG-Notification</em></span> in
+        which all parameters of a Subscription are specified. Main parameters
+        of a SubscribeRequest message are ConsumerReference and
+        TopicExpression defined according to the specific Dialect type. On the
+        other hand, before a Publisher starts sending Notifications it may be
+        obligated to register himself in
+        <span class="emphasis"><em>QCG-Notification</em></span>. The diagram below shows a
         sequence of events in order to initialize an asynchronous process of
         notifications between a Publisher and a NotificationConsumer.</p>
 
-        <div class="figure"><a id="idp126512"></a><p class="title"><strong>Figure 5. Message flows: creating a Subscription, notifying
+        <div class="figure"><a id="idp127200"></a><p class="title"><strong>Figure 5. Message flows: creating a Subscription, notifying
           NotificationConsumers</strong></p><div class="figure-contents">
           
@@ -376 +377 @@
             <p>A Subscriber sends the SubscribeRequest message with a
             NotificationConsumer location and TopicExpression parameters to
-            <span class="emphasis"><em>QCG Notification</em></span>.</p>
-          </li><li class="listitem">
-            <p><span class="emphasis"><em>QCG Notification</em></span> prepares appropriate
+            <span class="emphasis"><em>QCG-Notification</em></span>.</p>
+          </li><li class="listitem">
+            <p><span class="emphasis"><em>QCG-Notification</em></span> prepares appropriate
             records for a Subscription.</p>
           </li><li class="listitem">
-            <p>A Publisher register himself in <span class="emphasis"><em>QCG
-            Notification</em></span> by sending the RegisterPublisher
-            message.</p>
+            <p>A Publisher register himself in
+            <span class="emphasis"><em>QCG-Notification</em></span> by sending the
+            RegisterPublisher message.</p>
           </li><li class="listitem">
             <p>A registered Publisher sends the Notify message on a
-            specified Topic to a <span class="emphasis"><em>QCG Notification
+            specified Topic to a <span class="emphasis"><em>QCG-Notification
             </em></span>service.</p>
           </li><li class="listitem">
-            <p><span class="emphasis"><em>QCG Notification</em></span> checks if there are
+            <p><span class="emphasis"><em>QCG-Notification</em></span> checks if there are
             NotificationConsumers subscribed on a specified Topic. If so,
-            <span class="emphasis"><em>QCG Notification</em></span> sends asynchronous
+            <span class="emphasis"><em>QCG-Notification</em></span> sends asynchronous
             Notifications to these NotifcationConsumers.</p>
           </li></ol></div>
@@ -397 +398 @@
     </div>
 
-    <div class="sect2" title="UML-style Diagrams"><div class="titlepage"><div><div><h3 class="title"><a id="idp136496"></a>UML-style Diagrams</h3></div></div></div>
+    <div class="sect2" title="UML-style Diagrams"><div class="titlepage"><div><div><h3 class="title"><a id="idp137520"></a>UML-style Diagrams</h3></div></div></div>
       
 
@@ -454 +455 @@
       in a scenario and actions associated with that scenario.</p>
 
-      <div class="sect3" title="`Main Use Cases"><div class="titlepage"><div><div><h4 class="title"><a id="idp149312"></a>`Main Use Cases</h4></div></div></div>
-        
-
-        <div class="figure"><a id="idp150128"></a><p class="title"><strong>Figure 6. Use case diagram for a Publisher</strong></p><div class="figure-contents">
+      <div class="sect3" title="`Main Use Cases"><div class="titlepage"><div><div><h4 class="title"><a id="idp150304"></a>`Main Use Cases</h4></div></div></div>
+        
+
+        <div class="figure"><a id="idp151120"></a><p class="title"><strong>Figure 6. Use case diagram for a Publisher</strong></p><div class="figure-contents">
           
 
@@ -463 +464 @@
         </div></div><br class="figure-break"></br>
 
-        <div class="figure"><a id="idp153248"></a><p class="title"><strong>Figure 7. Use case diagram for a Subscriber</strong></p><div class="figure-contents">
+        <div class="figure"><a id="idp154160"></a><p class="title"><strong>Figure 7. Use case diagram for a Subscriber</strong></p><div class="figure-contents">
           
 
@@ -469 +470 @@
         </div></div><br class="figure-break"></br>
 
-        <div class="figure"><a id="idp156000"></a><p class="title"><strong>Figure 8. Use case diagram for a NotificationConsumer</strong></p><div class="figure-contents">
+        <div class="figure"><a id="idp156912"></a><p class="title"><strong>Figure 8. Use case diagram for a NotificationConsumer</strong></p><div class="figure-contents">
           
 
@@ -475 +476 @@
         </div></div><br class="figure-break"></br>
 
-        <div class="figure"><a id="idp158752"></a><p class="title"><strong>Figure 9. Use case diagram for QCG Notification</strong></p><div class="figure-contents">
+        <div class="figure"><a id="idp159856"></a><p class="title"><strong>Figure 9. Use case diagram for QCG-Notification</strong></p><div class="figure-contents">
           
 
-          <div class="mediaobject" style="text-align: center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_qcgnotification.png" style="text-align: middle" width="432" alt="Use case diagram for QCG Notification"></img></div>
+          <div class="mediaobject" style="text-align: center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_qcgnotification.png" style="text-align: middle" width="432" alt="Use case diagram for QCG-Notification"></img></div>
         </div></div><br class="figure-break"></br>
 
-        <div class="figure"><a id="idp161504"></a><p class="title"><strong>Figure 10. Use case diagram for a QCG Notification Administrator</strong></p><div class="figure-contents">
+        <div class="figure"><a id="idp162992"></a><p class="title"><strong>Figure 10. Use case diagram for a QCG-Notification Administrator</strong></p><div class="figure-contents">
           
 
-          <div class="mediaobject" style="text-align: center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_administrator.png" style="text-align: middle" width="432" alt="Use case diagram for a QCG Notification Administrator"></img></div>
+          <div class="mediaobject" style="text-align: center"><img src="http://apps.man.poznan.pl/trac/qcg-notification/raw-attachment/wiki/technicalGuideAndManual/use_administrator.png" style="text-align: middle" width="432" alt="Use case diagram for a QCG-Notification Administrator"></img></div>
         </div></div><br class="figure-break"></br>
       </div>
 
-      <div class="sect3" title="Main Sequence Diagrams"><div class="titlepage"><div><div><h4 class="title"><a id="idp164256"></a>Main Sequence Diagrams</h4></div></div></div>
-        
-
-        <div class="figure"><a id="idp164896"></a><p class="title"><strong>Figure 11. General sequence diagram</strong></p><div class="figure-contents">
+      <div class="sect3" title="Main Sequence Diagrams"><div class="titlepage"><div><div><h4 class="title"><a id="idp166304"></a>Main Sequence Diagrams</h4></div></div></div>
+        
+
+        <div class="figure"><a id="idp167008"></a><p class="title"><strong>Figure 11. General sequence diagram</strong></p><div class="figure-contents">
           
 
@@ -500 +501 @@
   </div>
 
-  <div class="sect1" title="User Guide for a Publisher, Subscriber and NotificationConsumer"><div class="titlepage"><div><div><h2 class="title"><a id="idp168048"></a>User Guide for a Publisher, Subscriber and
+  <div class="sect1" title="User Guide for a Publisher, Subscriber and NotificationConsumer"><div class="titlepage"><div><div><h2 class="title"><a id="idp170464"></a>User Guide for a Publisher, Subscriber and
     NotificationConsumer<span class="emphasis"><em> </em></span></h2></div></div></div>
     
 
-    <div class="sect2" title="Prefixes and Namespaces"><div class="titlepage"><div><div><h3 class="title"><a id="idp169120"></a>Prefixes and Namespaces</h3></div></div></div>
+    <div class="sect2" title="Prefixes and Namespaces"><div class="titlepage"><div><div><h3 class="title"><a id="idp171776"></a>Prefixes and Namespaces</h3></div></div></div>
       
 
@@ -511 +512 @@
       sections.</p>
 
-      <div class="table"><a id="idp170320"></a><p class="title"><strong>Table 1. Prefixes and Namespaces</strong></p><div class="table-contents">
+      <div class="table"><a id="idp173136"></a><p class="title"><strong>Table 1. Prefixes and Namespaces</strong></p><div class="table-contents">
         
 
@@ -518 +519 @@
     </div>
 
-    <div class="sect2" title="Interaction with QCG Notification"><div class="titlepage"><div><div><h3 class="title"><a id="idp188752"></a>Interaction with <span class="emphasis"><em>QCG Notification</em></span></h3></div></div></div>
+    <div class="sect2" title="Interaction with QCG-Notification"><div class="titlepage"><div><div><h3 class="title"><a id="idp194432"></a>Interaction with <span class="emphasis"><em>QCG-Notification</em></span></h3></div></div></div>
       
 
-      <p>In the next subsections an issue of cooperation with <span class="emphasis"><em>QCG
-      Notification</em></span> is presented independently for a Publisher,
-      Subscriber and NotificationConsumer. Although a conceptual style of
-      interaction is described here in details, technical particularities of
-      constructing messages are presented later.</p>
-
-      <div class="sect3" title="Publisher Interaction"><div class="titlepage"><div><div><h4 class="title"><a id="idp190848"></a>Publisher Interaction</h4></div></div></div>
-        
-
-        <div class="figure"><a id="idp191488"></a><p class="title"><strong>Figure 12. Publisher interaction sequence diagram</strong></p><div class="figure-contents">
+      <p>In the next subsections an issue of cooperation with
+      <span class="emphasis"><em>QCG-Notification</em></span> is presented independently for a
+      Publisher, Subscriber and NotificationConsumer. Although a conceptual
+      style of interaction is described here in details, technical
+      particularities of constructing messages are presented later.</p>
+
+      <div class="sect3" title="Publisher Interaction"><div class="titlepage"><div><div><h4 class="title"><a id="idp196496"></a>Publisher Interaction</h4></div></div></div>
+        
+
+        <div class="figure"><a id="idp197136"></a><p class="title"><strong>Figure 12. Publisher interaction sequence diagram</strong></p><div class="figure-contents">
           
 
@@ -539 +540 @@
         has to be registered before it starts sending Notifications. In this
         situation, a Publisher sends the RegisterPublisherRequest message to
-        <span class="emphasis"><em>QCG Notification</em></span>. If everything goes well it
+        <span class="emphasis"><em>QCG-Notification</em></span>. If everything goes well it
         receives the RegisterPublisherResponse message with a session ID. From
         this time a Publisher is entitled for sending Notify messages - the
@@ -550 +551 @@
       </div>
 
-      <div class="sect3" title="Subscriber interaction"><div class="titlepage"><div><div><h4 class="title"><a id="idp196000"></a>Subscriber interaction</h4></div></div></div>
-        
-
-        <div class="figure"><a id="idp196640"></a><p class="title"><strong>Figure 13. Subscriber interaction sequence diagram</strong></p><div class="figure-contents">
+      <div class="sect3" title="Subscriber interaction"><div class="titlepage"><div><div><h4 class="title"><a id="idp201824"></a>Subscriber interaction</h4></div></div></div>
+        
+
+        <div class="figure"><a id="idp202464"></a><p class="title"><strong>Figure 13. Subscriber interaction sequence diagram</strong></p><div class="figure-contents">
           
 
@@ -560 +561 @@
 
         <p>When a Subscriber wants to create a Subscription, it sends the
-        SubscribeRequest message to <span class="emphasis"><em>QCG Notification</em></span>.
+        SubscribeRequest message to <span class="emphasis"><em>QCG-Notification</em></span>.
         This message should contain an address of NotificationConsumer and a
         TopicExpression that specifies a Topic or a set of Topics on which
@@ -568 +569 @@
         From the version 2.5.0 of the system, the Subscriber may specify XSLT
         document that will be used to transform message content by certain
-        publishing modules. After creation of a Subscription <span class="emphasis"><em>QCG
-        Notification</em></span> sends the SubscribeResponse message with a
-        created Subscription ID. This ID should be attached to the
-        UnsubscribeRequest message when a Subscription is not wanted and the
-        Renew message when a Subscription should be refreshed. A Subscriber is
-        allowed to create many equal Subscriptions.</p>
+        publishing modules. After creation of a Subscription
+        <span class="emphasis"><em>QCG-Notification</em></span> sends the SubscribeResponse
+        message with a created Subscription ID. This ID should be attached to
+        the UnsubscribeRequest message when a Subscription is not wanted and
+        the Renew message when a Subscription should be refreshed. A
+        Subscriber is allowed to create many equal Subscriptions.</p>
 
         <p>If a scenario requires pull-style of notifications, a Subscriber
         can create a set of PullPoints. In a such situation, it has to invoke
-        the CreatePullPoint method offered by <span class="emphasis"><em>QCG Notification.
+        the CreatePullPoint method offered by <span class="emphasis"><em>QCG-Notification.
         <span class="emphasis"><em>The response parameter of this method will be an address to
         the newly created <span class="emphasis"><em>PullPoint resource (Subscribers can assign
@@ -586 +587 @@
       </div>
 
-      <div class="sect3" title="NotificationConsumer Interaction"><div class="titlepage"><div><div><h4 class="title"><a id="idp203344"></a>NotificationConsumer Interaction</h4></div></div></div>
-        
-
-        <div class="figure"><a id="idp204112"></a><p class="title"><strong>Figure 14. NotificationConsumer interaction sequence diagram</strong></p><div class="figure-contents">
+      <div class="sect3" title="NotificationConsumer Interaction"><div class="titlepage"><div><div><h4 class="title"><a id="idp208816"></a>NotificationConsumer Interaction</h4></div></div></div>
+        
+
+        <div class="figure"><a id="idp210352"></a><p class="title"><strong>Figure 14. NotificationConsumer interaction sequence diagram</strong></p><div class="figure-contents">
             
 
@@ -595 +596 @@
           </div></div><p><br class="figure-break"></br>The main capability of a NotificationConsumer is a
         receiving of Notify messages. A NotificationConsumer can implement an
-        interface for receiving Notify messages sending by <span class="emphasis"><em>QCG
-        Notification</em></span> or can be a client of a PullPoint. In the
-        second case, a NotificationConsumer can invoke GetMessages method
-        offered by a certain PullPoint. Messages buffered in the PullPoint
-        will be removed from the buffer and delivered in GetMessagesResponse
-        to the consumer.</p>
+        interface for receiving Notify messages sending by
+        <span class="emphasis"><em>QCG-Notification</em></span> or can be a client of a
+        PullPoint. In the second case, a NotificationConsumer can invoke
+        GetMessages method offered by a certain PullPoint. Messages buffered
+        in the PullPoint will be removed from the buffer and delivered in
+        GetMessagesResponse to the consumer.</p>
 
         <p>On the other hand, when a NotificationConsumer wants to receive
         the last Notification message sent on a specific Topic, it can do this
-        by sending GetCurrentMessageRequest to <span class="emphasis"><em>QCG
-        Notification</em></span>. Requested Notification will be supplied in
-        the GetCurrentMessageResponse message.</p>
+        by sending GetCurrentMessageRequest to
+        <span class="emphasis"><em>QCG-Notification</em></span>. Requested Notification will be
+        supplied in the GetCurrentMessageResponse message.</p>
       </div>
     </div>
@@ -613 +614 @@
       
 
-      <p>Before start-up of a <span class="emphasis"><em>QCG Notification</em></span>
+      <p>Before start-up of a <span class="emphasis"><em>QCG-Notification</em></span>
       service, there should be defined Topic Namespaces in a system. Topic
       Namespaces should be created (usually by Publishers) and delivered to
-      a<span class="emphasis"><em> QCG Notification</em></span> administrator in a form of XML
+      a<span class="emphasis"><em> QCG-Notification</em></span> administrator in a form of XML
       documents. A following record presents a sample Topic Namespace
       identified by
@@ -642 +643 @@
 &lt;/wstop:TopicNamespace&gt;</pre>
 
-      <p><span class="emphasis"><em>QCG Notification </em></span>supports three types of
+      <p><span class="emphasis"><em>QCG-Notification </em></span>supports three types of
       dialects: <span class="emphasis"><em>Simple</em></span>, <span class="emphasis"><em>Concrete</em></span> and
       <span class="emphasis"><em>Full</em></span>. If a message refer to Topics, it has to
@@ -657 +658 @@
     </div>
 
-    <div class="sect2" title="Extensions"><div class="titlepage"><div><div><h3 class="title"><a id="idp217984"></a>Extensions</h3></div></div></div>
+    <div class="sect2" title="Extensions"><div class="titlepage"><div><div><h3 class="title"><a id="idp225600"></a>Extensions</h3></div></div></div>
       
 
       <p>The Oasis standard for notifications doesn't define details for
       lower Levels of functionality so an architect of system is obligated to
-      introduce some extensions and clarifications. In the <span class="emphasis"><em>QCG
-      Notification </em></span>scenario there are several messages that have to
-      be expanded with additional information written as embedded XML. Some of
-      these extensions are related with other Oasis standards but some are
-      quite new. Technical details are described in the successive
-      subsections.</p>
-
-      <div class="sect3" title="TopicExpression"><div class="titlepage"><div><div><h4 class="title"><a id="idp219920"></a>TopicExpression</h4></div></div></div>
-        
-
-        <p><span class="emphasis"><em>QCG Notification </em></span>remote peers have to use
+      introduce some extensions and clarifications. In the
+      <span class="emphasis"><em>QCG-Notification </em></span>scenario there are several
+      messages that have to be expanded with additional information written as
+      embedded XML. Some of these extensions are related with other Oasis
+      standards but some are quite new. Technical details are described in the
+      successive subsections.</p>
+
+      <div class="sect3" title="TopicExpression"><div class="titlepage"><div><div><h4 class="title"><a id="idp226336"></a>TopicExpression</h4></div></div></div>
+        
+
+        <p><span class="emphasis"><em>QCG-Notification </em></span>remote peers have to use
         an appropriate TopicExpression XML element. The schema of this element
         is defined according to Oasis standard in<a class="ulink" href="http://docs.oasis-open.org/wsn/b-2.xsd"><a class="ulink" href="http://docs.oasis-open.org/wsn/b-2.xsd">
@@ -684 +685 @@
       </div>
 
-      <div class="sect3" title="QCG Notification Extensions"><div class="titlepage"><div><div><h4 class="title"><a id="idp222944"></a><span class="emphasis"><em>QCG Notification</em></span> Extensions</h4></div></div></div>
-        
-
-        <p><span class="emphasis"><em>QCG Notification</em></span> introduces some extensions
+      <div class="sect3" title="QCG-Notification Extensions"><div class="titlepage"><div><div><h4 class="title"><a id="idp229440"></a><span class="emphasis"><em>QCG-Notification</em></span> Extensions</h4></div></div></div>
+        
+
+        <p><span class="emphasis"><em>QCG-Notification</em></span> introduces some extensions
         to WSDL as well as schema documents related to the Oasis standard. The
         following schema defines these extensions. The first three elements
@@ -741 +742 @@
    &lt;/xsd:simpleType&gt;  
 
-&lt;!-- ================= QCG Notification manager : ListPullPoints ================== --&gt;
+&lt;!-- ===== QCG-Notification manager : ListPullPoints ===== --&gt;
 
    &lt;xsd:complexType name="ListSubscriptionsFilter"&gt;
@@ -801 +802 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : ListPublishersRegistrations ================== --&gt;
+&lt;!-- ===== QCG-Notification manager : ListPublishersRegistrations ===== --&gt;
 
    &lt;xsd:complexType name="ListPublishersRegistrationsFilter"&gt;
@@ -860 +861 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : ListPullPoints ================== --&gt;
+&lt;!-- ===== QCG-Notification manager : ListPullPoints ===== --&gt;
 
    &lt;xsd:complexType name="ListPullPointsFilter"&gt;
@@ -920 +921 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : ListTopicNamespaces ================== --&gt;
+&lt;!-- ===== QCG-Notification manager : ListTopicNamespaces ===== --&gt;
     
    &lt;xsd:complexType name="ListTopicNamespacesFilter"&gt;
@@ -945 +946 @@
     &lt;xsd:sequence&gt;
      &lt;xsd:element name="targetNamespace" type="xsd:anyURI" use="required"/&gt;
-     &lt;xsd:element name="Topics" type="xsd:anyURI" minOccurs="0" maxOccurs="unbounded"/&gt;
+     &lt;xsd:element name="Topics" type="xsd:anyURI" 
+      minOccurs="0" maxOccurs="unbounded"/&gt;
      &lt;xsd:any namespace="##other" processContents="lax"
       minOccurs="0" maxOccurs="unbounded"/&gt;
@@ -962 +964 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : AddTopicNamespace ================== --&gt;
+&lt;!-- ===== QCG-Notification manager : AddTopicNamespace ===== --&gt;
 
    &lt;xsd:element name="AddTopicNamespace"&gt;
@@ -983 +985 @@
    &lt;/xsd:element&gt;
 
-&lt;!-- ================= QCG Notification manager : RemoveTopicNamespace ================== --&gt;
+&lt;!-- ===== QCG-Notification manager : RemoveTopicNamespace ===== --&gt;
 
    &lt;xsd:element name="RemoveTopicNamespace"&gt;
@@ -1009 +1011 @@
     </div>
 
-    <div class="sect2" title="Methods Description"><div class="titlepage"><div><div><h3 class="title"><a id="idp238384"></a>Methods Description</h3></div></div></div>
+    <div class="sect2" title="Methods Description"><div class="titlepage"><div><div><h3 class="title"><a id="idp246832"></a>Methods Description</h3></div></div></div>
       
 
       <p>The main idea of this chapter is to present the types of messages
-      used in the <span class="emphasis"><em>QCG Notification</em></span> scenario as well as
+      used in the <span class="emphasis"><em>QCG-Notification</em></span> scenario as well as
       introduce how to construct and interpret these messages. The majority of
-      them is two-way style and initiated by <span class="emphasis"><em>QCG
-      Notification</em></span> clients. Exception is the Notify message that is
-      one-way style. In the first phase it is transported from a Publisher to
-      <span class="emphasis"><em>QCG Notification</em></span> and in the second it is
-      transported from <span class="emphasis"><em>QCG Notification</em></span> to subscribed
-      NotificationConsumers.</p>
-
-      <p>All supported by <span class="emphasis"><em>QCG Notification</em></span> message
+      them is two-way style and initiated by
+      <span class="emphasis"><em>QCG-Notification</em></span> clients. Exception is the Notify
+      message that is one-way style. In the first phase it is transported from
+      a Publisher to <span class="emphasis"><em>QCG-Notification</em></span> and in the second
+      it is transported from <span class="emphasis"><em>QCG-Notification</em></span> to
+      subscribed NotificationConsumers.</p>
+
+      <p>All supported by <span class="emphasis"><em>QCG-Notification</em></span> message
       types are presented and explained below.</p>
 
@@ -1038 +1040 @@
         </div>
 
-      <div class="sect3" title="SubscribeRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp246400"></a>SubscribeRequest</h4></div></div></div>
-        
-
-        <p>SubscribeRequest is sent by a Subscriber to <span class="emphasis"><em>QCG
-        Notification</em></span>. The message should contain information about
-        a NotificationConsumer and an expression defining Topic or Topics that
-        the Subscription will affect. If a message processing is successful, a
-        Subscription is created. It is possible to create many equal
-        Subscriptions by sending numerously the same SubscribeRequest
-        message.</p>
+      <div class="sect3" title="SubscribeRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp255648"></a>SubscribeRequest</h4></div></div></div>
+        
+
+        <p>SubscribeRequest is sent by a Subscriber to
+        <span class="emphasis"><em>QCG-Notification</em></span>. The message should contain
+        information about a NotificationConsumer and an expression defining
+        Topic or Topics that the Subscription will affect. If a message
+        processing is successful, a Subscription is created. It is possible to
+        create many equal Subscriptions by sending numerously the same
+        SubscribeRequest message.</p>
 
         <pre class="programlisting">SOAP-ENV:Envelope ... &gt;
@@ -1066 +1068 @@
      &lt;wsnt:Filter&gt;
       &lt;wsnt:TopicExpression  
-        <span class="bold"><strong>xmlns:tns="<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics</strong></span>"</strong></span> 
-        Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span>&gt;
+       <span class="bold"><strong>xmlns:tns=
+        "<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics</strong></span>"</strong></span> 
+       Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span>&gt;
            <span class="bold"><strong>tns://*</strong></span>
       &lt;/wsnt:TopicExpression&gt;
       &lt;wsnt:MessageContent
-        <span class="bold"><strong>xmlns:smnex=http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage</strong></span> 
-        Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"&gt;
+       <span class="bold"><strong>xmlns:smnex=
+        http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage</strong></span> 
+       Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"&gt;
            <span class="bold"><strong>boolean(//smnex:State[text()="on"])</strong></span>
       &lt;/wsnt:MessageContent&gt;
@@ -1112 +1116 @@
             <p>A Consumer address. It is significant to specify a correct
             prefix (http, https, xmpp). The prefix should be adequate to the
-            expected type of connection between <span class="emphasis"><em>QCG
-            Notification</em></span> and NotificationConsumer(s): http for
-            anonymous, https for ssl-based and xmpp for sending notifications
-            to jabber clients.</p>
+            expected type of connection between
+            <span class="emphasis"><em>QCG-Notification</em></span> and NotificationConsumer(s):
+            http for anonymous, https for ssl-based and xmpp for sending
+            notifications to jabber clients.</p>
           </li><li class="listitem">
             <p><span class="emphasis"><em>//wsnt:Subscribe/wsnt:Filter</em></span></p>
@@ -1161 +1165 @@
             suggestion for the termination time of the Subscription being
             created (expressed as a local time with timezone). If not present,
-            the termination time is determined automatically - <span class="emphasis"><em>QCG
-            Notification <span class="emphasis"><em>specify a default time
+            the termination time is determined automatically -
+            <span class="emphasis"><em>QCG-Notification <span class="emphasis"><em>specify a default time
             period</em></span></em></span> for the Subscription to be
             valid.</p>
@@ -1176 +1180 @@
       </div>
 
-      <div class="sect3" title="SubscribeResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp272816"></a>SubscribeResponse</h4></div></div></div>
+      <div class="sect3" title="SubscribeResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp285872"></a>SubscribeResponse</h4></div></div></div>
         
 
         <p>In answer on SubscribeRequest there is sent the
-        SubscribeResponse message. <span class="emphasis"><em>QCG Notification</em></span>
+        SubscribeResponse message. <span class="emphasis"><em>QCG-Notification</em></span>
         deliver in this message a reference to the created Subscription. This
         ID can be used for manipulation and to remove the Subscription.</p>
@@ -1220 +1224 @@
 
             <p>An address of a SubscriptionManager interface. In the
-            current solution it is the <span class="emphasis"><em>QCG Notification</em></span>
+            current solution it is the <span class="emphasis"><em>QCG-Notification</em></span>
             service address.</p>
           </li><li class="listitem">
@@ -1232 +1236 @@
       </div>
 
-      <div class="sect3" title="RenewRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp284192"></a>RenewRequest</h4></div></div></div>
+      <div class="sect3" title="RenewRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp298256"></a>RenewRequest</h4></div></div></div>
         
 
         <p>When a Subscriber wants to renew a Subscription, it can send the
-        RenewRequest message to <span class="emphasis"><em>QCG Notification</em></span>. The
+        RenewRequest message to <span class="emphasis"><em>QCG-Notification</em></span>. The
         message should contain the Subscription ID element and a new
         termination time suggestion.</p>
@@ -1281 +1285 @@
       </div>
 
-      <div class="sect3" title="RenewResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp294784"></a>RenewResponse</h4></div></div></div>
+      <div class="sect3" title="RenewResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp309152"></a>RenewResponse</h4></div></div></div>
         
 
@@ -1325 +1329 @@
             <p><span class="emphasis"><em>//wsnt:RenewResponse/wsnt:CurrentTime</em></span></p>
 
-            <p><span class="emphasis"><em><span class="emphasis"><em>A </em></span>QCG
-            Notification's</em></span> time when the Subscription was renewing
-            (expressed as UTC Time).</p>
+            <p><span class="emphasis"><em><span class="emphasis"><em>A
+            </em></span>QCG-Notification's</em></span> time when the
+            Subscription was renewing (expressed as UTC Time).</p>
           </li></ul></div>
       </div>
 
-      <div class="sect3" title="UnsubscribeRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp306512"></a>UnsubscribeRequest</h4></div></div></div>
+      <div class="sect3" title="UnsubscribeRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp320608"></a>UnsubscribeRequest</h4></div></div></div>
         
 
         <p>When a Subscriber wants to terminate a Subscription, it has to
-        send the UnsubscribeRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span>. The parameter attached to this request is a
-        Subscription ID.</p>
+        send the UnsubscribeRequest message to
+        <span class="emphasis"><em>QCG-Notification</em></span>. The parameter attached to this
+        request is a Subscription ID.</p>
 
         <pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -1371 +1375 @@
       </div>
 
-      <div class="sect3" title="UnsubscribeResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp315248"></a>UnsubscribeResponse</h4></div></div></div>
+      <div class="sect3" title="UnsubscribeResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp329408"></a>UnsubscribeResponse</h4></div></div></div>
         
 
@@ -1401 +1405 @@
       </div>
 
-      <div class="sect3" title="RegisterPublisherRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp321392"></a>RegisterPublisherRequest</h4></div></div></div>
+      <div class="sect3" title="RegisterPublisherRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp332736"></a>RegisterPublisherRequest</h4></div></div></div>
         
 
         <p>In order to sending Notifications, a Publisher can be obligated
-        to register himself previously in <span class="emphasis"><em>QCG
-        Notification</em></span>. For this purpose, it sends the
-        RegisterPublisherRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span>.</p>
+        to register himself previously in
+        <span class="emphasis"><em>QCG-Notification</em></span>. For this purpose, it sends the
+        RegisterPublisherRequest message to
+        <span class="emphasis"><em>QCG-Notification</em></span>.</p>
 
         <pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -1449 +1453 @@
             suggestion for the termination time of the Registration being
             created (expressed as a local time with timezone). If not present,
-            the termination time is determined automatically - <span class="emphasis"><em>QCG
-            Notification <span class="emphasis"><em>specify the default time
+            the termination time is determined automatically -
+            <span class="emphasis"><em>QCG-Notification <span class="emphasis"><em>specify the default time
             period</em></span></em></span> for the Registration to be valid.
             Every Notify message renews the termination time.</p>
@@ -1456 +1460 @@
       </div>
 
-      <div class="sect3" title="RegisterPublisherResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp334336"></a>RegisterPublisherResponse</h4></div></div></div>
+      <div class="sect3" title="RegisterPublisherResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp348240"></a>RegisterPublisherResponse</h4></div></div></div>
         
 
         <p>In a response to a successful registration process,
-        <span class="emphasis"><em>QCG Notification</em></span> sends RegisterPublisherResponse.
+        <span class="emphasis"><em>QCG-Notification</em></span> sends RegisterPublisherResponse.
         This message contains a reference to the created Registration. The
         attached ID is necessary to send any Notification message.</p>
@@ -1478 +1482 @@
       &lt;/wsa:Address&gt;
       &lt;wsa:ReferenceParameters&gt;
-         <span class="bold"><strong>&lt;RegisterPublisherID 
+       <span class="bold"><strong>&lt;RegisterPublisherID 
         xmlns="http://schemas.qoscosgrid.org/ntf/2011/04/extensions"&gt;
           1207382668
-         &lt;/RegisterPublisherID&gt;</strong></span>
+       &lt;/RegisterPublisherID&gt;</strong></span>
       &lt;/wsa:ReferenceParameters&gt;
      &lt;/wsnbr:PublisherRegistrationReference&gt;
@@ -1499 +1503 @@
 
             <p>An address of a PublisherRegistration Manager interface. In
-            the current solution it is the <span class="emphasis"><em>QCG
-            Notification</em></span> service address.</p>
+            the current solution it is the
+            <span class="emphasis"><em>QCG-Notification</em></span> service address.</p>
           </li><li class="listitem">
             <p><span class="emphasis"><em>//wsnbr:RegisterPublisherResponse/wsnbr:PublisherRegistrationReference/wsa:ReferenceParameters/RegisterPublisherID</em></span></p>
@@ -1511 +1515 @@
       </div>
 
-      <div class="sect3" title="Notify"><div class="titlepage"><div><div><h4 class="title"><a id="idp346192"></a>Notify</h4></div></div></div>
+      <div class="sect3" title="Notify"><div class="titlepage"><div><div><h4 class="title"><a id="idp360032"></a>Notify</h4></div></div></div>
         
 
@@ -1533 +1537 @@
       &lt;wsnt:Topic 
        Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span><span class="bold"><strong> 
-       xmlns:tns="<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics</strong></span>"&gt;
+       xmlns:tns=
+        "<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics</strong></span>"&gt;
           tns:House/Kitchen/Light</strong></span>
       &lt;/wsnt:Topic&gt;
@@ -1542 +1547 @@
       &lt;wsnt:ProducerReference&gt;
       &lt;wsnt:Message&gt;
-         <span class="bold"><strong>&lt;smnex:State 
-          xmlns:smnex="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"&gt;
+       <span class="bold"><strong>&lt;smnex:State 
+        xmlns:smnex=
+         "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"&gt;
              on
-         &lt;/smnex:State&gt;</strong></span>
+       &lt;/smnex:State&gt;</strong></span>
       &lt;/wsnt:Message&gt;
      &lt;/wsnt:NotificationMessage&gt;
@@ -1606 +1612 @@
       </div>
 
-      <div class="sect3" title="DestroyRegistrationRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp367728"></a>DestroyRegistrationRequest</h4></div></div></div>
+      <div class="sect3" title="DestroyRegistrationRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp382784"></a>DestroyRegistrationRequest</h4></div></div></div>
         
 
         <p>A Publisher can terminate a Registration by sending the
-        DestroyRegistrationRequest message to <span class="emphasis"><em>QCG
-        Notification</em></span>. The parameter attached to this request is a
-        Publisher Registration ID.</p>
+        DestroyRegistrationRequest message to
+        <span class="emphasis"><em>QCG-Notification</em></span>. The parameter attached to this
+        request is a Publisher Registration ID.</p>
 
         <pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -1646 +1652 @@
       </div>
 
-      <div class="sect3" title="DestroyRegistrationResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp377696"></a>DestroyRegistrationResponse</h4></div></div></div>
+      <div class="sect3" title="DestroyRegistrationResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp391616"></a>DestroyRegistrationResponse</h4></div></div></div>
         
 
@@ -1677 +1683 @@
       </div>
 
-      <div class="sect3" title="CreatePullPointRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp382608"></a>CreatePullPointRequest</h4></div></div></div>
+      <div class="sect3" title="CreatePullPointRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp395104"></a>CreatePullPointRequest</h4></div></div></div>
         
 
         <p>In scenarios where the pull-style of notifications delivery is
         needed, Subscribers can create PullPoints. To do this, a Subscriber
-        sends the CreatePullPointRequest message to <span class="emphasis"><em>QCG Notification
+        sends the CreatePullPointRequest message to <span class="emphasis"><em>QCG-Notification
         PullPoint</em></span>.</p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
@@ -1707 +1713 @@
       </div>
 
-      <div class="sect3" title="CreatePullPointResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp388896"></a>CreatePullPointResponse</h4></div></div></div>
+      <div class="sect3" title="CreatePullPointResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp404048"></a>CreatePullPointResponse</h4></div></div></div>
         
 
@@ -1743 +1749 @@
       </div>
 
-      <div class="sect3" title="GetMessages"><div class="titlepage"><div><div><h4 class="title"><a id="idp397584"></a>GetMessages</h4></div></div></div>
+      <div class="sect3" title="GetMessages"><div class="titlepage"><div><div><h4 class="title"><a id="idp412272"></a>GetMessages</h4></div></div></div>
         
 
@@ -1784 +1790 @@
       </div>
 
-      <div class="sect3" title="GetMessagesResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp405392"></a>GetMessagesResponse</h4></div></div></div>
+      <div class="sect3" title="GetMessagesResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp421200"></a>GetMessagesResponse</h4></div></div></div>
         
 
@@ -1802 +1808 @@
       &lt;wsnt:Topic 
        Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span>&gt;
-       <span class="bold"><strong>xmlns:tns="<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics</strong></span>"</strong></span>&gt;
+       <span class="bold"><strong>xmlns:tns=
+        "<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics</strong></span>"</strong></span>&gt;
           <span class="bold"><strong>tns:House/Kitchen/Light</strong></span>
       &lt;/wsnt:Topic&gt;
@@ -1811 +1818 @@
       &lt;wsnt:ProducerReference&gt;
       &lt;wsnt:Message&gt;
-         <span class="bold"><strong><span class="bold"><strong>&lt;smnex:State 
-          xmlns:smnex="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"&gt;
-             on
-         &lt;/smnex:State&gt;</strong></span></strong></span>
+       <span class="bold"><strong><span class="bold"><strong>&lt;smnex:State 
+        xmlns:smnex=
+         "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"&gt;
+            on
+       &lt;/smnex:State&gt;</strong></span></strong></span>
       &lt;/wsnt:Message&gt;
      &lt;/wsnt:NotificationMessage&gt;
@@ -1866 +1874 @@
       </div>
 
-      <div class="sect3" title="DestroyPullPointRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp427696"></a>DestroyPullPointRequest</h4></div></div></div>
+      <div class="sect3" title="DestroyPullPointRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp442064"></a>DestroyPullPointRequest</h4></div></div></div>
         
 
@@ -1895 +1903 @@
       </div>
 
-      <div class="sect3" title="DestroyPullPointResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp433584"></a>DestroyPullPointResponse</h4></div></div></div>
+      <div class="sect3" title="DestroyPullPointResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp447728"></a>DestroyPullPointResponse</h4></div></div></div>
         
 
@@ -1923 +1931 @@
       </div>
 
-      <div class="sect3" title="GetCurrentMessageRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp439232"></a>GetCurrentMessageRequest</h4></div></div></div>
+      <div class="sect3" title="GetCurrentMessageRequest"><div class="titlepage"><div><div><h4 class="title"><a id="idp453344"></a>GetCurrentMessageRequest</h4></div></div></div>
         
 
@@ -1930 +1938 @@
         Notification Message on a specified Topic. Single GetCurrentMessage
         should refer exactly one Topic and has to be expressed in a supported
-        Dialect type.</p>
+        Dialect type. The support for CurrentMessages influences some
+        overhead, however it may be disabled in the configuration file if the
+        support for this function is useless for a scenario.</p>
 
         <pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -1943 +1953 @@
      &lt;wsnt:Topic 
       Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span>&gt;
-        <span class="bold"><strong>xmlns:tns="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics"</strong></span>&gt;
-         <span class="bold"><strong>tns:</strong></span><span class="bold"><strong>House/Kitchen/Light</strong></span>
+       <span class="bold"><strong>xmlns:tns=
+        "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics"</strong></span>&gt;
+         <span class="bold"><strong> tns:</strong></span><span class="bold"><strong>House/Kitchen/Light</strong></span>
      &lt;/wsnt:Topic&gt;
     &lt;/wsnt:GetCurrentMessage&gt;
@@ -1979 +1990 @@
       </div>
 
-      <div class="sect3" title="GetCurrentMessageResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp452432"></a>GetCurrentMessageResponse</h4></div></div></div>
-        
-
-        <p>In a response to GetCurrentMessageRequest <span class="emphasis"><em>QCG
-        Notification</em></span> prepares GetCurrentMessageResponse. This
-        message includes the content of the last Notification
-        GetCurrentMessageRequest refers to.</p>
+      <div class="sect3" title="GetCurrentMessageResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp461568"></a>GetCurrentMessageResponse</h4></div></div></div>
+        
+
+        <p>In a response to GetCurrentMessageRequest
+        <span class="emphasis"><em>QCG-Notification</em></span> prepares
+        GetCurrentMessageResponse. This message includes the content of the
+        last Notification GetCurrentMessageRequest refers to.</p>
 
         <pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -2006 +2017 @@
       &lt;wsnt:ProducerReference&gt; 
       &lt;smn-ext:Message&gt;
-         <span class="bold"><strong><span class="bold"><strong>&lt;smnex:State 
-          xmlns:smnex="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"&gt;
+       <span class="bold"><strong><span class="bold"><strong>&lt;smnex:State 
+        xmlns:smnex=
+         "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"&gt;
              on
-         &lt;/smnex:State&gt;</strong></span></strong></span>
+       &lt;/smnex:State&gt;</strong></span></strong></span>
       &lt;/smn-ext:Message&gt;
      &lt;/smn-ext:CurrentMessage&gt;
@@ -2032 +2044 @@
             <p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/smn-ext:GetCurrentMessage/smn-ext:NotifyTime</em></span></p>
 
-            <p>The time when notification was received by <span class="emphasis"><em>QCG
-            Notification</em></span>; expressed as universal time (UTC).</p>
+            <p>The time when notification was received by
+            <span class="emphasis"><em>QCG-Notification</em></span>; expressed as universal time
+            (UTC).</p>
           </li><li class="listitem">
             <p><span class="emphasis"><em>//wsnt:GetCurrentMessageResponse/wsnt:ProducerReference/wsa:Address</em></span></p>
@@ -2048 +2061 @@
       </div>
 
-      <div class="sect3" title="ListSubscriptions"><div class="titlepage"><div><div><h4 class="title"><a id="idp469520"></a>ListSubscriptions</h4></div></div></div>
+      <div class="sect3" title="ListSubscriptions"><div class="titlepage"><div><div><h4 class="title"><a id="idp482960"></a>ListSubscriptions</h4></div></div></div>
         
 
         <p>The first method from the the group of administrative methods.
         It may be invoked to get an information about available subscriptions
-        in the <span class="emphasis"><em>QCG Notification</em></span> service. The method
+        in the <span class="emphasis"><em>QCG-Notification</em></span> service. The method
         consists of various filtering parameters.</p>
 
@@ -2089 +2102 @@
       &lt;wsnt:Filter&gt;
        &lt;wsnt:MessageContent 
-        <span class="bold"><strong>xmlns:smnex="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"</strong></span> 
+        <span class="bold"><strong>xmlns:smnex=
+         "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"</strong></span> 
         Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"&gt;
-         <span class="bold"><strong>boolean(//smnex:State[text()="on"])</strong></span>
+         <span class="bold"><strong> boolean(//smnex:State[text()="on"])</strong></span>
        &lt;/wsnt:MessageContent&gt;
        &lt;wsnt:TopicExpression 
-        <span class="bold"><strong>xmlns:tns="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics"</strong></span> 
+        <span class="bold"><strong>xmlns:tns=
+         "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics"</strong></span> 
         Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span>&gt;
-         <span class="bold"><strong>tns://*</strong></span>
+          <span class="bold"><strong>tns://*</strong></span>
        &lt;/wsnt:TopicExpression&gt;
       &lt;/wsnt:Filter&gt;
@@ -2114 +2129 @@
             <p><span class="emphasis"><em>//smn-ext:ListSubscriptions/smn-ext:Filter</em></span></p>
 
-            <p>The expanding element from <span class="emphasis"><em>QCG
-            Notification</em></span> schema. It consists of a number of
-            optional filtering parameters.</p>
+            <p>The expanding element from
+            <span class="emphasis"><em>QCG-Notification</em></span> schema. It consists of a
+            number of optional filtering parameters.</p>
           </li><li class="listitem">
             <p><span class="emphasis"><em>//smn-ext:ListSubscriptions/smn-ext:Filter/SubscriptionID</em></span></p>
@@ -2154 +2169 @@
       </div>
 
-      <div class="sect3" title="ListSubscriptionsResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp495728"></a>ListSubscriptionsResponse</h4></div></div></div>
+      <div class="sect3" title="ListSubscriptionsResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp510016"></a>ListSubscriptionsResponse</h4></div></div></div>
         
 
@@ -2188 +2203 @@
       &lt;wsnt:Filter&gt;
        &lt;wsnt:MessageContent 
-        <span class="bold"><strong>xmlns:smnex="</strong></span><span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"</strong></span> 
+        <span class="bold"><strong>xmlns:smnex=
+         "</strong></span><span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousemessage"</strong></span> 
         Dialect="http://www.w3.org/TR/1999/REC-xpath-19991116"&gt;
-        <span class="bold"><strong>boolean(//smnex:State[text()="on"])</strong></span>
+        <span class="bold"><strong>  boolean(//smnex:State[text()="on"])</strong></span>
        &lt;/wsnt:MessageContent&gt;
        &lt;wsnt:TopicExpression <span class="bold"><strong>
-        xmlns:tns="http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics"</strong></span> 
+        xmlns:tns=
+         "http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics"</strong></span> 
         Dialect=<span class="bold"><strong>"http://docs.oasis-open.org/wsn/t-1/TopicExpression/Full"</strong></span>&gt;
-         <span class="bold"><strong>tns://*
+         <span class="bold"><strong> tns://*
        </strong></span>&lt;/wsnt:TopicExpression&gt;
       &lt;/wsnt:Filter&gt;
@@ -2218 +2235 @@
 
             <p>This element contains a list of subscriptions received from
-            <span class="emphasis"><em>QCG Notification</em></span> (probably also filtered on
+            <span class="emphasis"><em>QCG-Notification</em></span> (probably also filtered on
             the basis of the smn-ext:Filter element sent in
             ListSubscriptions).</p>
@@ -2253 +2270 @@
       </div>
 
-      <div class="sect3" title="ListPublishersRegistrations"><div class="titlepage"><div><div><h4 class="title"><a id="idp520736"></a>ListPublishersRegistrations</h4></div></div></div>
+      <div class="sect3" title="ListPublishersRegistrations"><div class="titlepage"><div><div><h4 class="title"><a id="idp535568"></a>ListPublishersRegistrations</h4></div></div></div>
         
 
@@ -2306 +2323 @@
             <p><span class="emphasis"><em>//smn-ext:ListPublishersRegistrations/smn-ext:Filter</em></span></p>
 
-            <p>The element from <span class="emphasis"><em>QCG Notification</em></span>
+            <p>The element from <span class="emphasis"><em>QCG-Notification</em></span>
             schema. It consists of optional filtering parameters.</p>
           </li><li class="listitem">
@@ -2319 +2336 @@
             <p>This element enables filtering based on an addresses of
             Publishers. Depending on configuration, this address may be held
-            in the <span class="emphasis"><em>QCG Notification</em></span> service as an address
+            in the <span class="emphasis"><em>QCG-Notification</em></span> service as an address
             sent in the From element of WSA Header of RegisterPublisher
             message or an IP address of a Publisher.</p>
@@ -2341 +2358 @@
       </div>
 
-      <div class="sect3" title="ListPublisherRegistrationsResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp542336"></a>ListPublisherRegistrationsResponse</h4></div></div></div>
+      <div class="sect3" title="ListPublisherRegistrationsResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp557152"></a>ListPublisherRegistrationsResponse</h4></div></div></div>
         
 
@@ -2392 +2409 @@
 
             <p>The element contains a list of Publishers Registrations
-            received from <span class="emphasis"><em>QCG Notification</em></span> (probably also
+            received from <span class="emphasis"><em>QCG-Notification</em></span> (probably also
             filtered on the basis of the smn-ext:Filter element sent in a
             ListPublishersRegistrations message).</p>
@@ -2422 +2439 @@
       </div>
 
-      <div class="sect3" title="ListPullPoints"><div class="titlepage"><div><div><h4 class="title"><a id="idp561984"></a>ListPullPoints</h4></div></div></div>
+      <div class="sect3" title="ListPullPoints"><div class="titlepage"><div><div><h4 class="title"><a id="idp576880"></a>ListPullPoints</h4></div></div></div>
         
 
@@ -2475 +2492 @@
             <p><span class="emphasis"><em>//smn-ext:ListPullPoints/smn-ext:Filter</em></span></p>
 
-            <p>The element from <span class="emphasis"><em>QCG Notification</em></span>
+            <p>The element from <span class="emphasis"><em>QCG-Notification</em></span>
             schema. It consists of optional filtering parameters.</p>
           </li><li class="listitem">
@@ -2488 +2505 @@
             <p>This element enables filtering based on an addresses of
             PullPoint. The PullPoint address is assigned after creation of a
-            PullPoint in <span class="emphasis"><em>QCG Notification</em></span> and returned
+            PullPoint in <span class="emphasis"><em>QCG-Notification</em></span> and returned
             inside CreatePullPointResponse.</p>
           </li><li class="listitem">
@@ -2509 +2526 @@
       </div>
 
-      <div class="sect3" title="ListPullPointsResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp582752"></a>ListPullPointsResponse</h4></div></div></div>
+      <div class="sect3" title="ListPullPointsResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp597744"></a>ListPullPointsResponse</h4></div></div></div>
         
 
@@ -2560 +2577 @@
 
             <p>The element contains a list of PullPoints received from
-            <span class="emphasis"><em>QCG Notification</em></span> (probably also previously
+            <span class="emphasis"><em>QCG-Notification</em></span> (probably also previously
             filtered on the basis of the smn-ext:Filter element sent in a
             ListPullPoints message).</p>
@@ -2590 +2607 @@
       </div>
 
-      <div class="sect3" title="ListTopicNamespaces"><div class="titlepage"><div><div><h4 class="title"><a id="idp601968"></a>ListTopicNamespaces</h4></div></div></div>
+      <div class="sect3" title="ListTopicNamespaces"><div class="titlepage"><div><div><h4 class="title"><a id="idp614320"></a>ListTopicNamespaces</h4></div></div></div>
         
 
@@ -2625 +2642 @@
             <p><span class="emphasis"><em>//smn-ext:ListTopicNamespaces/smn-ext:Filter</em></span></p>
 
-            <p>The element from <span class="emphasis"><em>QCG Notification</em></span>
+            <p>The element from <span class="emphasis"><em>QCG-Notification</em></span>
             schema. It consists of optional filtering parameters.</p>
           </li><li class="listitem">
@@ -2636 +2653 @@
       </div>
 
-      <div class="sect3" title="ListTopicNamespacesResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp612816"></a>ListTopicNamespacesResponse</h4></div></div></div>
+      <div class="sect3" title="ListTopicNamespacesResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp626784"></a>ListTopicNamespacesResponse</h4></div></div></div>
         
 
@@ -2684 +2701 @@
 
             <p>The element contains a list of information about
-            TopicNamespaces received from <span class="emphasis"><em>QCG
-            Notification</em></span> (optionally filtered on the basis of the
-            smn-ext:Filter element sent in a ListTopicNamespaces
+            TopicNamespaces received from
+            <span class="emphasis"><em>QCG-Notification</em></span> (optionally filtered on the
+            basis of the smn-ext:Filter element sent in a ListTopicNamespaces
             message).</p>
           </li><li class="listitem">
@@ -2707 +2724 @@
       </div>
 
-      <div class="sect3" title="AddTopicNamespace"><div class="titlepage"><div><div><h4 class="title"><a id="idp628080"></a>AddTopicNamespace</h4></div></div></div>
+      <div class="sect3" title="AddTopicNamespace"><div class="titlepage"><div><div><h4 class="title"><a id="idp642272"></a>AddTopicNamespace</h4></div></div></div>
         
 
         <p>An administrative method. The method may be invoked to add a new
-        TopicNamespace to the <span class="emphasis"><em>QCG Notification</em></span>.</p>
+        TopicNamespace to the <span class="emphasis"><em>QCG-Notification</em></span>.</p>
 
         <pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
@@ -2724 +2741 @@
     &lt;smn-ext:AddTopicNamespace&gt;
      &lt;wstop:TopicNamespace 
-      targetNamespace="<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics2</strong></span>"&gt;
+      targetNamespace=
+       "<span class="bold"><strong>http://schemas.qoscosgrid.org/ntf/2011/04/sample/myhousetopics2</strong></span>"&gt;
       &lt;wstop:Topic final="false" name="<span class="bold"><strong>House</strong></span>"&gt;
        &lt;wstop:Topic ...&gt;
@@ -2752 +2770 @@
       </div>
 
-      <div class="sect3" title="AddTopicNamespaceResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp637824"></a>AddTopicNamespaceResponse</h4></div></div></div>
+      <div class="sect3" title="AddTopicNamespaceResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp649664"></a>AddTopicNamespaceResponse</h4></div></div></div>
         
 
         <p>A response message to a AddTopicNamespaceRequest. It is empty
         and only confirms successful addition of a TopicNamespace to the
-        <span class="emphasis"><em>QCG Notification</em></span> service. </p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
+        <span class="emphasis"><em>QCG-Notification</em></span> service. </p><pre class="programlisting">&lt;SOAP-ENV:Envelope ... &gt;
    &lt;SOAP-ENV:Header&gt;
     &lt;wsa:Action SOAP-ENV:mustUnderstand="1"&gt;
@@ -2780 +2798 @@
       </div>
 
-      <div class="sect3" title="RemoveTopicNamespace"><div class="titlepage"><div><div><h4 class="title"><a id="idp643072"></a>RemoveTopicNamespace</h4></div></div></div>
+      <div class="sect3" title="RemoveTopicNamespace"><div class="titlepage"><div><div><h4 class="title"><a id="idp657536"></a>RemoveTopicNamespace</h4></div></div></div>
         
 
         <p>The next administrative method. It is used to remove a
-        TopicNamespace from the <span class="emphasis"><em>QCG Notification</em></span> system.
+        TopicNamespace from the <span class="emphasis"><em>QCG-Notification</em></span> system.
         Note that the removing may be only temporary (active to the restart of
         the system) if the TopicNamespace file is protected by disabling write
@@ -2821 +2839 @@
       </div>
 
-      <div class="sect3" title="RemoveTopicNamespaceResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp653056"></a>RemoveTopicNamespaceResponse</h4></div></div></div>
+      <div class="sect3" title="RemoveTopicNamespaceResponse"><div class="titlepage"><div><div><h4 class="title"><a id="idp667344"></a>RemoveTopicNamespaceResponse</h4></div></div></div>
         
 
@@ -2851 +2869 @@
   </div>
 
-  <div class="sect1" title="Administration Guide of QCG Notification"><div class="titlepage"><div><div><h2 class="title"><a id="idp656832"></a>Administration Guide of <span class="emphasis"><em>QCG
-    Notification</em></span></h2></div></div></div>
+  <div class="sect1" title="Administration Guide of QCG-Notification"><div class="titlepage"><div><div><h2 class="title"><a id="idp247088"></a>Administration Guide of
+    <span class="emphasis"><em>QCG-Notification</em></span></h2></div></div></div>
     
 
-    <div class="sect2" title="Prerequisites"><div class="titlepage"><div><div><h3 class="title"><a id="idp659488"></a>Prerequisites</h3></div></div></div>
+    <div class="sect2" title="Prerequisites"><div class="titlepage"><div><div><h3 class="title"><a id="idp674032"></a>Prerequisites</h3></div></div></div>
       
 
-      <p>In order to build and install <span class="emphasis"><em>QCG
-      Notification</em></span>, an administrator has to appropriately configure
-      operating system. There is some dependencies to external software that
-      should be satisfied.</p>
-
-      <div class="sect3" title="QCG Core library"><div class="titlepage"><div><div><h4 class="title"><a id="idp661264"></a>QCG Core library</h4></div></div></div>
-        
-
-        <p><span class="emphasis"><em>QCG Notification</em></span> is based on the
-        <span class="emphasis"><em>QCG Core</em></span> library developed by the
-        <span class="emphasis"><em>QCG</em></span> team. QCG Core is a common utility library
+      <p>In order to build and install
+      <span class="emphasis"><em>QCG-Notification</em></span>, an administrator has to
+      appropriately configure operating system. There is some dependencies to
+      external software that should be satisfied.</p>
+
+      <div class="sect3" title="QCG-Core library"><div class="titlepage"><div><div><h4 class="title"><a id="idp675824"></a>QCG-Core library</h4></div></div></div>
+        
+
+        <p><span class="emphasis"><em>QCG-Notification</em></span> is based on the
+        <span class="emphasis"><em>QCG-Core</em></span> library developed by the
+        <span class="emphasis"><em>QCG</em></span> team. QCG-Core is a common utility library
         providing set of basic modules used by other components within QCG
         Project. For more information see QCG Core documentation.</p>
 
-        <p>The QCG Core library should be properly configured in prior to
-        preparation of <span class="emphasis"><em>QCG Notification</em></span>.</p>
+        <p>The proper version of QCG-Core library should be configured in
+        prior to preparation of <span class="emphasis"><em>QCG-Notification</em></span>.</p>
       </div>
     </div>
 
-    <div class="sect2" title="Building"><div class="titlepage"><div><div><h3 class="title"><a id="idp665136"></a>Building</h3></div></div></div>
+    <div class="sect2" title="Building"><div class="titlepage"><div><div><h3 class="title"><a id="idp679536"></a>Building</h3></div></div></div>
       
 
-      <p>Before you compile <span class="emphasis"><em>QCG Notification</em></span>, you need
+      <p>Before you compile <span class="emphasis"><em>QCG-Notification</em></span>, you need
       to run the configuration script first. It will try to check if all the
       requirements are met and whether needed third party software is
@@ -2894 +2912 @@
             <p>--prefix=DIR</p>
 
-            <p>specifies directory where <span class="emphasis"><em>QCG
-            Notification</em></span> will be installed.</p>
+            <p>specifies directory where
+            <span class="emphasis"><em>QCG-Notification</em></span> will be installed.</p>
 
             <p>Default: /opt/qcg</p>
@@ -2920 +2938 @@
             service should be build</p>
           </li></ul></div><p>After successful configuration step, compiling and
-      installing of <span class="emphasis"><em>QCG Notification</em></span> should be a
+      installing of <span class="emphasis"><em>QCG-Notification</em></span> should be a
       straightforward process:</p>
 
@@ -2928 +2946 @@
       <div class="note" title="Note" style="margin-left: 0.5in; margin-right: 0.5in;"><h3 class="title">Note</h3>
         <p>The installation step should be done either as
-        <code class="filename">root</code> or the user that will execute <span class="emphasis"><em>QCG
-        Notification</em></span> service, assuming he has necessary privileges
-        to do this.</p>
+        <code class="filename">root</code> or the user that will execute
+        <span class="emphasis"><em>QCG-Notification</em></span> service, assuming he has
+        necessary privileges to do this.</p>
       </div>
     </div>
 
-    <div class="sect2" title="Creating database for QCG Notification - the PostgreSQL example"><div class="titlepage"><div><div><h3 class="title"><a id="idp680896"></a>Creating database for <span class="emphasis"><em>QCG Notification</em></span> - the
+    <div class="sect2" title="Creating database for QCG-Notification - the PostgreSQL example"><div class="titlepage"><div><div><h3 class="title"><a id="idp695296"></a>Creating database for <span class="emphasis"><em>QCG-Notification</em></span> - the
       PostgreSQL example</h3></div></div></div>
       
 
-      <p><span class="emphasis"><em>QCG Notification</em></span> can be run in two basic
-      modes related to the database connection: without database or with
+      <p><span class="emphasis"><em>QCG-Notification</em></span> can be run in two basic
+      modes related to the database connection: without a database or with a
       database. Although the first option is sufficient for simple scenarios,
-      it reduces the overall functionality of the <span class="emphasis"><em>QCG
-      Notification</em></span> (e.g. disable PullPoints). Therefore using the
-      database is recomended and can be often essential.</p>
+      it reduces the overall functionality of
+      <span class="emphasis"><em>QCG-Notification</em></span> (e.g. disable PullPoints).
+      Therefore using the database is recommended and can be often
+      essential.</p>
 
       <p>You will find more detailed description of administrative tasks in
       PostgreSQL tutorial. However, the following basic steps are needed to
-      set up a database and appropriate tables for <span class="emphasis"><em>QCG
-      Notification</em></span> assuming that you have already setup a
-      PostgreSQL database:</p>
+      set up a database and appropriate tables for
+      <span class="emphasis"><em>QCG-Notification</em></span> assuming that you have already
+      setup a PostgreSQL database:</p>
 
       <p>By default, the first database user created will also be named
       <code class="filename">postgres</code>. In order to create a user for
-      <span class="emphasis"><em>QCG Notification</em></span> usage, for instance
+      <span class="emphasis"><em>QCG-Notification</em></span> usage, for instance
       <code class="filename">qcg-ntf</code>, type the following:</p>
 
@@ -2966 +2985 @@
 
       <p>and set up a table structure using the
-      <code class="filename">qcg-ntf-psql.sql</code> file from <span class="emphasis"><em>QCG
-      Notification</em></span> distribution - it can be found in
+      <code class="filename">qcg-ntf-psql.sql</code> file from
+      <span class="emphasis"><em>QCG-Notification</em></span> distribution - it can be found in
       <code class="filename">/opt/qcg/share/tools</code> directory by default.</p>
 
@@ -2975 +2994 @@
       Name. You can do this by editing system-wide configuration file (e.g.
       <code class="filename">/etc/odbc.ini)</code> or <code class="filename">.odbc.ini</code> in
-      home directory of the user that will be used to start <span class="emphasis"><em>QCG
-      Notification</em></span>.</p>
+      home directory of the user that will be used to start
+      <span class="emphasis"><em>QCG-Notification</em></span>.</p>
 
       <p>Assuming that ODBC are installed in /usr/local/lib and the choosed
-      name for <span class="emphasis"><em>QCG Notification</em></span> is
+      name for <span class="emphasis"><em>QCG-Notification</em></span> is
       <code class="filename">qcg-ntf</code> the configuration file should looks
       simmilar to the following:</p>
 
       <pre class="programlisting">[qcg-ntf]
-Description     = QCG Notification database
+Description     = QCG-Notification database
 Driver        = /usr/local/lib/libodbcpsql.so
 Setup         = /usr/local/lib/libodbcpsqlS.so
@@ -3006 +3025 @@
   </div>
 
-  <div class="sect1" title="Configuration of QCG Notification"><div class="titlepage"><div><div><h2 class="title"><a id="idp702064"></a>Configuration of <span class="emphasis"><em>QCG Notification</em></span></h2></div></div></div>
+  <div class="sect1" title="Configuration of QCG-Notification"><div class="titlepage"><div><div><h2 class="title"><a id="idp716544"></a>Configuration of <span class="emphasis"><em>QCG-Notification</em></span></h2></div></div></div>
     
 
-    <div class="sect2" title="Configuration File: qcg-ntfd.xml"><div class="titlepage"><div><div><h3 class="title"><a id="idp703168"></a>Configuration File: <code class="filename">qcg-ntfd.xml</code></h3></div></div></div>
+    <div class="sect2" title="Configuration File: qcg-ntfd.xml"><div class="titlepage"><div><div><h3 class="title"><a id="idp717776"></a>Configuration File: <code class="filename">qcg-ntfd.xml</code></h3></div></div></div>
       
 
@@ -3024 +3043 @@
     &lt;/sm:ModuleManager&gt;
 
-    &lt;sm:Service xsi:type="ntfd" description="QCG Notification"&gt;
+    &lt;sm:Service xsi:type="ntfd" description="QCG-Notification"&gt;
       &lt;sm:Logger&gt;
         &lt;sm:Filename&gt;/opt/qcg/var/log/qcg-ntf/qcg-ntfd.log&lt;/sm:Filename&gt;
@@ -3055 +3074 @@
         &lt;X509CertKeyFile&gt;/opt/qcg/etc/ssl/broker.pem&lt;/X509CertKeyFile&gt;
         &lt;X509KeyPass&gt;somepass&lt;/X509KeyPass&gt;
-        &lt;sm:TrustedCAFile&gt;/opt/qcg/etc/ssl/certs/qcg-ntf/ca.pem&lt;/sm:TrustedCAFile&gt;
+        &lt;sm:TrustedCAFile&gt;
+          /opt/qcg/etc/ssl/certs/qcg-ntf/ca.pem
+        &lt;/sm:TrustedCAFile&gt;
       &lt;/sm:Module&gt;
       
@@ -3061 +3082 @@
         &lt;NotificationsVar&gt;
           &lt;TopicNsDir&gt;/opt/qcg/etc/topicns&lt;/TopicNsDir&gt;
-          &lt;StrictCorrectnessCheckingEnabled&gt;false&lt;/StrictCorrectnessCheckingEnabled&gt;
+          &lt;StrictCorrectnessCheckingEnabled&gt;
+            false
+          &lt;/StrictCorrectnessCheckingEnabled&gt;
           &lt;DisableCurrentMessages&gt;false&lt;/DisableCurrentMessages&gt;
           &lt;SubscriptionManager&gt;
@@ -3164 +3187 @@
 
           <p>Initialization and configuration of the modules for the
-          Publisher side of <span class="emphasis"><em>QCG Notification</em></span>. The
+          Publisher side of <span class="emphasis"><em>QCG-Notification</em></span>. The
           following modules are currently supported:</p>
 
@@ -3185 +3208 @@
           </em></span>[smn:NotificationsVarType]</p>
 
-          <p>Various notification settings closely related to QCG
-          Notification service implementation.</p>
+          <p>Various notification settings closely related to
+          QCG-Notification service implementation.</p>
         </li><li class="listitem">
           <p><span class="emphasis"><em>//smn:Core/smn:NotificationsVar/smn:TopicNsDir
@@ -3364 +3387 @@
 
           <p>true, false - determines if a database should be enabled; in
-          the simplest configuration, <span class="emphasis"><em>QCG Notification</em></span>
+          the simplest configuration, <span class="emphasis"><em>QCG-Notification</em></span>
           can be used also without a database connection, however many options
           will be then unavailable. Default: true</p>
@@ -3388 +3411 @@
 
           <p>true, false - determines whether all information stored in a
-          database should be cleaned at starting of the QCG Notification
+          database should be cleaned at starting of the QCG-Notification
           service.</p>
         </li></ul></div>
@@ -3397 +3420 @@
 
       <p>Modules are located in the PREFIX/*/lib/modules directories and
-      are loaded during the<span class="emphasis"><em> QCG Notification</em></span> run time.
+      are loaded during the<span class="emphasis"><em> QCG-Notification</em></span> run time.
       Module definitions are specified in appropriate sections of the
       configuration file.</p>
 
-      <div class="sect3" title="Publisher modules"><div class="titlepage"><div><div><h4 class="title"><a id="idp794784"></a>Publisher modules</h4></div></div></div>
+      <div class="sect3" title="Publisher modules"><div class="titlepage"><div><div><h4 class="title"><a id="idp808864"></a>Publisher modules</h4></div></div></div>
         
 
@@ -3408 +3431 @@
         and notification channels that need to be setup. The first one is a
         communication channel between Subscriber/Publisher clients and
-        <span class="emphasis"><em>QCG Notification. </em></span>This type of communication is
+        <span class="emphasis"><em>QCG-Notification. </em></span>This type of communication is
         currently completely based on QCG Core library.</p>
 
         <p>The second type is an outgoing communication between
-        <span class="emphasis"><em>QCG Notification</em></span> and NotificationConsumers and it
-        is particular for <span class="emphasis"><em>QCG Notification</em></span>. In this
-        situation <span class="emphasis"><em>QCG Notification</em></span> plays a role of a
+        <span class="emphasis"><em>QCG-Notification</em></span> and NotificationConsumers and it
+        is particular for <span class="emphasis"><em>QCG-Notification</em></span>. In this
+        situation <span class="emphasis"><em>QCG-Notification</em></span> plays a role of a
         Notification Publisher. At this time, supported modules for this
         channel utilize a Web Service interface, XMPP interface and SMTP
@@ -3437 +3460 @@
   &lt;smn:RecvTimeout&gt;10&lt;/smn:RecvTimeout&gt;
   &lt;smn:SendTimeout&gt;10&lt;/smn:SendTimeout&gt;
-  &lt;smn:X509CertKeyFile&gt;/opt/qcg/etc/ssl/qcg-ntf/qcg-ntfd.pem&lt;/smn:X509CertKeyFile&gt;
+  &lt;smn:X509CertKeyFile&gt;
+    /opt/qcg/etc/ssl/qcg-ntf/qcg-ntfd.pem
+  &lt;/smn:X509CertKeyFile&gt;
   &lt;smn:X509KeyPass&gt;qcgpass&lt;/smn:X509KeyPass&gt;
   &lt;smn:TrustedCAFile&gt;/opt/qcg/etc/ssl/certs/qcg-ntf/ca.pem&lt;/smn:TrustedCAFile&gt;
@@ -3649 +3674 @@
     </div>
 
-    <div class="sect2" title="WS-Topics management"><div class="titlepage"><div><div><h3 class="title"><a id="idp870048"></a>WS-Topics management</h3></div></div></div>
+    <div class="sect2" title="WS-Topics management"><div class="titlepage"><div><div><h3 class="title"><a id="idp883872"></a>WS-Topics management</h3></div></div></div>
       
 
-      <p>In the current release, a topics management in <span class="emphasis"><em>QCG
-      Notification</em></span> is relatively simple. The first step is a
-      preparation of an XML document with a Topic Namespace definition. This
-      step can be done by one of the peers cooperating with <span class="emphasis"><em>QCG
-      Notification</em></span>. Then the document should be delivered to the
-      computer where <span class="emphasis"><em>QCG Notification</em></span> is installed. It
-      can be done in two ways: the document may be copied manually by QCG
-      Notification administrator to TopicNamespaces directory in prior to
-      <span class="emphasis"><em>a QCG Notification</em></span> startup or it can be send
-      through the <span class="emphasis"><em>QCG Notification</em></span> interface when
-      <span class="emphasis"><em>QCG Notification</em></span> is already running. In the last
+      <p>In the current release, a topics management in
+      <span class="emphasis"><em>QCG-Notification</em></span> is relatively simple. The first
+      step is a preparation of an XML document with a Topic Namespace
+      definition. This step can be done by one of the peers cooperating with
+      <span class="emphasis"><em>QCG-Notification</em></span>. Then the document should be
+      delivered to the computer where <span class="emphasis"><em>QCG-Notification</em></span> is
+      installed. It can be done in two ways: the document may be copied
+      manually by QCG-Notification administrator to TopicNamespaces directory
+      in prior to <span class="emphasis"><em>a QCG-Notification</em></span> startup or it can be
+      send through the <span class="emphasis"><em>QCG-Notification</em></span> interface when
+      <span class="emphasis"><em>QCG-Notification</em></span> is already running. In the last
       case, the TopicNamespaces are stored also in a files in TopicNamespace
       directory so they can be automatically loaded after restart of the
       service. The TopicNamespaces loaded from files may be protected from
-      unwanted removal by unsetting write permissions for a certain
+      unwanted removal by disabling write permissions for a certain
       file.</p>
 
@@ -3673 +3698 @@
     </div>
 
-    <div class="sect2" title="Starting QCG Notification"><div class="titlepage"><div><div><h3 class="title"><a id="idp875936"></a>Starting <span class="emphasis"><em>QCG Notification</em></span></h3></div></div></div>
+    <div class="sect2" title="Starting QCG-Notification"><div class="titlepage"><div><div><h3 class="title"><a id="idp889392"></a>Starting <span class="emphasis"><em>QCG-Notification</em></span></h3></div></div></div>
       
 
-      <p>To start <span class="emphasis"><em>QCG Notification</em></span> as a daemon
+      <p>To start <span class="emphasis"><em>QCG-Notification</em></span> as a daemon
       type:</p>
 
       <pre class="programlisting">$ ./qcg-ntfd</pre>
 
-      <p>If you start <span class="emphasis"><em>QCG Notification</em></span> with parameter
+      <p>If you start <span class="emphasis"><em>QCG-Notification</em></span> with parameter
       -h you will get an optional parameters list:</p><pre class="programlisting">$ ./qcg-ntfd -h
 usage: ./qcg-ntfd [-d] [-z config_file]
@@ -3689 +3714 @@
   -z config_file  configuration file, default is /opt/qcg/etc/qcg-ntfd.xml
   -v              print version information
-  -h              print this help</pre><p>Once you run <span class="emphasis"><em>QCG
-      Notification</em></span> as a daemon, a log file is created. Using
-      various log levels, you can log less or more details.</p>
+  -h              print this help</pre><p>Once you run
+      <span class="emphasis"><em>QCG-Notification</em></span> as a daemon, a log file is
+      created. Using various log levels, you can log less or more
+      details.</p>
     </div>
 
-    <div class="sect2" title="Stopping QCG Notification"><div class="titlepage"><div><div><h3 class="title"><a id="idp881408"></a>Stopping <span class="emphasis"><em>QCG Notification</em></span></h3></div></div></div>
+    <div class="sect2" title="Stopping QCG-Notification"><div class="titlepage"><div><div><h3 class="title"><a id="idp894960"></a>Stopping <span class="emphasis"><em>QCG-Notification</em></span></h3></div></div></div>