2.7. Recommendations for system deployment

<< Prev   Next >>

To simplify automated installation of new 1C:Enterprise versions on the user computer (including the initial system installation), the following file structure in a network directory is recommended (an option of a server directory on a computer running Windows is described):

• Fig. 11. Directory structure

On the figure above:

• \\Server\1CEDistr is a directory on Server where files required for the system deployment are located. On a computer running Linux or macOS, the \\Server\1CEDistr directory must be mounted on the computer. Using UNC paths on Linux and macOS is not supported.
• 1cestart is the launcher. For initial installation, start the launcher from this network directory. You can start the launcher from the local hard drive if paths to distribution packages are correctly set up in configuration files and the launcher settings allow automatic installation of the new application version.

  It is recommended that you import the launcher from the latest 1C:Enterprise version that is installed in a local network.

• ibcommon.v8i is a list of shared infobases (the name can be changed).
• 1cescmn.cfg is a common configuration file. We recommend that you specify the following parameters:
  • CommonInfoBases=FileNameWithTheListOfCommonInfobases.v8i. Set this parameter to display the list of infobases in the launcher.
  • InstallComponents. Use this parameter to specify the components you need to install on user computers.
  • DistributiveLocation. Use this parameter to specify 1C:Enterprise distribution package directory.
• 8.3.18.100 is a directory with the following 1C:Enterprise distribution packages:
  • Win32. Distribution package directory of the 32-bit application version for Windows.
  • Win64. Distribution package directory of the 64-bit application version for Windows.
  • macOS. Distribution package directory of the application version for macOS. The distribution packages are located in the *.dmg files.
  • Lin32. Distribution package directory of the 32-bit application version for Linux. The distribution packages are located in the *.run files.
  • Lin64. Distribution package directory of the 64-bit application version for Linux. The distribution packages are located in the *.run files.
• 8.3.18.150 is a directory with 1C:Enterprise distribution packages. The directory structure is similar to the directory with version 8.3.18.100 (see the previous paragraph).

In this example, the following common configuration file is used to install all components and two languages: Russian and English:

Content of 1cescmn.cfg file:

CommonInfoBases=ibcommon.v8i
DistributiveLocation=\\Server\1CDistr
DistributiveLocation=/Volumes/Server/1CDistr
DistributiveLocation=/mnt/server/1CDistr
InstallComponents=DESIGNERALLCLIENTS=1 SERVER=1 WEBSERVEREXT=1 CONFREPOSSERVER=1 SERVERCLIENT=1 CONVERTER77=1 LANGUAGES=ru

When a new 1C:Enterprise version is released (for example, 8.3.18.200), do the following:

• In the \\Server\1CDistr directory, for version 8.3.18.200, create a directory structure similar to the previously created versions.
• Place the distribution package files in the matching directories considering the operating system and the bitness (for Windows).

1C:Enterprise will automatically complete the installation on startup. Remember the following features when using such a deployment scheme:

• On Windows:
  • Launcher always installs 1C:Enterprise into the default folder. To change the installation directory, run the installer for the required version (setup.exe) manually.
  • Only the InstallComponents parameter from the common configuration file is used during installation. Other parameters do not affect the installation process and are not copied from the common configuration file to the local configuration file. In the example above, the following components are used:

InstallComponents=DESIGNERALLCLIENTS=1 SERVER=1 WEBSERVEREXT=1 CONFREPOSSERVER=1 SERVERCLIENT=1 CONVERTER77=1 LANGUAGES=ru

• During installation, the CommonCfgLocation parameter is written to the local configuration file. Its value is the path to the common configuration file, which is located in the deployment directory. In the example above, the path to this file is: \\server\1cdistr\1cescmn.cfg. Parameters specified in this file will be used both by the launcher and in the startup dialog box of the client application.
• Whenever Windows XP is unavailable in a list of client operating systems, there is no need to copy files with _xp name suffix to directories with distribution packages for OS Windows. Examples of such files: 1CEnterprise 8_xp.msi, 1026_xp.mst, 1031_xp.mst and so on.
  • On Linux:
• Server directory where the installation files are located must be mounted on the client computer in any way possible. On all client computers running Linux, this directory must be mounted at a mount point with the same name. In the example above, the \\Server\1CDistr directory is mounted at the /mnt/server/1CDistr mount point. Use forward slashes ("/") to specify the path.
• InstallComponents parameter of the common configuration file is ignored.
  • On macOS:
• Server directory where the installation files are located must be mounted on the client computer in any way possible. On all Apple client computers, this directory must be mounted at the mount point with the same name. In the example above, the \\Server\1CDistr directory is mounted at the /Volumes/Server/1CDistr mount point. Use forward slashes ("/") to specify the path.
• InstallComponents parameter of the common configuration file is ignored.

If the infobase is accessed via a web server, you can use other delivery methods for a client application distribution package.

<< Prev   Next >>