manifoldcf-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kwri...@apache.org
Subject svn commit: r1462853 [20/20] - in /manifoldcf/site/publish: en_US/ release/trunk/api/activedirectory/ release/trunk/api/activedirectory/org/apache/manifoldcf/authorities/authorities/activedirectory/ release/trunk/api/alfresco/ release/trunk/api/alfresc...
Date Sat, 30 Mar 2013 20:56:38 GMT
Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsPagesContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsPagesContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsPagesContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsPagesContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:43 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetDocURLsPagesContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsQueryContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsQueryContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsQueryContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetDocURLsQueryContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:43 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetDocURLsQueryContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:43 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetNamespacesAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNamespacesContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNamespacesContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNamespacesContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNamespacesContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:43 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetNamespacesNamespacesContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNsContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNsContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNsContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesNsContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:43 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetNamespacesNsContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesQueryContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesQueryContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesQueryContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetNamespacesQueryContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetNamespacesQueryContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetTimestampAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPageContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPageContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPageContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPageContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetTimestampPageContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPagesContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPagesContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPagesContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampPagesContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetTimestampPagesContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampQueryContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampQueryContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampQueryContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampQueryContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetTimestampQueryContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetTimestampRevContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevisionsContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevisionsContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevisionsContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiGetTimestampRevisionsContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiGetTimestampRevisionsContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiListPagesAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAllPagesContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAllPagesContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAllPagesContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesAllPagesContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiListPagesAllPagesContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesPContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesPContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesPContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesPContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiListPagesPContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesQueryContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesQueryContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesQueryContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiListPagesQueryContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiListPagesQueryContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiLoginAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIResultAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIResultAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIResultAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiLoginAPIResultAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiLoginAPIResultAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiTokenLoginAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIResultAPIContext.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIResultAPIContext.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIResultAPIContext.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.WikiTokenLoginAPIResultAPIContext.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 WikiConnector.WikiTokenLoginAPIResultAPIContext
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/WikiConnector.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:27 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:43 EDT 2013 -->
 <TITLE>
 WikiConnector
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-frame.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-frame.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-frame.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-frame.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 org.apache.manifoldcf.crawler.connectors.wiki
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-summary.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-summary.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-summary.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-summary.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 org.apache.manifoldcf.crawler.connectors.wiki
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-tree.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-tree.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-tree.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/org/apache/manifoldcf/crawler/connectors/wiki/package-tree.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:28 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 org.apache.manifoldcf.crawler.connectors.wiki Class Hierarchy
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="../../../../../../stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/api/wiki/overview-tree.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/api/wiki/overview-tree.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/api/wiki/overview-tree.html (original)
+++ manifoldcf/site/publish/release/trunk/api/wiki/overview-tree.html Sat Mar 30 20:56:07 2013
@@ -2,12 +2,12 @@
 <!--NewPage-->
 <HTML>
 <HEAD>
-<!-- Generated by javadoc (build 1.6.0_21) on Thu Mar 21 17:01:29 EDT 2013 -->
+<!-- Generated by javadoc (build 1.6.0_21) on Sat Mar 30 16:10:44 EDT 2013 -->
 <TITLE>
 Class Hierarchy
 </TITLE>
 
-<META NAME="date" CONTENT="2013-03-21">
+<META NAME="date" CONTENT="2013-03-30">
 
 <LINK REL ="stylesheet" TYPE="text/css" HREF="stylesheet.css" TITLE="Style">
 

Modified: manifoldcf/site/publish/release/trunk/en_US/end-user-documentation.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/end-user-documentation.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/en_US/end-user-documentation.html (original)
+++ manifoldcf/site/publish/release/trunk/en_US/end-user-documentation.html Sat Mar 30 20:56:07 2013
@@ -319,7 +319,7 @@ document.write("Last Published: " + docu
                    with all required services running and desired connection types properly registered.  If you think you need to know how to do that yourself, please visit the "Developer Resources" page.
             </p>
 <p>Most of this manual describes how to use the ManifoldCF user interface.  On a standard ManifoldCF deployment, you would reach that interface by giving your browser
-                  a URL something like this: <span class="codefrag">http://my-server-name:8080/acf-crawler-ui</span>.  This will, of course, differ from system to system.  Please contact your system administrator
+                  a URL something like this: <span class="codefrag">http://my-server-name:8345/mcf-crawler-ui</span>.  This will, of course, differ from system to system.  Please contact your system administrator
                   to find out what URL is appropriate for your environment.
             </p>
 <p>The ManifoldCF UI has been tested with Firefox and various incarnations of Internet Explorer.  If you use another browser, there is a small chance that the UI
@@ -832,34 +832,50 @@ document.write("Last Published: " + docu
 <div class="section">
 <a name="N1038B"></a><a name="solroutputconnector"></a>
 <h3 class="h4">Solr Output Connection</h3>
-<p>The Solr output connection type is designed to allow ManifoldCF to submit documents to an appropriate Solr pipeline, via the Solr
-                       HTTP ingestion API.  The configuration parameters are set to the default Solr values, which can be changed (since Solr's configuration can be changed).
-                       The Solr output connection type furthermore makes no judgment as to whether a given document is indexable or not - it accepts everything, and passes all documents
-                       on to the pipeline, where presumably the configured pipeline will decide if a document should be rejected or not.  (All of that happens without a Solr connection
-                       being aware of it in any way.)</p>
-<p>Unfortunately, this lack of specificity comes at a cost.  Unless you take care to filter documents properly in each job, large movie files or other opaque
-                       content may well be picked up and sent to Solr for indexing, which will greatly increase the dead load on the overall system.  It is therefore a good idea to review
-                       all crawls done through a Solr connection while they are underway, to be sure there isn't a misconfiguration of this kind.</p>
-<p>When you create a Solr output connection, five configuration tabs appear.  The "Server" tab allows you to configure the HTTP target of the connection:</p>
+<p>The Solr output connection type is designed to allow ManifoldCF to submit documents to either an appropriate Apache Solr instance,
+                       via the Solr HTTP API, or alternatively to a Solr Cloud cluster.  The configuration parameters are initially set to appropriate default
+                       values for a stand-alone Solr instance.</p>
+<p>When you create a Solr output connection, multiple configuration tabs appear.  The first tab is the "Solr type" tab.  Here you select
+                       whether you want your connection to communicate to a standalone Solr instance, or to a Solr Cloud cluster:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="Solr Configuration, Solr type tab" src="images/en_US/solr-configure-solr-type.PNG" width="80%"></div>
+<br>
+<br>
+<p>Select which kind of Solr installation you want to communicate with.  Based on your selection, you can proceed to either the "Server"
+                       tab (if a standalone instance) or to the "ZooKeeper" tab (if a SolrCloud cluster).</p>
+<p>The "Server" tab allows you to configure the HTTP parameters appropriate for communicating with a standalone Solr instance:</p>
 <br>
 <br>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="Solr Configuration, Server tab" src="images/en_US/solr-configure-server.PNG" width="80%"></div>
 <br>
 <br>
-<p>Fill in the fields according to your Solr configuration.  The Solr connection type supports only basic authentication at this time; if you have this enabled, supply the credentials
-                       as requested on the bottom part of the form.</p>
-<p>The second tab is the "Schema" tab, which allows you to specify the name of the Solr field to use as a document identifier.  The Solr connection type will treat
-                       this field as being a unique key for locating the indexed document for further modification or deletion:</p>
+<p>If your Solr setup is a standalone instance, fill in the fields according to your Solr configuration.  The Solr connection type supports
+                       only basic authentication at this time; if you have this enabled, supply the credentials as requested on the bottom part of the form.</p>
+<p>The "Zookeeper" tab allows your to configure the connection type to communicate with a Solr Cloud cluster:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="Solr Configuration, Zookeeper tab" src="images/en_US/solr-configure-zookeeper.PNG" width="80%"></div>
+<br>
+<br>
+<p>Here, add each ZooKeeper instance in the SolrCloud cluster to the list of ZooKeeper instances.  The connection comes preconfigured with
+                       "localhost" as being a ZooKeeper instance.  You may delete this if it is not the case.</p>
+<p>The next tab is the "Schema" tab, which allows you to specify the names of various Solr fields into which the Solr connection type will
+                       place built-in document metadata:</p>
 <br>
 <br>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="Solr Configuration, Schema tab" src="images/en_US/solr-configure-schema.PNG" width="80%"></div>
 <br>
 <br>
-<p>The third tab is the "Arguments" tab, which allows you to specify arbitrary arguments to be sent to Solr. All valid Solr update request parameters
-                       can be specified here. You can for instance add <a href="http://wiki.apache.org/solr/UpdateRequestProcessor">update.chain=myChain</a> to select the document processing pipeline/chain to use for
-                       processing documents in Solr. See the Solr documentation for more valid arguments. The tab looks like:</p>
+<p>The most important of these is the document identifier field, which MUST be present for the connection type to function.  This field will
+                       be used to uniquely identify the document within Solr, and will contain the document's URL.  The Solr connection type will treat this field as being
+                       a unique key for locating the indexed document for further modification or deletion.  The other Solr fields are optional, and largely self-
+                       explanatory.</p>
+<p>The next tab is the "Arguments" tab, which allows you to specify arbitrary arguments to be sent to Solr:</p>
 <br>
 <br>
 <div id="" style="text-align: center;">
@@ -868,18 +884,27 @@ document.write("Last Published: " + docu
 <br>
 <p>Fill in the argument name and value, and click the "Add" button.  Bear in mind that if you add an argument with the same name as an existing one, it will replace the
                        existing one with the new specified value.  You can delete existing arguments by clicking the "Delete" button next to the argument you want to delete.</p>
-<p>The fourth tab is the "Documents" tab, which allows you to do document filtering based on size and mime types. By specifying a maximum document length in bytes, you can filter out documents which exceed that size (e.g. 10485760 which is equivalent to 10 MB). If you only want to add documents with specific mime types, you can enter them into the "included mime types" field (e.g. "text/html" for filtering out all documents but HTML). The "excluded mime types" field is for excluding documents with specific mime types (e.g. "image/jpeg" for filtering out JPEG images). The tab looks like:</p>
+<p>Use this tab to specify any and all desired Solr update request parameters.  You can, for instance, add
+                       <a href="http://wiki.apache.org/solr/UpdateRequestProcessor">update.chain=myChain</a> to select a specific document processing pipeline/chain to
+                       use for processing documents. See the Solr documentation for more valid arguments.</p>
+<p>The next tab is the "Documents" tab, which allows you to do document filtering based on size and mime types. By specifying a maximum document
+                       length in bytes, you can filter out documents which exceed that size (e.g. 10485760 which is equivalent to 10 MB). If you only want to add
+                       documents with specific mime types, you can enter them into the "included mime types" field (e.g. "text/html" for filtering out all documents but HTML).
+                       The "excluded mime types" field is for excluding documents with specific mime types (e.g. "image/jpeg" for filtering out JPEG images). The tab looks like:</p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="Solr Configuration, Documents tab" src="images/en_US/solr-configure-documents.PNG" width="80%"></div>
 <br>
 <br>
-<p>The fifth tab is the "Commits" tab, which allows you to control the commit strategies. As well as committing documents at the end of every job, an option which is enabled by default, you may also commit each document within a certain time in milliseconds (e.g. "10000" for committing within 10 seconds). The <a href="http://wiki.apache.org/solr/CommitWithin">commit within</a> strategy will leave the responsibility to Solr instead of ManifoldCF. The tab looks like:</p>
+<p>The fifth tab is the "Commits" tab, which allows you to control the commit strategies. As well as committing documents at the end of every job, an
+                       option which is enabled by default, you may also commit each document within a certain time in milliseconds (e.g. "10000" for committing within
+                       10 seconds). The <a href="http://wiki.apache.org/solr/CommitWithin">commit within</a> strategy will leave the responsibility to Solr instead
+                       of ManifoldCF. The tab looks like:</p>
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="Solr Configuration, Documents tab" src="images/en_US/solr-configure-commits.PNG" width="80%"></div>
 <br>
 <br>
-<p>When you are done, don't forget to click the "Save" button to save your changes!  When you do, a connection summary and status screen will be presented, which
-                       may look something like this:</p>
+<p>When you are done, don't forget to click the "Save" button to save your changes!  When you do, a connection summary and status screen will be
+                       presented, which may look something like this:</p>
 <br>
 <br>
 <div id="" style="text-align: center;">
@@ -899,7 +924,7 @@ document.write("Last Published: " + docu
 <br>
 <p>Add a new mapping by filling in the "source" with the name of the metadata item from the repository, and "target" as the name of the output field in
                        Solr, and click the "Add" button.  Leaving the "target" field blank will result in all metadata items of that name not being sent to Solr.</p>
-<a name="N10408"></a><a name="osssoutputconnector"></a>
+<a name="N1042D"></a><a name="osssoutputconnector"></a>
 <h3 class="h4">OpenSearchServer Output Connection</h3>
 <p>The OpenSearchServer Output Connection allow ManifoldCF to submit documents to an OpenSearchServer instance, via the XML over HTTP API. The connector has been designed
             	to be as easy to use as possible.</p>
@@ -940,7 +965,7 @@ document.write("Last Published: " + docu
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="OpenSearchServer, history report" src="images/en_US/opensearchserver-history-report.PNG" width="80%"></div>
 <p>You may also refer to the <a href="http://www.open-search-server.com/documentation">OpenSearchServer's user documentation</a>.</p>
-<a name="N10453"></a><a name="esssoutputconnector"></a>
+<a name="N10478"></a><a name="esssoutputconnector"></a>
 <h3 class="h4">ElasticSearch Output Connection</h3>
 <p>The ElasticSearch Output Connection allow ManifoldCF to submit documents to an ElasticSearch instance, via the XML over HTTP API. The connector has been designed
             	to be as easy to use as possible.</p>
@@ -976,7 +1001,7 @@ document.write("Last Published: " + docu
 <div id="" style="text-align: center;">
 <img id="" class="figure" alt="ElasticSearch, history report" src="images/en_US/elasticsearch-history-report.png" width="80%"></div>
 <p>You may also refer to <a href="http://www.elasticsearch.org/guide">ElasticSearch's user documentation</a>.</p>
-<a name="N10497"></a><a name="gtsoutputconnector"></a>
+<a name="N104BC"></a><a name="gtsoutputconnector"></a>
 <h3 class="h4">MetaCarta GTS Output Connection</h3>
 <p>The MetaCarta GTS output connection type is designed to allow ManifoldCF to submit documents to an appropriate MetaCarta GTS search
                        appliance, via the appliance's HTTP Ingestion API.</p>
@@ -985,7 +1010,7 @@ document.write("Last Published: " + docu
 <p>When you configure a job to use a GTS-type output connection, two additional tabs will be presented to the user: "Collections" and "Document Templates".  These
                        tabs allow per-job specification of these GTS-specific features.</p>
 <p>More here later</p>
-<a name="N104AA"></a><a name="nulloutputconnector"></a>
+<a name="N104CF"></a><a name="nulloutputconnector"></a>
 <h3 class="h4">Null Output Connection</h3>
 <p>The null output connection type is meant primarily to function as an aid for people writing repository connection types.  It is not expected to be useful in practice.</p>
 <p>The null output connection type simply logs indexing and deletion requests, and does nothing else.  It does not have any special configuration tabs, nor does it
@@ -993,10 +1018,10 @@ document.write("Last Published: " + docu
 </div>
         
         
-<a name="N104B8"></a><a name="authorityconnectiontypes"></a>
+<a name="N104DD"></a><a name="authorityconnectiontypes"></a>
 <h2 class="h3">Authority Connection Types</h2>
 <div class="section">
-<a name="N104BE"></a><a name="adauthority"></a>
+<a name="N104E3"></a><a name="adauthority"></a>
 <h3 class="h4">Active Directory Authority Connection</h3>
 <p>An active directory authority connection is essential for enforcing security for documents from Windows shares, Microsoft SharePoint, and IBM FileNet repositories.
                        This connection type needs to be provided with information about how to log into an appropriate Windows domain controller, with a user that has sufficient privileges to
@@ -1030,7 +1055,7 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>Note that in this example, the Active Directory connection is not responding, which is leading to an error status message instead of "Connection working".</p>
-<a name="N104F7"></a><a name="ldapauthority"></a>
+<a name="N1051C"></a><a name="ldapauthority"></a>
 <h3 class="h4">LDAP Authority Connection</h3>
 <p>An LDAP authority connection can be used to provide document security in situations where there is no native document security
                       model in place.  Examples include Samba shares, Wiki pages,  RSS feeds, etc.</p>
@@ -1058,14 +1083,14 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>Note that in this example, the LDAP connection is not responding, which is leading to an error status message instead of "Connection working".</p>
-<a name="N10526"></a><a name="livelinkauthority"></a>
+<a name="N1054B"></a><a name="livelinkauthority"></a>
 <h3 class="h4">OpenText LiveLink Authority Connection</h3>
 <p>A LiveLink authority connection is needed to enforce security for documents retrieved from LiveLink repositories.</p>
-<p>In order to function, this connection type needs to be provided with 
-                    information about the name of the LiveLink server, and credentials appropriate for retrieving a user's ACLs from that machine.  Since LiveLink operates with its own list of users, you
-                    may also want to specify a rule-based mapping between an Active Directory user and the corresponding LiveLink user.  The authority type allows you to specify such a mapping using
+<p>In order to function, this connection type needs to be provided with information about the name of the LiveLink server, and credentials appropriate
+                    for retrieving a user's ACLs from that machine.  Since LiveLink operates with its own list of users, you may also want to specify a rule-based
+                    mapping between an Active Directory user and the corresponding LiveLink user.  The authority type allows you to specify such a mapping using
                     regular expressions.</p>
-<p>A LiveLink authority connection has two special tabs you will need to configure: the "Server" tab, and the "User Mapping" tab.</p>
+<p>A LiveLink authority connection has three special tabs you will need to configure: the "Server" tab, the "User Mapping" tab, and the "Cache" tab.</p>
 <p>The "Server" tab looks like this:</p>
 <br>
 <br>
@@ -1073,7 +1098,23 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Authority, Server tab" src="images/en_US/livelink-authority-server.PNG" width="80%"></div>
 <br>
 <br>
-<p>Enter the name of the desired LiveLink server, the LiveLink port, and the LiveLink credentials.</p>
+<p>Select the manner you want the connection to use to communicate with LiveLink.  Your options are:</p>
+<ul>
+                  
+<li>Internal (native LiveLink protocol)</li>
+                  
+<li>HTTP (communication with LiveLink through the IIS web server)</li>
+                  
+<li>HTTPS (communication with LiveLink through IIS using SSL)</li>
+                
+</ul>
+<p>Also, you need to enter the name of the desired LiveLink server, the LiveLink port, and the LiveLink server credentials.  If you have selected communication
+                    using HTTP or HTTPS, you must provide a relative CGI path to your LiveLink.  You may also need to provide web server credentials.  Basic authentication
+                    and older forms of NTLM are supported.  In order to use NTLM, specify a non-blank server domain name in the "Server HTTP domain" field, plus a non-
+                    qualified user name and password.  If basic authentication is desired, leave the "Server HTTP domain" field blank, and provide basic auth credentials in the
+                    "Server HTTP NTLM user name" and "Server HTTP NTLM password" fields.  For no web server authentication, leave these fields all blank.</p>
+<p>For communication using HTTPS, you will also need to upload your authority certificate(s) on the "Server" tab, to tell the connection which certificates to
+                    trust.  Upload your certificate using the browse button, and then click the "Add" button to add it to the trust store.</p>
 <p>The "User Mapping" tab looks like this:</p>
 <br>
 <br>
@@ -1082,12 +1123,22 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>The purpose of the "User Mapping" tab is to allow you to map the incoming user name and domain (usually from Active Directory) to its LiveLink equivalent.
-                       The mapping consists of a match expression, which is a regular expression where parentheses ("("
-                       and ")") mark sections you are interested in, and a replace string.  The sections marked with parentheses are called "groups" in regular expression parlance.  The replace string consists of constant text plus
-                       substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the first match group
-                       mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
-<p>For example, a match expression of <span class="codefrag">^(.*)\@([A-Z|a-z|0-9|_|-]*)\.(.*)$</span> with a replace string of <span class="codefrag">$(2)\$(1l)</span> would convert an AD username of
-                    <span class="codefrag">MyUserName@subdomain.domain.com</span> into the LiveLink user name <span class="codefrag">subdomain\myusername</span>.</p>
+                       The mapping consists of a match expression, which is a regular expression where parentheses ("(" and ")") mark sections you are interested in, and a
+                       replace string.  The sections marked with parentheses are called "groups" in regular expression parlance.  The replace string consists of constant text plus
+                       substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the first
+                       match group mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
+<p>For example, a match expression of <span class="codefrag">^(.*)\@([A-Z|a-z|0-9|_|-]*)\.(.*)$</span> with a replace string of <span class="codefrag">$(2)\$(1l)</span> would convert
+                      an Active Directory username of <span class="codefrag">MyUserName@subdomain.domain.com</span> into the LiveLink user name
+                      <span class="codefrag">subdomain\myusername</span>.</p>
+<p>The "Cache" tab allows you to configure how the authority connection keeps an individual user's information around:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Authority, Cache tab" src="images/en_US/livelink-authority-cache.PNG" width="80%"></div>
+<br>
+<br>
+<p>Here you set the time a user's information is kept around (the "Cache lifetime" field), and how many simultaneous users have their information cached
+                      (the "Cache LRU size" field).</p>
 <p>When you are done, click the "Save" button.  You will then see a summary and status for the authority connection:</p>
 <br>
 <br>
@@ -1095,9 +1146,9 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Authority Status" src="images/en_US/livelink-authority-status.PNG" width="80%"></div>
 <br>
 <br>
-<p>We suggest that you examine the status carefully and correct any reported errors before proceeding.  Note that in this example, the LiveLink server would not accept connections, which
-                    is leading to an error status message instead of "Connection working".</p>
-<a name="N10578"></a><a name="documentumauthority"></a>
+<p>We suggest that you examine the status carefully and correct any reported errors before proceeding.  Note that in this example, the LiveLink server would
+                    not accept connections, which is leading to an error status message instead of "Connection working".</p>
+<a name="N105C0"></a><a name="documentumauthority"></a>
 <h3 class="h4">EMC Documentum Authority Connection</h3>
 <p>A Documentum authority connection is required for enforcing security for documents retrieved from Documentum repositories.</p>
 <p>This connection type needs to be provided with information about what Content Server to connect to, and the credentials that should be used to retrieve a user's ACLs from that machine.
@@ -1146,7 +1197,7 @@ document.write("Last Published: " + docu
 <br>
 <p>Pay careful attention to the status, and be prepared to correct any
                     problems that are displayed.</p>
-<a name="N105CC"></a><a name="memexauthority"></a>
+<a name="N10614"></a><a name="memexauthority"></a>
 <h3 class="h4">Memex Patriarch Authority Connection</h3>
 <p>A Memex authority connection is required for enforcing security for documents retrieved from Memex repositories.</p>
 <p>This connection type needs to be provided with information about what Memex Server to connect to, and what user mapping to perform.
@@ -1183,7 +1234,7 @@ document.write("Last Published: " + docu
 <br>
 <p>We suggest that you examine the status carefully and correct any reported errors before proceeding.  Note that in this example, the Memex server has a license error, which
                     is leading to an error status message instead of "Connection working".</p>
-<a name="N1061B"></a><a name="meridioauthority"></a>
+<a name="N10663"></a><a name="meridioauthority"></a>
 <h3 class="h4">Autonomy Meridio Authority Connection</h3>
 <p>A Meridio authority connection is required for enforcing security for documents retrieved from Meridio repositories.</p>
 <p>This connection type needs to be provided with information about what Document Server to connect to, what Records Server to connect to, and what User Service Server
@@ -1257,7 +1308,7 @@ document.write("Last Published: " + docu
 </ul>
 <br>
 <p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
-<a name="N106A2"></a><a name="cmisauthority"></a>
+<a name="N106EA"></a><a name="cmisauthority"></a>
 <h3 class="h4">CMIS Authority Connection</h3>
 <p>A CMIS authority connection is required for enforcing security for documents retrieved from CMIS repositories.</p>
 <p>The CMIS specification includes the concept of authorities only depending on a specific document, this authority connector is only based on a regular expression comparator.</p>
@@ -1284,8 +1335,8 @@ document.write("Last Published: " + docu
                      and ")") mark sections you are interested in, and a replace string.  The sections marked with parentheses are called "groups" in regular expression parlance.  The replace string consists of constant text plus
                      substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the first match group
                      mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
-<p>For example, a match expression of <span class="codefrag">^(.*)\@([A-Z|a-z|0-9|_|-]*)\.(.*)$</span> with a replace string of <span class="codefrag">$(2)\$(1l)</span> would convert an AD username of
-                  <span class="codefrag">MyUserName@subdomain.domain.com</span> into the LiveLink user name <span class="codefrag">subdomain\myusername</span>.</p>
+<p>For example, a match expression of <span class="codefrag">^(.*)\@([A-Z|a-z|0-9|_|-]*)\.(.*)$</span> with a replace string of <span class="codefrag">$(2)\$(1l)</span> would convert an
+                   Active Directory username of <span class="codefrag">MyUserName@subdomain.domain.com</span> into the CMIS user name <span class="codefrag">subdomain\myusername</span>.</p>
 <p>When you are done, click the "Save" button.  You will then see a summary and status for the authority connection:</p>
 <br>
 <br>
@@ -1296,10 +1347,10 @@ document.write("Last Published: " + docu
 </div>
         
         
-<a name="N106F5"></a><a name="repositoryconnectiontypes"></a>
+<a name="N1073D"></a><a name="repositoryconnectiontypes"></a>
 <h2 class="h3">Repository Connection Types</h2>
 <div class="section">
-<a name="N106FB"></a><a name="filesystemrepository"></a>
+<a name="N10743"></a><a name="filesystemrepository"></a>
 <h3 class="h4">Generic File System Repository Connection</h3>
 <p>The generic file system repository connection type was developed primarily as an example, demonstration, and testing tool, although it can potentially be useful for indexing local
                        files that exist on the same machine that ManifoldCF is running on.  Bear in mind that there is no support in this connection type for any kind of
@@ -1338,7 +1389,7 @@ document.write("Last Published: " + docu
                        may then add rules to it.  Each rule has a match expression, an indication of whether the rule is intended to match files or directories, and an action (include or exclude).
                        Rules are evaluated from top to bottom, and the first rule that matches the file name is the one that is chosen.  To add a rule, select the desired pulldowns, type in 
                        a match file specification (e.g. "*.txt"), and click the "Add" button.</p>
-<a name="N10733"></a><a name="rssrepository"></a>
+<a name="N1077B"></a><a name="rssrepository"></a>
 <h3 class="h4">Generic RSS Repository Connection</h3>
 <p>The RSS connection type is specifically designed to crawl RSS feeds.  While the Web connection type can also extract links from RSS feeds, the RSS connection type
                        differs in the following ways:</p>
@@ -1551,7 +1602,7 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>Select the mode you want the connection to operate in.</p>
-<a name="N108B6"></a><a name="webrepository"></a>
+<a name="N108FE"></a><a name="webrepository"></a>
 <h3 class="h4">Generic Web Repository Connection</h3>
 <p>The Web connection type is effectively a reasonably full-featured web crawler.  It is capable of handling most kinds of authentication (basic, all forms of NTLM,
                        and session-based), and can extract links from the following kinds of documents:</p>
@@ -1922,7 +1973,7 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>Enter the name of the desired metadata on the left, and the desired value (if any) on the right, and click the "Add" button.</p>
-<a name="N10B08"></a><a name="jcifsrepository"></a>
+<a name="N10B50"></a><a name="jcifsrepository"></a>
 <h3 class="h4">Windows Share/DFS Repository Connection</h3>
 <p>The Windows Share connection type allows you to access content stored on Windows shares, even from non-Windows systems.  Also supported are Samba and various
                        third-party Network Attached Storage servers.</p>
@@ -2054,7 +2105,7 @@ document.write("Last Published: " + docu
 <p>Accessing some servers may result in "Couldn't connect to server: Logon failure: unknown user name or bad password" Connection Status, because the default version of NTLM used for
                        authentication is incompatible.  If this is the case, the Windows Share repository connector can be configured to use NTLMv1, rather than the NTLMv2 default. This is done by
                        setting the property "org.apache.manifoldcf.crawler.connectors.jcifs.usentlmv1" to "true" in properties.xml file.</p>
-<a name="N10BE2"></a><a name="wikirepository"></a>
+<a name="N10C2A"></a><a name="wikirepository"></a>
 <h3 class="h4">Wiki Repository Connection</h3>
 <p>The Wiki repository connection type allows you to index content from the main space of a Wiki or MediaWiki site.  The connection type uses the Wiki API
                   in order to fetch content.  Only publicly visible documents will be indexed, and there is thus no need of an authority for Wiki content.</p>
@@ -2068,7 +2119,7 @@ document.write("Last Published: " + docu
 <p>The protocol must be selected in the "Protocol" field.  At the moment only the "http" protocol is supported.  The server name must be provided in the "Server name" field.
                       The server port must be provided in the "Port" field.  Finally, the path part of the Wiki URL must be provided in the "Path name" field and must start with a "/" character.</p>
 <p>When you configure a job to use a repository connection of the Wiki type, no additional tabs are currently presented.</p>
-<a name="N10C00"></a><a name="jdbcrepository"></a>
+<a name="N10C48"></a><a name="jdbcrepository"></a>
 <h3 class="h4">Generic Database Repository Connection</h3>
 <p>The generic database connection type allows you to index content from a database table, served by one of the following databases:</p>
 <br>
@@ -2276,10 +2327,10 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>Enter a desired access token, and click the "Add" button.  You may enter multiple access tokens.</p>
-<a name="N10D4B"></a><a name="filenetrepository"></a>
+<a name="N10D93"></a><a name="filenetrepository"></a>
 <h3 class="h4">IBM FileNet P8 Repository Connection</h3>
 <p>More here later</p>
-<a name="N10D55"></a><a name="documentumrepository"></a>
+<a name="N10D9D"></a><a name="documentumrepository"></a>
 <h3 class="h4">EMC Documentum Repository Connection</h3>
 <p>The EMC Documentum connection type allows you index content from a Documentum Content Server instance.  A single connection allows you
                     to reach all documents contained on a single Content Server instance.  Multiple connections are therefore required to reach documents from multiple Content Server instances.</p>
@@ -2334,15 +2385,17 @@ document.write("Last Published: " + docu
 <p>For example, suppose you had a rule which had ".*/(.*)/(.*)/.*" as a match expression, and "$(1) $(2)" as the replace string.  If presented with the path
                     <span class="codefrag">Project/Folder_1/Folder_2/Filename</span>, it would output the string <span class="codefrag">Folder_1 Folder_2</span>.</p>
 <p>If more than one rule is present, the rules are all executed in sequence.  That is, the output of the first rule is modified by the second rule, etc.</p>
-<a name="N10DBB"></a><a name="livelinkrepository"></a>
+<a name="N10E03"></a><a name="livelinkrepository"></a>
 <h3 class="h4">OpenText LiveLink Repository Connection</h3>
-<p>The OpenText LiveLink connection type allows you to index content from LiveLink repositories.  LiveLink has a rich variety of different document types and metadata, which include
-                    basic documents, as well as compound documents, folders, workspaces, and projects.  A LiveLink connection is able to discover documents contained within all of these constructs.</p>
-<p>Documents described by LiveLink connections are typically secured by a LiveLink authority.  If you have not yet created a LiveLink authority, but would like your
-                    documents to be secured, please follow the direction in the section titled "OpenText LiveLink Authority Connection".</p>
-<p>A LiveLink connection has the following special tabs: "Server", "Document Access", and "Document View".  The "Server" tab allows you to select a LiveLink server to connect to, and also to provide
-                    appropriate credentials.  The "Document Access" tab describes the location of the LiveLink web interface, relative to the server, that will be used to fetch document content from LiveLink.
-                    The "Document View" tab affects how URLs to the fetched documents are constructed, for viewing results of searches.</p>
+<p>The LiveLink connection type allows you to index content from LiveLink repositories.  LiveLink has a rich variety of different document types and metadata,
+                    which include basic documents, as well as compound documents, folders, workspaces, and projects.  A LiveLink connection is able to discover documents
+                    contained within all of these constructs.</p>
+<p>Documents described by LiveLink connections are typically secured by a LiveLink authority.  If you have not yet created a LiveLink authority, but would
+                    like your documents to be secured, please follow the direction in the section titled "OpenText LiveLink Authority Connection".</p>
+<p>A LiveLink connection has the following special tabs: "Server", "Document Access", and "Document View".  The "Server" tab allows you to select a
+                    LiveLink server to connect to, and also to provide appropriate credentials.  The "Document Access" tab describes the location of the LiveLink web interface,
+                    relative to the server, that will be used to fetch document content from LiveLink. The "Document View" tab affects how URLs to the fetched documents
+                    are constructed, for viewing results of searches.</p>
 <p>The "Server" tab looks like this:</p>
 <br>
 <br>
@@ -2350,7 +2403,23 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Connection, Server tab" src="images/en_US/livelink-connection-server.PNG" width="80%"></div>
 <br>
 <br>
-<p>Enter the LiveLink server name, port, and credentials.</p>
+<p>Select the manner you want the connection to use to communicate with LiveLink.  Your options are:</p>
+<ul>
+                  
+<li>Internal (native LiveLink protocol)</li>
+                  
+<li>HTTP (communication with LiveLink through the IIS web server)</li>
+                  
+<li>HTTPS (communication with LiveLink through IIS using SSL)</li>
+                
+</ul>
+<p>Also, you need to enter the name of the desired LiveLink server, the LiveLink port, and the LiveLink server credentials.  If you have selected communication
+                    using HTTP or HTTPS, you must provide a relative CGI path to your LiveLink.  You may also need to provide web server credentials.  Basic authentication
+                    and older forms of NTLM are supported.  In order to use NTLM, specify a non-blank server domain name in the "Server HTTP domain" field, plus a non-
+                    qualified user name and password.  If basic authentication is desired, leave the "Server HTTP domain" field blank, and provide basic auth credentials in the
+                    "Server HTTP NTLM user name" and "Server HTTP NTLM password" fields.  For no web server authentication, leave these fields all blank.</p>
+<p>For communication using HTTPS, you will also need to upload your authority certificate(s) on the "Server" tab, to tell the connection which certificates to
+                    trust.  Upload your certificate using the browse button, and then click the "Add" button to add it to the trust store.</p>
 <p>The "Document Access" tab looks like this:</p>
 <br>
 <br>
@@ -2358,10 +2427,11 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Connection, Document Access tab" src="images/en_US/livelink-connection-document-access.PNG" width="80%"></div>
 <br>
 <br>
-<p>The server name is presumed to be the same as is on the "Server" tab.  Select the desired protocol.  If your LiveLink server is using a non-standard HTTP port for the specified protocol, enter the 
-                    port number.  If your LiveLink server is using NTLM authentication, enter an AD user name, password, and domain.  If your LiveLink is using HTTPS, browse locally for the appropriate
-                    certificate authority certificate, and click "Add" to upload that certificate to the connection's trust store.  (You may also use the server's certificate, but that is less resilient because the
-                    server's certificate may be changed periodically.)</p>
+<p>The server name is presumed to be the same as is on the "Server" tab.  Select the desired protocol for document retrieval.  If your LiveLink server
+                    is using a non-standard HTTP port for the specified protocol for document retrieval, enter the port number.  If your LiveLink server is using NTLM
+                    authentication to access documents, enter an Active Directory user name, password, and domain.  If your LiveLink is using HTTPS, browse locally
+                    for the appropriate certificate authority certificate, and click "Add" to upload that certificate to the connection's trust store.  (You may also use the server's
+                    certificate, but that is less resilient because the server's certificate may be changed periodically.)</p>
 <p>The "Document View" tab looks like this:</p>
 <br>
 <br>
@@ -2369,8 +2439,8 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Connection, Document Viewtab" src="images/en_US/livelink-connection-document-view.PNG" width="80%"></div>
 <br>
 <br>
-<p>If you want each document's view URL to be the same as its access URL, you can leave this tab unchanged.  If you want to direct users to a different CGI path when they view search results,
-                    you can specify that here.</p>
+<p>If you want each document's view URL to be the same as its access URL, you can leave this tab unchanged.  If you want to direct users to a different
+                    CGI path when they view search results, you can specify that here.</p>
 <p>When you are done, click the "Save" button.  You will see a summary screen that looks something like this:</p>
 <br>
 <br>
@@ -2378,7 +2448,8 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Connection Status" src="images/en_US/livelink-connection-status.PNG" width="80%"></div>
 <br>
 <br>
-<p>Make note of and correct any reported connection errors.  In this example, the connection has been correctly set up, so the connection status is "Connection working".</p>
+<p>Make note of and correct any reported connection errors.  In this example, the connection has been correctly set up, so the connection status is
+                    "Connection working".</p>
 <p></p>
 <p>A job created to use a LiveLink connection has the following additional tabs associated with it: "Paths", "Filters", "Security", and "Metadata".</p>
 <p>The "Paths" tab allows you to manage a list of LiveLink paths that act as starting points for indexing content:</p>
@@ -2388,11 +2459,12 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Job, Paths tab" src="images/en_US/livelink-job-paths.PNG" width="80%"></div>
 <br>
 <br>
-<p>Build each path by selecting from the available dropdown, and clicking the "+" button.  When your path is complete, click the "Add" button to add the path to the list of starting points.</p>
-<p>The "Filters" tab controls the criteria the LiveLink job will use to include or exclude content.  The filters are basically a list of rules.  Each rule has a document match field,
-                    and a matching action ("Include" or "Exclude").  When a LiveLink connection encounters a document, it evaluates the rules from top to bottom.
-                    If the rule matches, then it will be included or excluded from the job's document set depending on what you have selected for the matching action. A rule's match field specifies a
-                    character match, where "*" will match any number of characters, and "?" will match any single character.</p>
+<p>Build each path by selecting from the available dropdown, and clicking the "+" button.  When your path is complete, click the "Add" button to add the path
+                    to the list of starting points.</p>
+<p>The "Filters" tab controls the criteria the LiveLink job will use to include or exclude content.  The filters are basically a list of rules.  Each rule has a
+                    document match field, and a matching action ("Include" or "Exclude").  When a LiveLink connection encounters a document, it evaluates the rules from
+                    top to bottom.  If the rule matches, then it will be included or excluded from the job's document set depending on what you have selected for the
+                    matching action. A rule's match field specifies a character match, where "*" will match any number of characters, and "?" will match any single character.</p>
 <br>
 <br>
 <div id="" style="text-align: center;">
@@ -2408,8 +2480,8 @@ document.write("Last Published: " + docu
 <br>
 <br>
 <p>If you disable security, you can add your own access tokens to all
-                    jobs in the document set as they are indexed.  The format of the access tokens you would enter depends on the governing authority associated with the job's repository connection.
-                    Enter a token and click the "Add" button to add it to the list.</p>
+                    jobs in the document set as they are indexed.  The format of the access tokens you would enter depends on the governing authority associated with the
+                    job's repository connection. Enter a token and click the "Add" button to add it to the list.</p>
 <p>The "Metadata" tab allows you to select what specific metadata values from LiveLink you want to pass to the index:</p>
 <br>
 <br>
@@ -2417,19 +2489,21 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="LiveLink Job, Metadata tab" src="images/en_US/livelink-job-metadata.PNG" width="80%"></div>
 <br>
 <br>
-<p>If you want to pass all available LiveLink metadata to the index, then click the "All metadata" radio button.  Otherwise, you need to build LiveLink metadata paths and add them to the metadata list.
-                    Select the next metadata path segment, and click the appropriate "+" button to add it to the path.  You may add folder information, or a metadata category, at any point.</p>
-<p>Once you have drilled down to a metadata category, you can select the metadata attributes to include, or check the "All attributes in this category" checkbox.  When you are done, click the
-                    "Add" button to add the metadata attributes that you want to include in the index.</p>
-<p>You can also use the "Metadata" tab to have the connection send path data along with each document, as a piece of document metadata.  To enable this feature, enter the name of the metadata
-                    attribute you want this information to be sent into the "Path attribute name" field.  Then, add the rules you want to the list of rules.  Each rule has a match expression, which is a regular expression where
-                    parentheses ("(" and ")") mark sections you are interested in.  These sections are called "groups" in regular expression parlance.  The replace string consists of constant text plus
-                    substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the first match group
-                    mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
+<p>If you want to pass all available LiveLink metadata to the index, then click the "All metadata" radio button.  Otherwise, you need to build LiveLink
+                    metadata paths and add them to the metadata list. Select the next metadata path segment, and click the appropriate "+" button to add it to the path.
+                    You may add folder information, or a metadata category, at any point.</p>
+<p>Once you have drilled down to a metadata category, you can select the metadata attributes to include, or check the "All attributes in this category"
+                    checkbox.  When you are done, click the "Add" button to add the metadata attributes that you want to include in the index.</p>
+<p>You can also use the "Metadata" tab to have the connection send path data along with each document, as a piece of document metadata.  To enable
+                    this feature, enter the name of the metadata attribute you want this information to be sent into the "Path attribute name" field.  Then, add the rules you
+                    want to the list of rules.  Each rule has a match expression, which is a regular expression where parentheses ("(" and ")") mark sections you are
+                    interested in.  These sections are called "groups" in regular expression parlance.  The replace string consists of constant text plus
+                    substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the
+                    first match group mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
 <p>For example, suppose you had a rule which had ".*/(.*)/(.*)/.*" as a match expression, and "$(1) $(2)" as the replace string.  If presented with the path
                     <span class="codefrag">Project/Folder_1/Folder_2/Filename</span>, it would output the string <span class="codefrag">Folder_1 Folder_2</span>.</p>
 <p>If more than one rule is present, the rules are all executed in sequence.  That is, the output of the first rule is modified by the second rule, etc.</p>
-<a name="N10E6A"></a><a name="mexexrepository"></a>
+<a name="N10EC4"></a><a name="mexexrepository"></a>
 <h3 class="h4">Memex Patriarch Repository Connection</h3>
 <p>A Memex Patriarch connection allows you to index documents from a Memex server.</p>
 <p>Documents described by Memex connections are typically secured by a Memex authority.  If you have not yet created a Memex authority, but would like your
@@ -2463,7 +2537,7 @@ document.write("Last Published: " + docu
 <p></p>
 <p>Jobs based on Memex connections have the following special tabs: "Record Criteria", "Entities", and "Security".</p>
 <p>More here later</p>
-<a name="N10EAF"></a><a name="meridiorepository"></a>
+<a name="N10F09"></a><a name="meridiorepository"></a>
 <h3 class="h4">Autonomy Meridio Repository Connection</h3>
 <p>An Autonomy Meridio connection allows you to index documents from a set of Meridio servers.  Meridio's architecture allows you to separate services on multiple machines -
                     e.g. the document services can run on one machine, and the records services can run on another.  A Meridio connection type correspondingly is configured to describe each
@@ -2537,7 +2611,7 @@ document.write("Last Published: " + docu
 <p></p>
 <p>Jobs based on Meridio connections have the following special tabs: "Search Paths", "Content Types", "Categories", "Data Types", "Security", and "Metadata".</p>
 <p>More here later</p>
-<a name="N10F35"></a><a name="sharepointrepository"></a>
+<a name="N10F8F"></a><a name="sharepointrepository"></a>
 <h3 class="h4">Microsoft SharePoint Repository Connection</h3>
 <p>The Microsoft SharePoint connection type allows you to index documents from a Microsoft SharePoint site.  Bear in mind that a single SharePoint installation actually represents
                     a set of sites.  Some sites
@@ -2732,7 +2806,7 @@ document.write("Last Published: " + docu
 <li>We can include all metadata using the checkbox. (without selecting from the pulldown list)</li>                    
                 
 </ul>
-<a name="N1108F"></a><a name="cmisrepository"></a>
+<a name="N110E9"></a><a name="cmisrepository"></a>
 <h3 class="h4">CMIS Repository Connection</h3>
 <p>The CMIS Repository Connection type allows you to index content from any CMIS-compliant repository.</p>
 <p>By default each CMIS Connection manages a single CMIS repository, this means that if you have multiple CMIS repositories exposed by a single endpoint, you need to create a specific connection for each CMIS repository.</p>
@@ -2791,7 +2865,7 @@ document.write("Last Published: " + docu
 <img id="" class="figure" alt="CMIS Repository Connection, saving job" src="images/en_US/cmis-repository-connection-job-save.png" width="80%"></div>
 <br>
 <br>
-<a name="N11108"></a><a name="alfrescorepository"></a>
+<a name="N11162"></a><a name="alfrescorepository"></a>
 <h3 class="h4">Alfresco Repository Connection</h3>
 <p>The Alfresco Repository Connection type allows you to index content from an Alfresco repository.</p>
 <p>This connector is compatible with any Alfresco version (2.x, 3.x and 4.x).</p>

Modified: manifoldcf/site/publish/release/trunk/en_US/end-user-documentation.pdf
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/end-user-documentation.pdf?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
Binary files - no diff available.

Modified: manifoldcf/site/publish/release/trunk/en_US/how-to-build-and-deploy.html
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/how-to-build-and-deploy.html?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
--- manifoldcf/site/publish/release/trunk/en_US/how-to-build-and-deploy.html (original)
+++ manifoldcf/site/publish/release/trunk/en_US/how-to-build-and-deploy.html Sat Mar 30 20:56:07 2013
@@ -478,9 +478,9 @@ document.write("Last Published: " + docu
 <p>This connector needs OpenText's LAPI package in order to be run.  It is usually built against a set of stubs. The stubs, however, mimic the
               class structure of LAPI 9.7.1.  Later versions (such as 10.x) have a different class structure.  Therefore, you may need to rebuild ManifoldCF
               against your lapi.jar, in order for the connector to work properly.</p>
-<p>If you need to supply your own lapi.jar at build time, copy it to the source directory <em>connectors/livelink/lib-proprietary</em>, and build using "ant build".
+<p>If you need to supply your own lapi.jar and llssl.jar at build time, copy it to the source directory <em>connectors/livelink/lib-proprietary</em>, and build using "ant build".
               The lapi.jar will be copied into the right place in your <em>dist</em> directory automatically.</p>
-<p>If you do not wish to build, simply copy your lapi.jar into the binary distribution's <em>connector-lib-proprietary</em>
+<p>If you do not wish to build, simply copy your lapi.jar and llssl.jar into the binary distribution's <em>connector-lib-proprietary</em>
               directory, and uncomment the LiveLink-related connector lines in <em>connectors.xml</em> file.</p>
 <p></p>
 <a name="N1018E"></a><a name="Building+the+Meridio+connector"></a>

Added: manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-authority-cache.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-authority-cache.PNG?rev=1462853&view=auto
==============================================================================
Binary file - no diff available.

Propchange: manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-authority-cache.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Modified: manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-authority-server.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-authority-server.PNG?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
Binary files - no diff available.

Modified: manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-connection-server.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/livelink-connection-server.PNG?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
Binary files - no diff available.

Modified: manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-schema.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-schema.PNG?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
Binary files - no diff available.

Modified: manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-server.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-server.PNG?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
Binary files - no diff available.

Added: manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-solr-type.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-solr-type.PNG?rev=1462853&view=auto
==============================================================================
Binary file - no diff available.

Propchange: manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-solr-type.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-zookeeper.PNG
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-zookeeper.PNG?rev=1462853&view=auto
==============================================================================
Binary file - no diff available.

Propchange: manifoldcf/site/publish/release/trunk/en_US/images/en_US/solr-configure-zookeeper.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Modified: manifoldcf/site/publish/release/trunk/ja_JP/end-user-documentation.pdf
URL: http://svn.apache.org/viewvc/manifoldcf/site/publish/release/trunk/ja_JP/end-user-documentation.pdf?rev=1462853&r1=1462852&r2=1462853&view=diff
==============================================================================
Binary files - no diff available.



Mime
View raw message