Local installation - Alfresco Content Services - 23.4 - 23.4 - Ready - Alfresco - external

Alfresco Content Services

Platform
Alfresco
Product
Alfresco Content Services
Release
23.4
License

The diagram below shows the result of a local installation.

This image is a system architecture diagram from Alfresco Software Inc., illustrating the components and their interactions within the system. Here's the detailed description of the diagram: User: The user interacts with the system through various components. Control Node interacts with Playbook: Central control component and Inventory component. The Playbook controls interactions and deployments across all components. NGINX Proxy interacts with Transform Router and Digital Workspace. Transform Router interacts with Java, AIO Transform Engine, Repository & Share, PostgreSQL, and Common. Digital Workspace interacts with Sync Service and Shared File Service. Shared File Service interacts with Java and Repository & Share. Repository & Share interacts with Java, Sync Service, PostgreSQL, and Common. Search Service interacts with Repository & Share, Java, and PostgreSQL. AIO Transform Engine interacts with PostgreSQL. Sync Service interacts with ActiveMQ, Java, and Common. ActiveMQ interacts with Java. Tomcat interacts with Java. Java interacts with Common. All components are interconnected, ensuring seamless data flow and functionality within the system.

To install Content Services (Enterprise) on your local machine, navigate to the folder where you extracted the ZIP, and run the playbook as the current user (the playbook will escalate privileges when required)

cd alfresco-ansible-deployment-<version>
ansible-playbook playbooks/acs.yml -i inventory_local.yml

Alternatively, to deploy other versions of Content Services use one of the following commands:

  • 7.3:
    ansible-playbook playbooks/acs.yml -i inventory_local.yml -e
              "@7.3.N-extra-vars.yml"
  • 7.2:
    ansible-playbook playbooks/acs.yml -i inventory_local.yml -e
              "@7.2.N-extra-vars.yml"
  • 7.1:
    ansible-playbook playbooks/acs.yml -i inventory_local.yml -e
              "@7.1.N-extra-vars.yml"
  • 7.0:
    ansible-playbook playbooks/acs.yml -i inventory_local.yml -e
              "@7.0.N-extra-vars.yml"

If you see an error message during installation, then check for Troubleshooting.

Note: The playbook takes around 30 minutes to complete.

By default, the Content Services playbook will now also check Operating System compatibility. You can add the flag -e skip_os_test=true if you want to deploy on an unsupported Operating System distribution.

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

PLAY RECAP *******************************************************************************************************
acc_1                      : ok=24   changed=6    unreachable=0    failed=0    skipped=6    rescued=0    ignored=0
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

For details about the webapp URLs, location of logs, configuration etc., see Useful information.

If you’re deploying a production system, ensure that you review the additional information provided in Securing your installation.