incubator-connectors-commits mailing list archives

Site index · List index
Message view « Date » · « Thread »
Top « Date » · « Thread »
From kwri...@apache.org
Subject svn commit: r940550 [3/3] - in /incubator/lcf/site: publish/end-user-documentation.html publish/end-user-documentation.pdf src/documentation/content/xdocs/end-user-documentation.xml
Date Mon, 03 May 2010 18:12:29 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=940550&r1=940549&r2=940550&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 Mon May
 3 18:12:29 2010
@@ -484,7 +484,8 @@
                 <figure src="images/ad-configure-dc.PNG" alt="AD Configuration, Domain
Controller tab" width="80%"/>
                 <br/><br/>
                 <p>Fill in the requested values.  Note that the "Administrative user
name" field usually requires no domain suffix, but depending on the details of how the domain
-                       controller is configured, may sometimes only accept the "name@domain"
format.  When you are done, click the "Save" button.  When you do, a connection
+                       controller is configured, may sometimes only accept the "name@domain"
format.</p>
+                <p>When you are done, click the "Save" button.  When you do, a connection
                        summary and status screen will be presented, which
                        may look something like this:</p>
                 <br/><br/>
@@ -500,7 +501,25 @@
             
             <section id="documentumauthority">
                 <title>EMC Documentum Authority Connection</title>
-                <p>More here later</p>
+                <p>A Documentum authority connection is required for enforcing security
for documents retrieved from Documentum repositories.
+                       This connection type needs to be provided with information about what
Content Server to connect to, and the credentials that should be used to retrieve a user's
ACLs from that machine.</p>
+                <p>In addition, you can also specify whether or not you wish to include
auto-generated ACLs in every user's list.  Auto-generated ACLs are created within Documentum
for every folder
+                    object.  Because there are often a very large number of folders, including
these ACLs can bloat the number of LCF access tokens returned for a user to tens of thousands,
which can negatively
+                    impact perfomance.  Even more notably, few Documentum installations make
any real use of these ACLs in any way.  Since Documentum's ACLs are purely additive (that
is, there are no
+                    mechanisms for 'deny' semantics), the impact of a missing ACLs is only
to block a user from seeing something they otherwise could see.  It is thus safe, and often
desirable, to simply ignore the
+                    existence of these auto-generated ACLs.</p>
+                <p>A Documentum authority connection has three special tabs you will
need to configure: the "Docbase" tab, the "User Mapping" tab, and the "System ACLs" tab.</p>
+                <p>On the "Docbase" tab, select the desired Content Server, and enter
the appropriate credentials.  You may leave the "Domain" field blank if the Content Server
you specify does not have
+                    Active Directory support enabled.</p>
+                <p>On the "User Mapping" tab, you can specify whether the mapping between
incoming user names and Content Server user names is case sensitive or case insensitive. 
No other mappings
+                    are currently permitted.  Typically, Documentum instances operate in
conjunction with Active Directory, such that Documentum user names are either the same as
the Active Directory user names,
+                    or are the Active Directory user names mapped to all lower case characters.
 You may need to consult with your Documentum system administrator to decide what the correct
setting should be for
+                    this option.</p>
+                <p>On the "System ACLs" tab, you can choose to ignore all auto-generated
ACLs associated with a user.  We recommend that you try ignoring such ACLs, and only choose
the default if you have
+                    reason to believe that your Documentum content is protected in a significant
way by the use of auto-generated ACLs.  Your may need to consult with your Documentum system
administrator to
+                    decide what the proper setting should be for this option.</p>
+                <p>When you are done, click the "Save" button.  When you do, a connection
summary and status screen will be presented.  Pay careful attention to the status, and be
prepared to correct any
+                    problems that are displayed.</p>
             </section>
             
             <section id="memexauthority">
@@ -1131,6 +1150,8 @@
                 <p>On the "Docbase" tab, select the Content Server instance, and provide
your credentials.  You may leave the "Domain" field blank, if the Content Server instance
does not have AD integration enabled.</p>
                 <p>On the "Webtop tab, enter the components of the base URL of the
Webtop instance you want to use for serving the documents.  Remember that this information
will only be used to construct
                     a URL to the document to allow user inspection; it will not be used for
any crawling activities.</p>
+                <p>When you are done, click the "Save" button.  When you do, a connection
summary and status screen will be presented.  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>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



Mime
View raw message