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/05/06 17:49:16 UTC

svn commit: r941783 - in /incubator/lcf/site: publish/ publish/images/ src/documentation/content/xdocs/ src/documentation/resources/images/

Author: kwright
Date: Thu May  6 15:49:15 2010
New Revision: 941783

URL: http://svn.apache.org/viewvc?rev=941783&view=rev
Log:
Finish LiveLink documentation

Added:
    incubator/lcf/site/publish/images/livelink-connection-document-access.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-connection-document-view.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-connection-server.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-connection-status.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-job-filters.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-job-metadata.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-job-paths.PNG   (with props)
    incubator/lcf/site/publish/images/livelink-job-security.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-connection-document-access.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-connection-document-view.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-connection-server.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-connection-status.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-job-filters.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-job-metadata.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-job-paths.PNG   (with props)
    incubator/lcf/site/src/documentation/resources/images/livelink-job-security.PNG   (with props)
Modified:
    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.pdf
    incubator/lcf/site/publish/index.pdf
    incubator/lcf/site/publish/linkmap.pdf
    incubator/lcf/site/publish/mail.pdf
    incubator/lcf/site/publish/who.pdf
    incubator/lcf/site/src/documentation/content/xdocs/end-user-documentation.xml

Modified: incubator/lcf/site/publish/developer-resources.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/developer-resources.pdf?rev=941783&r1=941782&r2=941783&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=941783&r1=941782&r2=941783&view=diff
==============================================================================
--- incubator/lcf/site/publish/end-user-documentation.html (original)
+++ incubator/lcf/site/publish/end-user-documentation.html Thu May  6 15:49:15 2010
@@ -1901,7 +1901,7 @@ document.write("Last Published: " + docu
 <br>
 <p>Pay careful attention to the status, and be prepared to correct any
                     problems that are displayed.</p>
-<p>A job created to use a Documentum connection as the following additional tabs associated with it: "Paths", "Document Types", "Content Types", "Security", and "Path Metadata".</p>
+<p>A job created to use a Documentum connection has the following additional tabs associated with it: "Paths", "Document Types", "Content Types", "Security", and "Path Metadata".</p>
 <p>The "Paths" tab allows you to construct the paths within Documentum that you want to scan for content.  If no paths are selected, all content will be considered eligible.</p>
 <p>The "Document Types" tab allows you to select what document types you want to index.  Only document types that are derived from dm_document, which are flagged by the system administrator
                     as being "indexable", will be presented for your selection.  On this tab also, for each document type you index, you may choose included specific metadata for documents of that type, or you can
@@ -1921,14 +1921,105 @@ document.write("Last Published: " + docu
 <p>If more than one rule is present, the rules are all executed in sequence.  That is, the output of the first rule is modified by the second rule, etc.</p>
 <a name="N10ADF"></a><a name="livelinkrepository"></a>
 <h3 class="h4">OpenText LiveLink Repository Connection</h3>
-<p>More here later</p>
-<a name="N10AE9"></a><a name="mexexrepository"></a>
+<p>The OpenText LiveLink connection type allows you to index content from LiveLink repositories.  LiveLink has a rich variety of different document types and metadata, which include
+                    basic documents, as well as compound documents, folders, workspaces, and projects.  A LiveLink connection is able to discover documents contained within all of these constructs.</p>
+<p>Documents described by LiveLink connections are typically secured by a LiveLink authority.  If you have not yet created a LiveLink authority, but would like your
+                    documents to be secured, please follow the direction in the section titled "OpenText LiveLink Authority Connection".</p>
+<p>A LiveLink connection has the following special tabs: "Server", "Document Access", and "Document View".  The "Server" tab allows you to select a LiveLink server to connect to, and also to provide
+                    appropriate credentials.  The "Document Access" tab describes the location of the LiveLink web interface, relative to the server, that will be used to fetch document content from LiveLink.
+                    The "Document View" tab affects how URLs to the fetched documents are constructed, for viewing results of searches.</p>
+<p>The "Server" tab looks like this:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Connection, Server tab" src="images/livelink-connection-server.PNG" width="80%"></div>
+<br>
+<br>
+<p>Enter the LiveLink server name, port, and credentials.</p>
+<p>The "Document Access" tab looks like this:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Connection, Document Access tab" src="images/livelink-connection-document-access.PNG" width="80%"></div>
+<br>
+<br>
+<p>The server name is presumed to be the same as is on the "Server" tab.  Select the desired protocol.  If your LiveLink server is using a non-standard HTTP port for the specified protocol, enter the 
+                    port number.  If your LiveLink server is using NTLM authentication, enter an AD user name, password, and domain.  If your LiveLink is using HTTPS, browse locally for the appropriate
+                    certificate authority certificate, and click "Add" to upload that certificate to the connection's trust store.  (You may also use the server's certificate, but that is less resilient because the
+                    server's certificate may be changed periodically.)</p>
+<p>The "Document View" tab looks like this:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Connection, Document Viewtab" src="images/livelink-connection-document-view.PNG" width="80%"></div>
+<br>
+<br>
+<p>If you want each document's view URL to be the same as its access URL, you can leave this tab unchanged.  If you want to direct users to a different CGI path when they view search results,
+                    you can specify that here.</p>
+<p>When you are done, click the "Save" button.  You will see a summary screen that looks something like this:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Connection Status" src="images/livelink-connection-status.PNG" width="80%"></div>
+<br>
+<br>
+<p>Make note of and correct any reported connection errors.  In this example, the connection has been correctly set up, so the connection status is "Connection working".</p>
+<p>A job created to use a LiveLink connection has the following additional tabs associated with it: "Paths", "Filters", "Security", and "Metadata".</p>
+<p>The "Paths" tab allows you to manage a list of LiveLink paths that act as starting points for indexing content:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Job, Paths tab" src="images/livelink-job-paths.PNG" width="80%"></div>
+<br>
+<br>
+<p>Build each path by selecting from the available dropdown, and clicking the "+" button.  When your path is complete, click the "Add" button to add the path to the list of starting points.</p>
+<p>The "Filters" tab controls the criteria the LiveLink job will use to include or exclude content.  The filters are basically a list of rules.  Each rule has a document match field,
+                    and a matching action ("Include" or "Exclude").  When a LiveLink connection encounters a document, it evaluates the rules from top to bottom.
+                    If the rule matches, then it will be included or excluded from the job's document set depending on what you have selected for the matching action. A rule's match field specifies a
+                    character match, where "*" will match any number of characters, and "?" will match any single character.</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Job, Filters tab" src="images/livelink-job-filters.PNG" width="80%"></div>
+<br>
+<br>
+<p>Enter the match field value, select the match action, and click the "Add" button to add to the list of filters.</p>
+<p>The "Security" tab allows you to disable (or enable) LiveLink security for the documents associated with this job:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Job, Security tab" src="images/livelink-job-security.PNG" width="80%"></div>
+<br>
+<br>
+<p>If you disable security, you can add your own access tokens to all
+                    jobs in the document set as they are indexed.  The format of the access tokens you would enter depends on the governing authority associated with the job's repository connection.
+                    Enter a token and click the "Add" button to add it to the list.</p>
+<p>The "Metadata" tab allows you to select what specific metadata values from LiveLink you want to pass to the index:</p>
+<br>
+<br>
+<div id="" style="text-align: center;">
+<img id="" class="figure" alt="LiveLink Job, Metadata tab" src="images/livelink-job-metadata.PNG" width="80%"></div>
+<br>
+<br>
+<p>If you want to pass all available LiveLink metadata to the index, then click the "All metadata" radio button.  Otherwise, you need to build LiveLink metadata paths and add them to the metadata list.
+                    Select the next metadata path segment, and click the appropriate "+" button to add it to the path.  You may add folder information, or a metadata category, at any point.</p>
+<p>Once you have drilled down to a metadata category, you can select the metadata attributes to include, or check the "All attributes in this category" checkbox.  When you are done, click the
+                    "Add" button to add the metadata attributes that you want to include in the index.</p>
+<p>You can also use the "Metadata" tab to have the connection send path data along with each document, as a piece of document metadata.  To enable this feature, enter the name of the metadata
+                    attribute you want this information to be sent into the "Path attribute name" field.  Then, add the rules you want to the list of rules.  Each rule has a match expression, which is a regular expression where
+                    parentheses ("(" and ")") mark sections you are interested in.  These sections are called "groups" in regular expression parlance.  The replace string consists of constant text plus
+                    substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the first match group
+                    mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
+<p>For example, suppose you had a rule which had ".*/(.*)/(.*)/.*" as a match expression, and "$(1) $(2)" as the replace string.  If presented with the path
+                    <span class="codefrag">Project/Folder_1/Folder_2/Filename</span>, it would output the string <span class="codefrag">Folder_1 Folder_2</span>.</p>
+<p>If more than one rule is present, the rules are all executed in sequence.  That is, the output of the first rule is modified by the second rule, etc.</p>
+<a name="N10B8C"></a><a name="mexexrepository"></a>
 <h3 class="h4">Memex Patriarch Repository Connection</h3>
 <p>More here later</p>
-<a name="N10AF3"></a><a name="meridiorepository"></a>
+<a name="N10B96"></a><a name="meridiorepository"></a>
 <h3 class="h4">Autonomy Meridio Repository Connection</h3>
 <p>More here later</p>
-<a name="N10AFD"></a><a name="sharepointrepository"></a>
+<a name="N10BA0"></a><a name="sharepointrepository"></a>
 <h3 class="h4">Microsoft SharePoint Repository Connection</h3>
 <p>The Microsoft SharePoint connection type allows you to index documents from a Microsoft SharePoint site.  Bear in mind that a single SharePoint installation actually represents
                     a set of sites.  Some sites

Modified: incubator/lcf/site/publish/end-user-documentation.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/end-user-documentation.pdf?rev=941783&r1=941782&r2=941783&view=diff
==============================================================================
Files incubator/lcf/site/publish/end-user-documentation.pdf (original) and incubator/lcf/site/publish/end-user-documentation.pdf Thu May  6 15:49:15 2010 differ

Modified: incubator/lcf/site/publish/faq.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/faq.pdf?rev=941783&r1=941782&r2=941783&view=diff
==============================================================================
Files incubator/lcf/site/publish/faq.pdf (original) and incubator/lcf/site/publish/faq.pdf Thu May  6 15:49:15 2010 differ

Added: incubator/lcf/site/publish/images/livelink-connection-document-access.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-connection-document-access.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-connection-document-access.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-connection-document-view.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-connection-document-view.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-connection-document-view.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-connection-server.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-connection-server.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-connection-server.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-connection-status.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-connection-status.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-connection-status.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-job-filters.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-job-filters.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-job-filters.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-job-metadata.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-job-metadata.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-job-metadata.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-job-paths.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-job-paths.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-job-paths.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Added: incubator/lcf/site/publish/images/livelink-job-security.PNG
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/images/livelink-job-security.PNG?rev=941783&view=auto
==============================================================================
Binary file - no diff available.

Propchange: incubator/lcf/site/publish/images/livelink-job-security.PNG
------------------------------------------------------------------------------
    svn:mime-type = application/octet-stream

Modified: incubator/lcf/site/publish/index.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/index.pdf?rev=941783&r1=941782&r2=941783&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/lcf/site/publish/linkmap.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/linkmap.pdf?rev=941783&r1=941782&r2=941783&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/lcf/site/publish/mail.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/mail.pdf?rev=941783&r1=941782&r2=941783&view=diff
==============================================================================
Binary files - no diff available.

Modified: incubator/lcf/site/publish/who.pdf
URL: http://svn.apache.org/viewvc/incubator/lcf/site/publish/who.pdf?rev=941783&r1=941782&r2=941783&view=diff
==============================================================================
Binary files - no diff available.

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=941783&r1=941782&r2=941783&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 Thu May  6 15:49:15 2010
@@ -1206,7 +1206,7 @@
                 <br/><br/>
                 <p>Pay careful attention to the status, and be prepared to correct any
                     problems that are displayed.</p>
-                <p>A job created to use a Documentum connection as the following additional tabs associated with it: "Paths", "Document Types", "Content Types", "Security", and "Path Metadata".</p>
+                <p>A job created to use a Documentum connection has the following additional tabs associated with it: "Paths", "Document Types", "Content Types", "Security", and "Path Metadata".</p>
                 <p>The "Paths" tab allows you to construct the paths within Documentum that you want to scan for content.  If no paths are selected, all content will be considered eligible.</p>
                 <p>The "Document Types" tab allows you to select what document types you want to index.  Only document types that are derived from dm_document, which are flagged by the system administrator
                     as being "indexable", will be presented for your selection.  On this tab also, for each document type you index, you may choose included specific metadata for documents of that type, or you can
@@ -1228,7 +1228,74 @@
             
             <section id="livelinkrepository">
                 <title>OpenText LiveLink Repository Connection</title>
-                <p>More here later</p>
+                <p>The OpenText LiveLink connection type allows you to index content from LiveLink repositories.  LiveLink has a rich variety of different document types and metadata, which include
+                    basic documents, as well as compound documents, folders, workspaces, and projects.  A LiveLink connection is able to discover documents contained within all of these constructs.</p>
+                <p>Documents described by LiveLink connections are typically secured by a LiveLink authority.  If you have not yet created a LiveLink authority, but would like your
+                    documents to be secured, please follow the direction in the section titled "OpenText LiveLink Authority Connection".</p>
+                <p>A LiveLink connection has the following special tabs: "Server", "Document Access", and "Document View".  The "Server" tab allows you to select a LiveLink server to connect to, and also to provide
+                    appropriate credentials.  The "Document Access" tab describes the location of the LiveLink web interface, relative to the server, that will be used to fetch document content from LiveLink.
+                    The "Document View" tab affects how URLs to the fetched documents are constructed, for viewing results of searches.</p>
+                <p>The "Server" tab looks like this:</p>
+                <br/><br/>
+                <figure src="images/livelink-connection-server.PNG" alt="LiveLink Connection, Server tab" width="80%"/>
+                <br/><br/>
+                <p>Enter the LiveLink server name, port, and credentials.</p>
+                <p>The "Document Access" tab looks like this:</p>
+                <br/><br/>
+                <figure src="images/livelink-connection-document-access.PNG" alt="LiveLink Connection, Document Access tab" width="80%"/>
+                <br/><br/>
+                <p>The server name is presumed to be the same as is on the "Server" tab.  Select the desired protocol.  If your LiveLink server is using a non-standard HTTP port for the specified protocol, enter the 
+                    port number.  If your LiveLink server is using NTLM authentication, enter an AD user name, password, and domain.  If your LiveLink is using HTTPS, browse locally for the appropriate
+                    certificate authority certificate, and click "Add" to upload that certificate to the connection's trust store.  (You may also use the server's certificate, but that is less resilient because the
+                    server's certificate may be changed periodically.)</p>
+                <p>The "Document View" tab looks like this:</p>
+                <br/><br/>
+                <figure src="images/livelink-connection-document-view.PNG" alt="LiveLink Connection, Document Viewtab" width="80%"/>
+                <br/><br/>
+                <p>If you want each document's view URL to be the same as its access URL, you can leave this tab unchanged.  If you want to direct users to a different CGI path when they view search results,
+                    you can specify that here.</p>
+                <p>When you are done, click the "Save" button.  You will see a summary screen that looks something like this:</p>
+                <br/><br/>
+                <figure src="images/livelink-connection-status.PNG" alt="LiveLink Connection Status" width="80%"/>
+                <br/><br/>
+                <p>Make note of and correct any reported connection errors.  In this example, the connection has been correctly set up, so the connection status is "Connection working".</p>
+                <p>A job created to use a LiveLink connection has the following additional tabs associated with it: "Paths", "Filters", "Security", and "Metadata".</p>
+                <p>The "Paths" tab allows you to manage a list of LiveLink paths that act as starting points for indexing content:</p>
+                <br/><br/>
+                <figure src="images/livelink-job-paths.PNG" alt="LiveLink Job, Paths tab" width="80%"/>
+                <br/><br/>
+                <p>Build each path by selecting from the available dropdown, and clicking the "+" button.  When your path is complete, click the "Add" button to add the path to the list of starting points.</p>
+                <p>The "Filters" tab controls the criteria the LiveLink job will use to include or exclude content.  The filters are basically a list of rules.  Each rule has a document match field,
+                    and a matching action ("Include" or "Exclude").  When a LiveLink connection encounters a document, it evaluates the rules from top to bottom.
+                    If the rule matches, then it will be included or excluded from the job's document set depending on what you have selected for the matching action. A rule's match field specifies a
+                    character match, where "*" will match any number of characters, and "?" will match any single character.</p>
+                <br/><br/>
+                <figure src="images/livelink-job-filters.PNG" alt="LiveLink Job, Filters tab" width="80%"/>
+                <br/><br/>
+                <p>Enter the match field value, select the match action, and click the "Add" button to add to the list of filters.</p>
+                <p>The "Security" tab allows you to disable (or enable) LiveLink security for the documents associated with this job:</p>
+                <br/><br/>
+                <figure src="images/livelink-job-security.PNG" alt="LiveLink Job, Security tab" width="80%"/>
+                <br/><br/>
+                <p>If you disable security, you can add your own access tokens to all
+                    jobs in the document set as they are indexed.  The format of the access tokens you would enter depends on the governing authority associated with the job's repository connection.
+                    Enter a token and click the "Add" button to add it to the list.</p>
+                <p>The "Metadata" tab allows you to select what specific metadata values from LiveLink you want to pass to the index:</p>
+                <br/><br/>
+                <figure src="images/livelink-job-metadata.PNG" alt="LiveLink Job, Metadata tab" width="80%"/>
+                <br/><br/>
+                <p>If you want to pass all available LiveLink metadata to the index, then click the "All metadata" radio button.  Otherwise, you need to build LiveLink metadata paths and add them to the metadata list.
+                    Select the next metadata path segment, and click the appropriate "+" button to add it to the path.  You may add folder information, or a metadata category, at any point.</p>
+                <p>Once you have drilled down to a metadata category, you can select the metadata attributes to include, or check the "All attributes in this category" checkbox.  When you are done, click the
+                    "Add" button to add the metadata attributes that you want to include in the index.</p>
+                <p>You can also use the "Metadata" tab to have the connection send path data along with each document, as a piece of document metadata.  To enable this feature, enter the name of the metadata
+                    attribute you want this information to be sent into the "Path attribute name" field.  Then, add the rules you want to the list of rules.  Each rule has a match expression, which is a regular expression where
+                    parentheses ("(" and ")") mark sections you are interested in.  These sections are called "groups" in regular expression parlance.  The replace string consists of constant text plus
+                    substitutions of the groups from the match, perhaps modified.  For example, "$(1)" refers to the first group within the match, while "$(1l)" refers to the first match group
+                    mapped to lower case.  Similarly, "$(1u)" refers to the same characters, but mapped to upper case.</p>
+                <p>For example, suppose you had a rule which had ".*/(.*)/(.*)/.*" as a match expression, and "$(1) $(2)" as the replace string.  If presented with the path
+                    <code>Project/Folder_1/Folder_2/Filename</code>, it would output the string <code>Folder_1 Folder_2</code>.</p>
+                <p>If more than one rule is present, the rules are all executed in sequence.  That is, the output of the first rule is modified by the second rule, etc.</p>
             </section>
             
             <section id="mexexrepository">

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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

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