Deployment Guide

This page describes how to deploy Alfresco Content Services (ACS) using the Ansible playbook found in this project.

Before continuing we need to introduce some more Ansible concepts; control node, connection type and the inventory file.

The machine the playbook is run from is known as the control node. An inventory file is used to describe where the roles within the playbook should deploy to. There are two types of connection, local and ssh. Local means that everything will be installed on the control node, ssh means that everything will be deployed on one or more hosts, these hosts can be bare metal machines, Virtual machines or instances running on a public cloud. This is shown in the diagrams below:

Folder Structure

Regardless of role and connection type a consistent folder structure is used, you will find the deployed files in the following locations:

Path	Purpose
`/opt/alfresco`	Binaries
`/etc/opt/alfresco`	Configuration
`/var/opt/alfresco`	Data
`/var/log/alfresco`	Logs

Service Configuration

The following systemd services are deployed and can be used to stop and start Alfresco components:

Service Name	Purpose
`activemq.service`	ActiveMQ Service
`postgresql-<version>.service`	Postgresql DB Service (where `<version>` is 11 for ACS 6.2.N and 13 for ACS 7.x)
`nginx.service`	Nginx Service
`alfresco-content.service`	Alfresco Content Service
`alfresco-search.service`	Alfresco Search Service
`alfresco-shared-fs.service`	Alfresco Shared File Store Controller Service
`alfresco-sync.service`	Alfresco Sync Service
`alfresco-tengine-aio.service`	Alfresco AIO Transform Core Engine
`alfresco-transform-router.service`	Alfresco Transformation Router Service

TCP Port Configuration

Several roles setup services that listen on TCP ports and several roles wait for TCP ports to be listening before continuing execution (indicated by Yes in the "Required For Deployment" column). The table below shows the communication paths and port numbers used.

Target Host	Target Port	Source Hosts	Required For Deployment
activemq	61616	repository, syncservice, transformers	Yes
database	5432	repository, syncservice	Yes
repository	8080	nginx, search, syncservice	Yes
search	8983	repository	No
transformers (aio t-engine)	8090	repository	No
syncservice	9090	nginx	No
adw	80	nginx	No
nginx	80	`<client-ips>`	No
nginx	443	`<client-ips>`	No

NOTE: The transformers host will also contain the transform router process running on port 8095 and the shared file system process running on 8099 but communication between these components remains local.

Getting Started Quickly

The quickest way to get started and experiment with the playbook is by leveraging Vagrant to create a Virtualbox virtual machine to act as the control node and the target host.

Ensure your local machine has a minimum of 10G of memory and 4 CPUs
Clone this repository to your local machine
Install Vagrant
Install Virtualbox
Open Virtualbox application
In a terminal, navigate to the where you cloned the repository
Create environment variables to hold your Nexus credentials as shown below (replacing the values appropriately):
```
export NEXUS_USERNAME="<your-username>"
export NEXUS_PASSWORD="<your-password>"
```
Run the following command:
```
vagrant up
```
NOTE: The playbook takes around 30 minutes to complete.

Once ACS has initialized access the system using the following URLs using a browser:

Digital Workspace: http://172.100.100.100/workspace
Share: http://172.100.100.100/share
Repository: http://172.100.100.100/alfresco
API Explorer: http://172.100.100.100/api-explorer

To access the machine vagrant created and ran the playbook on use vagrant ssh.

Setup A Control Node

As mentioned in the introduction a control node is required to run the playbook. You can use any computer that has a Python installation as a control node; laptops, shared desktops, and servers can all run Ansible.

In the interest of keeping this guide simple we will use an AWS EC2 instance as the control node, the steps required are shown below:

Launch an EC2 instance using the Centos 7 or 8 (x86_64) AMI from the Marketplace (instance size/type does not matter)

Transfer the ZIP file to the control node and SSH into the machine

scp -i <yourpem-file> <local-path>/alfresco-ansible-deployment-<version>.zip centos@<control-node-ip>:/home/centos/
ssh -i <yourpem-file> centos@<control-node-ip>

Install the required dependencies for Ansible (replace the 7 with 8 in the URL if you're using CentOS 8)
```
sudo yum install -y unzip https://dl.fedoraproject.org/pub/epel/epel-release-latest-7.noarch.rpm
```
Install Ansible (replace el7 with el8 in the package name if you're using CentOS 8)
```
sudo yum install -y ansible-2.9.18-1.el7.noarch
```

Extract the ZIP file

unzip alfresco-ansible-deployment-<version>.zip

If you intend to deploy an Enterprise system, create environment variables to hold your Nexus credentials as shown below (replacing the values appropriately):
```
export NEXUS_USERNAME="<your-username>"
export NEXUS_PASSWORD="<your-password>"
```

Now you have the control node setup you can configure your deployment and decide what kind of deployment you would like.

To deploy everything on the control node follow the steps in the Locahost Deployment section or to deploy to one or more other machines follow the steps in the SSH Deployment section.

Configure Your Deployment

By default, without any configuration applied, the playbook will deploy a limited trial of the Enterprise version of Alfresco Content Services 7.x that goes into read-only mode after 2 days. If you'd like to try Alfresco Content Services for a longer period, request the 30-day Download Trial.

The sections below describe how you can configure your deployment before running the playbook.

License

If you have a valid license place your *.lic file in the configuration_files/licenses folder before running the playbook.

NOTE: You can also upload a license via the Admin Console once the system is running.

Alfresco Global Properties

You can provide your repository configuration by editing the configuration_files/alfresco-global.properties file.

The properties defined in this file will be appended to the generated "alfresco-global.properties" located in "/etc/opt/alfresco/content-services/classpath".

Enable SSL

If you have a FQDN and a certificate you want to use place the certificate and the key in the configuration_files/ssl_certificates folder before running the playbook. Also replace the fqdn_alfresco: "your_domain.com" with your own domain in group_vars/all.yml along with setting use_ssl: true.

NOTE: The certificate and the key should be named the same as the domain eg: your_domain.com.key and your_domain.com.crt

Override Playbook Variables

Ansible provides a mechanism to override variables provided by the playbook at runtime.

Whilst it's possible to override any variable defined by the playbook we have only tested changing the variables defined in group_vars/all.yml.

Variables can be overridden using either the --extra-vars or -e command line option when running the playbook.

If you have more than one variable to override we recommend using a separate file. The file name must be prefixed with "@", for example:

ansible-playbook ... --extra-vars "@my-vars.yml"

AMPs

Several AMP files are downloaded and applied during playbook execution, these are defined in a variable that can be overridden using the mechanism described in the previous section. Follow the steps below to apply your own AMPs

Open group_vars/all.yml and copy the whole amp_downloads variable definition
Create a new file and paste the amp_downloads variable
Add any additional AMPs you want to apply paying close attention to the dest property. If it's a repository AMP use the amps_repo folder, if it's a Share AMP use the amps_share folder
Save the file and reference it via the --extra-vars option when running the playbook

NOTE: This mechanism will be improved in a future release.

JVM Options

Each Java based service deployed by the playbook is configured with some default settings, including memory settings.

The defaults are defined in group_vars/all.yml so they can be overridden using the mechanism described above.

For example, to override the JAVA_OPTS environment variable for the All In One Transformer Engine place the following in your extra vars file:

tengine_environment:
  JAVA_OPTS: "$JAVA_OPTS -Xms512m -Xmx1g"

The *_environment variable is defined as a dictionary, all keys are added to the relevant components start script thus allowing you to define any number of environment variables.

External Databases

By default the playbook will deploy and configure a Postgres server for you. If you'd prefer to use an external database server you can override the repo_db_url variable as described previously.

An example custom database url is shown below:

repo_db_url: jdbc:mysql://54.164.117.56:3306/alfresco?useUnicode=yes&characterEncoding=UTF-8
repo_db_driver: com.mysql.jdbc.Driver

Along with the url the database driver binaries need to be provided for one or both services in the configuration_files/db_connector_repo and/or configuration_files/db_connector_sync folders.

The default database username (repo_db_username and/or sync_db_username) and password (repo_db_password and/or sync_db_password) in the configuration file group_vars/all.yml can also be overidden with your custom values.

Please refer to the Configuring Databases documentation for more detailed information.

Custom Keystore

By default the playbook deploys a default keystore to ease the installation process, however, we recommend you generate your own keystore following the instructions here.

There are three steps required to use a custom keystore:

Place your generated keystore file in the configuration_files/keystores folder (these get copied to /var/opt/alfresco/content-services/keystore)
Override the use_custom_keystores variable defined in group_vars/all.yml
Override the acs_environment variable and define your custom JAVA_TOOL_OPTIONS configuration

An example custom extra-vars file is shown below:

use_custom_keystores: true
acs_environment:
  JAVA_OPTS: " -Xms512m -Xmx3g -XX:+DisableExplicitGC
    -XX:+UseConcMarkSweepGC
    -Djava.awt.headless=true
    -XX:ReservedCodeCacheSize=128m
    $JAVA_OPTS"
  JAVA_TOOL_OPTIONS: " -Dencryption.keystore.type=pkcs12
    -Dencryption.cipherAlgorithm=AES/CBC/PKCS5Padding
    -Dencryption.keyAlgorithm=AES
    -Dencryption.keystore.location=/var/opt/alfresco/content-services/keystore/<your-keystore-file>
    -Dmetadata-keystore.password=<your-keystore-password>
    -Dmetadata-keystore.aliases=metadata
    -Dmetadata-keystore.metadata.password=<your-keystore-password>
    -Dmetadata-keystore.metadata.algorithm=AES"

Localhost Deployment

The diagram below shows the result of a localhost deployment.

To deploy ACS 7.1 Enterprise on the local machine navigate to the folder you extracted the ZIP to and execute the playbook as the current user using the following command (the playbook will escalate privileges when required):

ansible-playbook playbooks/acs.yml -i inventory_local.yml

Alternatively, to deploy an ACS Enterprise 7.0 system use the following command:

ansible-playbook playbooks/acs.yml -i inventory_local.yml -e "@7.0.N-extra-vars.yml"

Alternatively, to deploy an ACS Enterprise 6.2.N system use the following command:

ansible-playbook playbooks/acs.yml -i inventory_local.yml -e "@6.2.N-extra-vars.yml"

Or to deploy ACS Community use the following command:

ansible-playbook playbooks/acs.yml -i inventory_local.yml -e "@community-extra-vars.yml"

NOTE: The playbook takes around 30 minutes to complete.

Once the playbook is complete Ansible will display a play recap to let you know that everything is done, similar to the block below:

PLAY RECAP *******************************************************************************************************
activemq_1                 : ok=24   changed=0    unreachable=0    failed=0    skipped=17   rescued=0    ignored=0
adw_1                      : ok=24   changed=6    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0
database_1                 : ok=20   changed=0    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
nginx_1                    : ok=21   changed=8    unreachable=0    failed=0    skipped=8    rescued=0    ignored=0
repository_1               : ok=92   changed=43   unreachable=0    failed=0    skipped=14   rescued=0    ignored=0
search_1                   : ok=34   changed=13   unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
syncservice_1              : ok=39   changed=18   unreachable=0    failed=0    skipped=13   rescued=0    ignored=0
transformers_1             : ok=81   changed=10   unreachable=0    failed=0    skipped=44   rescued=0    ignored=0

Once ACS has initialized access the system using the following URLs with a browser:

Digital Workspace: http://<control-node-public-ip>/workspace (Enterprise Only)
Share: http://<control-node-public-ip>/share
Repository: http://<control-node-public-ip>/alfresco
API Explorer: http://<control-node-public-ip>/api-explorer

SSH Deployment

To deploy to hosts other than the control node an SSH connection is required. The control node must have network access to all the target hosts and permission to SSH into the machine.

The inventory file (inventory_ssh.yml) is used to specify the target IP addresses and the SSH connection details. You can specify one IP address for all the hosts to obtain a single-machine deployment, or different IP addresses for a multi-machine deployment.

The example snippet below demonstrates how to deploy the repository to a host with an IP address of 50.6.51.7 and SSH key at /path/to/ssh_key.pem.

repository:
  hosts:
    repository_1:
    connection: ssh
    ansible_host: 50.6.51.7
    ansible_private_key_file: "/path/to/ssh_key.pem"
    ansible_user: centos
    ansible_ssh_common_args: "-o UserKnownHostsFile=/dev/null -o ControlMaster=auto
      -o ControlPersist=60s -o ForwardX11=no -o LogLevel=ERROR
      -o IdentitiesOnly=yes -o StrictHostKeyChecking=no"

If you want to deploy everything to a single machine follow the steps in the Single Machine Deployment section, alternatively, to deploy to any number of separate machines follow the steps in the Multi Machine Deployment section.

Single Machine Deployment

The diagram below shows the result of a single machine deployment.

NOTE: You can optionally use the following guide to generate a target host and an inventory file for testing purposes.

Once you have prepared the target host and configured the inventory_ssh.yaml file you are ready to run the playbook.

To check your inventory file is configured correctly and the control node is able to connect to the target host navigate to the folder you extracted the ZIP to and run the following command:

ansible all -m ping -i inventory_ssh.yml

To deploy ACS 7.1 Enterprise on the target host execute the playbook as the current user using the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml

Alternatively, to deploy an ACS 7.0 Enterprise system use the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml -e "@7.0.N-extra-vars.yml"

Alternatively, to deploy an ACS 6.2.N Enterprise system use the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml -e "@6.2.N-extra-vars.yml"

Or to deploy ACS Community use the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml -e "@community-extra-vars.yml"

NOTE: The playbook takes around 30 minutes to complete.

Once the playbook is complete Ansible will display a play recap to let you know that everything is done, similar to the block below:

PLAY RECAP *******************************************************************************************************
activemq_1                 : ok=24   changed=0    unreachable=0    failed=0    skipped=17   rescued=0    ignored=0
adw_1                      : ok=24   changed=6    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0
database_1                 : ok=20   changed=0    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
nginx_1                    : ok=21   changed=8    unreachable=0    failed=0    skipped=8    rescued=0    ignored=0
repository_1               : ok=92   changed=43   unreachable=0    failed=0    skipped=14   rescued=0    ignored=0
search_1                   : ok=34   changed=13   unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
syncservice_1              : ok=39   changed=18   unreachable=0    failed=0    skipped=13   rescued=0    ignored=0
transformers_1             : ok=81   changed=10   unreachable=0    failed=0    skipped=44   rescued=0    ignored=0

Once ACS has initialized access the system using the following URLs with a browser:

Digital Workspace: http://<target-host-ip>/workspace (Enterprise Only)
Share: http://<target-host-ip>/share
Repository: http://<target-host-ip>/alfresco
API Explorer: http://<target-host-ip>/api-explorer

Multi Machine Deployment

The diagram below shows the result of a multi machine deployment.

NOTE: You can optionally use the following guide to generate target hosts and an inventory file for testing purposes.

Once you have prepared the target hosts (ensuring the relevant ports are accessible) and configured the inventory_ssh.yaml file you are ready to run the playbook.

NOTE at this stage ADW must be deployed on the same host (adw_1) as the NGinx reverse proxy (nginx_1)

To check your inventory file is configured correctly and the control node is able to connect to the target hosts run the following command:

ansible all -m ping -i inventory_ssh.yml

Optional To check if the required ports for the deployment are available on the target machine and we also have connectivity between nodes (ex. repository connecting to the db on 5432) please run the prerequisite_checks playbook before you deploy ACS. If there are any firewalls blocking connectivity this playbook will discover them.

ansible-playbook playbooks/prerequisite_checks.yml -i inventory_ssh.yml

To deploy ACS 7 Enterprise on the target hosts execute the playbook as the current user using the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml

Alternatively, to deploy an ACS 6.2.N Enterprise system use the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml -e "@6.2.N-extra-vars.yml"

Or to deploy ACS Community use the following command:

ansible-playbook playbooks/acs.yml -i inventory_ssh.yml -e "@community-extra-vars.yml"

NOTE: The playbook takes around 30 minutes to complete.

Once the playbook is complete Ansible will display a play recap to let you know that everything is done, similar to the block below:

PLAY RECAP *******************************************************************************************************
activemq_1                 : ok=24   changed=0    unreachable=0    failed=0    skipped=17   rescued=0    ignored=0
adw_1                      : ok=24   changed=6    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0
database_1                 : ok=20   changed=0    unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
nginx_1                    : ok=21   changed=8    unreachable=0    failed=0    skipped=8    rescued=0    ignored=0
repository_1               : ok=92   changed=43   unreachable=0    failed=0    skipped=14   rescued=0    ignored=0
search_1                   : ok=34   changed=13   unreachable=0    failed=0    skipped=11   rescued=0    ignored=0
syncservice_1              : ok=39   changed=18   unreachable=0    failed=0    skipped=13   rescued=0    ignored=0
transformers_1             : ok=81   changed=10   unreachable=0    failed=0    skipped=44   rescued=0    ignored=0

Once ACS has initialized access the system using the following URLs with a browser:

Digital Workspace: http://<nginx-host-ip>/workspace (Enterprise Only)
Share: http://<nginx-host-ip>/share
Repository: http://<nginx-host-ip>/alfresco
API Explorer: http://<nginx-host-ip>/api-explorer

Cleanup

What needs to be removed from a system will depend on your inventory configuration. The steps below presume a localhost or single machine deployment i.e. where all roles were run on the same machine.

Stop and remove the following systemd services:
- alfresco-transform-router.service
- alfresco-shared-fs.service
- alfresco-tengine-aio.service
- alfresco-sync.service
- alfresco-search.service
- alfresco-content.service
- nginx.service
- activemq.service
- postgresql-version.service (where version is 11 for ACS 6.2.N and 13 for ACS 7.x)
Remove the following yum packages:
- ImageMagick
- libreoffice
- nginx
- postgresql
Remove the following folders:
- /opt/apache-activemq-version
- /opt/apache-tomcat-version
- /opt/libreofficeversion
- /opt/openjdk-version
- /opt/alfresco
- /etc/opt/alfresco
- /var/opt/alfresco
- /var/log/alfresco
- /tmp/ansible_artefacts
- /tmp/Alfresco

NOTE: An additional "uninstall" playbook may be provided in the future.

Known Issues

The playbook downloads several large files so you will experience some pauses while they transfer and you'll also see the message "FAILED - RETRYING: Verifying if <file> finished downloading (nnn retries left)" appearing many times. Despite the wording this is not an error so please ignore and be patient!
The playbook is not yet fully idempotent so may cause issues if you make changes and run multiple times
The firewalld service can prevent the playbook from completing successfully if it's blocking the ports required for communication between the roles
The nginx and adw roles need to be deployed to the same host otherwise the playbook fails

Troubleshooting

Failed Downloads

If you see an error similar to the one below (in particular the mention of HTTP Error 401: Unauthorized or HTTP Error 401: basic auth failed) you've most likely forgotten to setup your Nexus credentials or mis-configured them.

fatal: [transformers_1]: FAILED! => {"msg": "An unhandled exception occurred while templating '{u'acs_zip_sha1_checksum': u\"{{ lookup('url', '{{ nexus_repository.enterprise_releases }}org/alfresco/alfresco-content-services-distribution/{{ acs.version }}/alfresco-content-services-distribution-{{ acs.version }}.zip.sha1', username=lookup('env', 'NEXUS_USERNAME'), password=lookup('env', 'NEXUS_PASSWORD')) }}\", u'adw_zip_sha1_checksum': u\"{{ lookup('url', '{{ nexus_repository.enterprise_releases }}/org/alfresco/alfresco-digital-workspace/{{ adw.version }}/alfresco-digital-workspace-{{ adw.version }}.zip.sha1', username=lookup('env', 'NEXUS_USERNAME'), password=lookup('env', 'NEXUS_PASSWORD')) }}\", u'acs_zip_url': u'{{ nexus_repository.enterprise_releases }}org/alfresco/alfresco-content-services-distribution/{{ acs.version }}/alfresco-content-services-distribution-{{ acs.version }}.zip'
...
...
Error was a <class 'ansible.errors.AnsibleError'>, original message: An unhandled exception occurred while running the lookup plugin 'url'. Error was a <class 'ansible.errors.AnsibleError'>, original message: Received HTTP error for https://artifacts.alfresco.com/nexus/service/local/repositories/enterprise-releases/content/org/alfresco/alfresco-content-services-distribution/7.0.0/alfresco-content-services-distribution-7.0.0.zip.sha1 : HTTP Error 401: Unauthorized"}

You can run the command shown below in the same terminal you're using to run the playbook to quickly test downloading a protected resource from Nexus.

wget -qO /dev/null --user=${NEXUS_USERNAME} --password=${NEXUS_PASSWORD} https://artifacts.alfresco.com/nexus/service/local/repositories/enterprise-releases/content/org/alfresco/alfresco-content-services-distribution/6.2.2/alfresco-content-services-distribution-6.2.2.pom

If everything is configured correctly you should see the following at the end of the output:

Saving to: ‘alfresco-content-services-distribution-6.2.2.pom’

alfresco-content-services-distribution-6.2.2.pom      100%[=============================================>]   8.53K  --.-KB/s    in 0.003s  

2021-02-18 13:50:44 (2.54 MB/s) - ‘alfresco-content-services-distribution-6.2.2.pom’ saved [8739/8739]

Nginx Failure

If the playbook fails not being able to start Nginx, make sure both ADW and Nginx point to the same host in the inventory file. Otherwise you'll encounter the error below:

TASK [../roles/adw : Ensure nginx service is running as configured.] **********************************
fatal: [adw_1]: FAILED! => {"changed": false, "msg": "Unable to start service nginx: Job for nginx.service failed because the control process exited with error code.
See "systemctl status nginx.service" and "journalctl -xe" for detail
s.\n"}

Communication Failures

If you are using a multi-machine deployment and the playbook fails with an error similar to the one shown below you may need to check the firewall configuration on the target hosts.

TASK [../roles/repository : Notify alfresco content service] 
*******************************************************************************************************
fatal: [repository_1]: FAILED! => {"changed": false, "elapsed": 300, "msg": "Timeout when waiting for 192.168.0.126:5432"}

Either disable the firewall completely or refer to the ports configuration section for what ports need to be accessible.

Presuming you are using firewalld the following example commands can be used to open a port, replacing <port-number> with the approriate number or replacing <service-name> with a well know service name e.g. "http".

firewall-cmd --permanent --add-port=<port-number>/tcp

or

firewall-cmd --permanent --add-service=<service-name>

After the firewall config has been set up a reload of the firewalld service is needed

If you are using a host that is behind a proxy you might experience timeouts or HTTP Error 401: Unauthorized errors.

A possible quick fix is to make http_proxy and https_proxy available to either current user or to the entire system.

export http_proxy=<protocol><proxy_address>
export https_proxy=<protocol><proxy_address>

or add the values in the /etc/environment

echo http_proxy=<protocol><proxy_address> >> /etc/environment
echo https_proxy=<protocol><proxy_address> >> /etc/environment

If this does not solve the issue, check the proxy configuration or contact your system administrator

Playbook Failures

If the playbook fails for some reason try re-running it with the -v option, if that still doesn't provide enough information try re-running with the -vvv option.

Alfresco Failures

If the playbook completes successfully but the system is not functioning the best place to start is the log files, these can be found in the /var/log/alfresco folder on the target hosts. Please note the nginx log files are owned by root as the nginx process is running as root so it can listen on port 80.

Provide feedback

Saved searches

Use saved searches to filter your results more quickly

deployment-guide.md

deployment-guide.md

Deployment Guide

Folder Structure

Service Configuration

TCP Port Configuration

Getting Started Quickly

Setup A Control Node

Configure Your Deployment

License

Alfresco Global Properties

Enable SSL

Override Playbook Variables

AMPs

JVM Options

External Databases

Custom Keystore

Localhost Deployment

SSH Deployment

Single Machine Deployment

Multi Machine Deployment

Cleanup

Known Issues

Troubleshooting

Failed Downloads

Nginx Failure

Communication Failures

Playbook Failures

Alfresco Failures

Files

deployment-guide.md

Latest commit

History

deployment-guide.md

File metadata and controls

Deployment Guide

Folder Structure

Service Configuration

TCP Port Configuration

Getting Started Quickly

Setup A Control Node

Configure Your Deployment

License

Alfresco Global Properties

Enable SSL

Override Playbook Variables

AMPs

JVM Options

External Databases

Custom Keystore

Localhost Deployment

SSH Deployment

Single Machine Deployment

Multi Machine Deployment

Cleanup

Known Issues

Troubleshooting

Failed Downloads

Nginx Failure

Communication Failures

Playbook Failures

Alfresco Failures