What does a thin client in 1C Enterprise mean? Publications. Thin client - a modern way of working

What are thick and thin clients in the 1C Enterprise 8.3 system? What are the differences between a thin and a thick client?

Your programmers call our accountants “fat clients”, take action!

From user complaints to the project manager.

1C Enterprise has a client-server architecture, which means that the system consists of two components - a client and a server. The client is the collective name of the consumer (user) application, and the server is the service part, hidden from the user.

Get 267 video lessons on 1C for free:

Thick client 1C

A thick client is a “usual” type of client application for 1C 8. The peculiarity of this type of application is that the system processes most of the information on the user’s computer. In a thick client, a very large part of the information is stored on the user's computer in the form of temporary files.

Since most of the data is processed on the user's computer, this mode is very demanding on the data channel.

Before the advent of the 1C 8.2 platform, this was the only option for launching the 1C system. To launch the thick client, use the file 1cv8.exe.

Work on developing an application solution () is only possible in thick client mode.

Thin client 1C

The thin client appeared in 1C with the release of platforms 8.2 and 8.3. Working in thin client mode is only possible in managed application mode.

In thin client mode, all actions are performed on the server, and the user only receives a display of the information received. This mode of operation does not require large resources of both the system and the communication channel. The thin client installation distribution takes up much less data.

The thin client is launched by the file 1cv8c.exe.

In addition to the thick and thin clients, there is also .

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.) .d.) 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, the 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.

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.

Many people are familiar with the name 1C, but not everyone understands exactly how it works. 1C: Enterprise is a software product that was originally developed to automate accounting. Today it is used to operate the entire enterprise. There are several options for interacting with the database; in this article we will look at the differences between the 1C thick and thin clients.

Fat client - a long-familiar work option

The original type of program viewing that existed in 1C: Enterprise from the very beginning is called thick. Before version 8:2 it was the only one, but now it is considered the simplest possible. It is worth noting that the application in question lives up to its name. Its functionality includes almost all possible commands, but it requires very good network speed and fairly large computer resources.

This is explained quite simply: the thick client processes most programs in the built-in 1C language on the user’s computer.

1. How the thick client works:
2. First, data is requested from the server;
3. The information is sent to the user's application;
4. The information is then processed.

Thin client - a modern way of working

Introduced in the latest update, the slim app is radically different from its predecessor. Now users can work from home without wasting extra bandwidth or overloading their personal PCs. This change is caused by some change in concepts about how such work should take place. The requested processes are processed not on the user's computer, but on the server computer, which then sends the received data to the requester. It turns out that users can breathe easy, but how can they find a device that can cope with the work of an entire huge enterprise? The manufacturer has also provided for this issue - the server can be divided into several computers, obtaining as much machine power as needed.

This is what the algorithm looks like:

• First, it sends a request for the necessary information;
• The server communicates with the database;
• 1C server processes the received data;
• The server sends the requested information to the user.

The information received is enough to understand that there are differences between the applications, so it would not be superfluous to familiarize yourself with such descriptions before starting work.

Does it make sense to use a thick client?

As already mentioned, many users do not want to accept innovations and remain faithful to the old application. But is it just a matter of devotion? No and no again.

Whenever possible, you should connect through a thick client. Today its functionality remains the most extensive and convenient. For example, the 1C configurator works only in the old version, and the file database is accessed exclusively through the “thick” version of the client application.

But no one argues that the idea of ​​a thin client sounds tempting, and everyone will benefit from the full implementation of this idea, especially large enterprises, for which all this was conceived. Rumor has it that in the coming years the entire software product will be transferred to a new client, but no one is talking about the fate of Tolstoy. Perhaps it will go down in history as unnecessary, but at the moment the time has not yet come to get rid of such convenience.