unstick r1873502

Revision 1873502

Date:
2020/02/02 11:55:39
Author:
kwright
Revision Log:
Update documentation to describe kerberos enabling
Files:

Legend:

 
Added
 
Removed
 
Modified
  • manifoldcf/trunk/site/src/documentation/content/xdocs/en_US/how-to-build-and-deploy.xml

     
    551 551 <li>Simplified multi-process model</li>
    552 552 <li>Command-driven multi-process model</li>
    553 553 </ul>
    554 <p>Each way has advantages and disadvantages. For example, single-process models limit the flexibility of deploying ManifoldCF components. Multi-process models require that
    554 <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
    555 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
    556 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
    557 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
    558 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>
    559 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>
    560 <p>
    561 <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
    555 562 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
    556 563 the easiest.</p>
    557 564 <section>
  • manifoldcf/trunk/site/src/documentation/content/xdocs/ja_JP/how-to-build-and-deploy.xml

     
    551 551 <li>Simplified multi-process model</li>
    552 552 <li>Command-driven multi-process model</li>
    553 553 </ul>
    554 <p>Each way has advantages and disadvantages. For example, single-process models limit the flexibility of deploying ManifoldCF components. Multi-process models require that
    554 <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
    555 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
    556 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
    557 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
    558 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>
    559 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>
    560 <p>
    561 <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
    555 562 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
    556 563 the easiest.</p>
    557 564 <section>
  • manifoldcf/trunk/site/src/documentation/content/xdocs/zh_CN/how-to-build-and-deploy.xml

     
    551 551 <li>Simplified multi-process model</li>
    552 552 <li>Command-driven multi-process model</li>
    553 553 </ul>
    554 <p>Each way has advantages and disadvantages. For example, single-process models limit the flexibility of deploying ManifoldCF components. Multi-process models require that
    554 <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
    555 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
    556 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
    557 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
    558 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>
    559 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>
    560 <p>
    561 <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
    555 562 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
    556 563 the easiest.</p>
    557 564 <section>