Publications. Publications How to work in a thin client 1c

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

Fig. 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 interacts the user with the 1C: Enterprise system. In fact, we have two main types of programs in which a user can work: this is a configurator, where the programmer develops an application solution, and an enterprise, where the user works with data and according to algorithms developed by the programmer. This was the case on 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 the 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, at the moment there are four types of client applications:

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

Why did it become necessary to split a common 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 it became necessary 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, the platform technologies that existed in the 8.0 and 8.1 editions became inapplicable in the new realities. As a result, platform 8.2 was developed, in which it was divided into three types: "thick", "thin" and web-client.

Let's analyze all types of clients in more detail.

"Thin client"

Let's start with a thin client. A "thin client" is a type of 1C: Enterprise client application, under which it is possible to work on the Internet. In essence, it only displays data on a form or in a report, there is no access to object types from the "thin client", and it is also impossible to execute queries under it. The resources of the device on which the thin client is running are used only for displaying data on the display screen, all calculations, requests and algorithms must be performed on the server side. You cannot work under this client type in the configurator.

This kind of client application is delivered as a separate distribution kit, which is called « Thin client 1C: Enterprise for Windows», downloaded from the 1C website (if there is an ITS subscription) and installed on the 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. In order for the thin client to work over HTTP and HTTPS, 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 modes.

Let's analyze the work of a "thin client" using different protocols. First of all, let's start with the TCP / IP we are used to (who does not know, this is the most common protocol for operating a local Ethernet network). There are two options for working with a thin client via Ethernet: a client-server option and working with a file base.

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

File option applicable when one or several users work within a small network, as well as when large amounts of data or cumbersome calculations are not used. In this variant of work, all data is located in one file. 1Cv8.1CD, which is called the "1C: Enterprise" file database. The work of the file version can be schematically represented as follows:

Fig. 1.1.2 Schematic representation of the file version

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

Fig. 1.1.3 Schematic representation of the client-server version

Let's go back to the "thin client". As mentioned above, this is a client application through the protocol TCP /IP can work with both a file base and a client-server architecture.

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 fact, emulates the operation of the server. This dedicated server environment is not a separate process in the operating system, but is part of the "thin client" process. It takes over loading the application configuration and other server actions necessary for the normal functioning of the "thin client".

In the case of the client-server version (Figure 1.1.5), the "thin client" interacts directly with the 1C: Enterprise server cluster via an Ethernet local network. In this version, the principles of operation are exactly the same as for the "fat client".

Why is it necessary to use a "thin client" when working over a local network, when for this you can work under a "thick client"? Good fast machines capable of taking on some calculations are not always used in the local network of an enterprise. Very often it can be computers "killed in the trash", and in this case, working under a "thin client" is quite justified. When working in a "thin client", smaller amounts of data pass through 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 computers on which this type of client application is running (in the case when used by client-server version of the base).

Now let's move on to working with the "thin client" via the Internet. Working with this kind 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 started on the server side. In this case, the following chain works: the "thin client" interacts with the web server through 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 go into detail on the configuration mechanisms of the "thin client" andweb client for working via the Internet, but we will touch only general points so that you understand the principle of operation.

And the last important feature of the "thin client": under it, you cannot work with the configurator. When you start the "thin client", the "configurator" button in the 1C starter will be absent (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.

Fig. 1.1.8. Thin client launch window

Web client

The next interesting type of client that we will analyze is a web client. This kind of client application is required to work only over the Internet. Moreover, if for the operation of the "thin client" on the local machine it was necessary to install the software, then to work under the web client it is not necessary to do this. All work with this client can be carried out 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 both with a regular file base and with a client-server architecture. The only thing is that in both cases, as in the case of a "thin client" via the Internet, it is necessary to install special software on the server side - a web server (usually Apache or IIS).

The principles of web-client operation in the case of a file base and client-server architecture are shown 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". Almost all the functionality provided by the built-in 1C programming language is available under this type of client. For example, under it you can work with queries and with applied types.

One of the features of the "thick client" is that it supports normal operation, i.e. under the "thick client" you can run applications developed for platforms 8.1 and 8.0. - regular applications. And also in managed applications to launch regular forms, which of course cannot be done in the "thin client".

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

"Thick client" is installed by a regular distribution kit and in the Windows operating system is launched by an executable file 1Cv8.exe.

Since working with a "thick client" requires significant computing power, you can communicate with the database either directly or via an Ethernet local network. This kind of client application can work with both a file database and a client-server architecture (over 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 via the local network to the 1C: Enterprise server cluster, 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 the server performance.

The "thick client" can work with the file base both directly: the base file is located on the same computer where the "thick client" is installed, and over the local network (Fig. 1.1.12). In the event that there is an interaction with the file database over the local network, full access to it must be provided through a shared network resource.

And as it 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 start the "thick client", you will see the "Configurator" button in the launch window (see Fig. 1.1.11).

Fig. 1.1.11 The "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 + — —
Ethernet LAN operation + + +
Working on the Internet — + +
Distribution installation required + + —
Working with the file base + + +
Working with sql server + + +
Working with regular applications + — —
Working with managed applications + + +
Opening Regular Forms in Managed Applications + — —

Tab. 1.1.1 Differences between different client applications.

Sometimes it seems that learning a programming language in 1C is difficult and difficult. In fact, programming in 1C is easy. My books will help you quickly and easily master programming in 1C: and "Fundamentals 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. No complicated technical terms;
  2. Over 600 pages of practical material;
  3. Each example is accompanied by a picture (screenshot);

15% discount promo code - 48PVXHeYu

Learn programming in 1C with the help of my book "Program in 1C in 11 steps"

  1. No complicated technical terms.
  2. Over 700 pages of practical material.
  3. Each task is accompanied by a picture (screenshot).
  4. A collection of tasks 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 to solve any problem, you liked it or turned out to be useful, then you can support my project by transferring any amount:

you can pay manually:

Yandex.Money - 410012882996301
Web Money - R955262494655

Join my groups.

The main difference between a thin and a thick 1C client is where the main calculations are carried out - on the server or at the user's workplace. This imposes some restrictions on the use of a particular work option.

In this article of the Integrus blog we will consider various client applications of the 1C system - what does a 1C thin client, a 1C thick client mean, what it is and what are the differences, and also in what cases it would be better to use each of them.

Thick client 1C

If you use 1C in the thick client mode, this means that all operations on data are carried out directly at the user's workplace, and the data itself is stored on the server, where the client application calls for them.

Such a client can perform almost all functions and work with application data types.

Installation of a 1C thick client is performed from the general distribution of the system, where it is listed as a separate component. With the question of how to run a thick client 1C 8.3, there should also be no difficulties - it is launched by the executable file 1cv8.exe.

Thin client 1C

Working in the 1C thin client mode means that on the server, in addition to storing data, almost all program code, requests are executed, temporary files and cache are stored. At his workplace, the user only enters the initial data and sees the display of the result on his monitor.

Installation of a 1C thin client is performed from the 1C distribution kit. If you do not have it, since you, for example, work with cloud 1C and rent it, then a separate distribution kit can be downloaded on the 1C website. Be sure to check that its version matches the version of the platform you are using.

A thin client for 1C: Enterprise is launched from the executable file 1cv8c.exe.

It is worth mentioning separately that for the 1C 8.3 thin client, the file mode of operation is not recommended, the client-server mode is preferable. While file mode is possible, all of the code will be executed on the user's computer, negating the benefits of a thin client.

As you can see, the main difference between a thin and a thick 1C client is where the main calculations are carried out - on the server or at the user's workplace.

This imposes some restrictions on the use of a particular work option:

  • an important difference between 1C thin and thick clients - working with the Configurator and the Query Console is possible only in the thick client mode
  • a thick client works over the TCP / IP protocol, therefore, it is quite demanding on the communication channel, since for its operation it is necessary to exchange relatively large amounts of information with the server
  • the 1C thin client works exclusively in the managed application mode, the functionality available to the user is limited in comparison with the functionality of the thick one, for example, you cannot operate with applied data types
  • using a thin client, it is possible to work with 1C via the Internet - a thin client can connect to a web server via http or https
  • A fat client has a fairly large distribution package, and there may be some difficulties with its installation and configuration, it is desirable that a qualified specialist does this. Whereas installation, configuration of a 1C 8.3 thin client, connection of an infobase is within the power of any more or less advanced user.

1C web client

1C web client - in essence, this is not a separate application, but rather a technology that allows you to work in a familiar 1C environment using a browser, simply by specifying the address of the corresponding 1C web server in the address bar. For it to work, you will need to first deploy a web server and publish an infobase on it, and the web client will only work with a 1C configuration that supports the requirements for a thin client.

The good thing about the web client is that you don't need to install anything at all on the user's device, it can function in all the most common browsers. Of the minuses, we can note the limited functionality and the fact that the presence of a web server is not always suitable for information security requirements.

What is faster than a thin or thick 1C client?

It is difficult to unequivocally answer the question: which 1C thin or thick client is faster? It depends on the conditions of use.

  • The thin client has low requirements for the user's device and communication channel, while the system's capabilities are almost fully used, but work can slow down if many employees simultaneously use the server's resources.
  • A fat client can require significant power from the user's computer and a good data transmission channel, while providing the user with a certain autonomy, his work is not affected by how many people simultaneously work with the system, whether there is an Internet connection, etc.

Therefore, before choosing and configuring a 1C client, it is advisable to analyze who and how uses 1C in your company, what types of 1C clients you will need.

  • If this is an accounting department located in an office, which can be provided with sufficiently powerful computers and it is easy to organize their administration, if all these computers are connected to a local network, then a thick client will be more convenient.
  • If your employees often have to work remotely, via the Internet, because they have frequent business trips or they are simply in other cities, because this is the infrastructure of your company, if they use low-power laptops or other mobile devices, then setting up a thin client will suit them 1C.

Updating 1C clients

And finally, a couple of words about how 1C clients are updated:

  • the thin client can be updated automatically via the Internet,
  • updates for a thick client must be downloaded from the 1C website or.

If you have questions about choosing a 1C client, installing, configuring, updating, administering 1C software products, you can contact the specialists of Integrus or see the section of our company's blog with instructions and recommendations on 1C topics.

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 for the entire enterprise. There are several options for interacting with the database, in this article we will consider the differences between a thick and thin 1C client.

A fat client is a familiar work option

The original view of the program, which existed in 1C: Enterprise from the very beginning, is called fat. Before version 8: 2, it was the only one, and now it is considered the simplest possible. It's worth noting that the app 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. The explanation is quite simple: the thick client processes most programs in the built-in 1C language on the user's computer.

How the fat client works:

  1. First, data is requested from the server;
  2. Server 1C sends a request to the database;
  3. Information is sent to the user's application;
  4. Further information is processed.

Thin client - modern way of working

Introduced in the latest update, the Thin application is fundamentally different from its predecessor. Now users can work from home without wasting unnecessary traffic or overloading their personal PCs. This change is caused by some change in concepts about how such work should proceed. The requested processes are processed not on the user's computer, but on the server computer, which then sends the received data to the supplicant. It turns out that users can breathe easy, but how to find a device that will cope with the work of a whole huge enterprise? The manufacturer has foreseen this issue too - the server can be divided into several computers, having received as much machine power as needed.

This is how the work 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 will not be superfluous to familiarize yourself with such descriptions before starting work.

Does it make sense to use a fat client?

As already mentioned, many users are unwilling to accept innovations and remain faithful to the old application. But is it only a matter of devotion? No and no again.

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

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

2016-12-07T18: 05: 29 + 00: 00

Many G8 users have already heard terms such as "Thick client" and "Thin client". But few people know what it means.

Fat client is the usual way to work with the program. We got used to it for a long time (since the days of 7.7 and 8.2). In details .

Thin client - this is the 1C launch mode for working via the Internet, when the accounting base is not on our computer or even on our network, but somewhere thousands of kilometers away on a remote server (possibly in another city or country). In details .

Simply put, for an ordinary accountant who works with the database directly on his computer or in the enterprise network, there is no difference between a thin and a thick client.

But it often happens that some errors appear in one client and are absent in the other. As, for example, with the display of transactions in 1C Accounting 8.3.

In this case, it can be useful to find out which client we are currently working in and change it to another.

How do you know which client you are working with? Look at the window with the version of your 1C (for the article):

There, in the "Application" section, your client will be indicated:

It is written about how to change a client.

Best regards, (teacher and developer).

for platform 8.2:

for platform 8.3:

Comment. Automatic update 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.

Setting up 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 the method for verifying the server certificate

Click the Finish button

Configuring automatic authorization on a 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 field with the infobase address)
  • In the "Select a web server user authentication method" section, select "Choose automatically" and click "Next".
  • In the certificate settings window, click Next.
  • In the "Additional launch parameters" section, specify the line: where login is the username of the web server user, and password is his password.

Click Finish and test your infobase connection.

More details about the Thin Client settings on the ITS website.

Setting up a 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 for the 1C Thin client. This will prevent the "Peer certificate cannot be authenticated with known CA certificates" SSL error.


Enter the name of the infobase, select the "Web Server" item and click the "Next" button

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

Click the Finish button

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

If to work in the 1C: Link service you want to use a thin client version other than those recommended above, you may need to configure the work on HTTP or installation Stunnel.

Configuring the Thin Client for HTTP

The Link Agent has the ability to work in a thin client via the HTTP protocol. However, HTTPS is the preferred protocol for working in a thin client via 1C: Link. It is not recommended to use the http protocol, as when using it, data is transmitted in unencrypted form 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 below:

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

    Configure the thin client:

Start the thin client and click the add button.


Enter the name of the infobase, select the "Web Server" item and click the "Next" button

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

Click the Finish button

Installing and configuring 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 the "Edit stunnel.conf" item

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

 

It might be helpful to read: