You are viewing a plain text version of this content. The canonical link for it is here.
Posted to commits@manifoldcf.apache.org by kw...@apache.org on 2010/10/05 03:38:44 UTC
svn commit: r1004501 - in /incubator/lcf/site: publish/ publish/images/
src/documentation/ src/documentation/content/xdocs/
src/documentation/resources/images/
Author: kwright
Date: Tue Oct 5 01:38:43 2010
New Revision: 1004501
URL: http://svn.apache.org/viewvc?rev=1004501&view=rev
Log:
Update site because of name change to ManifoldCF
Added:
incubator/lcf/site/publish/images/ManifoldCF-logo.PNG (with props)
incubator/lcf/site/src/documentation/resources/images/ManifoldCF-Logo.PNG
- copied, changed from r1004494, incubator/lcf/site/src/documentation/resources/images/ACF-logo.PNG
Removed:
incubator/lcf/site/publish/images/ACF-logo.PNG
incubator/lcf/site/src/documentation/resources/images/ACF-logo.PNG
Modified:
incubator/lcf/site/publish/developer-resources.html
incubator/lcf/site/publish/developer-resources.pdf
incubator/lcf/site/publish/end-user-documentation.html
incubator/lcf/site/publish/end-user-documentation.pdf
incubator/lcf/site/publish/faq.html
incubator/lcf/site/publish/faq.pdf
incubator/lcf/site/publish/index.html
incubator/lcf/site/publish/index.pdf
incubator/lcf/site/publish/linkmap.html
incubator/lcf/site/publish/linkmap.pdf
incubator/lcf/site/publish/mail.html
incubator/lcf/site/publish/mail.pdf
incubator/lcf/site/publish/who.html
incubator/lcf/site/publish/who.pdf
incubator/lcf/site/src/documentation/content/xdocs/developer-resources.xml
incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml
incubator/lcf/site/src/documentation/content/xdocs/index.xml
incubator/lcf/site/src/documentation/content/xdocs/mail.xml
incubator/lcf/site/src/documentation/skinconf.xml
Modified: incubator/lcf/site/publish/developer-resources.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/developer-resources.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/developer-resources.html (original)
+++ incubator/lcf/site/publish/developer-resources.html Tue Oct 5 01:38:43 2010
@@ -5,7 +5,7 @@
<meta content="Apache Forrest" name="Generator">
<meta name="Forrest-version" content="0.9-dev">
<meta name="Forrest-skin-name" content="lucene">
-<title>Apache Lucene Connectors Framework - Developer Resources</title>
+<title>ManifoldCF - Developer Resources</title>
<link type="text/css" href="skin/basic.css" rel="stylesheet">
<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
@@ -186,14 +186,14 @@ document.write("Last Published: " + docu
<a class="dida" href="developer-resources.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
PDF</a>
</div>
-<h1>Apache Lucene Connectors Framework - Developer Resources</h1>
+<h1>ManifoldCF - Developer Resources</h1>
<div id="minitoc-area">
<ul class="minitoc">
<li>
<a href="#source">Source Code</a>
</li>
<li>
-<a href="#understandingACF">Familiarize Yourself with the Concepts and Terminology</a>
+<a href="#understandingManifoldCF">Familiarize Yourself with the Concepts and Terminology</a>
</li>
<li>
<a href="#howtobuilddeploy">How to Build and Deploy</a>
@@ -229,20 +229,20 @@ document.write("Last Published: " + docu
<a name="N1000D"></a><a name="source"></a>
<h2 class="h3">Source Code</h2>
<div class="section">
-<p>The source files are now stored using Subversion (see http://subversion.tigris.org/ and http://svnbook.red-bean.com/)
+<p>The source files are stored using Subversion (see http://subversion.tigris.org/ and http://svnbook.red-bean.com/)
</p>
<p>
-<span class="codefrag">svn checkout http://svn.apache.org/repos/asf/incubator/lcf/trunk lcf-trunk</span>
+<span class="codefrag">svn checkout http://svn.apache.org/repos/asf/incubator/lcf/trunk mcf-trunk</span>
</p>
</div>
-<a name="N1001D"></a><a name="understandingACF"></a>
+<a name="N1001D"></a><a name="understandingManifoldCF"></a>
<h2 class="h3">Familiarize Yourself with the Concepts and Terminology</h2>
<div class="section">
-<p>Like any software project, ACF has its own underlying concepts and terminology. Read about that <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Lucene+Connectors+Framework+concepts">here</a>.
+<p>Like any software project, ManifoldCF has its own underlying concepts and terminology. Read about that <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/ManifoldCF+concepts">here</a>.
</p>
</div>
@@ -250,7 +250,7 @@ document.write("Last Published: " + docu
<a name="N1002B"></a><a name="howtobuilddeploy"></a>
<h2 class="h3">How to Build and Deploy</h2>
<div class="section">
-<p>Building ACF requires ant 1.7 or greater. Instructions for building and deploying can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Build+and+Deploy+Lucene+Connectors+Framework">here</a>.
+<p>Building ManifoldCF requires ant 1.7 or greater. Instructions for building and deploying can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Build+and+Deploy+ManifoldCF">here</a>.
</p>
</div>
@@ -258,7 +258,7 @@ document.write("Last Published: " + docu
<a name="N10039"></a><a name="howtointegrate"></a>
<h2 class="h3">How to Integrate</h2>
<div class="section">
-<p>ACF provides a number of API's and services. Documentation of these API's can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Programmatic+Operation+of+LCF">here</a>.
+<p>ManifoldCF provides a number of API's and services. Documentation of these API's can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Programmatic+Operation+of+ManifoldCF">here</a>.
</p>
</div>
@@ -266,18 +266,18 @@ document.write("Last Published: " + docu
<a name="N10047"></a><a name="securityarchitecturediagrams"></a>
<h2 class="h3">Security Architecture Diagrams</h2>
<div class="section">
-<p>For those who prefer a pictorial representation of ACF's security architecture, this might help.</p>
+<p>For those who prefer a pictorial representation of ManifoldCF's security architecture, this might help.</p>
<br>
<br>
<div id="" style="text-align: center;">
-<img id="" class="figure" alt="ACF Security Architecture" src="images/SecurityArchitecture.png" width="80%"></div>
+<img id="" class="figure" alt="ManifoldCF Security Architecture" src="images/SecurityArchitecture.png" width="80%"></div>
<br>
<br>
<p>If you are using Apache to perform authentication, the model is slightly different.</p>
<br>
<br>
<div id="" style="text-align: center;">
-<img id="" class="figure" alt="ACF Security Architecture, with Apache" src="images/LCFApacheArchitecture.png" width="80%"></div>
+<img id="" class="figure" alt="ManifoldCF Security Architecture, with Apache" src="images/LCFApacheArchitecture.png" width="80%"></div>
<br>
<br>
</div>
@@ -286,11 +286,11 @@ document.write("Last Published: " + docu
<a name="N1006A"></a><a name="processarchitecturediagrams"></a>
<h2 class="h3">Process Architecture Diagrams</h2>
<div class="section">
-<p>A pictorial representation of ACF's process architecture is below.</p>
+<p>A pictorial representation of ManifoldCF's process architecture is below.</p>
<br>
<br>
<div id="" style="text-align: center;">
-<img id="" class="figure" alt="ACF Process Architecture" src="images/LCFProcessArchitecture.png" width="80%"></div>
+<img id="" class="figure" alt="ManifoldCF Process Architecture" src="images/LCFProcessArchitecture.png" width="80%"></div>
<br>
<br>
</div>
@@ -299,7 +299,7 @@ document.write("Last Published: " + docu
<a name="N1007F"></a><a name="howtowriteconnectors"></a>
<h2 class="h3">How to Write Connectors</h2>
<div class="section">
-<p>Writing connectors for ACF is a great way to learn about the project and contribute something useful! Read about how to do that by navigating to the links provided below.
+<p>Writing connectors for ManifoldCF is a great way to learn about the project and contribute something useful! Read about how to do that by navigating to the links provided below.
</p>
<ul>
@@ -322,7 +322,7 @@ document.write("Last Published: " + docu
<a name="N1009B"></a><a name="debugging"></a>
<h2 class="h3">Debugging Connections</h2>
<div class="section">
-<p>Sooner or later, you will encounter a repository that should be supported, but doesn't seem to want to connect properly to ACF. When that happens, you will need all the help you
+<p>Sooner or later, you will encounter a repository that should be supported, but doesn't seem to want to connect properly to ManifoldCF. When that happens, you will need all the help you
can get. Start <a href="https://cwiki.apache.org/confluence/display/CONNECTORS/Debugging+Connections">here</a>, and if you find a new hint, technique,
or trick, don't forget to add it to the page!</p>
</div>
@@ -350,7 +350,7 @@ document.write("Last Published: " + docu
<a name="N100C8"></a><a name="Making a Contribution"></a>
<h2 class="h3">Making a Contribution</h2>
<div class="section">
-<p>ACF is always looking for contributions, especially in the areas of documentation. See the <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/HowToContribute">Wiki</a> for details on contributing. </p>
+<p>ManifoldCF is always looking for contributions. See the <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/HowToContribute">Wiki</a> for details on contributing. </p>
<p>We're also looking for logo ideas. Here are the <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Logo+Criteria">guidelines</a>.
</p>
</div>
Modified: incubator/lcf/site/publish/developer-resources.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/developer-resources.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/end-user-documentation.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/end-user-documentation.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/end-user-documentation.html (original)
+++ incubator/lcf/site/publish/end-user-documentation.html Tue Oct 5 01:38:43 2010
@@ -5,7 +5,7 @@
<meta content="Apache Forrest" name="Generator">
<meta name="Forrest-version" content="0.9-dev">
<meta name="Forrest-skin-name" content="lucene">
-<title>Apache Connectors Framework- End-user Documentation</title>
+<title>ManifoldCF- End-user Documentation</title>
<link type="text/css" href="skin/basic.css" rel="stylesheet">
<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
@@ -186,7 +186,7 @@ document.write("Last Published: " + docu
<a class="dida" href="end-user-documentation.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
PDF</a>
</div>
-<h1>Apache Connectors Framework- End-user Documentation</h1>
+<h1>ManifoldCF- End-user Documentation</h1>
<div id="minitoc-area">
<ul class="minitoc">
<li>
@@ -319,14 +319,14 @@ document.write("Last Published: " + docu
<a name="N1000D"></a><a name="overview"></a>
<h2 class="h3">Overview</h2>
<div class="section">
-<p>This manual is intended for an end-user of Apache Connectors Framework. It is assumed that the Framework has been properly installed, either by you or by a system integrator,
+<p>This manual is intended for an end-user of ManifoldCF. It is assumed that the Framework has been properly installed, either by you or by a system integrator,
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 Apache Connectors Framework user interface. On a standard Apache Connectors Framework deployment, you would reach that interface by giving your browser
- a URL something like this: <span class="codefrag">http://my-server-name:8080/lcf-crawler-ui</span>. This will, of course, differ from system to system. Please contact your system administrator
+<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
to find out what URL is appropriate for your environment.
</p>
-<p>The Apache Connectors Framework 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
+<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
will not work properly. Please let your system integrator know if you find any browser incompatibility problems.</p>
<p>When you do manage to enter the Framework user interface the first time, you should see a screen that looks something like this:</p>
<br>
@@ -523,14 +523,14 @@ document.write("Last Published: " + docu
will work correctly.</p>
<a name="N1015E"></a><a name="jobs"></a>
<h3 class="h4">Creating Jobs</h3>
-<p>A "job" in Apache Connectors Framework is a description of a set of documents. The Framework's job is to fetch this set of documents come from a specific repository connection, and
+<p>A "job" in ManifoldCF is a description of a set of documents. The Framework's job is to fetch this set of documents come from a specific repository connection, and
send them to a specific output connection. The repository connection that is associated with the job will determine exactly how this set of documents is described, and to some
degree how they are indexed. The output connection associated with the job can also affect how each document is indexed.</p>
<p>Every job is expected to be run more than once. Each time a job is run, it is responsible not only for sending new or changed documents to the output connection, but also for
notifying the output connection of any documents that are no longer part of the set. Note that there are two ways for a document to no longer be part of the included set of documents:
Either the document may have been deleted from the repository, or the document may no longer be included in the allowed set of documents. The Framework handles each case properly.</p>
<p>Deleting a job causes the output connection to be notified of deletion for all documents belonging to that job. This makes sense because the job represents the set of documents, which would
- otherwise be orphaned when the job was removed. (Some users make the assumption that a Apache Connectors Framework job represents nothing more than a task, which is an incorrect
+ otherwise be orphaned when the job was removed. (Some users make the assumption that a ManifoldCF job represents nothing more than a task, which is an incorrect
assumption.)</p>
<p>Note that the Framework allows jobs that describe overlapping sets of documents to be defined. Documents that exist in more than one job are treated in the following special ways:</p>
<ul>
@@ -562,7 +562,7 @@ document.write("Last Published: " + docu
<p>Note that continuous jobs <b>cannot</b> remove no-longer-included documents from the queue. They can only remove documents that have been deleted from the repository.</p>
<p>A job can independently be configured to start when explicitly started by a user, or to run on a user-specified schedule. If a job is set up to run on a schedule, it can be made to
start only at the beginning of a schedule window, or to start again within any remaining schedule window when the previous job run completes.</p>
-<p>There is no restriction in Apache Connectors Framework as to how many jobs many running at any given time.</p>
+<p>There is no restriction in ManifoldCF as to how many jobs many running at any given time.</p>
<p>You create a job by first clicking on the "List All Jobs" link on the left-side menu. The following screen will appear:</p>
<br>
<br>
@@ -661,7 +661,7 @@ document.write("Last Published: " + docu
queue for the job that have been processed at least once in the past.</p>
<a name="N1024E"></a><a name="statusreports"></a>
<h3 class="h4">Status Reports</h3>
-<p>Every job in Apache Connectors Framework describes a set of documents. A reference to each document in the set is kept in a job-specific queue. It is sometimes valuable for
+<p>Every job in ManifoldCF describes a set of documents. A reference to each document in the set is kept in a job-specific queue. It is sometimes valuable for
diagnostic reasons to examine this queue for information. The Framework UI has several canned reports which do just that.</p>
<p>Each status report allows you to select what documents you are interested in from a job's queue based on the following information:</p>
<ul>
@@ -737,7 +737,7 @@ document.write("Last Published: " + docu
up and down through the results using the "Prev" and "Next" links.</p>
<a name="N102DB"></a><a name="historyreports"></a>
<h3 class="h4">History Reports</h3>
-<p>For every repository connection, Apache Connectors Framework keeps a history of what has taken place involving that connection. This history includes both events that the
+<p>For every repository connection, ManifoldCF keeps a history of what has taken place involving that connection. This history includes both events that the
framework itself logs, as well as events that a repository connection or output connection will log. These individual events are categorized by "activity type". Some of the kinds of
activity types that exist are:</p>
<ul>
@@ -829,7 +829,7 @@ document.write("Last Published: " + docu
<div class="section">
<a name="N10381"></a><a name="solroutputconnector"></a>
<h3 class="h4">Solr Output Connection</h3>
-<p>The Solr output connection type is designed to allow Apache Connectors Framework to submit documents to an appropriate Solr pipeline, via the Solr
+<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
@@ -887,7 +887,7 @@ document.write("Last Published: " + docu
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="N103E0"></a><a name="gtsoutputconnector"></a>
<h3 class="h4">MetaCarta GTS Output Connection</h3>
-<p>The MetaCarta GTS output connection type is designed to allow Apache Connectors Framework to submit documents to an appropriate MetaCarta GTS search
+<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>
<p>The connection type implicitly understands that GTS can only handle text, HTML, XML, RTF, PDF, and Microsoft Office documents. All other document types will be
considered to be unindexable. This helps prevent jobs based on a GTS-type output connection from fetching data that is large, but of no particular relevance.</p>
@@ -983,7 +983,7 @@ document.write("Last Published: " + docu
<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.
In addition, you can also specify whether or not you wish to include auto-generated ACLs in every user's list. Auto-generated ACLs are created within Documentum for every folder
- object. Because there are often a very large number of folders, including these ACLs can bloat the number of ACF access tokens returned for a user to tens of thousands, which can negatively
+ object. Because there are often a very large number of folders, including these ACLs can bloat the number of ManifoldCF access tokens returned for a user to tens of thousands, which can negatively
impact perfomance. Even more notably, few Documentum installations make any real use of these ACLs in any way. Since Documentum's ACLs are purely additive (that is, there are no
mechanisms for 'deny' semantics), the impact of a missing ACLs is only to block a user from seeing something they otherwise could see. It is thus safe, and often desirable, to simply ignore the
existence of these auto-generated ACLs.</p>
@@ -1131,13 +1131,13 @@ document.write("Last Published: " + docu
<li>Windows security event logs</li>
-<li>ACF logs (see below)</li>
+<li>ManifoldCF logs (see below)</li>
<li>Packet captures (using a tool such as WireShark)</li>
</ul>
<br>
-<p>If you need specific ACF logging information, contact your system integrator.</p>
+<p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
</div>
@@ -1147,7 +1147,7 @@ document.write("Last Published: " + docu
<a name="N105C3"></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 Apache Connectors Framework is running on. Bear in mind that there is no support in this connection type for any kind of
+ 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
security, and the options are somewhat limited.</p>
<p>The file system repository connection type provides no configuration tabs beyond the standard ones. However, please consider setting a "Maximum connections per
JVM" value on the "Throttling" tab to at least one per worker thread, or 30, for best performance.</p>
@@ -2244,13 +2244,13 @@ document.write("Last Published: " + docu
<li>Windows security event logs</li>
-<li>ACF logs (see below)</li>
+<li>ManifoldCF logs (see below)</li>
<li>Packet captures (using a tool such as WireShark)</li>
</ul>
<br>
-<p>If you need specific ACF logging information, contact your system integrator.</p>
+<p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
<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>
@@ -2261,7 +2261,7 @@ document.write("Last Published: " + docu
in SharePoint are directly related to others (e.g. they are subsites), while some sites operate relatively independently of one another.</p>
<p>The SharePoint connection type is designed so that one SharePoint repository connection can access all SharePoint sites from a specific root site though its explicit subsites.
It is the case
- that it is desirable in some very large SharePoint installations to access <b>all</b> SharePoint sites using a single connection. But the ACF SharePoint connection type today
+ that it is desirable in some very large SharePoint installations to access <b>all</b> SharePoint sites using a single connection. But the ManifoldCF SharePoint connection type today
does not support
that model as of yet. If this functionality is important for you, contact your system integrator.</p>
<p>SharePoint uses a web URL model for addressing sites, subsites, libraries, and files. The best way to figure out how to set up a SharePoint connection type is therefore to start
@@ -2302,13 +2302,13 @@ document.write("Last Published: " + docu
<li>Windows security event logs</li>
-<li>ACF logs (see below)</li>
+<li>ManifoldCF logs (see below)</li>
<li>Packet captures (using a tool such as WireShark)</li>
</ul>
<br>
-<p>If you need specific ACF logging information, contact your system integrator.</p>
+<p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
<p></p>
<p>When you configure a job to use a repository connection of the generic database type, several additional tabs are presented. These are, in order, "Paths", "Security", and "Metadata".</p>
<p>The "Paths" tab allows you to build a list of rules describing the SharePoint content that you want to include in your job. When the SharePoint connection type encounters a subsite,
Modified: incubator/lcf/site/publish/end-user-documentation.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/end-user-documentation.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Files incubator/lcf/site/publish/end-user-documentation.pdf (original) and incubator/lcf/site/publish/end-user-documentation.pdf Tue Oct 5 01:38:43 2010 differ
Modified: incubator/lcf/site/publish/faq.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/faq.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/faq.html (original)
+++ incubator/lcf/site/publish/faq.html Tue Oct 5 01:38:43 2010
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
Modified: incubator/lcf/site/publish/faq.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/faq.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Files incubator/lcf/site/publish/faq.pdf (original) and incubator/lcf/site/publish/faq.pdf Tue Oct 5 01:38:43 2010 differ
Added: incubator/lcf/site/publish/images/ManifoldCF-logo.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/ManifoldCF-logo.PNG?rev=1004501&view=auto
==============================================================================
Binary file - no diff available.
Propchange: incubator/lcf/site/publish/images/ManifoldCF-logo.PNG
------------------------------------------------------------------------------
svn:mime-type = application/octet-stream
Modified: incubator/lcf/site/publish/index.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/index.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/index.html (original)
+++ incubator/lcf/site/publish/index.html Tue Oct 5 01:38:43 2010
@@ -5,7 +5,7 @@
<meta content="Apache Forrest" name="Generator">
<meta name="Forrest-version" content="0.9-dev">
<meta name="Forrest-skin-name" content="lucene">
-<title>Welcome to Apache Connectors Framework!</title>
+<title>Welcome to ManifoldCF!</title>
<link type="text/css" href="skin/basic.css" rel="stylesheet">
<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
@@ -189,14 +189,14 @@ document.write("Last Published: " + docu
<a class="dida" href="index.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
PDF</a>
</div>
-<h1>Welcome to Apache Connectors Framework!</h1>
+<h1>Welcome to ManifoldCF!</h1>
<div id="minitoc-area">
<ul class="minitoc">
<li>
<a href="#Incubation+Status">Incubation Status</a>
</li>
<li>
-<a href="#What+Is+the+Apache+Connectors+Framework%3F">What Is the Apache Connectors Framework?</a>
+<a href="#What+Is+ManifoldCF%3F">What Is ManifoldCF?</a>
</li>
<li>
<a href="#Project+status">Project status</a>
@@ -208,6 +208,9 @@ document.write("Last Published: " + docu
<a href="#News">News</a>
<ul class="minitoc">
<li>
+<a href="#03+October+2010+-+Apache+Connectors+Framework+officially+becomes+Apache+ManifoldCF">03 October 2010 - Apache Connectors Framework officially becomes Apache ManifoldCF</a>
+</li>
+<li>
<a href="#19+August+2010+-+Lucene+Connectors+Framework+officially+becomes+Apache+Connectors+Framework">19 August 2010 - Lucene Connectors Framework officially becomes Apache Connectors Framework</a>
</li>
<li>
@@ -227,31 +230,31 @@ document.write("Last Published: " + docu
<a name="N1000D"></a><a name="Incubation+Status"></a>
<h2 class="h3">Incubation Status</h2>
<div class="section">
-<p>Apache Connectors Framework (ACF) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Lucene PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+<p>ManifoldCF (formerly Apache Connectors Framework) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Lucene PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
</p>
</div>
-<a name="N10017"></a><a name="What+Is+the+Apache+Connectors+Framework%3F"></a>
-<h2 class="h3">What Is the Apache Connectors Framework?</h2>
+<a name="N10017"></a><a name="What+Is+ManifoldCF%3F"></a>
+<h2 class="h3">What Is ManifoldCF?</h2>
<div class="section">
-<p>The Apache Connectors Framework (ACF) is an effort to provide build and support an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr. ACF also defines a security model for target repositories that permits them to enforce source-repository security policies.</p>
+<p>ManifoldCF is an effort to provide build and support an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr. ACF also defines a security model for target repositories that permits them to enforce source-repository security policies.</p>
<p>Currently included connectors support FileNet P8 (IBM), Documentum (EMC), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), Windows shares (Microsoft), and SharePoint (Microsoft). Also included are a general file system connector, a general JDBC connector, a general RSS crawler, and a general web crawler. Currently supported targets include Apache Solr and QBase (formerly MetaCarta) GTS. The complete repository compatibility list can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/SupportedConnectors">here</a>.</p>
-<p>The original ACF code base was granted by MetaCarta, Inc., to the Apache Software Foundation in December 2009. The MetaCarta effort represented more than five years of successful development and testing in multiple, challenging enterprise environments.</p>
+<p>The original ManifoldCF code base was granted by MetaCarta, Inc., to the Apache Software Foundation in December 2009. The MetaCarta effort represented more than five years of successful development and testing in multiple, challenging enterprise environments.</p>
</div>
<a name="N1002B"></a><a name="Project+status"></a>
<h2 class="h3">Project status</h2>
<div class="section">
-<p>There are currently no released versions of ACF available, although one is planned However, a trunk svn checkout has been built and successfully hand-tested. Nightly builds and online javadoc will be coming shortly.</p>
+<p>There are currently no released versions of ManifoldCF available, although one is planned However, a trunk svn checkout has been built and successfully hand-tested. Nightly builds and online javadoc will be coming shortly.</p>
</div>
<a name="N10035"></a><a name="A+philosophical+note+about+third-party+repositories"></a>
<h2 class="h3">A philosophical note about third-party repositories</h2>
<div class="section">
-<p>Many of the connectors included with ACF currently require third-party libraries, packages, or other licensed materials in order to be built. The code for these connectors can be distributed under Apache guidelines because they are conditionally compiled; that is, you as a developer must supply the necessary third-party components before the connector will build. While we have every intention of trying to reduce the number of affected connectors by means of clean-room development under the auspices of ASF, realistically the current situation will not change in any dramatic way very quickly. The focus of this group remains primarily on providing solutions.</p>
+<p>Many of the connectors included with ManifoldCF currently require third-party libraries, packages, or other licensed materials in order to be built. The code for these connectors can be distributed under Apache guidelines because they are conditionally compiled; that is, you as a developer must supply the necessary third-party components before the connector will build. While we have every intention of trying to reduce the number of affected connectors by means of clean-room development under the auspices of ASF, realistically the current situation will not change in any dramatic way very quickly. The focus of this group remains primarily on providing solutions.</p>
<p>The required libraries, tools, and procedures for building each of these connectors are well documented in the Wiki pages for this project.</p>
</div>
@@ -259,16 +262,19 @@ document.write("Last Published: " + docu
<a name="N10042"></a><a name="News"></a>
<h2 class="h3">News</h2>
<div class="section">
-<a name="N10048"></a><a name="19+August+2010+-+Lucene+Connectors+Framework+officially+becomes+Apache+Connectors+Framework"></a>
+<a name="N10048"></a><a name="03+October+2010+-+Apache+Connectors+Framework+officially+becomes+Apache+ManifoldCF"></a>
+<h3 class="h4">03 October 2010 - Apache Connectors Framework officially becomes Apache ManifoldCF</h3>
+<p>Developer community approves second name change</p>
+<a name="N10052"></a><a name="19+August+2010+-+Lucene+Connectors+Framework+officially+becomes+Apache+Connectors+Framework"></a>
<h3 class="h4">19 August 2010 - Lucene Connectors Framework officially becomes Apache Connectors Framework</h3>
<p>Developer community approves name change</p>
-<a name="N10052"></a><a name="07+July+2010+-+Lucene+Connectors+Framework+first+release+proposed"></a>
+<a name="N1005C"></a><a name="07+July+2010+-+Lucene+Connectors+Framework+first+release+proposed"></a>
<h3 class="h4">07 July 2010 - Lucene Connectors Framework first release proposed</h3>
<p>Criteria for LCF's first official release proposed</p>
-<a name="N1005C"></a><a name="21+May+2010+-+Lucene+Connectors+Framework+in+Prague"></a>
+<a name="N10066"></a><a name="21+May+2010+-+Lucene+Connectors+Framework+in+Prague"></a>
<h3 class="h4">21 May 2010 - Lucene Connectors Framework in Prague</h3>
<p>LCF introductory talk planned for Lucene/Solr Eurocon, Prague, Czech Republic</p>
-<a name="N10066"></a><a name="12+January+2010+-+Lucene+Connectors+Framework+launches%21"></a>
+<a name="N10070"></a><a name="12+January+2010+-+Lucene+Connectors+Framework+launches%21"></a>
<h3 class="h4">12 January 2010 - Lucene Connectors Framework launches!</h3>
<p>LCF officially becomes an incubating project of the Apache Software Foundation</p>
</div>
Modified: incubator/lcf/site/publish/index.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/index.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/linkmap.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/linkmap.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/linkmap.html (original)
+++ incubator/lcf/site/publish/linkmap.html Tue Oct 5 01:38:43 2010
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
Modified: incubator/lcf/site/publish/linkmap.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/linkmap.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/mail.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/mail.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/mail.html (original)
+++ incubator/lcf/site/publish/mail.html Tue Oct 5 01:38:43 2010
@@ -5,7 +5,7 @@
<meta content="Apache Forrest" name="Generator">
<meta name="Forrest-version" content="0.9-dev">
<meta name="Forrest-skin-name" content="lucene">
-<title>Apache Connectors Framework - Mailing Lists</title>
+<title>ManifoldCF - Mailing Lists</title>
<link type="text/css" href="skin/basic.css" rel="stylesheet">
<link media="screen" type="text/css" href="skin/screen.css" rel="stylesheet">
<link media="print" type="text/css" href="skin/print.css" rel="stylesheet">
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
@@ -186,32 +186,32 @@ document.write("Last Published: " + docu
<a class="dida" href="mail.pdf"><img alt="PDF -icon" src="skin/images/pdfdoc.gif" class="skin"><br>
PDF</a>
</div>
-<h1>Apache Connectors Framework - Mailing Lists</h1>
+<h1>ManifoldCF - Mailing Lists</h1>
<div id="minitoc-area">
<ul class="minitoc">
<li>
-<a href="#ACF Mailing Lists">ACF Mailing Lists</a>
+<a href="#ACF Mailing Lists">ManifoldCF Mailing Lists</a>
</li>
<li>
-<a href="#user">ACF User Mailing List</a>
+<a href="#user">ManifoldCF User Mailing List</a>
</li>
<li>
-<a href="#dev">ACF Development Mailing List</a>
+<a href="#dev">ManifoldCF Development Mailing List</a>
</li>
<li>
-<a href="#commits">ACF Commits Mailing List</a>
+<a href="#commits">ManifoldCF Commits Mailing List</a>
</li>
</ul>
</div>
<a name="N1000C"></a><a name="ACF Mailing Lists"></a>
-<h2 class="h3">ACF Mailing Lists</h2>
+<h2 class="h3">ManifoldCF Mailing Lists</h2>
<div class="section">
-<p>The Apache Connectors Framework supports several mailing lists.</p>
+<p>The ManifoldCF project supports several mailing lists.</p>
</div>
<a name="N10015"></a><a name="user"></a>
-<h2 class="h3">ACF User Mailing List</h2>
+<h2 class="h3">ManifoldCF User Mailing List</h2>
<div class="section">
<p>User questions on how to use ACF.</p>
<ul>
@@ -232,9 +232,9 @@ document.write("Last Published: " + docu
</div>
<a name="N10030"></a><a name="dev"></a>
-<h2 class="h3">ACF Development Mailing List</h2>
+<h2 class="h3">ManifoldCF Development Mailing List</h2>
<div class="section">
-<p>Discussion on the development of the internals of ACF.</p>
+<p>Discussion on the development of the internals of ManifoldCF.</p>
<ul>
<li>
@@ -253,7 +253,7 @@ document.write("Last Published: " + docu
</div>
<a name="N1004B"></a><a name="commits"></a>
-<h2 class="h3">ACF Commits Mailing List</h2>
+<h2 class="h3">ManifoldCF Commits Mailing List</h2>
<div class="section">
<p>Commit messages</p>
<ul>
Modified: incubator/lcf/site/publish/mail.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/mail.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/publish/who.html
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/who.html?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/publish/who.html (original)
+++ incubator/lcf/site/publish/who.html Tue Oct 5 01:38:43 2010
@@ -39,7 +39,7 @@
|start Project Logo
+-->
<div class="projectlogo">
-<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache Connectors Framework" src="images/ACF-logo.PNG" title="Connectors Framework"></a>
+<a href="http://incubator.apache.org/lcf"><img class="logoImage" alt="Apache ManifoldCF" src="images/ManifoldCF-logo.PNG" title="ManifoldCF"></a>
</div>
<!--+
|end Project Logo
Modified: incubator/lcf/site/publish/who.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/who.pdf?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/src/documentation/content/xdocs/developer-resources.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/content/xdocs/developer-resources.xml?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/src/documentation/content/xdocs/developer-resources.xml (original)
+++ incubator/lcf/site/src/documentation/content/xdocs/developer-resources.xml Tue Oct 5 01:38:43 2010
@@ -1,60 +1,60 @@
<?xml version="1.0"?>
<document>
-<header><title>Apache Lucene Connectors Framework - Developer Resources</title></header>
+<header><title>ManifoldCF - Developer Resources</title></header>
<properties>
</properties>
<body>
<section id="source">
<title>Source Code</title>
- <p>The source files are now stored using Subversion (see http://subversion.tigris.org/ and http://svnbook.red-bean.com/)
+ <p>The source files are stored using Subversion (see http://subversion.tigris.org/ and http://svnbook.red-bean.com/)
</p>
<p>
- <code>svn checkout http://svn.apache.org/repos/asf/incubator/lcf/trunk lcf-trunk</code>
+ <code>svn checkout http://svn.apache.org/repos/asf/incubator/lcf/trunk mcf-trunk</code>
</p>
</section>
- <section id="understandingACF">
+ <section id="understandingManifoldCF">
<title>Familiarize Yourself with the Concepts and Terminology</title>
- <p>Like any software project, ACF has its own underlying concepts and terminology. Read about that <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Lucene+Connectors+Framework+concepts">here</a>.
+ <p>Like any software project, ManifoldCF has its own underlying concepts and terminology. Read about that <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/ManifoldCF+concepts">here</a>.
</p>
</section>
<section id="howtobuilddeploy">
<title>How to Build and Deploy</title>
- <p>Building ACF requires ant 1.7 or greater. Instructions for building and deploying can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Build+and+Deploy+Lucene+Connectors+Framework">here</a>.
+ <p>Building ManifoldCF requires ant 1.7 or greater. Instructions for building and deploying can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Build+and+Deploy+ManifoldCF">here</a>.
</p>
</section>
<section id="howtointegrate">
<title>How to Integrate</title>
- <p>ACF provides a number of API's and services. Documentation of these API's can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Programmatic+Operation+of+LCF">here</a>.
+ <p>ManifoldCF provides a number of API's and services. Documentation of these API's can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Programmatic+Operation+of+ManifoldCF">here</a>.
</p>
</section>
<section id="securityarchitecturediagrams">
<title>Security Architecture Diagrams</title>
- <p>For those who prefer a pictorial representation of ACF's security architecture, this might help.</p>
+ <p>For those who prefer a pictorial representation of ManifoldCF's security architecture, this might help.</p>
<br/><br/>
- <figure src="images/SecurityArchitecture.png" alt="ACF Security Architecture" width="80%"/>
+ <figure src="images/SecurityArchitecture.png" alt="ManifoldCF Security Architecture" width="80%"/>
<br/><br/>
<p>If you are using Apache to perform authentication, the model is slightly different.</p>
<br/><br/>
- <figure src="images/LCFApacheArchitecture.png" alt="ACF Security Architecture, with Apache" width="80%"/>
+ <figure src="images/LCFApacheArchitecture.png" alt="ManifoldCF Security Architecture, with Apache" width="80%"/>
<br/><br/>
</section>
<section id="processarchitecturediagrams">
<title>Process Architecture Diagrams</title>
- <p>A pictorial representation of ACF's process architecture is below.</p>
+ <p>A pictorial representation of ManifoldCF's process architecture is below.</p>
<br/><br/>
- <figure src="images/LCFProcessArchitecture.png" alt="ACF Process Architecture" width="80%"/>
+ <figure src="images/LCFProcessArchitecture.png" alt="ManifoldCF Process Architecture" width="80%"/>
<br/><br/>
</section>
<section id="howtowriteconnectors">
<title>How to Write Connectors</title>
- <p>Writing connectors for ACF is a great way to learn about the project and contribute something useful! Read about how to do that by navigating to the links provided below.
+ <p>Writing connectors for ManifoldCF is a great way to learn about the project and contribute something useful! Read about how to do that by navigating to the links provided below.
</p>
<ul>
<li><a href="http://cwiki.apache.org/confluence/display/CONNECTORS/How+to+Write+an+Output+Connector">How to write an output connector</a></li>
@@ -65,7 +65,7 @@
<section id="debugging">
<title>Debugging Connections</title>
- <p>Sooner or later, you will encounter a repository that should be supported, but doesn't seem to want to connect properly to ACF. When that happens, you will need all the help you
+ <p>Sooner or later, you will encounter a repository that should be supported, but doesn't seem to want to connect properly to ManifoldCF. When that happens, you will need all the help you
can get. Start <a href="https://cwiki.apache.org/confluence/display/CONNECTORS/Debugging+Connections">here</a>, and if you find a new hint, technique,
or trick, don't forget to add it to the page!</p>
</section>
@@ -87,7 +87,7 @@
<section id="Making a Contribution">
<title>Making a Contribution</title>
- <p>ACF is always looking for contributions, especially in the areas of documentation. See the <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/HowToContribute">Wiki</a> for details on contributing. </p>
+ <p>ManifoldCF is always looking for contributions. See the <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/HowToContribute">Wiki</a> for details on contributing. </p>
<p>We're also looking for logo ideas. Here are the <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/Logo+Criteria">guidelines</a>.
</p>
</section>
Modified: incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml (original)
+++ incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml Tue Oct 5 01:38:43 2010
@@ -1,20 +1,20 @@
<?xml version="1.0"?>
<document>
-<header><title>Apache Connectors Framework- End-user Documentation</title></header>
+<header><title>ManifoldCF- End-user Documentation</title></header>
<properties>
</properties>
<body>
<section id="overview">
<title>Overview</title>
- <p>This manual is intended for an end-user of Apache Connectors Framework. It is assumed that the Framework has been properly installed, either by you or by a system integrator,
+ <p>This manual is intended for an end-user of ManifoldCF. It is assumed that the Framework has been properly installed, either by you or by a system integrator,
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 Apache Connectors Framework user interface. On a standard Apache Connectors Framework deployment, you would reach that interface by giving your browser
- a URL something like this: <code>http://my-server-name:8080/lcf-crawler-ui</code>. This will, of course, differ from system to system. Please contact your system administrator
+ <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: <code>http://my-server-name:8080/acf-crawler-ui</code>. 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 Apache Connectors Framework 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
+ <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
will not work properly. Please let your system integrator know if you find any browser incompatibility problems.</p>
<p>When you do manage to enter the Framework user interface the first time, you should see a screen that looks something like this:</p>
<br/><br/>
@@ -177,14 +177,14 @@
</section>
<section id="jobs">
<title>Creating Jobs</title>
- <p>A "job" in Apache Connectors Framework is a description of a set of documents. The Framework's job is to fetch this set of documents come from a specific repository connection, and
+ <p>A "job" in ManifoldCF is a description of a set of documents. The Framework's job is to fetch this set of documents come from a specific repository connection, and
send them to a specific output connection. The repository connection that is associated with the job will determine exactly how this set of documents is described, and to some
degree how they are indexed. The output connection associated with the job can also affect how each document is indexed.</p>
<p>Every job is expected to be run more than once. Each time a job is run, it is responsible not only for sending new or changed documents to the output connection, but also for
notifying the output connection of any documents that are no longer part of the set. Note that there are two ways for a document to no longer be part of the included set of documents:
Either the document may have been deleted from the repository, or the document may no longer be included in the allowed set of documents. The Framework handles each case properly.</p>
<p>Deleting a job causes the output connection to be notified of deletion for all documents belonging to that job. This makes sense because the job represents the set of documents, which would
- otherwise be orphaned when the job was removed. (Some users make the assumption that a Apache Connectors Framework job represents nothing more than a task, which is an incorrect
+ otherwise be orphaned when the job was removed. (Some users make the assumption that a ManifoldCF job represents nothing more than a task, which is an incorrect
assumption.)</p>
<p>Note that the Framework allows jobs that describe overlapping sets of documents to be defined. Documents that exist in more than one job are treated in the following special ways:</p>
<ul>
@@ -206,7 +206,7 @@
<p>Note that continuous jobs <b>cannot</b> remove no-longer-included documents from the queue. They can only remove documents that have been deleted from the repository.</p>
<p>A job can independently be configured to start when explicitly started by a user, or to run on a user-specified schedule. If a job is set up to run on a schedule, it can be made to
start only at the beginning of a schedule window, or to start again within any remaining schedule window when the previous job run completes.</p>
- <p>There is no restriction in Apache Connectors Framework as to how many jobs many running at any given time.</p>
+ <p>There is no restriction in ManifoldCF as to how many jobs many running at any given time.</p>
<p>You create a job by first clicking on the "List All Jobs" link on the left-side menu. The following screen will appear:</p>
<br/><br/>
<figure src="images/list-jobs.PNG" alt="List Jobs" width="80%"/>
@@ -278,7 +278,7 @@
</section>
<section id="statusreports">
<title>Status Reports</title>
- <p>Every job in Apache Connectors Framework describes a set of documents. A reference to each document in the set is kept in a job-specific queue. It is sometimes valuable for
+ <p>Every job in ManifoldCF describes a set of documents. A reference to each document in the set is kept in a job-specific queue. It is sometimes valuable for
diagnostic reasons to examine this queue for information. The Framework UI has several canned reports which do just that.</p>
<p>Each status report allows you to select what documents you are interested in from a job's queue based on the following information:</p>
<ul>
@@ -335,7 +335,7 @@
</section>
<section id="historyreports">
<title>History Reports</title>
- <p>For every repository connection, Apache Connectors Framework keeps a history of what has taken place involving that connection. This history includes both events that the
+ <p>For every repository connection, ManifoldCF keeps a history of what has taken place involving that connection. This history includes both events that the
framework itself logs, as well as events that a repository connection or output connection will log. These individual events are categorized by "activity type". Some of the kinds of
activity types that exist are:</p>
<ul>
@@ -412,7 +412,7 @@
<section id="solroutputconnector">
<title>Solr Output Connection</title>
- <p>The Solr output connection type is designed to allow Apache Connectors Framework to submit documents to an appropriate Solr pipeline, via the Solr
+ <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
@@ -457,7 +457,7 @@
<section id="gtsoutputconnector">
<title>MetaCarta GTS Output Connection</title>
- <p>The MetaCarta GTS output connection type is designed to allow Apache Connectors Framework to submit documents to an appropriate MetaCarta GTS search
+ <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>
<p>The connection type implicitly understands that GTS can only handle text, HTML, XML, RTF, PDF, and Microsoft Office documents. All other document types will be
considered to be unindexable. This helps prevent jobs based on a GTS-type output connection from fetching data that is large, but of no particular relevance.</p>
@@ -542,7 +542,7 @@
<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.
In addition, you can also specify whether or not you wish to include auto-generated ACLs in every user's list. Auto-generated ACLs are created within Documentum for every folder
- object. Because there are often a very large number of folders, including these ACLs can bloat the number of ACF access tokens returned for a user to tens of thousands, which can negatively
+ object. Because there are often a very large number of folders, including these ACLs can bloat the number of ManifoldCF access tokens returned for a user to tens of thousands, which can negatively
impact perfomance. Even more notably, few Documentum installations make any real use of these ACLs in any way. Since Documentum's ACLs are purely additive (that is, there are no
mechanisms for 'deny' semantics), the impact of a missing ACLs is only to block a user from seeing something they otherwise could see. It is thus safe, and often desirable, to simply ignore the
existence of these auto-generated ACLs.</p>
@@ -656,11 +656,11 @@
<br/>
<ul>
<li>Windows security event logs</li>
- <li>ACF logs (see below)</li>
+ <li>ManifoldCF logs (see below)</li>
<li>Packet captures (using a tool such as WireShark)</li>
</ul>
<br/>
- <p>If you need specific ACF logging information, contact your system integrator.</p>
+ <p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
</section>
</section>
@@ -671,7 +671,7 @@
<section id="filesystemrepository">
<title>Generic File System Repository Connection</title>
<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 Apache Connectors Framework is running on. Bear in mind that there is no support in this connection type for any kind of
+ 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
security, and the options are somewhat limited.</p>
<p>The file system repository connection type provides no configuration tabs beyond the standard ones. However, please consider setting a "Maximum connections per
JVM" value on the "Throttling" tab to at least one per worker thread, or 30, for best performance.</p>
@@ -1472,11 +1472,11 @@
<br/>
<ul>
<li>Windows security event logs</li>
- <li>ACF logs (see below)</li>
+ <li>ManifoldCF logs (see below)</li>
<li>Packet captures (using a tool such as WireShark)</li>
</ul>
<br/>
- <p>If you need specific ACF logging information, contact your system integrator.</p>
+ <p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
<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>
@@ -1489,7 +1489,7 @@
in SharePoint are directly related to others (e.g. they are subsites), while some sites operate relatively independently of one another.</p>
<p>The SharePoint connection type is designed so that one SharePoint repository connection can access all SharePoint sites from a specific root site though its explicit subsites.
It is the case
- that it is desirable in some very large SharePoint installations to access <b>all</b> SharePoint sites using a single connection. But the ACF SharePoint connection type today
+ that it is desirable in some very large SharePoint installations to access <b>all</b> SharePoint sites using a single connection. But the ManifoldCF SharePoint connection type today
does not support
that model as of yet. If this functionality is important for you, contact your system integrator.</p>
<p>SharePoint uses a web URL model for addressing sites, subsites, libraries, and files. The best way to figure out how to set up a SharePoint connection type is therefore to start
@@ -1522,11 +1522,11 @@
<br/>
<ul>
<li>Windows security event logs</li>
- <li>ACF logs (see below)</li>
+ <li>ManifoldCF logs (see below)</li>
<li>Packet captures (using a tool such as WireShark)</li>
</ul>
<br/>
- <p>If you need specific ACF logging information, contact your system integrator.</p>
+ <p>If you need specific ManifoldCF logging information, contact your system integrator.</p>
<p></p>
<p>When you configure a job to use a repository connection of the generic database type, several additional tabs are presented. These are, in order, "Paths", "Security", and "Metadata".</p>
<p>The "Paths" tab allows you to build a list of rules describing the SharePoint content that you want to include in your job. When the SharePoint connection type encounters a subsite,
Modified: incubator/lcf/site/src/documentation/content/xdocs/index.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/content/xdocs/index.xml?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/src/documentation/content/xdocs/index.xml (original)
+++ incubator/lcf/site/src/documentation/content/xdocs/index.xml Tue Oct 5 01:38:43 2010
@@ -6,37 +6,41 @@
<document>
<header>
- <title>Welcome to Apache Connectors Framework!</title>
+ <title>Welcome to ManifoldCF!</title>
</header>
<body>
<section>
<title>Incubation Status</title>
- <p>Apache Connectors Framework (ACF) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Lucene PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
+ <p>ManifoldCF (formerly Apache Connectors Framework) is an effort undergoing incubation at The Apache Software Foundation (ASF), sponsored by the Lucene PMC. Incubation is required of all newly accepted projects until a further review indicates that the infrastructure, communications, and decision making process have stabilized in a manner consistent with other successful ASF projects. While incubation status is not necessarily a reflection of the completeness or stability of the code, it does indicate that the project has yet to be fully endorsed by the ASF.
</p>
</section>
<section>
- <title>What Is the Apache Connectors Framework?</title>
- <p>The Apache Connectors Framework (ACF) is an effort to provide build and support an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr. ACF also defines a security model for target repositories that permits them to enforce source-repository security policies.</p>
+ <title>What Is ManifoldCF?</title>
+ <p>ManifoldCF is an effort to provide build and support an open source framework for connecting source content repositories like Microsoft Sharepoint and EMC Documentum, to target repositories or indexes, such as Apache Solr. ACF also defines a security model for target repositories that permits them to enforce source-repository security policies.</p>
<p>Currently included connectors support FileNet P8 (IBM), Documentum (EMC), LiveLink (OpenText), Patriarch (Memex), Meridio (Autonomy), Windows shares (Microsoft), and SharePoint (Microsoft). Also included are a general file system connector, a general JDBC connector, a general RSS crawler, and a general web crawler. Currently supported targets include Apache Solr and QBase (formerly MetaCarta) GTS. The complete repository compatibility list can be found <a href="http://cwiki.apache.org/confluence/display/CONNECTORS/SupportedConnectors">here</a>.</p>
- <p>The original ACF code base was granted by MetaCarta, Inc., to the Apache Software Foundation in December 2009. The MetaCarta effort represented more than five years of successful development and testing in multiple, challenging enterprise environments.</p>
+ <p>The original ManifoldCF code base was granted by MetaCarta, Inc., to the Apache Software Foundation in December 2009. The MetaCarta effort represented more than five years of successful development and testing in multiple, challenging enterprise environments.</p>
</section>
<section>
<title>Project status</title>
- <p>There are currently no released versions of ACF available, although one is planned However, a trunk svn checkout has been built and successfully hand-tested. Nightly builds and online javadoc will be coming shortly.</p>
+ <p>There are currently no released versions of ManifoldCF available, although one is planned However, a trunk svn checkout has been built and successfully hand-tested. Nightly builds and online javadoc will be coming shortly.</p>
</section>
<section>
<title>A philosophical note about third-party repositories</title>
- <p>Many of the connectors included with ACF currently require third-party libraries, packages, or other licensed materials in order to be built. The code for these connectors can be distributed under Apache guidelines because they are conditionally compiled; that is, you as a developer must supply the necessary third-party components before the connector will build. While we have every intention of trying to reduce the number of affected connectors by means of clean-room development under the auspices of ASF, realistically the current situation will not change in any dramatic way very quickly. The focus of this group remains primarily on providing solutions.</p>
+ <p>Many of the connectors included with ManifoldCF currently require third-party libraries, packages, or other licensed materials in order to be built. The code for these connectors can be distributed under Apache guidelines because they are conditionally compiled; that is, you as a developer must supply the necessary third-party components before the connector will build. While we have every intention of trying to reduce the number of affected connectors by means of clean-room development under the auspices of ASF, realistically the current situation will not change in any dramatic way very quickly. The focus of this group remains primarily on providing solutions.</p>
<p>The required libraries, tools, and procedures for building each of these connectors are well documented in the Wiki pages for this project.</p>
</section>
<section>
<title>News</title>
<section>
+ <title>03 October 2010 - Apache Connectors Framework officially becomes Apache ManifoldCF</title>
+ <p>Developer community approves second name change</p>
+ </section>
+ <section>
<title>19 August 2010 - Lucene Connectors Framework officially becomes Apache Connectors Framework</title>
<p>Developer community approves name change</p>
</section>
Modified: incubator/lcf/site/src/documentation/content/xdocs/mail.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/content/xdocs/mail.xml?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/src/documentation/content/xdocs/mail.xml (original)
+++ incubator/lcf/site/src/documentation/content/xdocs/mail.xml Tue Oct 5 01:38:43 2010
@@ -1,13 +1,13 @@
<?xml version="1.0"?>
<document>
<header>
- <title>Apache Connectors Framework - Mailing Lists</title>
+ <title>ManifoldCF - Mailing Lists</title>
</header>
<body>
- <section id="ACF Mailing Lists"><title>ACF Mailing Lists</title>
- <p>The Apache Connectors Framework supports several mailing lists.</p>
+ <section id="ACF Mailing Lists"><title>ManifoldCF Mailing Lists</title>
+ <p>The ManifoldCF project supports several mailing lists.</p>
</section>
- <section id="user"><title>ACF User Mailing List</title>
+ <section id="user"><title>ManifoldCF User Mailing List</title>
<p>User questions on how to use ACF.</p>
<ul>
<li><a href="mailto:connectors-user-subscribe@incubator.apache.org">Subscribe</a></li>
@@ -15,15 +15,15 @@
<li><a href="http://mail-archives.apache.org/mod_mbox/incubator-connectors-user/">Archive</a></li>
</ul>
</section>
- <section id="dev"><title>ACF Development Mailing List</title>
- <p>Discussion on the development of the internals of ACF.</p>
+ <section id="dev"><title>ManifoldCF Development Mailing List</title>
+ <p>Discussion on the development of the internals of ManifoldCF.</p>
<ul>
<li><a href="mailto:connectors-dev-subscribe@incubator.apache.org">Subscribe</a></li>
<li><a href="mailto:connectors-dev-unsubscribe@incubator.apache.org">Unsubscribe</a></li>
<li><a href="http://mail-archives.apache.org/mod_mbox/incubator-connectors-dev/">Archive</a></li>
</ul>
</section>
- <section id="commits"><title>ACF Commits Mailing List</title>
+ <section id="commits"><title>ManifoldCF Commits Mailing List</title>
<p>Commit messages</p>
<ul>
<li><a href="mailto:connectors-commits-subscribe@incubator.apache.org">Subscribe</a></li>
Copied: incubator/lcf/site/src/documentation/resources/images/ManifoldCF-Logo.PNG (from r1004494, incubator/lcf/site/src/documentation/resources/images/ACF-logo.PNG)
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/ManifoldCF-Logo.PNG?p2=incubator/lcf/site/src/documentation/resources/images/ManifoldCF-Logo.PNG&p1=incubator/lcf/site/src/documentation/resources/images/ACF-logo.PNG&r1=1004494&r2=1004501&rev=1004501&view=diff
==============================================================================
Binary files - no diff available.
Modified: incubator/lcf/site/src/documentation/skinconf.xml
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/skinconf.xml?rev=1004501&r1=1004500&r2=1004501&view=diff
==============================================================================
--- incubator/lcf/site/src/documentation/skinconf.xml (original)
+++ incubator/lcf/site/src/documentation/skinconf.xml Tue Oct 5 01:38:43 2010
@@ -65,10 +65,10 @@ which will be used to configure the chos
<!-- mandatory project logo
default skin: renders it at the top -->
- <project-name>Apache Connectors Framework</project-name>
- <project-description>Connectors Framework</project-description>
+ <project-name>Apache ManifoldCF</project-name>
+ <project-description>ManifoldCF</project-description>
<project-url>http://incubator.apache.org/lcf</project-url>
- <project-logo>images/ACF-logo.PNG</project-logo>
+ <project-logo>images/ManifoldCF-logo.PNG</project-logo>
<!-- Alternative static image:
<project-logo>images/project-logo.gif</project-logo> -->