-
Zextras Carbonio 23.6.0
-
-
- Older Version's Changelogs
- Changelog Version 23.2.0
- Changelog version 23.3.0
- Changelog Version 23.4.0
- Changelog Version 23.5.0
- Changelog Version 23.7.0
- Changelog Version 23.6.0
- Changelog version 23.9.0
- Changelog Version 23.10.0
- Changelog for Release 23.11.0 of Carbonio
- Changelog for Release 23.12.0 of Carbonio
-
-
-
-
Carbonio Community Edition
-
Suite for Zimbra
- Zextras Suite documentation
- Introduction
- Installation Instructions for Zextras Suite
- Licencing of Zextras Suite
- File Management for Licences
- Zextras Backup
- Backup and Restore by Zextras
- Zextras Backup Advanced Methods
- Zextras for Mobile
- Service for Address Books
- Troubleshooting Zextras Mobile
- Powerstore Zextras
- The Indexing of Attachments
- Extractor of External Content
- Delegated Admin Provisioning Zextras Admin
- The Zextras Drive
- Docs Zextras
- Authentique Zextras
- Team Zextras
- Video Server Zextras
- CLI
- next6 back
-
- Changelog for Zextras 3.1.x releases
- Changelog for Zextras Suite 3.2.0
- Changelog for Zextras Suite 3.3.0
- Zextras Suite Changelog - Release 3.4.0
- Changelog for Zextras Suite 3.5.0
- Changelog for Zextras Suite 3.6.0
- Changelog for Zextras Suite 3.7.0
- Changelog for Zextras Suite 3.8.0
- Changelog for Zextras Suite 3.9.0
- Changelog for Zextras Suite 3.10.0
- Changelog for Zextras Suite 3.11.0
- Changelog for Zextras Suite 3.12.0
- Changelog for Zextras Suite 3.13.0
- Changelog for Zextras Suite 3.14.0
- Changelog for Zextras Suite 3.15.0
- Changelog for Zextras Suite 3.16.0
- Changelog for Zextras Suite 3.17.0
- Changelog for Zextras Suite 3.18.0
- Zextras Suite Changelog - Release 3.19.0
- next4 back
A cluster engaging with a database instance hosted by a third-party service provider is a common example of external service integration. Carbonio Mesh is used to deploy in Carbonio CE circumstances like this one.
The Scenario and the Requirements
Our example scenario consists of a Carbonio CE Multi-Server installation that contains the following components:
- Carbonio Files Nodes: one or more
- One cluster node (potentially distinct from the Carbonio Files Nodes) was chosen as the terminating gateway.
- Carbonio Files uses a PostgreSQL database, which can either
- A server that is not part of the Carbonio CE infrastructure.
- A third-party service hosts the website remotely.
Because the process needs manual file editing and running commands, the setup requires access to the command line when terminating the gateway, however certain instructions at the conclusion of the procedure require access to the database node.
Finally, keep the cluster credential password handy because token creation requires it.
Let us now begin the operation by first installing Carbonio Mesh and then Carbonio Files.
Setup and security
A few actions must be completed during the initial setup.
Make a committed user.
Create policies. Carbonio Mesh must be made aware of the services to be routed, which in our case is the Carbonio Files database, carbonio-files-db.
Create a directory to hold all of the settings.
The Definition of External Service
Routing of Services
CAFile
Service Systemd
Carbonio-files-db configuration
- set the database name
- configure username and password
Installation of Carbonio Files Nodes
Take Services Out of Catalogue
- Stop the systemd unit service and remove the configuration file from the system.
- Uninstall the gateway configuration.