What does thin client 1c mean? Publications. Determining the correct thin client version

Users of the service can work with applications not only in a web browser, but also in the 1C:Enterprise thin client.

This article will tell you how to install and use a thin client on a computer running the Windows operating system.

1. Determining the required version of the thin client

First you need to determine which version of the thin client you need.

2. Download the thin client

Download the required version of the thin client. Here are links to download thin client installation programs for those used in the service website versions of the 1C:Enterprise 8 platform and various versions of Windows:

A 64-bit thin client should only be installed if recommended by your service organization or service support line.

If the Internet browser does not ask where to place the downloaded file, the file will be saved in the folder designated in the default browser settings. Typically this folder is called Downloads or Downloads.

Automatic updating of the thin client under Windows XP and Windows Vista does not work. Therefore, you will have to install a new version of the thin client every time you update the version of the 1C:Enterprise platform in the service. This is not very convenient and we recommend that you consider upgrading to a more modern operating system.

3. Installing a thin client

Install the thin client using the downloaded installation file:

4. Setting up the thin client

For the convenience of working with the 1C:Enterprise 8 thin client, it is recommended to enable the mode for displaying a list of infobases in the form of a tree (this only needs to be done once):

1. Launch the thin client.
2. Click in the window Launch 1C:Enterprise button Setting...
3. Check box Display as a tree.
4. Press the button OK.

After this, the group will be located in the list of thin client infobases website with points.

for platform 8.2:

for platform 8.3:

Comment. Automatic updating of a thin client under Windows XP and Windows Vista via 1C:Link may not work. This is not very convenient and we recommend that you consider upgrading to a more modern operating system.

Configuring the 1C Thin Client to work with the 1C: Enterprise 8 platform version 8.3.4.437 and higher

Install the root certificate of the 1C: Link service in the Windows certificate store according to the instructions for the Internet Explorer browser.

https://<ваш-сайт>.link.1c.ru/xxx

Select "Windows Certificates" as a method to verify the server certificate

Click "Done"

Setting up automatic authorization on the web server

• Select the required information security in the 1C Thin Client and click the “change” button
• Click on the "Advanced" link (located under the infobase address field)
• In the "Select a web server user authentication method" section, select "Select automatically" and click "Next".
• In the certificate settings window, click "Next".
• In the "Additional launch parameters" section, specify the line: where login is the web server user login, and password is his password.

Click the "Finish" button and check the connection to the infobase.

Read more about the Thin Client settings on the ITS website.

Configuring the 1C Thin Client to work with the 1C: Enterprise 8 platform version 8.2.19.121 and higher

To work in a thin client, download . Save instead <1C>\bin\cacert.pem , where<1C> - installation directory of the 1C Thin Client. This will prevent the SSL error "Peer certificate cannot be authenticated with known CA certificates" from appearing.

Enter the name of the infobase, select "Web server" and click "Next"

Enter the address of your infobase: https://<ваш-сайт>.link.1c.ru/xxx,where xxx is your web application path.

Click "Done"

Configuring the 1C Thin Client to work with the 1C: Enterprise 8 platform of versions not included in the list of recommended ones

If you want to use a thin client version different from those recommended above to work in the 1C: Link service, you may need to configure the work according to HTTP or installation STunnel.

Configuring the Thin Client to work via HTTP

The Link Agent has the ability to work in a thin client using the HTTP protocol. However, the preferred protocol for working in a thin client via 1C:Link is HTTPS. It is not recommended to use the http protocol, since when used, data is transmitted unencrypted and can be intercepted by an attacker.

If you are sure of the need to use this protocol to work in a thin client through the 1C:Link service, you can use the instructions presented below:

Open the link agent control panel and enable work via HTTP (section 4.4 of the 1C:Link user manual).

Set up the thin client:

Launch the thin client and click the Add button.

Enter the name of the infobase, select "Web server" and click "Next"

Enter the address of your infobase: http://<ваш-сайт>.link.1c.ru/xxx,where xxx is your web application path.

Click "Done"

Installation and configuration of Stunnel

Install the Stunnel program on a computer with a 1C Thin Client. After installing the program, run it.

In the window that opens, select "Configuration"

In the drop-down menu, select "Edit stunnel.conf"

Notepad will open with the configuration file. Replace the text in the file with the following lines.

After you have installed the platform, created an empty configuration (or installed some educational demo configuration), then when you launch the 1C starter you will see two buttons: “1C Enterprise” and “Configurator” (for this you need to select some database from the list, see Fig. 1.1.1).

Rice. 1.1.1. Starter 1C

By and large, these are the two main types of client applications.

What is a client application anyway? A client application is a program installed on the user’s computer that allows the user to interact with the 1C: Enterprise system. In fact, we have two main types of programs in which the user can work: a configurator, where the programmer develops an application solution, and an enterprise, where the user works with data and algorithms developed by the programmer. This was the case in platforms 8.0 and 8.1. With the advent of platform 8.2, and then platform 8.3, the number of client applications increased.

After the release of platform 8.2, “1C: Enterprise” in user application mode can work in thin and thick clients, and a web client has also appeared that allows you to work with “1C: Enterprise” from a web browser.

In total, there are currently four types of client applications:

• "Thin client"
• "Fat Client"
• Web client

Why did it become necessary to divide a regular client application into three types: “thin”, “thick” and web client? This is due to the development of technology in general and the Internet in particular. Very often the need began to arise to work with 1C: Enterprise via the Internet, and this began to impose certain restrictions, since the bandwidth of the Internet is much narrower than that of a regular local network. Therefore, those platform technologies that existed in editions 8.0 and 8.1 have become inapplicable in the new realities. As a result, platform 8.2 was developed, which was divided into three types: “thick”, “thin” and web client.

Let's look at all types of clients in more detail.

"Thin client"

Let's start with the thin client. “Thin client” is a type of 1C: Enterprise client application that can be used to work over the Internet. At its core, it only displays data on a form or in a report; there is no access to object types from the thin client, and you cannot run queries under it. The resources of the device on which the thin client is running are used only to display data on the display screen; all calculations, queries and algorithms must be performed on the server side. You cannot work in the configurator under this client type.

This type of client application is supplied as a separate distribution, which is called « Thin client 1C:Enterprise for Windows», downloaded from the 1C website (if you have an ITS subscription) and installed on your local machine. The executable file in the Windows operating system is called 1Cv8с.exe.

The “thin client” can communicate with the database via TCP/IP, HTTP, HTTPS protocols. In order for the thin client to work over the HTTP and HTTPS protocols, a Web server, such as Apache or IIS, must be installed and configured on the server side. And the most interesting thing: the web server can interact with 1C-Enterprise both in file and client-server mode.

Let's analyze the work of the “thin client” using different protocols. First of all, let's start with the familiar TCP/IP (for those who don't know, this is the most common protocol for operating an Ethernet local network). There are two options for working with a thin client over an Ethernet network: client-server option and working with a file database.

Let's consider both of these options for working with 1C: Enterprise:

File option applicable when one or more users work within a small network, and also when large amounts of data or cumbersome calculations are not used. In this version of work, all data is located in one file 1Cv8.1CD, which is called the “1C: Enterprise” file database. Schematically, the operation of the file option can be represented as follows:

Rice. 1.1.2 Schematic representation of the operation of the file option

Client-server option has a more complex structure. It is designed for large numbers of users and for cumbersome calculations of massive amounts of data. In total, this option has three links: the client is the application on which the end user works; server cluster "1C: Enterprise" is a program that ensures interaction between the client and the database management system; SQL - server (database management system) is a special program designed to organize a database and store it. It can be represented schematically like this:

Rice. 1.1.3 Schematic representation of the client-server version

Let's return to the “thin client”. As mentioned above, this is a client application via the protocol TCP/IP can work with both the file database option and the client-server architecture option.

In the file mode of operation (Fig. 1.1.4), the “thin client” interacts directly with the file database. At the same time, a specialized server environment is organized on the “thin client” side, which, in essence, emulates the operation of a server. This specialized server environment is not allocated as a separate process in the operating system, but is included in the thin client process. It takes care of loading the application configuration and other server actions necessary for the normal functioning of the thin client.

In the case of the client-server option (Figure 1.1.5), the thin client directly interacts with a cluster of 1C:Enterprise servers via a local Ethernet network. In this version, the operating principles are exactly the same as for the “thick client”.

Why do you need to use a “thin client” when working on a local network, when you can work under a “thick client” for this? The local network of an enterprise does not always use good, fast machines capable of taking on some calculations. Very often these can be “destroyed” computers, and in this case, working under a “thin client” is completely justified. When working in a “thin client”, smaller amounts of data pass over the local network, all calculations are carried out on the server, and not on the local machine, and therefore lower performance requirements are set for the computers on which this type of client application is running (in the case when used client-server version of the database operation).

Now let's move on to working with the “thin client” via the Internet. Working with this type of client application via the Internet is possible both in the file version and in the client-server version.

But in both cases, for its full functioning, a web server (Apache or IIS) must be installed and running on the server side. In this case, the following chain works: the “thin client” interacts with the web server via the HTTP and HTTPS protocols, and the web server already interacts either directly with the file database (see Fig. 1.1.6) or with the 1C: Enterprise server cluster. , and the server cluster interacts with the SQL server according to the familiar scheme.

In this book, we will not examine in detail the mechanisms for configuring the “thin client” andweb client for working via the Internet, but we will touch only on general points so that you understand the principle of operation.

And the last important feature of the “thin client”: under it you do not have the opportunity to work with the configurator. When you launch the “thin client”, the “configurator” button in the 1C starter will be missing (see Figure 1.1.8). In principle, this is logical: there is no point in giving access to a “heavy” configurator when you have limited network resources.

Rice. 1.1.8. View of the thin client launch window

Web client

The next interesting type of client that we will look at is a web client. This type of client application is required to work only over the Internet. Moreover, if in order to operate a “thin client” on a local machine it was necessary to install software, then in order to work under a web client this is not necessary. All work with this client can be done through an Internet browser (Mozilla, Opera, Internet Explorer, etc.). This is a very convenient type of “thin client”: any user, anywhere in the world from any device can launch an Internet browser, enter the address of the web server where the database is published, and gain access to this very database. There is no need to download or install any software.

The Web client can work with both a regular file database and a client-server architecture. The only thing is that in both cases, as in the case of a “thin client” working via the Internet, it is necessary to install special software on the server side - a web server (usually Apache or IIS).

The principles of operation of a web client in the case of a file database and client-server architecture are presented in Fig. 1.1.9 and 1.1.10

"Fat Client"

“Thick client” is the main type of client under which you can carry out normal work with 1C: Enterprise. Under this type of client, almost all the functionality provided by the built-in 1C programming language is available. For example, you can work with queries and application types under it.

One of the features of the “thick client” is that it supports operation in normal mode, i.e. under the “thick client” you can run applications developed under the 8.1 and 8.0 platforms. – regular applications. You can also launch regular forms in managed applications, which naturally cannot be done in a thin client.

We will talk in detail about regular and managed applications in the next chapter.

The “thick client” is installed by a regular distribution kit and is launched as an executable file in the Windows operating system 1Cv8.exe.

Since working with a “thick client” requires significant computing power, you can communicate with the database either directly or via a local Ethernet network. This type of client application can work with both a file database and a client-server architecture (using the TCP/IP protocol).

In the case when the client-server version of the “thick client” operation is used (Fig. 1.1.13), the “thick client” is connected to the 1C:Enterprise server cluster via the local network, and the server cluster interacts with the SQL server ( DBMS). Moreover, the server cluster and the DBMS can be located on different computers; the administrator has the ability to separate them in order to optimize server performance.

The thick client can work with a file database either directly: the database file is located on the same computer where the thick client is installed, or via a local network (Fig. 1.1.12). If there is interaction with a file database over a local network, full access to it must be provided through a shared network resource.

And as should already be clear, the “thick client” is the only user application from which you can freely open the configurator and conduct development. No other 1C:Enterprise user application allows you to do this. When you launch the “thick client”, you will see the “Configurator” button in the launch window (see Fig. 1.1.11).

Rice. 1.1.11 Thick client launch window

And in conclusion, we present a table that clearly makes it clear how these three types of client applications differ: “thick client”, “thin client” and web client.

	"Fat Client"	"Thin client"	Web client
Working with the configurator	+	—	—
Work via Ethernet local network	+	+	+
Internet work	—	+	+
Distribution installation required	+	+	—
Working with a file database	+	+	+
Working with sql server	+	+	+
Working with regular applications	+	—	—
Working with managed applications	+	+	+
Open regular forms in managed apps	+	—	—

Table 1.1.1 Differences between various client applications.

Sometimes it seems that learning the programming language in 1C is complicated and difficult. In fact, programming in 1C is easy. My books will help you easily and quickly master programming in 1C: and “Basics of development in 1C: Taxi”

This book is suitable for those who have already started programming and are experiencing certain difficulties with this topic and for those who have been programming for a long time, but have never worked with 1C managed forms.

1. Without complex technical terms;
2. More than 600 pages of practical material;
3. Each example is accompanied by a drawing (screenshot);

Promo code for a 15% discount - 48PVXHeYu

Learn programming in 1C with the help of my book “Programming in 1C in 11 steps”

1. No complicated technical terms.
2. Over 700 pages of practical material.
3. Each task is accompanied by a drawing (screenshot).
4. A collection of problems for homework.
5. The book is written in clear and simple language - for a beginner.
6. The book is sent by email in PDF format. Can be opened on any device!

If this lesson helped you solve any problem, you liked it or found it useful, then you can support my project by donating any amount:

You can pay manually:

Yandex.Money - 410012882996301
Web Money - R955262494655

Join my groups.

1C:Enterprise programs, which have become the leader in automation, are increasingly being integrated into the business and enterprise network. The 8th version of the program is no longer intended only for accounting and has long gone beyond the limits of one or two computers. Its capabilities are increasingly being used not only by managers to control financial transactions, but also by CRM managers, storekeepers for warehouse accounting, etc.

In this regard, the load on the local computer network of the enterprise and on the computer center - the server on which the 1C databases are located - has sharply increased. Understanding this, the developer has provided several options for deploying 1C:Enterprise programs - file and client-server.

File version 1C: pros and cons

The simplest and cheapest option for deploying the 1C:Enterprise 8 platform is the file option. Many people make the mistake of saying that it is not suitable for multi-user networking. Not at all, this option can be used both for one user without network versions, and for sharing with up to 5 clients. To set up the operation of the file version of 1C, you can use a simple computer on which a directory is “shared” (access to a shared folder is open), in which there is actually a single file with a database. Naturally, this computer must be constantly turned on for users to have access to the database. The second not very pleasant moment is full access of all users working with the program to this shared folder, i.e. each of them can not only work with 1C, but also have the opportunity to copy this database to their computer (flash drive, removable disk, etc.) ...) or simply delete. This suggests the conclusion that it is impossible to control the safety of data in a large company. And of course, one cannot help but say that when using the file version of 1C deployment, all calculations and operations are performed on the client’s computer, so workstations must have a good supply of computing power: a powerful processor and sufficient RAM. And at the current dollar exchange rate, not everyone can afford it, considering, moreover, that with the release of each new version of the program, the requirements for the hardware only become higher.

A significant advantage can be considered the almost zero costs for the server part - it can be a simple powerful computer on which, for example, a chief accountant works with a good hard drive and a network card with a bandwidth of 1 GB/s. Even regular (non-server) operating systems will provide up to 5 connections from 1C clients. Backup is also quite simple, which, by the way, in the latest versions can be configured using standard 1C tools.

Client connections to file 1C

For users to work with the file server version of 1C:Enterprise, there are 2 options: “thick client” and web client. The first option is the simplest; it is the one used in local versions and is not worthy of much attention. But when using the web client, there is practically no need to install software. To work in this mode, you only need a compatible web browser, which can be launched on almost any platform and even on a tablet via 3G Internet. Of course, you will have to complicate the setup a little, since you will need a web server in addition to the file server, but this will bring a lot of advantages:

• work on any device and any operating system (MacOS, Linux, Windows, Android tablet, etc.);
• work from any place where there is Internet (of course, with appropriate settings);
• there is no need to install and update software on workstations.

  General points for deploying file server 1C

  The issue of licensing cannot be avoided: to connect each client, regardless of the type of connection, in addition to the program itself, you must purchase a client license for access by a simultaneously working user. This can be either a hardware key (USB token) or a software PIN code.

  In the next part of the article, I will dwell in detail on the client-server version of 1C:Enterprise, the pros and cons of this approach, and options for saving on software.

Most 1C users, in particular 8s, have repeatedly heard such commonly used terms as “thin client” and “thick client”, but most probably do not understand their meaning.

In principle, for an ordinary user who uses the program every day at work, the difference between a thin and a thick client is not noticeable, since such a user does not need to delve into the technical intricacies of the processes performed by the computer and their algorithms. But at the same time, it will not be superfluous to understand, at least at a primitive level, the main features of the 1C 8.3 platform, knowledge of which in critical situations will help solve some problematic issues.

For example, it may be quite possible that some errors constantly appear in one computer, while in another, on the contrary, they are completely absent. In such a situation, understanding the nuances of the work of different clients, it is often enough to simply change one client to another, and thus quickly solve the problem.

So, what are the differences between the 1C thick and thin clients?

Thick client 1C

In this mode, the main part of the information is processed on the user's computer. Therefore, this mode is very demanding on network speed.

Thin client 1C

In this mode, all operations are performed on the server where the database is stored. The user is only shown a display of the received data.
For example, to generate a report, the resources of the server are used, and not the client PC, as is the case with the “thick client”.
This allows you to reduce the resource requirements of client computers and network speed. Also for this reason, the thin client distribution takes up less space.