You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@knox.apache.org by mo...@apache.org on 2018/07/03 19:13:37 UTC
svn commit: r1835012 [1/5] - in /knox: site/books/knox-0-10-0/
site/books/knox-0-11-0/ site/books/knox-0-12-0/ site/books/knox-0-13-0/
site/books/knox-0-14-0/ site/books/knox-0-3-0/ site/books/knox-0-4-0/
site/books/knox-0-5-0/ site/books/knox-0-6-0/ s...
Author: more
Date: Tue Jul 3 19:13:36 2018
New Revision: 1835012
URL: http://svn.apache.org/viewvc?rev=1835012&view=rev
Log:
KNOX-1209 - Style improvements to the 1.1.0 User Guide (Lars Francke)
Modified:
knox/site/books/knox-0-10-0/user-guide.html
knox/site/books/knox-0-11-0/user-guide.html
knox/site/books/knox-0-12-0/user-guide.html
knox/site/books/knox-0-13-0/user-guide.html
knox/site/books/knox-0-14-0/user-guide.html
knox/site/books/knox-0-3-0/knox-0-3-0.html
knox/site/books/knox-0-4-0/knox-0-4-0.html
knox/site/books/knox-0-5-0/knox-0-5-0.html
knox/site/books/knox-0-6-0/user-guide.html
knox/site/books/knox-0-7-0/user-guide.html
knox/site/books/knox-0-8-0/user-guide.html
knox/site/books/knox-0-9-0/user-guide.html
knox/site/books/knox-0-9-1/user-guide.html
knox/site/books/knox-1-0-0/user-guide.html
knox/site/books/knox-1-1-0/user-guide.html
knox/trunk/books/1.1.0/admin_ui.md
knox/trunk/books/1.1.0/book.md
knox/trunk/books/1.1.0/book_client-details.md
knox/trunk/books/1.1.0/book_gateway-details.md
knox/trunk/books/1.1.0/book_getting-started.md
knox/trunk/books/1.1.0/book_knox-samples.md
knox/trunk/books/1.1.0/book_limitations.md
knox/trunk/books/1.1.0/book_service-details.md
knox/trunk/books/1.1.0/book_topology_port_mapping.md
knox/trunk/books/1.1.0/book_troubleshooting.md
knox/trunk/books/1.1.0/book_ui_service_details.md
knox/trunk/books/1.1.0/config.md
knox/trunk/books/1.1.0/config_advanced_ldap.md
knox/trunk/books/1.1.0/config_audit.md
knox/trunk/books/1.1.0/config_authn.md
knox/trunk/books/1.1.0/config_authz.md
knox/trunk/books/1.1.0/config_ha.md
knox/trunk/books/1.1.0/config_hadoop_auth_provider.md
knox/trunk/books/1.1.0/config_id_assertion.md
knox/trunk/books/1.1.0/config_kerberos.md
knox/trunk/books/1.1.0/config_knox_sso.md
knox/trunk/books/1.1.0/config_ldap_authc_cache.md
knox/trunk/books/1.1.0/config_ldap_group_lookup.md
knox/trunk/books/1.1.0/config_metrics.md
knox/trunk/books/1.1.0/config_mutual_authentication_ssl.md
knox/trunk/books/1.1.0/config_pac4j_provider.md
knox/trunk/books/1.1.0/config_pam_authn.md
knox/trunk/books/1.1.0/config_preauth_sso_provider.md
knox/trunk/books/1.1.0/config_sso_cookie_provider.md
knox/trunk/books/1.1.0/config_webappsec_provider.md
knox/trunk/books/1.1.0/knox_cli.md
knox/trunk/books/1.1.0/quick_start.md
knox/trunk/books/1.1.0/service_config.md
knox/trunk/books/1.1.0/service_hbase.md
knox/trunk/books/1.1.0/service_hive.md
knox/trunk/books/1.1.0/service_kafka.md
knox/trunk/books/1.1.0/service_livy.md
knox/trunk/books/1.1.0/service_oozie.md
knox/trunk/books/1.1.0/service_solr.md
knox/trunk/books/1.1.0/service_storm.md
knox/trunk/books/1.1.0/service_webhcat.md
knox/trunk/books/1.1.0/service_webhdfs.md
knox/trunk/books/1.1.0/websocket-support.md
knox/trunk/books/1.1.0/x-forwarded-headers.md
knox/trunk/books/common/header.md
Modified: knox/site/books/knox-0-10-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-10-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-10-0/user-guide.html (original)
+++ knox/site/books/knox-0-10-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -156,7 +156,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -3117,7 +3117,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-11-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-11-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-11-0/user-guide.html (original)
+++ knox/site/books/knox-0-11-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -170,7 +170,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -3326,7 +3326,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-12-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-12-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-12-0/user-guide.html (original)
+++ knox/site/books/knox-0-12-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -184,7 +184,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -3609,7 +3609,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-13-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-13-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-13-0/user-guide.html (original)
+++ knox/site/books/knox-0-13-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -202,7 +202,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -3651,7 +3651,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps described here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports, user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-14-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-14-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-14-0/user-guide.html (original)
+++ knox/site/books/knox-0-14-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -217,7 +217,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -4637,7 +4637,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps described here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports, user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p>
Modified: knox/site/books/knox-0-3-0/knox-0-3-0.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-3-0/knox-0-3-0.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-3-0/knox-0-3-0.html (original)
+++ knox/site/books/knox-0-3-0/knox-0-3-0.html Tue Jul 3 19:13:36 2018
@@ -129,7 +129,7 @@ Server: Jetty(6.1.26)
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip file or with rpm. With rpm based install the following directories are created in addition to those described in this section.</p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip file or with rpm. With rpm based install the following directories are created in addition to those described in this section.</p>
<pre><code>/usr/lib/knox
/var/log/knox
/var/run/knox
@@ -1118,7 +1118,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the GATEWAY_HOME current directory. The GATEWAY_HOME directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changes to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-site.xm
l configuration file. In sandbox this configuration file is located at /etc/hadoop/conf/hdfs-site.xml. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-4-0/knox-0-4-0.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-4-0/knox-0-4-0.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-4-0/knox-0-4-0.html (original)
+++ knox/site/books/knox-0-4-0/knox-0-4-0.html Tue Jul 3 19:13:36 2018
@@ -122,7 +122,7 @@ Server: Jetty(6.1.26)
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -1507,7 +1507,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the GATEWAY_HOME current directory. The GATEWAY_HOME directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changes to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-site.xm
l configuration file. In sandbox this configuration file is located at /etc/hadoop/conf/hdfs-site.xml. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-5-0/knox-0-5-0.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-5-0/knox-0-5-0.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-5-0/knox-0-5-0.html (original)
+++ knox/site/books/knox-0-5-0/knox-0-5-0.html Tue Jul 3 19:13:36 2018
@@ -127,7 +127,7 @@ Server: Jetty(6.1.26)
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -1808,7 +1808,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the GATEWAY_HOME current directory. The GATEWAY_HOME directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changes to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-site.xm
l configuration file. In sandbox this configuration file is located at /etc/hadoop/conf/hdfs-site.xml. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-6-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-6-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-6-0/user-guide.html (original)
+++ knox/site/books/knox-0-6-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -142,7 +142,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -2132,7 +2132,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the GATEWAY_HOME current directory. The GATEWAY_HOME directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changes to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-site.xm
l configuration file. In sandbox this configuration file is located at /etc/hadoop/conf/hdfs-site.xml. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-7-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-7-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-7-0/user-guide.html (original)
+++ knox/site/books/knox-0-7-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -146,7 +146,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -2573,7 +2573,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-8-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-8-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-8-0/user-guide.html (original)
+++ knox/site/books/knox-0-8-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -147,7 +147,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -2801,7 +2801,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-9-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-9-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-9-0/user-guide.html (original)
+++ knox/site/books/knox-0-9-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -154,7 +154,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -3004,7 +3004,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-0-9-1/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-0-9-1/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-0-9-1/user-guide.html (original)
+++ knox/site/books/knox-0-9-1/user-guide.html Tue Jul 3 19:13:36 2018
@@ -154,7 +154,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -3004,7 +3004,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps describe here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p><h3><a id="WebHDFS">WebHDFS</a> <a href="#WebHDFS"><img src="markbook-section-link.png"/></a></h3><p>REST API access to HDFS in a Hadoop cluster is provided by WebHDFS. The <a href="http://hadoop.apache.org/docs/stable/hadoop-project-dist/hadoop-hdfs/WebHDFS.html">WebHDFS REST API</a> documentation is available online. WebHDFS must be enabled in the hdfs-si
te.xml configuration file. In the sandbox this configuration file is located at <code>/etc/hadoop/conf/hdfs-site.xml</code>. Note the properties shown below as they are related to configuration required by the gateway. Some of these represent the default values and may not actually be present in hdfs-site.xml.</p>
Modified: knox/site/books/knox-1-0-0/user-guide.html
URL: http://svn.apache.org/viewvc/knox/site/books/knox-1-0-0/user-guide.html?rev=1835012&r1=1835011&r2=1835012&view=diff
==============================================================================
--- knox/site/books/knox-1-0-0/user-guide.html (original)
+++ knox/site/books/knox-1-0-0/user-guide.html Tue Jul 3 19:13:36 2018
@@ -217,7 +217,7 @@ curl -i -k -u guest:guest-password -X GE
<ol>
<li>The gateway is <em>not</em> collocated with the Hadoop clusters themselves.</li>
<li>The host names and IP addresses of the cluster services are accessible by the gateway where ever it happens to be running.</li>
-</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="http://hortonworks.com/products/hortonworks-sandbox">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWAY_HOME}</code></p>
+</ol><p>All of the instructions and samples provided here are tailored and tested to work “out of the box” against a <a href="https://hortonworks.com/products/sandbox/">Hortonworks Sandbox 2.x VM</a>.</p><h4><a id="Apache+Knox+Directory+Layout">Apache Knox Directory Layout</a> <a href="#Apache+Knox+Directory+Layout"><img src="markbook-section-link.png"/></a></h4><p>Knox can be installed by expanding the zip/archive file.</p><p>The table below provides a brief explanation of the important files and directories within <code>{GATEWAY_HOME}</code></p>
<table>
<thead>
<tr>
@@ -4637,7 +4637,7 @@ dep/commons-codec-1.7.jar
<li>The example commands are executed within the context of the <code>GATEWAY_HOME</code> current directory. The <code>GATEWAY_HOME</code> directory is the directory within the Apache Knox Gateway installation that contains the README file and the bin, conf and deployments directories.</li>
<li>The <a href="http://curl.haxx.se/">cURL</a> command line HTTP client utility is installed and functional.</li>
<li>A few examples optionally require the use of commands from a standard Groovy installation. These examples are optional but to try them you will need Groovy <a href="http://groovy.codehaus.org/Installing+Groovy">installed</a>.</li>
- <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="http://hortonworks.com/products/hortonworks-sandbox">Sandbox</a> version 2.</li>
+ <li>The default configuration for all of the samples is setup for use with Hortonworks’ <a href="https://hortonworks.com/products/sandbox/">Sandbox</a> version 2.</li>
</ul><h3><a id="Customization">Customization</a> <a href="#Customization"><img src="markbook-section-link.png"/></a></h3><p>Using these samples with other Hadoop installations will require changes to the steps described here as well as changes to referenced sample scripts. This will also likely require changes to the gateway’s default configuration. In particular host names, ports, user names and password may need to be changed to match your environment. These changes may need to be made to gateway configuration and also the Groovy sample script files in the distribution. All of the values that may need to be customized in the sample scripts can be found together at the top of each of these files.</p><h3><a id="cURL">cURL</a> <a href="#cURL"><img src="markbook-section-link.png"/></a></h3><p>The cURL HTTP client command line utility is used extensively in the examples for each service. In particular this form of the cURL command line is used repeatedly.</p>
<pre><code>curl -i -k -u guest:guest-password ...
</code></pre><p>The option -i (aka –include) is used to output HTTP response header information. This will be important when the content of the HTTP Location header is required for subsequent requests.</p><p>The option -k (aka –insecure) is used to avoid any issues resulting from the use of demonstration SSL certificates.</p><p>The option -u (aka –user) is used to provide the credentials to be used when the client is challenged by the gateway.</p><p>Keep in mind that the samples do not use the cookie features of cURL for the sake of simplicity. Therefore each request via cURL will result in an authentication.</p>