You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@manifoldcf.apache.org by kw...@apache.org on 2020/02/02 11:55:39 UTC

svn commit: r1873502 - in /manifoldcf/trunk/site/src/documentation/content/xdocs: en_US/how-to-build-and-deploy.xml ja_JP/how-to-build-and-deploy.xml zh_CN/how-to-build-and-deploy.xml

Author: kwright
Date: Sun Feb  2 11:55:39 2020
New Revision: 1873502

URL: http://svn.apache.org/viewvc?rev=1873502&view=rev
Log:
Update documentation to describe kerberos enabling

Modified:
    manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml
    manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml
    manifoldcf/trunk/site/src/documentation/content/xdocs/zh_CN/how-to-build-and-deploy.xml

Modified: manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml
URL: http://svn.apache.org/viewvc/manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml?rev=1873502&r1=1873501&r2=1873502&view=diff
==============================================================================
--- manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml (original)
+++ manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml Sun Feb  2 11:55:39 2020
@@ -551,7 +551,14 @@ mvn clean package
           <li>Simplified multi-process model</li>
           <li>Command-driven multi-process model</li>
         </ul>
-        <p>Each way has advantages and disadvantages.  For example, single-process models limit the flexibility of deploying ManifoldCF components.  Multi-process models require that
+        <p>All examples have similar script structure and construction.  For example, there are always options files you can modify to control the behavior of individual processes.  These
+          files have names of the form: <em>*-options.env.win</em> and <em>*-options.env.unix</em>.  They contain a list of switches to be used in starting up the JVM.  These
+          switches also include memory specification (the <em>-Xmx</em> switch), as well as a predefined <em>-D</em> switch that is meant to enable Kerberos (for the connectors
+          it is implemented for).  In general, for <em>-D</em> switches in options files, you will want to change them for all options files in the example deployment you are using, to
+          insure that all processes operate in the same environment.  For example, to enable Kerberos, you must change the options files in the following way: the <em>-Djava.security.auth.login.config=</em>
+          line should be changed to <em>-Djava.security.auth.login.config=jaas-client.conf</em>, and the <em>jaas-client.conf</em> file filled out properly for your installation.</p>
+        <p>
+        <p>Each example deployment has advantages and disadvantages.  For example, single-process models limit the flexibility of deploying ManifoldCF components.  Multi-process models require that
           inter-process synchronization be properly configured.  If you are just starting out with ManifoldCF, we suggest you try the quick-start single process model first, since that is
           the easiest.</p>
         <section>

Modified: manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml
URL: http://svn.apache.org/viewvc/manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml?rev=1873502&r1=1873501&r2=1873502&view=diff
==============================================================================
--- manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml (original)
+++ manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml Sun Feb  2 11:55:39 2020
@@ -551,7 +551,14 @@ mvn clean package
           <li>Simplified multi-process model</li>
           <li>Command-driven multi-process model</li>
         </ul>
-        <p>Each way has advantages and disadvantages.  For example, single-process models limit the flexibility of deploying ManifoldCF components.  Multi-process models require that
+        <p>All examples have similar script structure and construction.  For example, there are always options files you can modify to control the behavior of individual processes.  These
+          files have names of the form: <em>*-options.env.win</em> and <em>*-options.env.unix</em>.  They contain a list of switches to be used in starting up the JVM.  These
+          switches also include memory specification (the <em>-Xmx</em> switch), as well as a predefined <em>-D</em> switch that is meant to enable Kerberos (for the connectors
+          it is implemented for).  In general, for <em>-D</em> switches in options files, you will want to change them for all options files in the example deployment you are using, to
+          insure that all processes operate in the same environment.  For example, to enable Kerberos, you must change the options files in the following way: the <em>-Djava.security.auth.login.config=</em>
+          line should be changed to <em>-Djava.security.auth.login.config=jaas-client.conf</em>, and the <em>jaas-client.conf</em> file filled out properly for your installation.</p>
+        <p>
+        <p>Each example deployment has advantages and disadvantages.  For example, single-process models limit the flexibility of deploying ManifoldCF components.  Multi-process models require that
           inter-process synchronization be properly configured.  If you are just starting out with ManifoldCF, we suggest you try the quick-start single process model first, since that is
           the easiest.</p>
         <section>

Modified: manifoldcf/trunk/site/src/documentation/content/xdocs/zh_CN/how-to-build-and-deploy.xml
URL: http://svn.apache.org/viewvc/manifoldcf/trunk/site/src/documentation/content/xdocs/zh_CN/how-to-build-and-deploy.xml?rev=1873502&r1=1873501&r2=1873502&view=diff
==============================================================================
--- manifoldcf/trunk/site/src/documentation/content/xdocs/zh_CN/how-to-build-and-deploy.xml (original)
+++ manifoldcf/trunk/site/src/documentation/content/xdocs/zh_CN/how-to-build-and-deploy.xml Sun Feb  2 11:55:39 2020
@@ -551,7 +551,14 @@ mvn clean package
           <li>Simplified multi-process model</li>
           <li>Command-driven multi-process model</li>
         </ul>
-        <p>Each way has advantages and disadvantages.  For example, single-process models limit the flexibility of deploying ManifoldCF components.  Multi-process models require that
+        <p>All examples have similar script structure and construction.  For example, there are always options files you can modify to control the behavior of individual processes.  These
+          files have names of the form: <em>*-options.env.win</em> and <em>*-options.env.unix</em>.  They contain a list of switches to be used in starting up the JVM.  These
+          switches also include memory specification (the <em>-Xmx</em> switch), as well as a predefined <em>-D</em> switch that is meant to enable Kerberos (for the connectors
+          it is implemented for).  In general, for <em>-D</em> switches in options files, you will want to change them for all options files in the example deployment you are using, to
+          insure that all processes operate in the same environment.  For example, to enable Kerberos, you must change the options files in the following way: the <em>-Djava.security.auth.login.config=</em>
+          line should be changed to <em>-Djava.security.auth.login.config=jaas-client.conf</em>, and the <em>jaas-client.conf</em> file filled out properly for your installation.</p>
+        <p>
+        <p>Each example deployment has advantages and disadvantages.  For example, single-process models limit the flexibility of deploying ManifoldCF components.  Multi-process models require that
           inter-process synchronization be properly configured.  If you are just starting out with ManifoldCF, we suggest you try the quick-start single process model first, since that is
           the easiest.</p>
         <section>