incubator-connectors-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kwri...@apache.org
Subject svn commit: r933752 [3/3] - in /incubator/lcf/site: publish/ publish/images/ src/documentation/content/xdocs/ src/documentation/resources/images/
Date Tue, 13 Apr 2010 19:17:23 GMT
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=933752&r1=933751&r2=933752&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 Apr 13 19:17:21 2010
@@ -1,19 +1,522 @@
 <?xml version="1.0"?>
 <document>
-<header><title>Apache Lucene Connector Framework- End-user Documentation</title></header>
+<header><title>Apache Lucene Connectors Framework- End-user Documentation</title></header>
 <properties>
 </properties>
 <body>
 
-    <section id="enduserdoc">
-        <title>End-user Documentation</title>
-        <p>The end-user documentation for LCF currently exists in a set of LaTeX files, that 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/documentation lcf-documentation</code>
-        </p>
-        <p>Current plans call for this documentation to be converted and included here, on this website.</p>
-    </section>
+        <section id="overview">
+            <title>Overview</title>
+            <p>This manual is intended for an end-user of Lucene Connectors Framework.  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 connectors 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 Lucene Connectors Framework user interface.  On a standard Lucene 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
+                  to find out what URL is appropriate for your environment.
+            </p>
+            <p>The Lucene 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
+                  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/>
+            <figure src="images/welcome-screen.PNG" alt="Welcome Screen" width="80%"/>
+            <br/><br/>
+            <p>On the left, there are menu options you can select.  The main pane on the right shows a welcome message, but depending on what you select on the left, the contents of the main pane
+                  will change.  Before you try to accomplish anything, please take a moment to read the descriptions below of the menu selections, and thus get an idea of how the Framework works
+                  as a whole.
+            </p>
+            <section id="outputs">
+                <title>Defining Output Connections</title>
+                <p>The Framework UI's left-side menu contains a link for listing output connections.  An output connection is a connection to a system or place where documents fetched from various
+                       repositories can be written to.  This is often a search engine.</p>
+                <p>All jobs must specify an output connection.  You can create an output connection by clicking the "List Output Connections" link in the left-side navigation menu.  When you do this, the
+                       following screen will appear:</p>
+                <br/><br/>
+                <figure src="images/list-output-connections.PNG" alt="List Output Connections" width="80%"/>
+                <br/><br/>
+                <p>On a freshly created system, there may well be no existing output connections listed.  If there are already output connections, they will be listed on this screen, along with links that allow
+                      you to view, edit, or delete them.  To create a new output connection, click the "Add new output connection" link at the bottom.  The following screen will then appear:</p>
+                <br/><br/>
+                <figure src="images/add-new-output-connection-name.PNG" alt="Add New Output Connection, specify Name" width="80%"/>
+                <br/><br/>
+                <p>The tabs across the top each present a different view of your output connection.  Each tab allows you to edit a different characteristic of that connection.  The exact set of tabs you see
+                       depends on the connection type you choose for the connection.</p>
+                <p>Start by giving your connection a name and a description.  Remember that all output connection names must be unique, and cannot be changed after the connection is defined.  The name must be
+                       no more than 32 characters long.  The description can be up to 255 characters long.  When you are done, click on the "Type" tab.  The Type tab for the connection will then appear:</p>
+                <br/><br/>
+                <figure src="images/add-new-output-connection-type.PNG" alt="Add New Output Connection, select Type" width="80%"/>
+                <br/><br/>
+                <p>The list of output connection types in the pulldown box, and what they are each called, is determined by your system integrator.  Each selection represents your choice of a different
+                       output connector.  The configuration tabs for each different kind of output connector are described in separate sections below.</p>
+                <p>After you choose an output connection type, click the "Continue" button at the bottom of the pane.  You will then see all the tabs appropriate for that kind of connection appear, and a
+                       "Save" button will also appear at the bottom of the pane.  You <b>must</b> click the "Save" button when you are done in order to create your connection.  If you click "Cancel" instead, the new connection
+                       will not be created.  (The same thing will happen if you click on any of the navigation links in the left-hand pane.)</p>
+                <p>Every output connection has a "Throttling" tab.  The tab looks like this:</p>
+                <br/><br/>
+                <figure src="images/output-throttling.PNG" alt="Output Connection Throttling" width="80%"/>
+                <br/><br/>
+                <p>On this tab, you can specify only one thing: how many open connections are allowed at any given time to the system the output connection talks with.  This restriction helps prevent
+                       that system from being overloaded, or in some cases exceeding its license limitations.  Conversely, making this number larger allows for greater overall throughput.  The default
+                       value is 10, which may not be optimal for all types of output connections.  Please refer to the section of the manual describing your output connection type for more precise
+                       recommendations.
+                </p>
+                <p>Please refer to the section of the manual describing your chosen output connection type for a description of the tabs appropriate for that connection type.</p>
+                
+                <p>After you save your connection, a summary screen will be displayed that describes your connection's configuration.  This summary screen contains a line where the connection's status
+                       is displayed.  If you did everything correctly, the message "Connection working" will be displayed as a status.  If there was a problem, you will see a connection-type-specific diagnostic message instead.
+                       If this happens, you will need to correct the problem, by either fixing your infrastructure, or by editing the connection configuration appropriately, before the output connection
+                       will work correctly.</p>
+            </section>
+            <section id="authorities">
+                <title>Defining Authority Connections</title>
+                <p>The Framework UI's left-side menu contains a link for listing authority connections.  An authority connection is a connection to a system that defines a particular security environment.
+                       For example, if you want to index some documents that are protected by Active Directory, you would need to configure an Active Directory authority connection.</p>
+                <p>You may not need an authority if you do not mind that portions of all the documents you want to index are visible to everyone.  For web crawling and RSS crawling, this might be the
+                       situation.  Most other repositories have some security mechanism, however.</p>
+                <p>You should define your authority connections <b>before</b> setting up your repository connections.  While it is possible to change the relationship between a repository connection
+                       and its authority after-the-fact, in practice such changes may cause many documents to require reindexing.</p>
+                <p>You can create an authority connection by clicking the "List Authority Connections" link in the left-side navigation menu.  When you do this, the
+                       following screen will appear:</p>
+                <br/><br/>
+                <figure src="images/list-authority-connections.PNG" alt="List Authority Connections" width="80%"/>
+                <br/><br/>
+                <p>On a freshly created system, there may well be no existing authority connections listed.  If there are already authority connections, they will be listed on this screen, along with links
+                       that allow you to view, edit, or delete them.  To create a new authority connection, click the "Add a new connection" link at the bottom.  The following screen will then appear:</p>
+                <br/><br/>
+                <figure src="images/add-new-authority-connection-name.PNG" alt="Add New Authority Connection, specify Name" width="80%"/>
+                <br/><br/>
+                <p>The tabs across the top each present a different view of your authority connection.  Each tab allows you to edit a different characteristic of that connection.  The exact set of tabs you see
+                       depends on the connection type you choose for the connection.</p>
+                <p>Start by giving your connection a name and a description.  Remember that all authority connection names must be unique, and cannot be changed after the connection is defined.  The name must be
+                       no more than 32 characters long.  The description can be up to 255 characters long.  When you are done, click on the "Type" tab.  The Type tab for the connection will then appear:</p>
+                <br/><br/>
+                <figure src="images/add-new-authority-connection-type.PNG" alt="Add New Authority Connection, select Type" width="80%"/>
+                <br/><br/>
+                <p>The list of authority connection types in the pulldown box, and what they are each called, is determined by your system integrator.  Each selection represents your choice of a different
+                       authority connector.  The configuration tabs for each different kind of authority connector are described in separate sections below.</p>
+                <p>After you choose an authority connection type, click the "Continue" button at the bottom of the pane.  You will then see all the tabs appropriate for that kind of connection appear, and a
+                       "Save" button will also appear at the bottom of the pane.  You <b>must</b> click the "Save" button when you are done in order to create your connection.  If you click "Cancel" instead, the new connection
+                       will not be created.  (The same thing will happen if you click on any of the navigation links in the left-hand pane.)</p>
+                <p>Every authority connection has a "Throttling" tab.  The tab looks like this:</p>
+                <br/><br/>
+                <figure src="images/authority-throttling.PNG" alt="Authority Connection Throttling" width="80%"/>
+                <br/><br/>
+                <p>On this tab, you can specify only one thing: how many open connections are allowed at any given time to the system the authority connection talks with.  This restriction helps prevent
+                       that system from being overloaded, or in some cases exceeding its license limitations.  Conversely, making this number larger allows for smaller average search latency.  The default
+                       value is 10, which may not be optimal for all types of authority connections.  Please refer to the section of the manual describing your authority connection type for more precise
+                       recommendations.
+                </p>
+                <p>Please refer to the section of the manual describing your chosen authority connection type for a description of the tabs appropriate for that connection type.</p>
+
+                <p>After you save your connection, a summary screen will be displayed that describes your connection's configuration.  This summary screen contains a line where the connection's status
+                       is displayed.  If you did everything correctly, the message "Connection working" will be displayed as a status.  If there was a problem, you will see a connection-type-specific diagnostic message instead.
+                       If this happens, you will need to correct the problem, by either fixing your infrastructure, or by editing the connection configuration appropriately, before the authority connection
+                       will work correctly.</p>
+                       
+            </section>
+            <section id="connectors">
+                <title>Defining Repository Connections</title>
+                <p>The Framework UI's left-hand menu contains a link for listing repository connections.  A repository connection is a connection to the repository system that contains the documents
+                       that you are interested in indexing.</p>
+                <p>All jobs require you to specify a repository connection, because that is where they get their documents from.  It is therefore necessary to create a repository connection before
+                       indexing any documents.</p>
+                <p>A repository connection also may have an associated authority connection.  This specified authority determines the security environment in which documents from the repository
+                       connection are placed.  While it is possible to change the specified authority for a repository connection after a crawl has been done, in practice this will require that all documents
+                       associated with that repository connection be reindexed.  Therefore, we recommend that you set up your desired authority connection before defining your repository connection.</p>
+                <p>You can create a repository connection by clicking the "List Repository Connections" link in the left-side navigation menu.  When you do this, the
+                       following screen will appear:</p>
+                <br/><br/>
+                <figure src="images/list-repository-connections.PNG" alt="List Repository Connections" width="80%"/>
+                <br/><br/>
+                <p>On a freshly created system, there may well be no existing repository connections listed.  If there are already repository connections, they will be listed on this screen, along with links
+                       that allow you to view, edit, or delete them.  To create a new repository connection, click the "Add a new connection" link at the bottom.  The following screen will then appear:</p>
+                <br/><br/>
+                <figure src="images/add-new-repository-connection-name.PNG" alt="Add New Repository Connection, specify Name" width="80%"/>
+                <br/><br/>
+                <p>The tabs across the top each present a different view of your repository connection.  Each tab allows you to edit a different characteristic of that connection.  The exact set of tabs you see
+                       depends on the connection type you choose for the connection.</p>
+                <p>Start by giving your connection a name and a description.  Remember that all repository connection names must be unique, and cannot be changed after the connection is defined.  The name must be
+                       no more than 32 characters long.  The description can be up to 255 characters long.  When you are done, click on the "Type" tab.  The Type tab for the connection will then appear:</p>
+                <br/><br/>
+                <figure src="images/add-new-repository-connection-type.PNG" alt="Add New Repository Connection, select Type" width="80%"/>
+                <br/><br/>
+                <p>The list of repository connection types in the pulldown box, and what they are each called, is determined by your system integrator.  Each selection represents your choice of a different
+                       repository connector.  The configuration tabs for each different kind of repository connector are described in separate sections below.</p>
+                <p>You may also at this point select the authority connection to secure all documents fetched from this repository with.  Bear in mind that only some authority connection types are compatible with any
+                       given repository connection types.  Read the details of your desired repository or authority connection type to understand its intentions, and how it is expected to be used.</p>
+                <p>After you choose a repository connection type and an authority connection, click the "Continue" button at the bottom of the pane.  You will then see all the tabs appropriate for that kind of connection appear, and a
+                       "Save" button will also appear at the bottom of the pane.  You <b>must</b> click the "Save" button when you are done in order to create or update your connection.  If you click "Cancel" instead, the new connection
+                       will not be created.  (The same thing will happen if you click on any of the navigation links in the left-hand pane.)</p>
+                <p>Every repository connection has a "Throttling" tab.  The tab looks like this:</p>
+                <br/><br/>
+                <figure src="images/repository-throttling.PNG" alt="Repository Connection Throttling" width="80%"/>
+                <br/><br/>
+                <p>On this tab, you can specify two things.  The first is how many open connections are allowed at any given time to the system the authority connection talks with.  This restriction helps prevent
+                       that system from being overloaded, or in some cases exceeding its license limitations.  Conversely, making this number larger allows for smaller average search latency.  The default
+                       value is 10, which may not be optimal for all types of repository connections.  Please refer to the section of the manual describing your authority connection type for more precise
+                       recommendations.  The second specifies how rapidly, on average, the crawler will fetch documents via this connection.
+                </p>
+                <p>Each connection type has its own notion of "throttling bin".  A throttling bin is the name of a resource whose access needs to be throttled.  For example, the Web Connector uses a
+                       document's server name as the throttling bin associated with the document, since (presumably) it will be access to each individual server that will need to be throttled independently.
+                </p>
+                <p>On the repository connection "Throttling" tab, you can specify an unrestricted number of throttling descriptions.  Each throttling description consists of a regular expression that describes
+                       a family of throttling bins, plus a helpful description, plus an average number of fetches per minute for each of the throttling bins that matches the regular expression.  If a given
+                       throttling bin matches more than one throttling description, the most conservative fetch rate is chosen.</p>
+                <p>The simplest regular expression you can use is the empty regular expression.  This will match all of the connection type's throttle bins, and thus will allow you to specify a default
+                       throttling policy for the connection.  Set the desired average fetch rate, and click the "Add" button.  The throttling tab will then appear something like this:</p>
+                <br/><br/>
+                <figure src="images/repository-throttling-with-throttle.PNG" alt="Repository Connection Throttling With Throttle" width="80%"/>
+                <br/><br/>
+                <p>If no throttle descriptions are added, no fetch-rate throttling will be performed.</p>
+                <p>Please refer to the section of the manual describing your chosen repository connection type for a description of the tabs appropriate for that connection type.</p>
+
+                <p>After you save your connection, a summary screen will be displayed that describes your connection's configuration.  This summary screen contains a line where the connection's status
+                       is displayed.  If you did everything correctly, the message "Connection working" will be displayed as a status.  If there was a problem, you will see a connection-type-specific diagnostic message instead.
+                       If this happens, you will need to correct the problem, by either fixing your infrastructure, or by editing the connection configuration appropriately, before the authority connection
+                       will work correctly.</p>
+                       
+            </section>
+            <section id="jobs">
+                <title>Creating Jobs</title>
+                <p>A "job" in Lucene 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
+                       send them to a specific output connection.  The repository connection type 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 type 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 Lucene Connectors Framework 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>
+                    <li>When a job is deleted, the output connection is notified of deletion of documents belonging to that job only if they don't belong to another job</li>
+                    <li>The version of the document sent to the output connection depends on which job was run last</li>
+                </ul>
+                <p>The subtle logic of overlapping documents means that you probably want to avoid this situation entirely, if it is at all feasible.</p>
+                <p>A typical non-continuous run of a job has the following stages of execution:</p>
+                <ol>
+                    <li>Adding the job's new, changed, or deleted starting points to the queue ("seeding")</li>
+                    <li>Fetching documents, discovering new documents, and detecting deletions</li>
+                    <li>Removing no-longer-included documents from the queue</li>
+                </ol>
+                <p>Jobs can also be run "continuously", which means that the job never completes, unless it is aborted.  A continuous run has different stages of execution:</p>
+                <ol>
+                    <li>Adding the job's new, changed, or deleted starting points to the queue ("seeding")</li>
+                    <li>Fetching documents, discovering new documents, and detecting deletions, while reseeding periodically</li>
+                </ol>
+                <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 Lucene Connectors Framework 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%"/>
+                <br/><br/>
+                <p>You may view, edit, or delete any existing jobs by clicking on the appropriate link.  You may also create a new job that is a copy of an existing job.  But to create a brand-new job,
+                       click the "Add a new job" link at the bottom.  You will then see the following page:</p>
+                <br/><br/>
+                <figure src="images/add-new-job-name.PNG" alt="Add New Job, name tab" width="80%"/>
+                <br/><br/>
+                <p>Give your job a name.  Note that job names do <b>not</b> have to be unique, although it is probably less confusing to have a different name for each one.  Then, click the
+                       "Connection" tab:</p>
+                <br/><br/>
+                <figure src="images/add-new-job-connection.PNG" alt="Add New Job, connection tab" width="80%"/>
+                <br/><br/>
+                <p>Now, you should select both the output connection name, and the repository connection name.  Bear in mind that whatever you select cannot be changed after the job is saved
+                       the first time.</p>
+                <p>You also have the opportunity to modify the job's priority and start method at this time.  The priority
+                       controls how important this job's documents are, relative to documents from any other job.  The higher the number, the more important it is considered for that job's documents to be
+                       fetched first.  The start method is as previously described; you get a choice of manual start, starting on the beginning of a scheduling window, or starting whenever possible within
+                       a scheduling window.</p>
+                <p>Make your selections, and click "Continue".  The rest of the job's tabs will now appear, and a
+                       "Save" button will also appear at the bottom of the pane.  You <b>must</b> click the "Save" button when you are done in order to create or update your job.  If you click "Cancel" instead, the new job
+                       will not be created.  (The same thing will happen if you click on any of the navigation links in the left-hand pane.)</p>
+                <p>All jobs have a "Scheduling" tab.  The scheduling tab allows you to set up schedule-related configuration information:</p>
+                <br/><br/>
+                <figure src="images/add-new-job-scheduling.PNG" alt="Add New Job, scheduling tab" width="80%"/>
+                <br/><br/>
+                <p>On this tab, you can specify the following parameters:</p>
+                <ul>
+                    <li>Whether the job runs continuously, or scans every document once</li>
+                    <li>How long a document should remain alive before it is 'expired', and removed from the index</li>
+                    <li>How long an interval before a document is re-checked, to see if it has changed</li>
+                    <li>How long to wait before reseeding initial documents</li>
+                </ul>
+                <br/>
+                <p>The last three parameters only make sense if a job is a continuously running one, as the UI indicates.</p>
+                <p>The other thing you can do on this time is to define an appropriate set of scheduling records.  Each scheduling record defines some related set of intervals during which the job can run.  The
+                       intervals are determined by the starting time (which is defined by the day of week, month, day, hour, and minute pulldowns), and the maximum run time in minutes, which determines
+                       when the interval ends.  It is, of course, possible to select multiple values for each of the pulldowns, in which case you be describing a starting time that had to match at least <b>one</b>
+                       of the selected values for <b>each</b> of the specified fields.</p>
+                <p>Once you have selected the schedule values you want, click the "Add Scheduled Time" button:</p>
+                <br/><br/>
+                <figure src="images/add-new-job-scheduling-with-record.PNG" alt="Add New Job, scheduling tab with record" width="80%"/>
+                <br/><br/>
+                <p>The example shows a schedule where crawls are run on Saturday and Sunday nights at 2 AM, and run for no more than 4 hours.</p>
+                <p>The rest of the job tabs depend on the types of the connections you selected.  Please refer to the section of the manual
+                       describing your chosen repository and output connection types for a description of the job tabs appropriate for those connection types.</p>
+            </section>
+            <section id="executing">
+                <title>Executing Jobs</title>
+                <p>You can follow what is going on, and control the execution of your jobs, by clicking on the "Status and Job Management" link on the left-side navigation menu.  When you do, you might
+                       see something like this:</p>
+                <br/><br/>
+                <figure src="images/job-status.PNG" alt="Job Status" width="80%"/>
+                <br/><br/>
+                <p>From here, you can click the "Refresh" link at the bottom of the main pane to see an updated status display, or you can directly control the job using the links in the leftmost
+                       status column.  Allowed actions you may see at one point or another include:</p>
+                <ul>
+                    <li>Start (start the job)</li>
+                    <li>Abort(abort the job)</li>
+                    <li>Pause (pause the job)</li>
+                    <li>Resume (resume the job)</li>
+                    <li>Restart (equivalent to aborting the job, and starting it all over again)</li>
+                </ul>
+                <br/>
+                <p>The columns "Documents", "Active", and "Processed" have very specific means as far as documents in the job's queue are concerned.  The "Documents" column counts all the documents
+                       that belong to the job.  The "Active" column counts all of the documents for that job that are queued up for processing.  The "Processed" column counts all documents that are on the
+                       queue for the job that have been processed at least once in the past.</p>
+            </section>
+            <section id="statusreports">
+                <title>Status Reports</title>
+                <p>Every job in Lucene 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
+                       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>
+                    <li>The job</li>
+                    <li>The document identifier</li>
+                    <li>The document's status and state</li>
+                    <li>When the document is scheduled to be processed next</li>
+                </ul>
+                <section id="documentstatus">
+                    <title>Document Status</title>
+                    <p>A document status report simply lists all matching documents from within the queue, along with their state, status, and planned future activity.  You might use this report if you were
+                           trying to figure out (for example) whether a specific document had been processed yet during a job run.</p>
+                    <p>Click on the "Document Status" link on the left-hand menu.  You will see a screen that looks something like this:</p>
+                    <br/><br/>
+                    <figure src="images/document-status-select-connection.PNG" alt="Document Status, select connection" width="80%"/>
+                    <br/><br/>
+                    <p>Select the desired connection.  You may also select the desired document state and status, as well as specify a regular expression for the document identifier, if you want.  Then,
+                           click the "Continue" button:</p>
+                    <br/><br/>
+                    <figure src="images/document-status-select-job.PNG" alt="Document Status, select job" width="80%"/>
+                    <br/><br/>
+                    <p>Select the job whose documents you want to see, and click "Continue" once again.  The results will display:</p>
+                    <br/><br/>
+                    <figure src="images/document-status-example.PNG" alt="Document Status, example" width="80%"/>
+                    <br/><br/>
+                    <p>You may alter the criteria, and click "Go" again, if you so choose.  Or, you can alter the number of result rows displayed at a time, and click "Go" to redisplay.  Finally, you can page
+                           up and down through the results using the "Prev" and "Next" links.</p>
+                </section>
+                <section id="queuestatus">
+                    <title>Queue Status</title>
+                    <p>A queue status report is an aggregate report that counts the number of occurrences of documents in specified classes.  The classes are specified as a grouping within a regular
+                           expression, which is matched against all specified document identifiers.  The results that are displayed are counts of documents.  There will be a column for each combination of
+                           document state and status.</p>
+                    <p>For example, a class specification of "()" will produce exactly one result row, and will provide a count of documents that are in each state/status combination.  A class description
+                           of "(.*)", on the other hand, will create one row for each document identifier, and will put a "1" in the column representing state and status of that document, with a "0" in all other
+                           column positions.</p>
+                    <p>Click the "Queue Status" link on the left-hand menu.  You will see a screen that looks like this:</p>
+                    <br/><br/>
+                    <figure src="images/queue-status-select-connection.PNG" alt="Queue Status, select connection" width="80%"/>
+                    <br/><br/>
+                    <p>Select the desired connection.  You may also select the desired document state and status, as well as specify a regular expression for the document identifier, if you want.  You
+                           will probably want to change the document identifier class from its default value of "(.*)".  Then, click the "Continue" button:</p>
+                    <br/><br/>
+                    <figure src="images/queue-status-select-job.PNG" alt="Queue Status, select job" width="80%"/>
+                    <br/><br/>
+                    <p>Select the job whose documents you want to see, and click "Continue" once again.  The results will display:</p>
+                    <br/><br/>
+                    <figure src="images/queue-status-example.PNG" alt="Queue Status, example" width="80%"/>
+                    <br/><br/>
+                    <p>You may alter the criteria, and click "Go" again, if you so choose.  Or, you can alter the number of result rows displayed at a time, and click "Go" to redisplay.  Finally, you can page
+                           up and down through the results using the "Prev" and "Next" links.</p>
+
+                </section>
+            </section>
+            <section id="historyreports">
+                <title>History Reports</title>
+                <p>For every repository connection, Lucene Connectors Framework 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>
+                    <li>Job start</li>
+                    <li>Job end</li>
+                    <li>Job abort</li>
+                    <li>Various connection-type-specific read or access operations</li>
+                    <li>Various connection-type-specific output or indexing operations</li>
+                </ul>
+                <p>This history can be enormously helpful in understand how your system is behaving, and whether or not it is working properly.  For this reason, the Framework UI has the ability to
+                       generate several canned reports which query this history data and display the results.</p>
+                <p>All history reports allow you to specify what history records you are interested in including.  These records are selected using the following criteria:</p>
+                <ul>
+                    <li>The repository connection name</li>
+                    <li>The activity type(s) desired</li>
+                    <li>The start time desired</li>
+                    <li>The end time desired</li>
+                    <li>The identifier(s) involved, specified as a regular expression</li>
+                    <li>The result(s) produced, specified as a regular expression</li>
+                </ul>
+                <p>The actual reports available are designed to be useful for diagnosing both access issues, and performance issues.  See below for a summary of the types available.</p>
+                <section id="simplehistory">
+                    <title>Simple History Reports</title>
+                    <p>As the name suggests, a simple history report does not attempt to aggregate any data, but instead just lists matching records from the repository connection's history.
+                           These records are initially presented in most-recent-first order, and include columns for the start and end time of the event, the kind of activity represented by the event,
+                           the identifier involved, the number of bytes involved, and the results of the event.  Once displayed, you may choose to display more or less data, or reorder the display by column, or page through the data.</p>
+                    <p>To get started, click on the "Simple History" link on the left-hand menu.  You will see a screen that looks like this:</p>
+                    <br/><br/>
+                    <figure src="images/simple-history-select-connection.PNG" alt="Simple History Report, select connection" width="80%"/>
+                    <br/><br/>
+                    <p>Now, select the desired repository connection from the pulldown in the upper left hand corner.  If you like, you can also change the specified date/time range, or specify an identifier
+                           regular expression or result code regular expression.  By default, the date/time range selects all events within the last hour, while the identifier regular expression and result code
+                           regular expression matches all identifiers and result codes.</p>
+                    <p>Next, click the "Continue" button.  A list of pertinent activities should then appear in a pulldown in the upper right:</p>
+                    <br/><br/>
+                    <figure src="images/simple-history-select-activities.PNG" alt="Simple History Report, select activities" width="80%"/>
+                    <br/><br/>
+                    <p>You may select one or more activities that you would like a report on.  When you are done, click the "Go" button.  The results will appear, ordered by time, most recent event first:</p>
+                    <br/><br/>
+                    <figure src="images/simple-history-example.PNG" alt="Simple History Report, example" width="80%"/>
+                    <br/><br/>
+                    <p>You may alter the criteria, and click "Go" again, if you so choose.  Or, you can alter the number of result rows displayed at a time, and click "Go" to redisplay.  Finally, you can page
+                           up and down through the results using the "Prev" and "Next" links.</p>
+                    <p>Please bear in mind that the report redisplays whatever matches each time you click "Go".  So, if your time interval goes from an hour beforehand to "now", and you have activity
+                           happening, you will see different results each time "Go" is clicked.</p>
+                </section>
+                <section id="maxactivity">
+                    <title>Maximum Activity Reports</title>
+                    <p>A maximum activity report is an aggregate report used primarily to display the maximum rate that events occur within a specified time interval.  MHL</p>
+                </section>
+                <section id="maxbandwidth">
+                    <title>Maximum Bandwidth Reports</title>
+                    <p>A maximum bandwidth report is an aggregate report used primarily to display the maximum byte rate that pertains to events occurring within a specified time interval.  MHL</p>
+                </section>
+                <section id="resulthistogram">
+                    <title>Result Histogram Reports</title>
+                    <p>A result histogram report is an aggregate report is used to count the occurrences of each kind of matching result for all matching events.  MHL</p>
+                </section>
+            </section>
+            
+            <section id="credentials">
+                <title>A Note About Credentials</title>
+                <p>If any of your selected connection type require credentials, you may find it necessary to approach your system administrator to obtain an appropriate set.  System administrators
+                       are often reluctant to provide accounts and credentials that have any more power than is utterly necessary, and sometimes not even that.  Great care has been taken in the
+                       development of all connection types to be sure they require no more privilege than is utterly necessary.  If a security-related warning appears when you view a connection's
+                       status, you must inform the system administrator that the credentials are inadequate to allow the connector to accomplish its task, and work with him/her to correct the problem.
+                </p>
+            </section>
+
+        </section>
+        
+        <section id="outputconnectiontypes">
+            <title>Output Connection Types</title>
+            
+            <section id="solroutputconnector">
+                <title>Solr Output Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="gtsoutputconnector">
+                <title>GTS Output Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="nulloutputconnector">
+                <title>Null Output Connection</title>
+                <p>More here later</p>
+            </section>
+            
+        </section>
+        
+        <section id="authorityconnectiontypes">
+            <title>Authority Connection Types</title>
+            
+            <section id="adauthority">
+                <title>Active Directory Authority Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="livelinkauthority">
+                <title>OpenText LiveLink Authority Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="documentumauthority">
+                <title>EMC Documentum Authority Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="memexauthority">
+                <title>Memex Patriarch Authority Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="meridioauthority">
+                <title>Autonomy Meridio Authority Connection</title>
+                <p>More here later</p>
+            </section>
+            
+        </section>
+        
+        <section id="repositoryconnectiontypes">
+            <title>Repository Connection Types</title>
+            <p>More here later</p>
+
+            <section id="jcifsrepository">
+                <title>Windows Share/DFS Repository Connection</title>
+                <p>More here later</p>
+            </section>
+
+            <section id="filenetrepository">
+                <title>IBM FileNet P8 Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="documentumrepository">
+                <title>EMC Documentum Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="filesystemrepository">
+                <title>Generic File System Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="jdbcrepository">
+                <title>Generic Database Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="livelinkrepository">
+                <title>OpenText LiveLink Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="mexexrepository">
+                <title>Memex Patriarch Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="meridiorepository">
+                <title>Autonomy Meridio Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="sharepointrepository">
+                <title>Microsoft SharePoint Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="rssrepository">
+                <title>Generic RSS Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+            <section id="webrepository">
+                <title>Generic Web Repository Connection</title>
+                <p>More here later</p>
+            </section>
+            
+        </section>
 
 </body>
 </document>

Added: incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-name.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-name.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-name.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-name.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-type.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-type.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-type.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-authority-connection-type.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-job-connection.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-job-connection.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-connection.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-connection.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-job-name.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-job-name.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-name.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-name.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling-with-record.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling-with-record.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling-with-record.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling-with-record.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-job-scheduling.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-name.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-name.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-name.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-name.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-type.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-type.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-type.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-output-connection-type.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-name.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-name.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-name.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-name.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-type.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-type.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-type.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/add-new-repository-connection-type.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/authority-throttling.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/authority-throttling.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/authority-throttling.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/authority-throttling.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/document-status-example.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/document-status-example.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/document-status-example.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/document-status-example.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/document-status-select-connection.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/document-status-select-connection.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/document-status-select-connection.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/document-status-select-connection.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/document-status-select-job.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/document-status-select-job.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/document-status-select-job.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/document-status-select-job.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/job-status.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/job-status.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/job-status.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/job-status.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/list-authority-connections.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/list-authority-connections.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/list-authority-connections.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/list-authority-connections.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/list-jobs.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/list-jobs.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/list-jobs.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/list-jobs.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/list-output-connections.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/list-output-connections.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/list-output-connections.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/list-output-connections.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/list-repository-connections.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/list-repository-connections.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/list-repository-connections.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/list-repository-connections.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/output-throttling.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/output-throttling.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/output-throttling.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/output-throttling.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/queue-status-example.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/queue-status-example.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/queue-status-example.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/queue-status-example.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/queue-status-select-connection.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/queue-status-select-connection.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/queue-status-select-connection.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/queue-status-select-connection.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/queue-status-select-job.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/queue-status-select-job.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/queue-status-select-job.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/queue-status-select-job.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/repository-throttling-with-throttle.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/repository-throttling-with-throttle.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/repository-throttling-with-throttle.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/repository-throttling-with-throttle.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/repository-throttling.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/repository-throttling.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/repository-throttling.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/repository-throttling.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/simple-history-example.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/simple-history-example.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/simple-history-example.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/simple-history-example.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/simple-history-select-activities.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/simple-history-select-activities.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/simple-history-select-activities.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/simple-history-select-activities.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/simple-history-select-connection.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/simple-history-select-connection.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/simple-history-select-connection.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/simple-history-select-connection.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/src/documentation/resources/images/welcome-screen.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/src/documentation/resources/images/welcome-screen.PNG?rev=933752&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/src/documentation/resources/images/welcome-screen.PNG
------------------------------------------------------------------------------
    svn:executable = *

Propchange: incubator/lcf/site/src/documentation/resources/images/welcome-screen.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream



Mime
View raw message