As we transition to the new Hyland Community, some post links may be temporarily disrupted as we finalize redirects. We apologize for the inconvenience and are working to resolve this as quickly as possible. Details.
<alfresco-config> <!– Global config section –> <config replace="true"> <flags> <!– Developer debugging setting to turn on DEBUG mode for client scripts in the browser –> <client-debug>false</client-debug> <!– LOGGING can always be toggled at runtime when in DEBUG mode (Ctrl, Ctrl, Shift, Shift). This flag automatically activates logging on page load. –> <client-debug-autologging>false</client-debug-autologging> </flags> </config> <config evaluator="string-compare" condition="WebFramework"> <web-framework> <!– SpringSurf Autowire Runtime Settings –> <!– Developers can set mode to 'development' to disable; SpringSurf caches, FreeMarker template caching and Rhino JavaScript compilation. –> <autowire> <!– Pick the mode: "production" or "development" –> <mode>production</mode> </autowire> </web-framework> </config> <config evaluator="string-compare" condition="Replication"> <share-urls> <!– To discover a Repository Id, browse to the remote server's CMIS landing page at: http://{server}:{port}/alfresco/service/cmis/index.html The Repository Id field is found under the "CMIS Repository Information" expandable panel. Example config entry: <share-url repositoryId="622f9533-2a1e-48fe-af4e-ee9e41667ea4">http://new-york-office:8080/share/</share-url> –> </share-urls> </config> <!– Document Library config section –> <config evaluator="string-compare" condition="DocumentLibrary" replace="true"> <tree> <!– Whether the folder Tree component should enumerate child folders or not. This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures. –> <evaluate-child-folders>false</evaluate-child-folders> <!– Optionally limit the number of folders shown in treeview throughout Share. –> <maximum-folder-count>-1</maximum-folder-count> </tree> <!– Used by the "Manage Aspects" action For custom aspects, remember to also add the relevant i18n string(s) cm_myaspect=My Aspect –> <aspects> <!– Aspects that a user can see –> <visible> <aspect name="cm:generalclassifiable" /> <aspect name="cm:complianceable" /> <aspect name="cm:dublincore" /> <aspect name="cm:effectivity" /> <aspect name="cm:summarizable" /> <aspect name="cm:versionable" /> <aspect name="cm:templatable" /> <aspect name="cm:emailed" /> <aspect name="emailserver:aliasable" /> <aspect name="cm:taggable" /> <aspect name="app:inlineeditable" /> <aspect name="gd:googleEditable" /> <aspect name="cm:geographic" /> <aspect name="exif:exif" /> </visible> <!– Aspects that a user can add. Same as "visible" if left empty –> <addable> </addable> <!– Aspects that a user can remove. Same as "visible" if left empty –> <removeable> </removeable> </aspects> <!– Used by the "Change Type" action Define valid subtypes using the following example: <type name="cm:content"> <subtype name="cm:mysubtype" /> </type> Remember to also add the relevant i18n string(s): cm_mysubtype=My SubType –> <types> <type name="cm:content"> </type> <type name="cm:folder"> </type> </types> <!– If set, will present a WebDAV link for the current item on the Document and Folder details pages. Also used to generate the "View in Alfresco Explorer" action for folders. –> <repository-url>http://localhost:8080/alfresco</repository-url> <!– Google Docsâ„¢ integration –> <google-docs> <!– Enable/disable the Google Docs UI integration (Extra types on Create Content menu, Google Docs actions). –> <enabled>false</enabled> <!– The mimetypes of documents Google Docs allows you to create via the Share interface. The I18N label is created from the "type" attribute, e.g. google-docs.doc=Google Docs™ Document –> <creatable-types> <creatable type="doc">application/msword</creatable> <creatable type="xls">application/vnd.ms-excel</creatable> <creatable type="ppt">application/vnd.ms-powerpoint</creatable> </creatable-types> </google-docs> <!– File upload configuration –> <file-upload> <!– Adobe Flashâ„¢ In certain environments, an HTTP request originating from Flash cannot be authenticated using an existing session. See: http://bugs.adobe.com/jira/browse/FP-4830 For these cases, it is useful to disable the Flash-based uploader for Share Document Libraries. –> <adobe-flash-enabled>true</adobe-flash-enabled> </file-upload> </config> <!– Repository Library config section –> <config evaluator="string-compare" condition="RepositoryLibrary" replace="true"> <!– Root nodeRef or xpath expression for top-level folder. e.g. alfresco://user/home, /app:company_home/st:sites/cm:site1 If using an xpath expression, ensure it is properly ISO9075 encoded here. –> <root-node>alfresco://company/home</root-node> <tree> <!– Whether the folder Tree component should enumerate child folders or not. This is a relatively expensive operation, so should be set to "false" for Repositories with broad folder structures. –> <evaluate-child-folders>false</evaluate-child-folders> <!– Optionally limit the number of folders shown in treeview throughout Share. –> <maximum-folder-count>500</maximum-folder-count> </tree> </config> <!– Kerberos settings –> <config evaluator="string-compare" condition="Kerberos" replace="true"> <kerberos> <!– Password for HTTP service account. The account name *must* be built from the HTTP server name, in the format : HTTP/<server_name>@<realm> (NB this is because the web browser requests an ST for the HTTP/<server_name> principal in the current realm, so if we're to decode that ST, it has to match.) –> <password>secret</password> <!– Kerberos realm and KDC address. –> <realm>ALFRESCO.ORG</realm> <!– Service Principal Name to use on the repository tier. This must be like: HTTP/host.name@REALM –> <endpoint-spn>HTTP/repository.server.com@ALFRESCO.ORG</endpoint-spn> <!– JAAS login configuration entry name. –> <config-entry>ShareHTTP</config-entry> </kerberos> </config> <!– Overriding endpoints to reference an Alfresco server with external SSO enabled NOTE: If utilising a load balancer between web-tier and repository cluster, the "sticky sessions" feature of your load balancer must be used. NOTE: If alfresco server location is not localhost:8080 then also combine changes from the "example port config" section below. *Optional* keystore contains SSL client certificate + trusted CAs. Used to authenticate share to an external SSO system such as CAS Remove the keystore section if not required i.e. for NTLM. –> <config evaluator="string-compare" condition="Remote"> <remote> <connector> <id>alfrescoCookie</id> <name>Alfresco Connector</name> <description>Connects to an Alfresco instance using cookie-based authentication</description> <class>org.springframework.extensions.webscripts.connector.AlfrescoConnector</class> </connector> <endpoint> <id>alfresco</id> <name>Alfresco - user access</name> <description>Access to Alfresco Repository WebScripts that require user authentication</description> <connector-id>alfrescoCookie</connector-id> <endpoint-url>http://localhost:8080/alfresco/wcs</endpoint-url> <identity>user</identity> <external-auth>true</external-auth> </endpoint> </remote> </config> <!– example port config used to access remote Alfresco server (default is 8080) –> <!– <config evaluator="string-compare" condition="Remote"> <remote> <endpoint> <id>alfresco-noauth</id> <name>Alfresco - unauthenticated access</name> <description>Access to Alfresco Repository WebScripts that do not require authentication</description> <connector-id>alfresco</connector-id> <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url> <identity>none</identity> </endpoint> <endpoint> <id>alfresco</id> <name>Alfresco - user access</name> <description>Access to Alfresco Repository WebScripts that require user authentication</description> <connector-id>alfresco</connector-id> <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url> <identity>user</identity> </endpoint> <endpoint> <id>alfresco-feed</id> <name>Alfresco Feed</name> <description>Alfresco Feed - supports basic HTTP authentication via the EndPointProxyServlet</description> <connector-id>http</connector-id> <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url> <basic-auth>true</basic-auth> <identity>user</identity> </endpoint> </remote> </config> –> </alfresco-config>
