Merge branch 'candidate-7.6.0' into candidate-7.6.x

Signed-off-by: Richard Chapman <rchapman@hpccsystems.com>

docs/EN_US/HPCCSystemAdmin/HPCCSystemAdministratorsGuide.xml

@@ -2,10 +2,12 @@
 <!DOCTYPE article PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book xml:base="../">
-  <title>HPCC Systems<superscript>®</superscript> Administrator's Guide</title>
+  <title>HPCC Systems<superscript>®</superscript> Administrator's
+  Guide</title>
 
   <bookinfo>
-    <title>HPCC  Systems<superscript>®</superscript> Administrator's Guide</title>
+    <title>HPCC Systems<superscript>®</superscript> Administrator's
+    Guide</title>
 
     <mediaobject>
       <imageobject>
@@ -74,12 +76,13 @@
       parallel-processing computing platform that solves Big Data
       problems.</para>
 
-      <para>HPCC Systems platform stores and processes large quantities of data, processing
-      billions of records per second using massive parallel processing
-      technology. Large amounts of data across disparate data sources can be
-      accessed, analyzed, and manipulated in fractions of seconds. HPCC Systems
-      functions as both a processing and a distributed data storage
-      environment, capable of analyzing terabytes of information.</para>
+      <para>HPCC Systems platform stores and processes large quantities of
+      data, processing billions of records per second using massive parallel
+      processing technology. Large amounts of data across disparate data
+      sources can be accessed, analyzed, and manipulated in fractions of
+      seconds. HPCC Systems functions as both a processing and a distributed
+      data storage environment, capable of analyzing terabytes of
+      information.</para>
     </sect1>
 
     <sect1 id="HPCC_Architectural_Overview">
@@ -130,8 +133,9 @@
       <sect2 id="HPCC_Clusters" role="brk">
         <title>Clusters</title>
 
-        <para>HPCC Systems environment contains clusters which you define and use
-        according to your needs. The types of clusters used by HPCC Systems:</para>
+        <para>HPCC Systems environment contains clusters which you define and
+        use according to your needs. The types of clusters used by HPCC
+        Systems:</para>
 
         <sect3 id="SysAdm_Thor_Cluster">
           <title>Thor</title>
@@ -178,8 +182,8 @@
         <title>System Servers</title>
 
         <para>The System Servers are integral middleware components of an HPCC
-        Systems platform. They are used to control workflow and inter-component
-        communication.</para>
+        Systems platform. They are used to control workflow and
+        inter-component communication.</para>
 
         <sect3 id="SysAdm_Dali">
           <title>Dali</title>
@@ -195,8 +199,8 @@
           -clients</emphasis>)</para>
 
           <para>Another task Dali performs is to act as the locking manager.
-          HPCC Systems uses Dali's locking manager to control shared and exclusive
-          locks to metadata.</para>
+          HPCC Systems uses Dali's locking manager to control shared and
+          exclusive locks to metadata.</para>
         </sect3>
 
         <sect3 id="SysAdm_Sahsa">
@@ -428,18 +432,18 @@
     <title>Hardware and Software Requirements</title>
 
     <para>This chapter describes some of the hardware and software
-    requirements in order to run the HPCC Systems platform. HPCC Systems is designed to run on
-    commodity hardware, which makes building and maintaining large scale
-    (petabytes) clusters economically feasible. When planning your cluster
-    hardware, you will need to balance a number of considerations specific to
-    your needs.</para>
+    requirements in order to run the HPCC Systems platform. HPCC Systems is
+    designed to run on commodity hardware, which makes building and
+    maintaining large scale (petabytes) clusters economically feasible. When
+    planning your cluster hardware, you will need to balance a number of
+    considerations specific to your needs.</para>
 
     <para>This section provides some insight into the hardware and
     infrastructure that HPCC Systems works well on. This is not an exclusive
     comprehensive set of instructions, nor a mandate on what hardware you must
     have. Consider this as a guide to use when looking to implement or scale
-    your HPCC Systems platform. These suggestions should be taken into consideration for
-    your specific enterprise needs.</para>
+    your HPCC Systems platform. These suggestions should be taken into
+    consideration for your specific enterprise needs.</para>
 
     <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/Hardware.xml"
                 xpointer="xpointer(//*[@id='HW-Switch'])"
@@ -462,20 +466,21 @@
     <title>Hardware and Components</title>
 
     <para>This section provides some insight as to what sort of hardware and
-    infrastructure optimally HPCC Systems works well on. This is not an exclusive
-    comprehensive set of instructions, nor a mandate on what hardware you must
-    have. Consider this as a guide to use when looking to implement or scale
-    your HPCC Systems platform. These suggestions should be taken into consideration for
-    your specific enterprise needs.</para>
-
-    <para>HPCC Systems is designed to run on commodity hardware, which makes building
-    and maintaining large scale (petabytes) clusters economically feasible.
-    When planning your cluster hardware, you will need to balance a number of
-    considerations, including fail-over domains and potential performance
-    issues. Hardware planning should include distributing HPCC Systems across multiple
-    physical hosts, such as a cluster. Generally, one type of best practice is
-    to run HPCC Systems processes of a particular type, for example Thor, Roxie, or
-    Dali, on a host configured specifically for that type of process.</para>
+    infrastructure optimally HPCC Systems works well on. This is not an
+    exclusive comprehensive set of instructions, nor a mandate on what
+    hardware you must have. Consider this as a guide to use when looking to
+    implement or scale your HPCC Systems platform. These suggestions should be
+    taken into consideration for your specific enterprise needs.</para>
+
+    <para>HPCC Systems is designed to run on commodity hardware, which makes
+    building and maintaining large scale (petabytes) clusters economically
+    feasible. When planning your cluster hardware, you will need to balance a
+    number of considerations, including fail-over domains and potential
+    performance issues. Hardware planning should include distributing HPCC
+    Systems across multiple physical hosts, such as a cluster. Generally, one
+    type of best practice is to run HPCC Systems processes of a particular
+    type, for example Thor, Roxie, or Dali, on a host configured specifically
+    for that type of process.</para>
 
     <sect1 id="SysAdm_ThorHW">
       <title>Thor Hardware</title>
@@ -492,21 +497,21 @@
 
       <para>It is important to note that HPCC Systems by nature is a parallel
       processing system and all Thor slave nodes will be exercising at
-      precisely the same time. So when allocating more than one HPCC Systems Thor
-      slave per physical machine assure that each slave meets the recommended
-      requirements.</para>
+      precisely the same time. So when allocating more than one HPCC Systems
+      Thor slave per physical machine assure that each slave meets the
+      recommended requirements.</para>
 
       <para>For instance, 1 physical server with 48 cores, 96GB RAM, 10Gb/sec
       network and 2GB/sec sequential I/O would be capable of running ten (10)
-      HPCC Systems Thor slaves at optimal efficiency. The order of optimization for
-      resource usage in a Thor slave node is disk I/O 60%, network 30%, and
-      CPU 10%. Any increase in sequential I/O will have the most impact on
-      speed, followed by improvements in network, followed by improvements in
-      CPU.</para>
+      HPCC Systems Thor slaves at optimal efficiency. The order of
+      optimization for resource usage in a Thor slave node is disk I/O 60%,
+      network 30%, and CPU 10%. Any increase in sequential I/O will have the
+      most impact on speed, followed by improvements in network, followed by
+      improvements in CPU.</para>
 
-      <para>Network architecture is also an important consideration. HPCC Systems Thor
-      nodes work optimally in a streamlined network architecture between all
-      Thor slave processes.</para>
+      <para>Network architecture is also an important consideration. HPCC
+      Systems Thor nodes work optimally in a streamlined network architecture
+      between all Thor slave processes.</para>
 
       <para>RAID is recommended and all RAID levels suitable for sequential
       read/write operations and high availability are acceptable. For example,
@@ -516,19 +521,19 @@
     <sect1 id="SysAdm_RoxieHW">
       <title>Roxie Hardware Configurations</title>
 
-      <para>HPCC Systems Roxie processes require require a proper, yet different (from
-      Thor) balance of CPU, RAM, network, and disk I/O in order to ensure
-      efficient operations. A single HPCC Systems Roxie node works optimally when
-      allocated 6 or more CPU cores, 24GB RAM, 1Gb/sec network backbone, and
-      400/sec 4k random read IOPS.</para>
+      <para>HPCC Systems Roxie processes require require a proper, yet
+      different (from Thor) balance of CPU, RAM, network, and disk I/O in
+      order to ensure efficient operations. A single HPCC Systems Roxie node
+      works optimally when allocated 6 or more CPU cores, 24GB RAM, 1Gb/sec
+      network backbone, and 400/sec 4k random read IOPS.</para>
 
-      <para>Each HPCC Systems Roxie node is presented two hard drives, each capable of
-      200/sec 4k random seek IOPS. Hard drive recommendations for Roxie
-      efficiency are 15K SAS, or SSD. A good rule of thumb is the more random
-      read IOPS the better and faster your Roxie will perform.</para>
+      <para>Each HPCC Systems Roxie node is presented two hard drives, each
+      capable of 200/sec 4k random seek IOPS. Hard drive recommendations for
+      Roxie efficiency are 15K SAS, or SSD. A good rule of thumb is the more
+      random read IOPS the better and faster your Roxie will perform.</para>
 
-      <para>Running multiple HPCC Systems Roxie nodes on a single physical server is
-      not recommended, except in the cases of virtualization or
+      <para>Running multiple HPCC Systems Roxie nodes on a single physical
+      server is not recommended, except in the cases of virtualization or
       containers.</para>
 
       <para>Configure your system to balance the size of your Thor and Roxie
@@ -541,13 +546,14 @@
     <sect1 id="SysAdm_Dali_Sasha">
       <title>Dali and Sasha Hardware Configurations</title>
 
-      <para>HPCC Systems Dali processes store cluster metadata in RAM. For optimal
-      efficiency, provide at least 48GB of RAM, 6 or more CPU cores, 1Gb/sec
-      network interface and a high availability disk for a single HPCC Systems Dali.
-      The HPCC Systems Dali processes are one of the few native active/passive
-      components. Using standard "swinging disk" clustering is recommended for
-      a high availability setup. For a single HPCC Systems Dali process, any suitable
-      High Availability (HA) RAID level is fine.</para>
+      <para>HPCC Systems Dali processes store cluster metadata in RAM. For
+      optimal efficiency, provide at least 48GB of RAM, 6 or more CPU cores,
+      1Gb/sec network interface and a high availability disk for a single HPCC
+      Systems Dali. The HPCC Systems Dali processes are one of the few native
+      active/passive components. Using standard "swinging disk" clustering is
+      recommended for a high availability setup. For a single HPCC Systems
+      Dali process, any suitable High Availability (HA) RAID level is
+      fine.</para>
 
       <para>Sasha only stores data to locally available disks, reading data
       from Dali then processing it by archiving workunits (WUs) to disk. It is
@@ -641,26 +647,26 @@
   <chapter id="Routine_Maintenance">
     <title>Routine Maintenance</title>
 
-    <para>In order to ensure that your HPCC Systems platform keeps running optimally,
-    some care and maintenance is required. The following sections address
-    routine maintenance tasks for your HPCC Systems platform.</para>
+    <para>In order to ensure that your HPCC Systems platform keeps running
+    optimally, some care and maintenance is required. The following sections
+    address routine maintenance tasks for your HPCC Systems platform.</para>
 
     <!--***SYSTEM HEALTH CHECK UP***TO COME***-->
 
     <sect1 id="SysAdmin_DataHandling">
       <title>Data Handling</title>
 
-      <para>When you start working with your HPCC Systems platform, you will want to
-      have some data on the system to process. Data gets transferred to the
-      HPCC Systems platform by a process called a spray. Likewise to get data out from
-      an HPCC Systems platform it must be desprayed.</para>
+      <para>When you start working with your HPCC Systems platform, you will
+      want to have some data on the system to process. Data gets transferred
+      to the HPCC Systems platform by a process called a spray. Likewise to
+      get data out from an HPCC Systems platform it must be desprayed.</para>
 
-      <para>As the HPCC Systems platform is a computer cluster the data gets deployed out over the
-      nodes that make up the cluster. A <emphasis>spray</emphasis> or import
-      is the relocation of a data file from one location (such as a Landing
-      Zone) to a cluster. The term spray was adopted due to the nature of the
-      file movement -- the file is partitioned across all nodes within a
-      cluster.</para>
+      <para>As the HPCC Systems platform is a computer cluster the data gets
+      deployed out over the nodes that make up the cluster. A
+      <emphasis>spray</emphasis> or import is the relocation of a data file
+      from one location (such as a Landing Zone) to a cluster. The term spray
+      was adopted due to the nature of the file movement -- the file is
+      partitioned across all nodes within a cluster.</para>
 
       <para>A <emphasis>despray</emphasis> or export is the relocation of a
       data file from a Data Refinery cluster to a single machine location
@@ -678,8 +684,10 @@
       protocol, something like a WinSCP.</para>
 
       <para>For more information about HPCC Systems data handling see the
-      <emphasis>HPCC Systems<superscript>®</superscript> Data Handling</emphasis> and the <emphasis>HPCC Systems<superscript>®</superscript> Data
-      Tutorial</emphasis> documents.</para>
+      <emphasis>HPCC Systems<superscript>®</superscript> Data
+      Handling</emphasis> and the <emphasis>HPCC
+      Systems<superscript>®</superscript> Data Tutorial</emphasis>
+      documents.</para>
 
       <!--***CAN TIE THIS ALL TOGETHER - as part of routine maint. clean up some data files... archive data... etc. ***TO COME***-->
     </sect1>
@@ -796,11 +804,12 @@
 
           <para><emphasis role="bold">Backupnode</emphasis></para>
 
-          <para>Backupnode is a tool that is packaged with HPCC Systems platform. Backupnode
-          allows you to backup Thor nodes on demand or in a script. You can
-          also use backupnode regularly in a crontab or by adding a backupnode
-          component with Configuration Manager to your environment. You would
-          always want to run it on the Thor master of that cluster.</para>
+          <para>Backupnode is a tool that is packaged with HPCC Systems
+          platform. Backupnode allows you to backup Thor nodes on demand or in
+          a script. You can also use backupnode regularly in a crontab or by
+          adding a backupnode component with Configuration Manager to your
+          environment. You would always want to run it on the Thor master of
+          that cluster.</para>
 
           <para>The following example is one suggested way for invoking
           backupnode manually.</para>
@@ -905,8 +914,8 @@
     <sect1 id="SysAdm_Log_Files">
       <title>Log Files</title>
 
-      <para>HPCC Systems provides a wealth of information which can be used to debug,
-      track transactions, application performance, and troubleshooting
+      <para>HPCC Systems provides a wealth of information which can be used to
+      debug, track transactions, application performance, and troubleshooting
       purposes. You can review HPCC Systems messages as they are reported and
       captured in the log files. Log files can help you in understanding what
       is occurring on the system and useful in troubleshooting.</para>
@@ -1115,16 +1124,17 @@
   <chapter id="OnDemand_Maintenance">
     <title>System Configuration and Management</title>
 
-    <para>HPCC Systems require configuration. The Configuration Manager
-    tool (configmgr) included with the system software is a valuable piece of
-    setting up your HPCC Systems platform. The Configuration Manager is a graphical tool
-    provided that can be used to configure your system. Configuration Manager
-    has a wizard that you can run which will easily generate an environment
-    file to get you configured, up and running quickly. There is an advanced
-    option available through Configuration Manager which allows for a more
-    specific configuration, while still using the graphical interface. If
-    desired you can edit the environment files using any xml or text editor
-    however the file structure must remain valid.</para>
+    <para>HPCC Systems require configuration. The Configuration Manager tool
+    (configmgr) included with the system software is a valuable piece of
+    setting up your HPCC Systems platform. The Configuration Manager is a
+    graphical tool provided that can be used to configure your system.
+    Configuration Manager has a wizard that you can run which will easily
+    generate an environment file to get you configured, up and running
+    quickly. There is an advanced option available through Configuration
+    Manager which allows for a more specific configuration, while still using
+    the graphical interface. If desired you can edit the environment files
+    using any xml or text editor however the file structure must remain
+    valid.</para>
 
     <para>
       <figure>
@@ -1188,8 +1198,8 @@
 
                 <entry><emphasis role="bold">WARNING</emphasis>: These
                 settings are essential to proper system operation. Only expert
-                level HPCC Systems administrators should attempt to change any aspects
-                of this file.</entry>
+                level HPCC Systems administrators should attempt to change any
+                aspects of this file.</entry>
               </row>
             </tbody>
           </tgroup>
@@ -1198,8 +1208,9 @@
 
       <programlisting>/etc/HPCCSystems</programlisting>
 
-      <para>Environment.conf is required upon startup of the HPCC Systems platform. The
-      environment.conf is where the HPCC Systems environment file is defined.</para>
+      <para>Environment.conf is required upon startup of the HPCC Systems
+      platform. The environment.conf is where the HPCC Systems environment
+      file is defined.</para>
 
       <programlisting>/opt/HPCCSystems/environment.xml</programlisting>
 
@@ -1270,12 +1281,12 @@ jvmoptions=-XX:-UsePerfData
 # Enabling both may lead to unpredicatable results
 # including segfaults or undefined symbol errors.
 #
-# If you would prefer to use python 3 and disable python2, change the line below to read
-#  additionalPlugins=python3
+# If you would prefer to use python 2 and disable python3, change the line below to read
+#  additionalPlugins=python2
 #
 # Multiple paths can be specified (separate with :, or ; on Windows).
 # Relative paths are assumed to be relative to /opt/HPCCSystems/versioned
-additionalPlugins=python2
+additionalPlugins=python3
 
 # To en-/disable Drop Zone restriction.
 # Default is enabled (true).
@@ -1309,9 +1320,10 @@ classpath=/opt/HPCCSystems/classes
 runtime=/var/lib/HPCCSystems
 lock=/var/lock/HPCCSystems</programlisting>
 
-        <para>The HPCC Systems platform will not run properly without the proper paths, and in some
-        cases needs the absolute path. If a process or component can't find a
-        path you will get an error message such as the following:</para>
+        <para>The HPCC Systems platform will not run properly without the
+        proper paths, and in some cases needs the absolute path. If a process
+        or component can't find a path you will get an error message such as
+        the following:</para>
 
         <programlisting>"There are no components configured to run on the node..." </programlisting>
 
@@ -1489,17 +1501,17 @@ lock=/var/lock/HPCCSystems</programlisting>
       <sect2 id="Using_nice">
         <title>Using nice</title>
 
-        <para>The HPCC Systems platform supports <emphasis>nice</emphasis>-based
-        priorities using the nice Linux utility which invokes scripts and
-        programs with specified priorities. The priority assigned to a process
-        indicates to the CPU to provide more or less time than to other
-        processes. A nice value of -20 is the highest priority, and a value of
-        19 is the lowest.</para>
+        <para>The HPCC Systems platform supports
+        <emphasis>nice</emphasis>-based priorities using the nice Linux
+        utility which invokes scripts and programs with specified priorities.
+        The priority assigned to a process indicates to the CPU to provide
+        more or less time than to other processes. A nice value of -20 is the
+        highest priority, and a value of 19 is the lowest.</para>
 
         <para>The default environment.conf file is delivered with the nice
-        value disabled. If you wish to use nice to prioritize HPCC Systems processes,
-        you need to modify the environment.conf file to enable nice. You can
-        also adjust the nice value in environment.conf.</para>
+        value disabled. If you wish to use nice to prioritize HPCC Systems
+        processes, you need to modify the environment.conf file to enable
+        nice. You can also adjust the nice value in environment.conf.</para>
       </sect2>
 
       <sect2 id="SysAdm_OtherEnv.conf">
@@ -1594,8 +1606,8 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
     <sect1 id="SystemD_initScripts">
       <title>Initialization under Systemd</title>
 
-      <para>The primary tool for starting and stopping the HPCC Systems platform on a
-      target machine using systemd is the
+      <para>The primary tool for starting and stopping the HPCC Systems
+      platform on a target machine using systemd is the
       <emphasis>hpccsystems-platform.target</emphasis>. This target script is
       dependent on the environment.xml file, and gets generated using the
       <emphasis>generate-hpccsystems-target.sh</emphasis> script that is
@@ -1659,9 +1671,9 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
         <title id="SystemD_Ulimits">Systemd ulimits</title>
 
         <para>If you wish to set custom ulimits for specific hpccsystems
-        components, do so in the templates located in </para>
+        components, do so in the templates located in</para>
 
-        <para>/opt/HPCCSystems/etc/systemd/system </para>
+        <para>/opt/HPCCSystems/etc/systemd/system</para>
 
         <para>so that they persist across regenerations of the
         hpccsystems-platform.target and component service scripts. For the
@@ -1675,14 +1687,15 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
       <para>The performance of your system can vary depending on how some
       components interact. One area which could impact performance is the
       relationship with users, groups, and Active Directory. If possible,
-      having a separate Active Directory specific to HPCC Systems could be a good
-      policy. There have been a few instances where just one Active Directory
-      servicing many, diverse applications has been less than optimal.</para>
+      having a separate Active Directory specific to HPCC Systems could be a
+      good policy. There have been a few instances where just one Active
+      Directory servicing many, diverse applications has been less than
+      optimal.</para>
 
-      <para>HPCC Systems makes setting up your Active Directory OU's relatively easy.
-      ESP creates all the OU's for you when it starts up, based on the
-      settings you defined in Configuration Manager. You can then start
-      Dali/ESP and use ECLWatch to add or modify users or groups.</para>
+      <para>HPCC Systems makes setting up your Active Directory OU's
+      relatively easy. ESP creates all the OU's for you when it starts up,
+      based on the settings you defined in Configuration Manager. You can then
+      start Dali/ESP and use ECLWatch to add or modify users or groups.</para>
 
       <para>You can assign permissions to each user individually, however it
       is more manageable to assign these permissions to groups, and then add
@@ -1811,12 +1824,12 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
     <title>Best Practices</title>
 
     <para>This chapter outlines various forms of best practices established by
-    long time HPCC Systems users and administrators running HPCC Systems in a high
-    availability, demanding production environment. While it is not required
-    that you run your environment in this manner, as your specific
+    long time HPCC Systems users and administrators running HPCC Systems in a
+    high availability, demanding production environment. While it is not
+    required that you run your environment in this manner, as your specific
     requirements may vary. This section provides some best practice
-    recommendations established after several years of running HPCC Systems in a
-    demanding, intense, production environment.</para>
+    recommendations established after several years of running HPCC Systems in
+    a demanding, intense, production environment.</para>
 
     <sect1 id="BP_Cluster_Redundancy" role="nobrk">
       <title>Cluster Redundancy</title>
@@ -1940,12 +1953,12 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
     <sect1 id="BP_High_Availability">
       <title>High Availability</title>
 
-      <para>If you require high availability for your HPCC Systems platform, there are
-      some additional considerations that you should be aware of. This is not
-      comprehensive list, and it is not meant to be step-by-step instructions
-      for setting up disaster recovery. Instead this section just provides
-      some more information to consider when incorporating HPCC Systems into your
-      disaster recovery plan.</para>
+      <para>If you require high availability for your HPCC Systems platform,
+      there are some additional considerations that you should be aware of.
+      This is not comprehensive list, and it is not meant to be step-by-step
+      instructions for setting up disaster recovery. Instead this section just
+      provides some more information to consider when incorporating HPCC
+      Systems into your disaster recovery plan.</para>
 
       <sect2 id="Thor_HA">
         <title>Thor</title>
@@ -2073,10 +2086,10 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
       <para>There are several other aspects to best practice considerations,
       and these will change with your system requirements. The following
       sections are some best practice considerations for some aspects of the
-      HPCC Systems platform. Keep in mind that suggested best practices are merely
-      suggested and may not be appropriate for your needs. A thorough review
-      of the considerations highlighted here can be very helpful if your needs
-      align with the stated considerations.</para>
+      HPCC Systems platform. Keep in mind that suggested best practices are
+      merely suggested and may not be appropriate for your needs. A thorough
+      review of the considerations highlighted here can be very helpful if
+      your needs align with the stated considerations.</para>
 
       <!--/*Further elaboration of both User permissions, and permission settings... also some hardware set up best practices. Suggested***/-->
 
@@ -2253,9 +2266,9 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
             </mediaobject>
           </figure></para>
 
-        <para>Open up the HPCC Systems Configuration Manager and proceed to the
-        Advanced View option. For more information about using ConfigMgr see
-        Using Configuration Manager. <orderedlist>
+        <para>Open up the HPCC Systems Configuration Manager and proceed to
+        the Advanced View option. For more information about using ConfigMgr
+        see Using Configuration Manager. <orderedlist>
             <listitem>
               <para>Select your ESP Service (the default is the <emphasis
               role="bold">myws_ecl</emphasis>) from the Navigator panel on the
@@ -2291,8 +2304,8 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
         configured to take full advantage of the resources available per node
         using Virtual Thor slaves.</para>
 
-        <para>In HPCC Systems platform versions prior to 6.0.0, cluster configurations were
-        typically set to N number of <emphasis
+        <para>In HPCC Systems platform versions prior to 6.0.0, cluster
+        configurations were typically set to N number of <emphasis
         role="bold">slavesPerNode</emphasis><indexterm>
             <primary>slavesPerNode</primary>
           </indexterm> <emphasis></emphasis> , where N equalled or approached
@@ -2461,8 +2474,8 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
         <para>Thor, Roxie, and ECL Agent clusters all have options in the
         configuration to enable huge page support. The Transparent Huge Pages
         are enabled for Thor, Roxie, and ECL Agent clusters in the default
-        HPCC Systems environment. Thor clusters can stand to benefit more from huge
-        pages than can Roxie.</para>
+        HPCC Systems environment. Thor clusters can stand to benefit more from
+        huge pages than can Roxie.</para>
 
         <para>You can check the file
         /sys/kernel/mm/transparent_hugepage/enabled to see what your OS
@@ -2480,8 +2493,8 @@ dfsSSLPrivateKeyFile=/keyfilepath/keyfile</programlisting>Set the <emphasis
           "hugepages=N" parameter at boot. With huge pages you also need to
           explicitly allocate the size.</para>
 
-          <para>In HPCC Systems, there are three places in the configuration manager
-          to set the attributes to use Huge Pages.</para>
+          <para>In HPCC Systems, there are three places in the configuration
+          manager to set the attributes to use Huge Pages.</para>
 
           <para>There are attributes in each component, in the ECL Agent
           attributes, in Roxie attributes, and in Thor attributes. In each
@@ -2508,7 +2521,8 @@ heapUseTransparentHugePages</programlisting>
   <chapter id="Resources">
     <title>System Resources</title>
 
-    <para>There are additional resources available for the HPCC Systems System.</para>
+    <para>There are additional resources available for the HPCC Systems
+    System.</para>
 
     <sect1 id="HPCC_Resources" role="nobrk">
       <title>HPCC Systems Resources</title>
@@ -2519,11 +2533,11 @@ heapUseTransparentHugePages</programlisting>
       Systems<superscript>®</superscript> Web Portal at <ulink
       url="http://hpccsystems.com/">http://hpccsystems.com/</ulink> for
       software updates, plugins, support, documentation, and more. This is
-      where you can find resources useful for running and maintaining HPCC Systems on
-      the web portal.</para>
+      where you can find resources useful for running and maintaining HPCC
+      Systems on the web portal.</para>
 
-      <para>ECL Watch provides a link to the HPCC Systems portal's download page:
-      <ulink
+      <para>ECL Watch provides a link to the HPCC Systems portal's download
+      page: <ulink
       url="http://hpccsystems.com/download">http://hpccsystems.com/download</ulink>.
       This is the page where you can download Installation packages, virtual
       images, source code, documentation, and tutorials.</para>
@@ -2532,8 +2546,8 @@ heapUseTransparentHugePages</programlisting>
     <sect1 id="SysAdm_Addl_Resources">
       <title>Additional Resources</title>
 
-      <para>Additional help with HPCC Systems and Learning ECL is also available.
-      There are online courses available. Go to :</para>
+      <para>Additional help with HPCC Systems and Learning ECL is also
+      available. There are online courses available. Go to :</para>
 
       <para><ulink
       url="https://learn.lexisnexis.com/hpcc">https://learn.lexisnexis.com/hpcc

docs/EN_US/Installing_and_RunningTheHPCCPlatform/Installing_and_RunningTheHPCCPlatform.xml

@@ -2,10 +2,12 @@
 <!DOCTYPE book PUBLIC "-//OASIS//DTD DocBook XML V4.5//EN"
 "http://www.oasis-open.org/docbook/xml/4.5/docbookx.dtd">
 <book lang="en_US" xml:base="../">
-  <title>Installing &amp; Running the HPCC Systems<superscript>®</superscript> Platform</title>
+  <title>Installing &amp; Running the HPCC Systems<superscript>®</superscript>
+  Platform</title>
 
   <bookinfo>
-    <title>Installing &amp; Running the HPCC Systems<superscript>®</superscript> Platform</title>
+    <title>Installing &amp; Running the HPCC
+    Systems<superscript>®</superscript> Platform</title>
 
     <mediaobject>
       <imageobject>
@@ -74,8 +76,9 @@
         <ulink
         url="https://hpccsystems.com/Why-HPCC/How-it-works">https://hpccsystems.com/Why-HPCC/How-it-works</ulink>
         for more details.</para>
-      </footnote> Systems<superscript>®</superscript> Community Edition on a single node to start and then
-    optionally, expand it to a larger cluster of nodes.</para>
+      </footnote> Systems<superscript>®</superscript> Community Edition on a
+    single node to start and then optionally, expand it to a larger cluster of
+    nodes.</para>
 
     <para>The HPCC Systems Thor technology is designed to effectively process,
     analyze, and find links and associations within high volumes of complex
@@ -83,9 +86,10 @@
     petabytes of data, and is significantly faster than competing technologies
     while requiring less hardware and resources.</para>
 
-    <para>The HPCC Systems Roxie technology - also known as the Rapid Data Delivery
-    Engine or RDDE - uses a combination of technologies and techniques that
-    produce extremely fast throughput for queries on indexed data.</para>
+    <para>The HPCC Systems Roxie technology - also known as the Rapid Data
+    Delivery Engine or RDDE - uses a combination of technologies and
+    techniques that produce extremely fast throughput for queries on indexed
+    data.</para>
 
     <para>This translates into better quality answers in less time so that
     organizations can cope with massive data and efficiently turn information
@@ -162,7 +166,8 @@
           system.</para>
 
           <para>Using a browser, go to <emphasis role="bold">ECL
-          Watch</emphasis> running on port 8010 of your HPCC Systems Node.</para>
+          Watch</emphasis> running on port 8010 of your HPCC Systems
+          Node.</para>
 
           <para>For example, http://nnn.nnn.nnn.nnn:8010, where
           nnn.nnn.nnn.nnn is your node's IP address.</para>
@@ -186,8 +191,8 @@
       <sect2 id="Installing_NowWhat">
         <title>Now What?</title>
 
-        <para>Now that you have HPCC Systems started and running, what do you want to
-        do? Maybe evaluate your needs and proceed to develop a custom
+        <para>Now that you have HPCC Systems started and running, what do you
+        want to do? Maybe evaluate your needs and proceed to develop a custom
         configuration suitable for those needs. Maybe you want to expand your
         system and add nodes. Those topics and several others are covered in
         the following sections.</para>
@@ -206,8 +211,8 @@
 
             <listitem>
               <para>Read <emphasis role="bold">Using Config Manager</emphasis>
-              to learn how to configure an HPCC Systems platform using Advanced
-              View.</para>
+              to learn how to configure an HPCC Systems platform using
+              Advanced View.</para>
             </listitem>
 
             <listitem>
@@ -228,8 +233,8 @@
     system.</para>
 
     <para>Configuration Manager is the utility with which we configure the
-    HPCC Systems platform. It is run on your Linux Server and you access its interface
-    using a browser.<figure>
+    HPCC Systems platform. It is run on your Linux Server and you access its
+    interface using a browser.<figure>
         <title>System Overview: Thor</title>
 
         <mediaobject>
@@ -250,11 +255,11 @@
     <sect1 id="initial-set-up-single-node">
       <title>Initial Setup-Single Node</title>
 
-      <para>This section covers installing the HPCC Systems on a single node. This
-      will enable the HPCC Systems platform to operate successfully; however, the real
-      strength of the HPCC Systems platform is when it is run in a multi-node environment and
-      can leverage the ability to perform operations using Massively Parallel
-      Processing (MPP).</para>
+      <para>This section covers installing the HPCC Systems on a single node.
+      This will enable the HPCC Systems platform to operate successfully;
+      however, the real strength of the HPCC Systems platform is when it is
+      run in a multi-node environment and can leverage the ability to perform
+      operations using Massively Parallel Processing (MPP).</para>
 
       <para>In addition, on a production system, you would dedicate one or
       more nodes to each server process. See the <emphasis>Using Configruation
@@ -446,9 +451,9 @@ gpgcheck=0</programlisting></para>
             role="bold">L</emphasis>anguage (ECL) is a declarative, data
             centric programming language used to manage all aspects of the
             massive data joins, sorts, and builds that truly differentiate
-            HPCC Systems (High Performance Computing Cluster) from other technologies
-            in its ability to provide flexible data analysis on a massive
-            scale.</para>
+            HPCC Systems (High Performance Computing Cluster) from other
+            technologies in its ability to provide flexible data analysis on a
+            massive scale.</para>
           </footnote> code using either ECL IDE, the command line ECL
         compiler, or the ECL Command line tool.</para>
 
@@ -612,13 +617,14 @@ gpgcheck=0</programlisting></para>
           used to submit it to a target cluster for compilation by the remote
           compiler server (eclccserver).</para>
 
-          <para>To submit a job using the ECL CLI, make sure the HPCC Systems platform has been
-          started and use the following syntax: <programlisting>ecl run  hello.ecl --target=hthor --server=&lt;IP Address of the ESP node&gt;:8010</programlisting></para>
+          <para>To submit a job using the ECL CLI, make sure the HPCC Systems
+          platform has been started and use the following syntax:
+          <programlisting>ecl run  hello.ecl --target=hthor --server=&lt;IP Address of the ESP node&gt;:8010</programlisting></para>
 
           <para>The workunit<footnote>
-              <para>A Workunit is a record of a task submitted to an HPCC Systems cluster. It
-              contains an identifier--workunit ID, the ECL code, results, and
-              other information about the job.</para>
+              <para>A Workunit is a record of a task submitted to an HPCC
+              Systems cluster. It contains an identifier--workunit ID, the ECL
+              code, results, and other information about the job.</para>
             </footnote> result is returned to the command line.</para>
 
           <para>View the full details of the workunit using the ECL Watch
@@ -631,7 +637,8 @@ gpgcheck=0</programlisting></para>
           <para>Setting up an <emphasis role="bold">ecl.ini</emphasis> file
           makes running a workunit a little easier when you want to use the
           same settings every time you submit a workunit in this way. See the
-          <emphasis>HPCC Systems Client Tools </emphasis>manual for details.</para>
+          <emphasis>HPCC Systems Client Tools </emphasis>manual for
+          details.</para>
 
           <para>If your ECL is more complex than a single source file, you can
           use the eclcc compiler locally to create an archive to be sent to
@@ -716,9 +723,9 @@ gpgcheck=0</programlisting></para>
                 target cluster.</para>
 
                 <para><emphasis role="bold">Thor</emphasis> is the Data
-                Refinery component of your HPCC Systems platform. It is a disk based massively
-                parallel computer cluster, optimized for sorting,
-                manipulating, and transforming massive data.</para>
+                Refinery component of your HPCC Systems platform. It is a disk
+                based massively parallel computer cluster, optimized for
+                sorting, manipulating, and transforming massive data.</para>
 
                 <para><figure>
                     <title>Select target</title>
@@ -888,8 +895,9 @@ gpgcheck=0</programlisting></para>
           <listitem>
             <?dbfo keep-together="always"?>
 
-            <para>Enter all the IP addresses you want to use for this HPCC Systems cluster.
-            Alternatively, you could enter the hostname(s).</para>
+            <para>Enter all the IP addresses you want to use for this HPCC
+            Systems cluster. Alternatively, you could enter the
+            hostname(s).</para>
 
             <para>The IP addresses do not need to be contiguous. In the image
             below, we specified the IP addresses nn.nnn.nnn.1-125 and
@@ -1102,10 +1110,10 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
 
           <listitem>
             <para>If you have added new machines to the cluster, you need to
-            copy and install the HPCC Systems package onto all nodes, and generate and
-            clone the SSH keys. This can be done using the install-cluster.sh
-            script which is provided with HPCC Systems. Use the following
-            command:</para>
+            copy and install the HPCC Systems package onto all nodes, and
+            generate and clone the SSH keys. This can be done using the
+            install-cluster.sh script which is provided with HPCC Systems. Use
+            the following command:</para>
 
             <programlisting>/opt/HPCCSystems/sbin/install-cluster.sh -k &lt;package-file-name&gt;</programlisting>
 
@@ -1124,8 +1132,9 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
             role="bold">every</emphasis> node.</para>
 
             <para>You may want to create a script to push out the XML file to
-            all nodes. A sample script is provided with HPCC Systems. The following
-            command copies the XML files out to all nodes as required:</para>
+            all nodes. A sample script is provided with HPCC Systems. The
+            following command copies the XML files out to all nodes as
+            required:</para>
 
             <para><programlisting>sudo /opt/HPCCSystems/sbin/hpcc-push.sh -s &lt;sourcefile&gt; -t &lt;destinationfile&gt;
 </programlisting>Where the &lt;sourcefile&gt; is the absolute path to the file
@@ -1142,7 +1151,7 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
           <listitem>
             <para>Restart the HPCC Systems on <emphasis
             role="bold">every</emphasis> node. The following command starts
-             HPCC Systems on an individual node:</para>
+            HPCC Systems on an individual node:</para>
 
             <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStart.xml"
                         xpointer="element(/1)"
@@ -1163,16 +1172,16 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
 
                     <entry><para>You may want to use a script to push this
                     command out to every node. A sample script is provided
-                    with HPCC Systems. Use the following command to start HPCC Systems on all
-                    nodes:</para><para><programlisting>sudo /opt/HPCCSystems/sbin/hpcc-run.sh systemctl start hpccsystems-platform.target</programlisting></para></entry>
+                    with HPCC Systems. Use the following command to start HPCC
+                    Systems on all nodes:</para><para><programlisting>sudo /opt/HPCCSystems/sbin/hpcc-run.sh systemctl start hpccsystems-platform.target</programlisting></para></entry>
                   </row>
                 </tbody>
               </tgroup>
             </informaltable>
 
-            <para>This script can also be used to stop HPCC Systems on all nodes and
-            to start and stop individual components on all nodes. See the
-            appendix (<link linkend="Example-Scripts">Appendix:Example
+            <para>This script can also be used to stop HPCC Systems on all
+            nodes and to start and stop individual components on all nodes.
+            See the appendix (<link linkend="Example-Scripts">Appendix:Example
             Scripts</link>) for more details.</para>
           </listitem>
         </orderedlist>
@@ -1180,11 +1189,11 @@ sudo cp /etc/HPCCSystems/source/NewEnvironment.xml /etc/HPCCSystems/environment.
         <sect3 id="Addl_SSH_KeyInfo">
           <title>Additional SSH Key Information</title>
 
-          <para>On multi-node HPCC Systems, certificates and SSH keys must
-          all match across all nodes for the system to work properly. If you
-          used the <emphasis>install-cluster.sh</emphasis> script as outlined
-          in the steps above, this would make sure that everything is properly
-          in sync. However, it is still a good idea to verify that they do all
+          <para>On multi-node HPCC Systems, certificates and SSH keys must all
+          match across all nodes for the system to work properly. If you used
+          the <emphasis>install-cluster.sh</emphasis> script as outlined in
+          the steps above, this would make sure that everything is properly in
+          sync. However, it is still a good idea to verify that they do all
           match up. Another way to ensure this is to use the delivered
           <emphasis>hpcc-push.sh</emphasis> script. For example, the following
           commands would push out the certificate, key, and public key out to
@@ -1219,7 +1228,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
         <sect3 id="StartStop_ToStartSystem">
           <title>To start the system:</title>
 
-          <para>To start your HPCC Systems platform issue the following command;</para>
+          <para>To start your HPCC Systems platform issue the following
+          command;</para>
 
           <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStart.xml"
                       xpointer="element(/1)"
@@ -1232,7 +1242,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
         <sect3 id="StartStop_StopTheSystem">
           <title>To stop the system:</title>
 
-          <para>To stop your HPCC Systems platform issue the following command;</para>
+          <para>To stop your HPCC Systems platform issue the following
+          command;</para>
 
           <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
                       xpointer="element(/1)"
@@ -1289,8 +1300,9 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
 
         <orderedlist>
           <listitem>
-            <para>If the system is running, stop the HPCC Systems platform, using this
-            command on <emphasis role="bold">every</emphasis> node:</para>
+            <para>If the system is running, stop the HPCC Systems platform,
+            using this command on <emphasis role="bold">every</emphasis>
+            node:</para>
 
             <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/SysDStop.xml"
                         xpointer="element(/1)"
@@ -1340,15 +1352,15 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     <title>More Examples</title>
 
     <para>This section contains additional ECL examples you can use on your
-    HPCC Systems cluster. You can run these on a single-node system or a larger
-    multi-node cluster.</para>
+    HPCC Systems cluster. You can run these on a single-node system or a
+    larger multi-node cluster.</para>
 
     <sect1 id="IR_AnagramExamples" role="nobrk">
       <title>Anagram Examples</title>
 
-      <para>The following examples display some of things that HPCC Systems can do.
-      Running through these examples will help your understanding of HPCC Systems and
-      ECL.</para>
+      <para>The following examples display some of things that HPCC Systems
+      can do. Running through these examples will help your understanding of
+      HPCC Systems and ECL.</para>
 
       <xi:include href="Installing_and_RunningTheHPCCPlatform/Inst-Mods/anagram1.xml"
                   xpointer="xpointer(//*[@id='ECLExample_Anagram1'])"
@@ -1390,7 +1402,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     <para>To familiarize yourself with what your system can do we recommend
     following the steps in<itemizedlist spacing="compact">
         <listitem>
-          <para>The <emphasis role="bold">HPCC Systems Data Tutorial</emphasis></para>
+          <para>The <emphasis role="bold">HPCC Systems Data
+          Tutorial</emphasis></para>
         </listitem>
 
         <listitem>
@@ -1400,7 +1413,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
 
         <listitem>
           <para>Read <emphasis role="bold">Using Config Manager</emphasis> to
-          learn how to configure an HPCC Systems platform using Advanced View.</para>
+          learn how to configure an HPCC Systems platform using Advanced
+          View.</para>
         </listitem>
 
         <listitem>
@@ -1488,7 +1502,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
                 <row>
                   <entry>&lt;package-name&gt;</entry>
 
-                  <entry>Name of the HPCC Systems package to install. Required</entry>
+                  <entry>Name of the HPCC Systems package to install.
+                  Required</entry>
                 </row>
 
                 <row>
@@ -1568,26 +1583,27 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
         <para><?hard-pagebreak ?><emphasis
         role="bold">Examples:</emphasis></para>
 
-        <para>This example installs the HPCC Systems platform packages to remaining
-        nodes and pushes out the active environment.xml file to those
-        nodes.:</para>
+        <para>This example installs the HPCC Systems platform packages to
+        remaining nodes and pushes out the active environment.xml file to
+        those nodes.:</para>
 
         <para><programlisting>sudo /opt/HPCCSystems/sbin/install-cluster.sh hpccsystems-platform-xxxx-<emphasis>n.n.nnnn</emphasis> 
 </programlisting></para>
 
         <para>(where <emphasis>n.n.nnnn</emphasis> is the build number)</para>
 
-        <para>This example installs the HPCC Systems platform packages to all nodes
-        and pushes out the active environment.xml file to those nodes. It also
-        generates ssh keys and pushes them out to all nodes.</para>
+        <para>This example installs the HPCC Systems platform packages to all
+        nodes and pushes out the active environment.xml file to those nodes.
+        It also generates ssh keys and pushes them out to all nodes.</para>
 
         <para><programlisting>sudo /opt/HPCCSystems/sbin/install-cluster.sh -k hpccsystems-platform-xxxx-<emphasis>n.n.nnnn</emphasis> 
 </programlisting></para>
 
         <para>(where <emphasis>n.n.nnnn</emphasis> is the build number)</para>
 
-        <para>This example installs the HPCC Systems platform packages and pushes out
-        the active environment.xml file to 8 concurrent nodes.:</para>
+        <para>This example installs the HPCC Systems platform packages and
+        pushes out the active environment.xml file to 8 concurrent
+        nodes.:</para>
 
         <para><programlisting>sudo /opt/HPCCSystems/sbin/install-cluster.sh -n 8 hpccsystems-platform-xxxx-<emphasis>n.n.nnnn</emphasis> 
 </programlisting></para>
@@ -1688,8 +1704,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
           </informaltable></para>
 
         <para>The <emphasis role="bold">deploy-java-files.sh</emphasis>
-        script, is used to deploy java files (source) to HPCC Systems cluster hosts
-        and update the classpath variable in environment.conf.</para>
+        script, is used to deploy java files (source) to HPCC Systems cluster
+        hosts and update the classpath variable in environment.conf.</para>
 
         <para>This script runs a command on all IP addresses or host names in
         the active environment.xml. The IP addresses are defined when editing
@@ -1802,8 +1818,8 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
                 <row>
                   <entry>-c, --comp</entry>
 
-                  <entry>HPCC Systems component. For example, dali@mydali.service,
-                  roxie@myroxie.service, etc.</entry>
+                  <entry>HPCC Systems component. For example,
+                  dali@mydali.service, roxie@myroxie.service, etc.</entry>
                 </row>
 
                 <row>
@@ -1867,9 +1883,9 @@ sudo /opt/HPCCSystems/sbin/hpcc-push.sh \
     <sect1 id="Uninstalling-the-HPCC">
       <title>Uninstalling the HPCC Systems Platform</title>
 
-      <para>To uninstall the HPCC Systems platform, issue the appropriate commands for
-      your system. If necessary, do so on each node that it is installed
-      on.</para>
+      <para>To uninstall the HPCC Systems platform, issue the appropriate
+      commands for your system. If necessary, do so on each node that it is
+      installed on.</para>
 
       <para><emphasis role="bold">Centos/Red Hat</emphasis></para>
 
@@ -1915,8 +1931,8 @@ init_start_thor--></property></para>
       <title>hpcc-init</title>
 
       <para>CentOS 6 and other System V based operating systems do not support
-      the systemd calls utilized by HPCC Systems. We will continue to
-      support the old System V style init.d calls.</para>
+      the systemd calls utilized by HPCC Systems. We will continue to support
+      the old System V style init.d calls.</para>
 
       <para><emphasis role="bold">hpcc-init
       </emphasis><emphasis><emphasis>[</emphasis>option<emphasis>]</emphasis>
@@ -2040,10 +2056,10 @@ sudo /etc/init.d/hpcc-init -c esp start
         system service will support "start", "stop" and "restart"
         options.</para>
 
-        <para>The reporting and logging for HPCC Systems systemd will differ from the
-        previous hpcc-init type. The systemd logs do not have any output to
-        STDOUT/STDERROR, instead it logs to /var/log/syslog. To view the
-        output:</para>
+        <para>The reporting and logging for HPCC Systems systemd will differ
+        from the previous hpcc-init type. The systemd logs do not have any
+        output to STDOUT/STDERROR, instead it logs to /var/log/syslog. To view
+        the output:</para>
 
         <programlisting>journalctl -u &lt;service&gt; -f  </programlisting>
 
@@ -2060,15 +2076,15 @@ sudo /etc/init.d/hpcc-init -c esp start
 
         <programlisting>/etc/init.d/hpcc-init status</programlisting>
 
-        <para>HPCC Systems services started through systemd will be listed as active
-        in systemd. They can be listed as "sudo systemctl list-units
+        <para>HPCC Systems services started through systemd will be listed as
+        active in systemd. They can be listed as "sudo systemctl list-units
         [PATTERN...]". To remove them from the systemd active service list,
         you must run the stop service from the "service" or "systemctl"
         commands (as shown above) even though it is already stopped by
         directly calling /etc/init.d/&lt;hpcc-init|dafilesrv&gt; stop.</para>
 
-        <para>HPCC Systems uninstall will automatically remove HPCC Systems services from
-        active list and /etc/systemd/system/ directory.</para>
+        <para>HPCC Systems uninstall will automatically remove HPCC Systems
+        services from active list and /etc/systemd/system/ directory.</para>
       </sect2>
     </sect1>
 
@@ -2129,8 +2145,8 @@ sudo /etc/init.d/hpcc-init -c esp start
         </listitem>
 
         <listitem>
-          <para>Install the HPCC Systems ECL IDE (Double-click the installation file and
-          Wine will install it).</para>
+          <para>Install the HPCC Systems ECL IDE (Double-click the
+          installation file and Wine will install it).</para>
         </listitem>
       </orderedlist>
     </sect1>
@@ -2139,11 +2155,11 @@ sudo /etc/init.d/hpcc-init -c esp start
       <title>External Language Support</title>
 
       <para>This section covers the steps to add external language support to
-      the HPCC Systems platform. HPCC Systems offers support for several programming
-      languages, some have additional dependencies that must be installed.
-      External language support is included with the platform installation
-      package, however there are RPM-based HPCC Systems platform installation packages
-      that explicitly state <emphasis role="bold">with
+      the HPCC Systems platform. HPCC Systems offers support for several
+      programming languages, some have additional dependencies that must be
+      installed. External language support is included with the platform
+      installation package, however there are RPM-based HPCC Systems platform
+      installation packages that explicitly state <emphasis role="bold">with
       plugins</emphasis>.</para>
 
       <para><emphasis role="bold">RPM-based systems:</emphasis></para>
@@ -2203,15 +2219,16 @@ sudo /etc/init.d/hpcc-init -c esp start
       <sect2 id="Add_On_Java" role="brk">
         <title>Java</title>
 
-        <para>You can run external Java code on the HPCC Systems platform. Compiled
-        Java can be used either as a .class (or a .jar) and called from ECL
-        just like any other ECL function.</para>
+        <para>You can run external Java code on the HPCC Systems platform.
+        Compiled Java can be used either as a .class (or a .jar) and called
+        from ECL just like any other ECL function.</para>
 
         <para>To extract the JNI signatures:</para>
 
         <programlisting>javap -s</programlisting>
 
-        <para>To set up Java to integrate with the HPCC Systems platform:</para>
+        <para>To set up Java to integrate with the HPCC Systems
+        platform:</para>
 
         <orderedlist>
           <listitem>
@@ -2238,8 +2255,8 @@ sudo /etc/init.d/hpcc-init -c esp start
                 <listitem>
                   <para>using classpath value in environment.conf</para>
 
-                  <para>The default configuration file for the HPCC Systems platform
-                  is <emphasis
+                  <para>The default configuration file for the HPCC Systems
+                  platform is <emphasis
                   role="bold">/etc/HPCCSystems/environment.conf</emphasis> you
                   will need to edit this file to point to your Java build
                   directory.</para>
@@ -2267,8 +2284,8 @@ sudo /etc/init.d/hpcc-init -c esp start
 
             <para>For more information see the <link
             linkend="Starting-and-stopping">Starting-and-stopping</link> the
-            HPCC Systems platform in the <emphasis>Installing and Running The HPCC Systems
-            Platform</emphasis> document.</para>
+            HPCC Systems platform in the <emphasis>Installing and Running The
+            HPCC Systems Platform</emphasis> document.</para>
           </listitem>
 
           <listitem>
@@ -2298,7 +2315,8 @@ add1(10);
         <para>You can call Java from ECL just like any other ECL function.
         Java static functions can be easily prototyped using ECL types.</para>
 
-        <para>Additional examples of Java for HPCC Systems can be found at:</para>
+        <para>Additional examples of Java for HPCC Systems can be found
+        at:</para>
 
         <para><ulink
         url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl</ulink></para>
@@ -2361,7 +2379,8 @@ add1(10);
 </programlisting>If this successfully executes, you have correctly set up
             JavaScript to work with your HPCC Systems platform.</para>
 
-            <para>Additional examples of HPCC Systems code can be found at:</para>
+            <para>Additional examples of HPCC Systems code can be found
+            at:</para>
 
             <para><ulink
             url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/embedjava.ecl</ulink></para>
@@ -2372,15 +2391,16 @@ add1(10);
       <sect2 id="Add_Python_support" role="brk">
         <title>Python</title>
 
-        <para>HPCC Systems supports Python2 by default. The HPCC Systems platform includes
-        plugins for both Python2 and Python3, but only one may be safely
-        enabled at a time as the Python libraries export the same symbols for
-        both versions. Enabling both may lead to unpredictable results
-        including segmentation faults or undefined symbol errors.</para>
+        <para>HPCC Systems supports Python3 by default. The HPCC Systems
+        platform includes plugins for both Python2 and Python3, but only one
+        may be safely enabled at a time as the Python libraries export the
+        same symbols for both versions. Enabling both may lead to
+        unpredictable results including segmentation faults or undefined
+        symbol errors.</para>
 
-        <para>By default the Python3 plugin will be present but disabled, and
-        the Python2 plugin will be present and enabled. If you want to use
-        Python3 modify the your environment.conf file according to the example
+        <para>By default the Python2 plugin will be present but disabled, and
+        the Python3 plugin will be present and enabled. If you want to use
+        Python2 modify the your environment.conf file according to the example
         in the file. A cluster updated from an older version may not have the
         appropriate entries in the environment.conf file to support either
         version of Python.</para>
@@ -2430,10 +2450,12 @@ ENDEMBED;
 split_words('Once upon a time');
 
 </programlisting>If this successfully executes, you have correctly set up
-            Python to work with your HPCC Systems platform. You can now embed Python
-            anywhere you would use ECL within with your HPCC Systems platform.</para>
+            Python to work with your HPCC Systems platform. You can now embed
+            Python anywhere you would use ECL within with your HPCC Systems
+            platform.</para>
 
-            <para>Additional examples of HPCC Systems code can be found at:</para>
+            <para>Additional examples of HPCC Systems code can be found
+            at:</para>
 
             <para><ulink
             url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl/</ulink></para>
@@ -2484,8 +2506,9 @@ split_words('Once upon a time');
       <sect2 id="R" role="brk">
         <title>R</title>
 
-        <para>The HPCC Systems platform supports embedded R code. To enable R support
-        within The HPCC Systems<superscript>®</superscript> Platform:</para>
+        <para>The HPCC Systems platform supports embedded R code. To enable R
+        support within The HPCC Systems<superscript>®</superscript>
+        Platform:</para>
 
         <orderedlist>
           <listitem>
@@ -2632,7 +2655,8 @@ SUM(NOFOLD(s1b + s2b), a);
 </programlisting>If this successfully executes, you have correctly set up R to
             work with your HPCC Systems platform.</para>
 
-            <para>Additional examples of HPCC Systems code can be found at:</para>
+            <para>Additional examples of HPCC Systems code can be found
+            at:</para>
 
             <para><ulink
             url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/regress/embedR.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl/embedR.ecl</ulink></para>
@@ -2647,8 +2671,9 @@ SUM(NOFOLD(s1b + s2b), a);
           <para>Some additional considerations for mapping data types in
           R.</para>
 
-          <para>In HPCC Systems the ECL <emphasis role="bold">RECORD</emphasis> maps
-          to an R <emphasis>list</emphasis>.</para>
+          <para>In HPCC Systems the ECL <emphasis
+          role="bold">RECORD</emphasis> maps to an R
+          <emphasis>list</emphasis>.</para>
 
           <para>An ECL <emphasis role="bold">DATASET</emphasis> including a
           nested dataset is mapped to an R
@@ -2657,9 +2682,9 @@ SUM(NOFOLD(s1b + s2b), a);
           <para>An ECL <emphasis role="bold">SET</emphasis> is mapped to an R
           <emphasis>vector</emphasis>.</para>
 
-          <para>These principals apply to passing data from HPCC Systems to R or data
-          returning to HPCC Systems from R. There are usage examples of these concepts
-          available at:</para>
+          <para>These principals apply to passing data from HPCC Systems to R
+          or data returning to HPCC Systems from R. There are usage examples
+          of these concepts available at:</para>
 
           <para><ulink
           url="https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/ecl/regress/embedR2.ecl">https://github.com/hpcc-systems/HPCC-Platform/tree/master/testing/regress/ecl/embedR2.ecl</ulink></para>

esp/src/eclwatch/nls/bs/hpcc.js

@@ -55,6 +55,8 @@
     Attach: "Prikačite",
     Attribute: "Atribut",
     AttributesAreRequired: "Atributi su potrebni",
+    Audience: "Publika",
+    AuditLogs: "Dnevnik Za Pregled",
     AutoRefresh: "Osvježi",
     AutoRefreshEvery: "Automatsko osvježivanje svakih x minuta",
     AutoRefreshIncrement: "Automatski korak osvježivanja",
@@ -101,6 +103,7 @@
     Completed: "Kompletiran",
     ComplexityWarning: "Više od praga {threshold} aktivnosti ({activityCount}) - zaustavite prikaz podataka?",
     Component: "Komponenta",
+    ComponentLogs: "Dnevnik Komponenti",
     Compress: "Sabijte",
     Compressed: "Komprimirani",
     CompressedFileSize: "Komprimirana Veličina Datoteke",
@@ -117,8 +120,10 @@
     ContinueWorking: "Nastavite sa radom",
     Copied: "Kopirano!",
     Copy: "Kopirajte",
-    CopyToClipboard: "Kopirajte u clipboard",
+    CopyToClipboard: "Kopirajte u klipboard",
+    CopyURLToClipboard: "Kopirajte URL u klipbord",
     CopyWUIDs: "Kopiraj WUID-ove u klipbord",
+    CopyWUIDToClipboard: "Kopirajte WUID u klipbord",
     Count: "Izbrojte",
     CPULoad: "Učitavanje procesora",
     Create: "Kreirajte",
@@ -232,6 +237,7 @@
     ErrorUploadingFile: "Greška prilikom prenosa datoteke(a). Pokušajte provjeriti dozvole za prenos.",
     ErrorWarnings: "Greška/Upozorenja",
     Escape: "Eskejp",
+    ESPBindings: "ESP Veze",
     ESPBuildVersion: "ESP Trenutna Verzija",
     ESPNetworkAddress: "ESP Netvork Adresa",
 	ESPProcessName: "Ime ESP procesa",
@@ -320,6 +326,7 @@
     Index: "Indeks",
     Info: "Informacija",
     InfoDialog: "Dijalog Informacije",
+    Informational: "Informativan",
     InheritedPermissions: "Naslijeđene Dozvole",
     Inputs: "Unosi",
     InUse: "U upotrebi",
@@ -405,12 +412,13 @@
     Mappings: "Mapiranja",
     Mask: "Maska",
     Max: "Maksimum",
+    MaximizeRestore: "Maksimiziraj/Povrati prethodno stanje",
     MaximumNumberOfSlaves: "Maksimalan Broj Izvršilaca",
     MaxNode: "Maksimalni Nod/čvor",
     MaxRecordLength: "Maksimalna Dužina Rekorda",
     MaxSize: "Maksimalna Veličina",
     MaxSkew: "Maksimalni Skju (Distorzija)",
-    MaximizeRestore: "Maksimiziraj/Povrati prethodno stanje",
+    MaxSkewPart: "Maksimalan Skju Dio",
     Mean: "Srednja Vrijednost",
     MemberOf: "Član Od",
     Members: "Članovi",
@@ -423,6 +431,7 @@
     Minor: "Minoran",
     MinSize: "Minimalna Veličina",
 	MinSkew: "Minimalni Skju (Distorzija)",
+    MinSkewPart: "Minimalan Skju Dio",
     Missing: "Nedostaje",
     MixedNodeStates: "Svi Nodovi Nemaju Isti Status",
     Modification: "Promijena",
@@ -558,6 +567,7 @@
     Property: "Svojstvo",
     Protect: "Zaštitite",
     Protected: "Zašticen",
+    Protocol: "Protokol",
     Publish: "Objavite",
     Published: "Objavljen",
     PublishedBy: "Objavljivač",
@@ -629,6 +639,7 @@
     Restart: "Ponovo Pokrenite",
     Restarted: "Ponovo Pokternut",
     Restore: "Vratite na Staro Stanje",
+    Restricted: "Ograničen",
     Resubmit: "Ponovo Podnesite",
     Resubmitted: "Ponovo Poslat",
     ResubmitTooltip: "Reaktivirajte ovu radnu jedinicu",
@@ -658,10 +669,12 @@
     Server: "Server",
 	ServiceName: "Ime Servisa",
     Services: "Servisi",
+    ServiceType: "Vrsta usluge",
     SetBanner: "Postavite Zastavicu",
     SetTextError: "Neuspješno prikazivanje teksta (da li je tekst predug?). Koristite ‘pomagače’ za preuzimanje datoteka.",
     SetToFailed: "Postavite Na Neuspješan",
     Severity: "Ozbiljnost",
+    ShareWorkunit: "Podijeli Workunit URL",
     Show: "Pokažite",
     ShowProcessesUsingFilter: "Prikažite procese koristeći filter",
     ShowSVG: "Pokažite SVG",
@@ -805,6 +818,8 @@
     title_Results: "Rezultati",
     title_SearchResults: "Rezultati Pretraživanja",
     title_SourceFiles: "Originalni Fajlovi",
+    title_SystemServers: "Sistemski serveri",
+    title_SystemServersLegacy: "Sistemski serveri (legat)",
     title_TargetClusters: "Ciljni Klasteri",
     title_Topology: "Topologija",
     title_TpThorStatus: "Stanje Thora",

esp/src/eclwatch/nls/hr/hpcc.js

@@ -55,6 +55,8 @@
     Attach: "Prikačite",
     Attribute: "Atribut",
     AttributesAreRequired: "Atributi su potrebni",
+    Audience: "Publika",
+    AuditLogs: "Dnevnik Za Pregled",
     AutoRefresh: "Osvježi",
     AutoRefreshEvery: "Automatsko osvježivanje svakih x minuta",
     AutoRefreshIncrement: "Automatski korak osvježivanja",
@@ -101,6 +103,7 @@
     Completed: "Kompletiran",
     ComplexityWarning: "Više od praga {threshold} aktivnosti ({activityCount}) - prekinite prikaz podataka?",
     Component: "Komponenta",
+    ComponentLogs: "Dnevnik Komponenti",
     Compress: "Sabijte",
     Compressed: "Komprimirani",
     CompressedFileSize: "Komprimirana Veličina Datoteke",
@@ -118,7 +121,9 @@
     Copied: "Kopirano!",
     Copy: "Kopirajte",
     CopyToClipboard: "Kopirajte u međuspremnik",
+    CopyURLToClipboard: "Kopirajte URL u međuspremnik",
     CopyWUIDs: "Kopiraj WUID-ove u međuspremnik",
+    CopyWUIDToClipboard: "Kopirajte WUID u međuspremnik",
     Count: "Izbrojte",
     CPULoad: "Učitavanje CPU-a",
     Create: "Izradite",
@@ -232,6 +237,7 @@
     ErrorUploadingFile: "Pogreška prilikom prenosa datoteke(a). Pokušajte provjeriti dozvole za prenos.",
     ErrorWarnings: "Greška/Upozorenja",
     Escape: "Eskejp",
+    ESPBindings: "ESP Veze",
     ESPBuildVersion: "ESP Trenutna Verzija",
     ESPNetworkAddress: "ESP Netvork Adresa",
     ESPProcessName: "Naziv ESP procesa",
@@ -320,6 +326,7 @@
     Index: "Indeks",
     Info: "Informacija",
     InfoDialog: "Dijalog Informacije",
+    Informational: "Informativan",
     InheritedPermissions: "Naslijeđene Dozvole",
     Inputs: "Unosi",
     InUse: "U uporabi",
@@ -411,6 +418,7 @@
     MaxRecordLength: "Maksimalna Dužina Rekorda",
     MaxSize: "Maksimalna Veličina",
     MaxSkew: "Maksimalni Skju (Distorzija)",
+    MaxSkewPart: "Maksimalan Skju Dio",
     Mean: "Srednja Vrijednost",
     MemberOf: "Član Od",
     Members: "Članovi",
@@ -423,6 +431,7 @@
     Minor: "Minoran",
     MinSize: "Minimalna Veličina",
     MinSkew: "Minimalni Skju (Distorzija)",
+    MinSkewPart: "Minimalan Skju Dio",
     Missing: "Nedostaje",
     MixedNodeStates: "Svi Nodovi Nemaju Isti Status",
     Modification: "Promijena",
@@ -558,6 +567,7 @@
     Property: "Svojstvo",
     Protect: "Zaštitite",
     Protected: "Zašticen",
+    Protocol: "Protokol",
     Publish: "Objavite",
     Published: "Objavljen",
     PublishedBy: "Objavljivač",
@@ -629,6 +639,7 @@
     Restart: "Ponovo Pokrenite",
     Restarted: "Ponovo Pokternut",
     Restore: "Vratite na Staro Stanje",
+    Restricted: "Ograničen",
     Resubmit: "Ponovo Podnesite",
     Resubmitted: "Ponovo Poslat",
     ResubmitTooltip: "Reaktivirajte ovu radnu jedinicu",
@@ -658,10 +669,12 @@
     Server: "Server",
     ServiceName: "Ime Servisa",
     Services: "Servisi",
+    ServiceType: "Vrsta usluge",
     SetBanner: "Postavite Zastavicu",
     SetTextError: "Neuspješno prikazivanje teksta (da li je tekst predug?). Koristite ‘pomagače’ za preuzimanje datoteka.",
     SetToFailed: "Postavite Na Neuspješan",
     Severity: "Ozbiljnost",
+    ShareWorkunit: "Podijeli Workunit URL",
     Show: "Pokažite",
     ShowProcessesUsingFilter: "Prikažite procese koristeći filter",
     ShowSVG: "Pokažite SVG",
@@ -805,6 +818,8 @@
     title_Results: "Rezultati",
     title_SearchResults: "Rezultati Pretraživanja",
     title_SourceFiles: "Originalni Fajlovi",
+    title_SystemServers: "Sistemski serveri",
+    title_SystemServersLegacy: "Sistemski serveri (legat)",
     title_TargetClusters: "Ciljni Klasteri",
     title_Topology: "Topologija",
     title_TpThorStatus: "Stanje Thora",

esp/src/eclwatch/nls/pt-br/hpcc.js

@@ -55,6 +55,8 @@
     Attach: "Anexar",
     Attribute: "Attributo",
     AttributesAreRequired: "Atributos são necessários",
+    Audience: "Público",
+    AuditLogs: "Registro de auditoria",
     AutoRefresh: "Recarregar Automático",
     AutoRefreshEvery: "Atualização automática a cada x minutos",
     AutoRefreshIncrement: "Auto Incrementar Atualização",
@@ -101,6 +103,7 @@
     Completed: "Completo",
     ComplexityWarning: "Mais de {limite} atividades ({Contador de atividades}) - suprimir amostragem inicial?",
     Component: "Componente",
+    ComponentLogs: "Log de componentes",
     Compress: "Compactar",
     Compressed: "Comprimido",
     CompressedFileSize: "Tamanho do Arquivo Comprimido",
@@ -118,7 +121,9 @@
     Copied: "Copiado!",
     Copy: "Copiar",
     CopyToClipboard: "Copiar para área de transferência",
+    CopyURLToClipboard: "Copiar URL para a área de transferência",
     CopyWUIDs: "Copiar WUIDs para a área de transferência",
+    CopyWUIDToClipboard: "Copiar WUID para a área de transferência",
     Count: "Conta",
     CPULoad: "Carga do CPU ",
     Create: "Criar",
@@ -232,6 +237,7 @@
     ErrorUploadingFile: "Erro ao carregar arquivos. Tente verificar permissões.",
     ErrorWarnings: "Error/Aviso(s)",
     Escape: "Escapar",
+    ESPBindings: "Ligações ESP",
     ESPBuildVersion: "Versão‎ do ESP",  // jshint ignore:line
     ESPNetworkAddress: "Endereço de Rede do ESP",
     ESPProcessName: "Nome do Processo ESP",
@@ -321,6 +327,7 @@
     Index: "Índice",
     Info: "Info",
     InfoDialog: "Caixa de Informação",
+    Informational: "Informativo",
     InheritedPermissions: "Permissão Herdada",
     Inputs: "Insumos",
     InUse: "Em uso",
@@ -412,6 +419,7 @@
     MaxRecordLength: "Maximo tamanho do registro",
     MaxSize: "Tamanho máximo",
     MaxSkew: "Viás Max",
+    MaxSkewPart: "Pedaço Viás Max",
     Mean: "Média",
     MemberOf: "Membro de",
     Members: "Membros",
@@ -424,6 +432,7 @@
     Minor: "Menor",
     MinSize: "Tamanho mínimo",
     MinSkew: "Viás Min",
+    MinSkewPart: "Pedaço Viás Min",
     Missing: "Não encontrado",
     MixedNodeStates: "Estados de Nós misturados",
     Modification: "Modificação",
@@ -559,6 +568,7 @@
     Property: "Propriedade",
     Protect: "Proteger",
     Protected: "Protegido",
+    Protocol: "Protocolo",
     Publish: "Publicado",
     Published: "Publicado",
     PublishedBy: "Publicado por",
@@ -630,6 +640,7 @@
     Restart: "Reiniciar",
     Restarted: "Recomeçar",
     Restore: "Restaurar",
+    Restricted: "Restrito",
     Resubmit: "Resubmeter",
     Resubmitted: "Submeter de novo",
     ResubmitTooltip: "Submeter unidade de trabalho de novo",
@@ -659,10 +670,12 @@
     Server: "Servidor",
     ServiceName: "Nome do Serviço",
     Services: "Serviços",
+    ServiceType: "Tipo de serviço",
     SetBanner: "Fixar Banner",
     SetTextError: "Erro para mostrar texto(muito longo?)  Use ‘ajuda’ para baixar",
     SetToFailed: "Indicar como Falhado",
     Severity: "Severidade",
+    ShareWorkunit: "Compartilhar URL do Workunit",
     Show: "Exibir",
     ShowProcessesUsingFilter: "Mostrar processos usando filtro",
     ShowSVG: "Mostrar SVG",
@@ -808,6 +821,8 @@
     title_Results: "Atividade",
     title_SearchResults: "Resultados de busca",
     title_SourceFiles: "Arquivo(s) da Fonte",
+    title_SystemServers: "Servidores do sistema",
+    title_SystemServersLegacy: "Servidores do sistema (herdados)",
     title_TargetClusters: "Clusters de Alvo",
     title_Topology: "Topologia",
     title_TpThorStatus: "Estado de Thor",

esp/src/eclwatch/nls/sr/hpcc.js

@@ -55,6 +55,8 @@
     Attach: "Причврстите",
     Attribute: "Атрибут",
     AttributesAreRequired: "Атрибути су потребни",
+    Audience: "Публика",
+    AuditLogs: "Дневник за ревизију",
     AutoRefresh: "Освежи",
     AutoRefreshEvery: "Аутоматско освеживање сваких к минута",
     AutoRefreshIncrement: "Аутоматски корак освежавања",
@@ -102,6 +104,7 @@
     Completed: "Комплетиран",
     ComplexityWarning: "Више од прага {threshold} активности ({activityCount}) - прекините приказ података?",
     Component: "Компонента",
+    ComponentLogs: "Дневник компонената",
     Compress: "Сабијте",
     Compressed: "Компримирани",
     CompressedFileSize: "Компримирана Величина Датотеке",
@@ -119,7 +122,9 @@
     Copied: "Копирано!",
     Copy: "Копирајте",
     CopyToClipboard: "Копирај у клипборд",
+    CopyURLToClipboard: "Копирај УРЛ у клипборд",
     CopyWUIDs: "Копирај ВУИД-ове у клипборд",
+    CopyWUIDToClipboard: "Копирај ВУИД у клипборд",
     Count: "Избројте",
     CPULoad: "Учитавање процесора",
     Create: "Креирај",
@@ -233,6 +238,7 @@
     ErrorUploadingFile: "Грешка приликом преноса фајла(а). Покушајте провјерити дозволе за пренос",
     ErrorWarnings: "Грешка/Упозорења",
     Escape: "Ескејп",
+    ESPBindings: "ЕСП везе",
     ESPBuildVersion: "ЕСП Тренутна Верзија",
     ESPNetworkAddress: "ЕСП Нетворк Адреса",
     ESPProcessName: "Назив ЕСП процеса",
@@ -321,6 +327,7 @@
     Index: "Индекс",
     Info: "Информација",
     InfoDialog: "Диалог Информације",
+    Informational: "Информативно",
     InheritedPermissions: "Наслеђене Дозволе",
     Inputs: "Уноси",
     InUse: "У употреби",
@@ -412,6 +419,7 @@
     MaxRecordLength: "Максимална Дужина Рекорда",
     MaxSize: "Максимална величина",
     MaxSkew: "Максимално изобличење",
+    MaxSkewPart: "Максимални Ску Дио",
     Mean: "средња вредност",
     MemberOf: "Члан Од",
     Members: "Чланови",
@@ -424,6 +432,7 @@
     Minor: "Миноран",
     MinSize: "Минимална Величина",
     MinSkew: "Минимално изобличење",
+    MinSkewPart: "Минимални Ску Дио",
     Missing: "Недостаје",
     MixedNodeStates: "Сви Нодови Немају Исти Статус",
     Modification: "Промена",
@@ -559,6 +568,7 @@
     Property: "Својствo",
     Protect: "Заштитите",
     Protected: "Заштићен",
+    Protocol: "Протокол",
     Publish: "Објавите",
     Published: "Објављен",
     PublishedBy: "Објављивач",
@@ -630,6 +640,7 @@
     Restart: "Поново Покрените",
     Restarted: "Поново Поктернут",
     Restore: "Вратите на Старо Стање",
+    Restricted: "Ограничен",
     Resubmit: "Поново Поднесите",
     Resubmitted: "Поново Послат",
     ResubmitTooltip: "Реактивирајте ову радну јединицу",
@@ -659,10 +670,12 @@
     Server: "Сервер",
     ServiceName: "Име Сервисa",
     Services: "Сервиси",
+    ServiceType: "Врста услуге",
     SetBanner: "Поставите Заставицу",
     SetTextError: "Неуспешно приказивање текста (да ли је текст предуг?). Користите ‘помагаче’ за преузимање датотека.",
     SetToFailed: "Поставите На Неуспешан",
     Severity: "Озбиљност",
+    ShareWorkunit: "Дели Воркунит УРЛ",
     Show: "Прокажите",
     ShowProcessesUsingFilter: "Прикажи процесе користећи филтер",
     ShowSVG: "Прокажите СВГ",
@@ -806,6 +819,8 @@
     title_Results: "Резултати",
     title_SearchResults: "Резултати Претраживања",
     title_SourceFiles: "Оригиналне Датотеке",
+    title_SystemServers: "Системски сервери",
+    title_SystemServersLegacy: "Системски сервери (стари)",
     title_TargetClusters: "Циљни кластери",
     title_Topology: "Топологија",
     title_TpThorStatus: "Стање Тора",