Directory structureĪfter you’ve extracted the Content Services distribution zip, several directories and configuration files will be available in the Content Services home directory. For more information, see Generate secure keys.

Important: After installation, you must generate and install your own certificates to secure the installation. Note: If you’re including Alfresco Content Connector for AWS S3 as part of your installation, don’t start Content Services before applying the S3 AMP file. Use the clean_tomcat.bat or clean_tomcat.sh command. Note: If you deployed previous versions of Content Services, you must remove any temporary files created by your application server. You’re now ready to install any additional software that you require, and install integrations. See Install Alfresco Search Services for more information.

See the supported platforms page for the supported versions.Ĭreate an additional classpath to Tomcat, which will be shared among all web applications.Ĭreate the directories required for a Content Services installation under :Ĭhange the value of the shared.loader= property to the following: shared.loader=$ token is replaced by the local server name) ĭownload and install Tomcat following the instructions from. The installation directory for Tomcat is represented as. Install an instance of Tomcat manually and modify it to use the correct directory structure and files for Content Services. Use this method of installing Content Services if you’ve already have installed a JRE, a supported database, a supported application server, a message broker, and the additional components.įor information about securing Tomcat, see Tomcat security considerations. For manual installation, you must ensure that the required software is installed on the machine. For more complex Content Services installations, or if you wish to use an existing Tomcat application server, you can use the Web Archive (WAR) bundle to install Content Services on any platform.

War file extract software windows