This task describes how to deploy the web
application.
- Deploy the Share web application to Liferay by copying the share.war file from your SkyVault Tomcat instance into Liferay's deploy folder.
- Locate the <LIFERAY_HOME>/tomcat-6.0.18/conf/catalina.properties file and open it in an editor.
-
Locate the shared.loader property and set it to the following
value:
shared.loader=${catalina.home}/shared/classes,${catalina.home}/shared/lib/*.jar
- Create the directory <LIFERAY_HOME>/tomcat-6.0.18/shared/classes/alfresco/web-extension/.
-
Add the following configuration to a new file called
share-config-custom.xml.
Note: If your SkyVault Tomcat instance is running on another host or a non-standard port, you must modify the endpoint-url parameters to point to the correct location of your repository. For example:
<alfresco-config> <!-- example port config used to access remote SkyVault server (default is 8080) --> <config evaluator="string-compare" condition="Remote"> <remote> <endpoint> <id>alfresco-noauth</id> <name>SkyVault - unauthenticated access</name> <description>Access to SkyVault 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>SkyVault - user access</name> <description>Access to SkyVault 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>SkyVault Feed</name> <description>SkyVault 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> <!-- Overriding endpoints to reference a SkyVault 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 SkyVault 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. NOTE: For Kerberos SSO rename the "KerberosDisabled" condition above to "Kerberos" NOTE: For external SSO switch the endpoint connector to "AlfrescoHeader" and set the userHeader to the name of the HTTP header that the external SSO uses to provide the authenticated user name. --> <config evaluator="string-compare" condition="Remote"> <remote> <keystore> <path>alfresco/web-extension/alfresco-system.p12</path> <type>pkcs12</type> <password>alfresco-system</password> </keystore> <connector> <id>alfrescoCookie</id> <name>SkyVault Connector</name> <description>Connects to a SkyVault instance using cookie-based authentication</description> <class>org.alfresco.web.site.servlet.SlingshotAlfrescoConnector</class> <userHeader>SsoUserHeader</userHeader> </connector> <connector> <id>alfrescoHeader</id> <name>SkyVault Connector</name> <description>Connects to a SkyVault instance using header and cookie-based authentication</description> <class>org.alfresco.web.site.servlet.SlingshotAlfrescoConnector</class> <userHeader>SsoUserHeader</userHeader> </connector> <endpoint> <id>alfresco</id> <name>SkyVault - user access</name> <description>Access to SkyVault Repository WebScripts that require user authentication</description> <connector-id>alfrescoHeader</connector-id> <endpoint-url>http://localhost:8080/alfresco/wcs</endpoint-url> <identity>user</identity> <external-auth>true</external-auth> </endpoint> </remote> </config> </alfresco-config>