2.3.3. Installation for ARM64 or E2K processors

<< Prev   Next >>

1C:Enterprise distribution package for Linux on ARM64 or E2K processors consists of several packages. Use these packages to install client applications and a server cluster. A package file name consists of several parts: 1c-enterprise-<version1>-<add-in>_<version2>_<arch>.<extension>:

• <add-in>:
  • client. 1C:Enterprise client applications (thick client and thin client).
  • thin-client. 1C:Enterprise thin client (file infobase mode is not supported).
  • common. Common 1C:Enterprise add-ins.
  • server. 1C:Enterprise server add-ins and the integrity monitoring utility.
  • ws. Adapter for publishing a web client and 1C:Enterprise Internet services on Apache HTTP Server of supported versions.
  • crs. Configuration repository server.\
  • An add-in name can end with the -nls suffix. This means that a package with this name contains additional national resources (in addition to Russian and English localizations) for the respective package. So, the server add-in is located in two files: server (the server itself) and server-nls (additional national resources).
• <version1>. Full version number of 1C:Enterprise package. All version elements are dot-separated. For example, for 1C:Enterprise version 8.3.22.100, version1 of the package name will contain the 8.3.22.100 string.
• <version2>. Full version number of 1C:Enterprise package. The first three number elements are dot-separated. The last (fourth) number element is preceded by a hyphen ("-"). For example, for 1C:Enterprise version 8.3.22.100, version2 of the package name will contain the 8.3.22-100 string.
• <arch>. Processor architecture for which this package is used:
  • arm64. ARM64 processor.
  • e2k-8с. E2K processor.
• <extension>:
  • RPM version: rpm
  • DEB version: deb

If necessary, the required package file name is generated according to the rules above. If the name of the package you install is required, it is specified based on the add-in name. For example, the name of the common package for DEB version 8.3.22.100 looks as follows: 1c-enterprise-8.3.22.100-common_8.3.22-100-arm64.deb.

During installation, consider the following dependencies between packages:

• common has no dependencies.
• server depends on common.
• ws depends on common.
• crs depends on common, server, and ws.
• client depends on server.
• thin-client has no dependencies. No other 1C:Enterprise packages are required for a thin client. It conflicts with the common package. You can install either thin-client or other packages.
• National resource packages depend on their package.

To install a package, first install all the packages that this package depends on. For example, to install 1C:Enterprise thick client and Designer, first install the common and server packages and then install the client package.

Installation requires superuser (root) rights.

<< Prev   Next >>