Deploying 3.3WAR Liferay5

[luissala]

1. REDIRECT Portlets
   

InstallationLiferay3.3
The alfresco.war and share.war files now deploy directly into Liferay with hardly any special instructions.

1. Copy the template alfresco-global.properties to liferay-portal-5.2.3/tomcat-6.0.18/lib
   
2. Add these lines
   

   authentication.chain=alfrescoNtlm1:alfrescoNtlm,external1:external
   

   external.authentication.proxyUserName=
   

   
   

   This includes the new external subsystem in the authentication chain. This is preconfigured to recognise the X-Alfresco-Remote-User HTTP header that share now sends to the repository in requests where external authentication is enabled. It also assumes a secure connection to the repository and disables use of a ‘proxy user’ (one identified by a SSL certificate) but if you do want to use a public connection securely, you can set up a proxy user and SSL certificate as described here.
   

   
   
3. To configure Share, create a file liferay-portal-5.2.3/tomcat-6.0.18/lib/alfresco/web-extension/share-config-custom.xml containing the following. Note: Modify endpoint-url parameters to match actual Repository deployment.
   

<alfresco-config>

   <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-feed</id>
            <name>Alfresco Feed</name>
            <description>Alfresco Feed - supports basic HTTP authentication</description>
            <connector-id>http</connector-id>
            <endpoint-url>http://localhost:8080/alfresco/s</endpoint-url>
            <basic-auth>true</basic-auth>
            <identity>user</identity>
         </endpoint>

         <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>

</alfresco-config>

After auto-deployment of alfresco.war and share.war, portlets will show up in the 'Alfresco' or 'Undefined' categories.