VirtualViewer® on distributed Tomcat for Alfresco
It is possible to have each element of Alfresco Content Services, including VirtualViewer, installed across separate Tomcat instances.
The example configuration changes below are based on our ACS docker-compose.yml
example. VirtualViewer’s content handler and repository AMP need to be configured for this to work properly.
Configuring the Alfresco Content Repository URL in VirtualViewer
VirtualViewer needs to know how to contact the Alfresco Content Repository. Make the following configuration changes to the VirtualViewer tomcat instance.
-
Install VirtualViewer Alfresco in a tomcat instance if you have not already done so.
-
Open
webapps/virtualviewer/WEB-INF/web.xml
and add the following<init-param>
to the<servlet>
section:<init-param> <param-name>alfrescoBaseUrl</param-name> <param-value>http://alfresco:8080/alfresco</param-value> </init-param>
-
Change the URL in
<param-value>
to the URL wherealfresco-content-repository
can be reached. -
Restart the Tomcat instance.
Configure VirtualViewer’s URL in Alfresco Content Repository AMP
The VirtualViewer snowbound-repo-X.X.AMP
in the alfresco-content-repository
instance needs to be configured to contact the VirtualViewer AJAX interface.
-
If you have not already done so, apply the
snowbound-repo-X.X.AMP
file to the Alfresco Content Repository Tomcat instance. -
Open
webapps/alfresco/WEB-INF/classes/alfresco/module/snowbound-repo/alfresco-global.propertie
s. -
Look for the line containing the property
snowbound.cache.servers=
.
Set this property to the URL where your VirtualViewer AJAX Servlet can be reached. For example, snowbound.cache.servers=http://vv-alfresco:8080/virtualviewer/AjaxServlet
.
- Restart the Tomcat instance.
Have questions, corrections, or concerns about this topic? Please let us know!