As described in the builder_pre_installation section there are some system requirements that the instance must meet before installing Builder.
It’s important to note that although CARTO On-premises products are prepared to run inside a Linux system that meets the previous requirements, it has no knowledge of what there is outside that system. The On-premises technical administrator must be able to prepare the system to work in a specific way inside the network.
Certain network configurations that require backend or frontend applications to be integrated with custom external services or protocols like non-transparent proxies, external authentication services, etc.. may not be compatible with CARTO on-premises.
We focus on delivering applications and services that provide the biggest value for LI solutions but we don’t provide, by default, customized integration with clients services.
If you have doubts about how CARTO on-premises applications will work in your specific network topology, please don’t hesitate to contact us. Our technical experts will be willing to discuss with you different solutions and approaches.
As commented above CARTO Builder on-premises is prepared to work without crossing the boundaries of the instance where it is running. CARTO does not monitor, send or receive any type of information from the on-premise services installed. However, depending on the connectivity of the environment there may be some limitations on the service.
CARTO Builder on-premises can run in two different modes:
When we release a new version of CARTO on-premises we generate a simple to use command line installer. This installer together with an easy to read and to modify configuration file allows installing the entire stack or just one role in any instance just running one command.
Our installer runs some consistency checks before finishing in order to detect any possible error and not to leave an inconsistent installation. Once the installation has finished either the entire stack or the specific role that has been installed will be fully configured and ready to use.
The installation process is as easy as running these commands:
1 2 3 4 tar xfz carto-builder-<version>-rhel-7-x86_64.tar.gz cd carto-builder-<version>-rhel-7-x86_64 sudo ./cartoctl init --license license1.lic sudo ./cartoctl nodes install
or, in the case of multi host installation:
1 2 3 tar xfz carto-builder-<version>-rhel-7-x86_64.tar.gz cd carto-builder-<version>-rhel-7-x86_64 sudo ./cartoctl init --license license1.lic
~/.carto/config.ymland define your node architecture by setting the node fqdns and the roles that must be installed in each node.
config.ymlconfig database defined in step number (2) into
~/.carto/config.ymland perform the node installation.
cartoctlwill automatically detect the node fqdn and will then match it with
~/.carto/config.ymlin order to install the suitable roles accordingly.
1 sudo ./cartoctl nodes install
The upgrade process is similar. Running the installer is enough to detect the current running system and upgrade it.
1 sudo ./cartoctl nodes upgrade