1s thin client file version. Publications

The release of versions 8.2 and 8.3 of the 1C:Enterprise program marked a major leap in the development of the system architecture. Among other things, this manifested itself in the possibility of choosing the type of client. Consider the differences between "thick" and "thin" clients in 1C.

Differences in data display are in the form of a client-server system.

Program architecture

The system in 1C is built on a client-server basis. The term client is commonly understood as a set of user-oriented consumer applications. The concept of a server is a service part in 1C, which is hidden and independent of the user. The client-server system can be represented by different types. So "thick" and "thin" are different kinds of client-server system. The time has come to consider their differences.

Meet the Fat Client

What is "thick"? - This is the usual type of application that we have been working with in 1C since 7.7. In 1C 8.0 and 8.1, it has been preserved. It is characterized by the fact that the server itself, and information processing, temporary files, cache - all this is located on the user's computer. This achieves its full functionality and independence from the Internet.

And it is called thick because powerful data channels are needed to process these powerful processes - thick (meaning bandwidth). And the exchange in them goes according to the TCP / IP protocol. Until the advent of 8.2, he was the only type for odinski to work. It is characterized by complexity in installation and high cost.

IMPORTANT. Development of applied solutions in the configurator is available only from this client.

Selecting a thin client

In 1C, a thin client appeared with version 8.2. Working in this mode is called managed application. In practice, this manifests itself in the fact that all information processing processes, data, temporary files, query execution, cache - all this is already on a remote server, access to which is practically limited. And the display of the result (finished data) is displayed on the user's monitor.

An example of this would be working with a web application. When using such a client, increased system resources and exchange channels are not required - these channels are already thin (designed for a smaller flow). Installing the distribution is simple and does not take up much space. On the one hand, allowing you to work with 1C via the Internet, on the other hand, it only supports user mode, depriving you of the use of the configurator.

Now you know what are the differences between a 1C thick and thin client and you can choose the best version of the client-server for your enterprise.

1C:Enterprise programs, which have become the leader in automation, are increasingly integrated into the business and the enterprise network. The 8th version of the program is no longer intended only for bookkeeping and has long gone beyond one or two computers. Its capabilities are increasingly being used not only by managers to control financial transactions, but also by managers in CRM, 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 bases are located has sharply increased. Realizing this, the developer 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 mistakenly say that it is not suitable for multi-user networking. Not at all, this work option can be used both for work by one user without network versions, and for sharing up to 5 clients. To configure the operation of the 1C file option, you can use a simple computer on which the directory is "shared" (access to the shared folder is open), in which, in fact, there is one single file with the database. Naturally, this computer must be constantly turned on so that users can access the database. The second not very pleasant moment is the 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 has the ability to copy this database to their computer (flash drive, removable disk, etc. .d) or simply delete. This leads to the conclusion that it is impossible to control the safety of data in a large company. And of course, one cannot fail to say that when using the 1C file deployment option, 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 this, at the current dollar rate, not everyone can afford, considering, moreover, that with the release of each new version of the program, the requirements for the hardware become only higher.

A significant plus can be considered 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 conventional (non-server) operating systems will provide up to 5 1C client connections. It is also quite simple to carry out backup, which, by the way, in the latest versions can be configured by regular means of 1C itself.

Client connections to file 1C

For users to work with the file-server version of 1C:Enterprise, 2 options are possible: "thick client" and web client. The first option is the simplest, it is 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. This mode only requires a compatible web browser that can be run on almost any platform and even on a tablet via 3G internet. Of course, you will have to complicate the setup a little, because you will need a web server, in addition to the file one, 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 the appropriate settings);
• there is no need to install and update software on workstations.

  General moments of deployment of file-server 1C

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

  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.

1C is client-server software and this means that 1C consists of two programs - client and server. The 1C server program is running on the server. The user on his computer works in 1C client program, which is briefly called the 1C client.

There are several types of clients in 1C, which allows you to use the program on different computer equipment, different operating systems, geographically distributed.

One of the 1C clients allows you to use 1C using a regular Internet browser on any operating system (even on a Mac). Another 1C client is on a PDA, for example, a production PDA in a warehouse for inventory, with a barcode scanner.

Let's look at what 1C clients are, what are their differences, how do they look and how to work with them?

Thick client 1C

The simplest and most well-known 1C client is the 1C thick client (“normal”). Prior to version 1C 8.2, apart from it, no other options were provided and were not.

The 1C configurator (currently) only works in the 1C thick client. It is also recommended to work with the file database using the 1C thick client.

At the moment, it is assumed that all 1C configurations will be transferred to the 1C thin client in the next year or two. Therefore, the exact fate of the 1C thick client in the future remains unclear, it will probably not be used.

Thick client 1C works under Windows. He is called fat because of the demands on the resources of the user's computer. Also, a 1C thick client can request fairly large amounts of data over the network.

From the programmer's point of view, the main difference between the 1C thick client is that it executes most of the programs in the built-in 1C language on the user's computer. For example, 1C wants to execute a query from the database:

• 1C client requests data from 1C server
• Data is sent to the client 1C
• Client 1C processes data.

The 1C thick client interface looks like this. By default, only the user menu is open. The user selects a menu item, which usually opens a window (or a list). Next, the user works with the list.

In some configurations for a thick 1C client, there is a desktop. It looks like this. First of all, these are the Accounting and Payroll and Human Resources configurations.

Thin client 1C

Thin client 1C appeared relatively recently. For the 1C thin client, the Trade Management configuration (version 11) has already been released. The 1C thin client is installed by default bundled with other 1C client options, but it can be installed separately (only it).

The 1C configurator does not work in the 1C thin client. It can work with the file version of the database, but it is better to use client-server mode.

Thin client 1C also works under Windows. It is called thin because of the correct organization of the client-server organization of the program. Unlike a 1C thick client, a query from the database will look like this:

• The 1C client sends to the 1C server the user's need to request data from the 1C server
• Server 1C requests data from the database
• Server 1C processes data
• The result of data processing is sent to the 1C client.

As you understand, plus and minus are immediately born. Plus - no demands on the resources of the user's computer, less traffic is expected. Minus - exactingness to server resources Higher.

The last disadvantage for large companies is removed by the fact that the 1C server can be scaled, that is, you can install a system of several 1C servers on different computers and they will work in conjunction.

The 1C thin client interface looks like this. By default, the user's desktop opens. It is divided into blocks by types of accounting. The user opens a bookmark and uses hyperlinks to open the lists.

An additional difference between a 1C thin client and a thick one is that it can work not only over TCP / IP, like a thick one, but also via HTTP, like a 1C web client.

Web client 1C (Web client 1C, Linux client 1C)

The 1C web client allows you to use 1C through a regular Internet browser. You don't need to install anything to use it. You can use it under any operating system, including, for example, on the iPad.

You can see what 1C looks like when working in the 1C web client right now. To do this, go to the official configuration demo Trade Management (version 11) .

To use the 1C web client, you need to raise a web server. It is used exclusively as a transport and sends requests to the 1C server. The logic for executing queries and processing data in the 1C web client is the same as in the 1C thin client. For work, automatic conversion of the built-in 1C language to JavaScript is used.

In the 1C web client, you cannot use any 1C configurations - only those written specifically for working with the 1C thin client. In theory, the development of the configuration for the 1C thin client and for the 1C web client are the same (the interface and system behavior should be the same too).

However, there are rumors that at least at the moment not everything is so smooth and some functions cause errors in the 1C web client, although they work in the 1C thin client.

The 1C web client interface looks like this. As you can see, it differs little from the 1C thin client.

Client 1C for PDAs (Extension 1C for Pocket PCs)

1C can also be used on PDAs (PDAs, smartphones). There are even special production PDAs, for work in a warehouse or in a store, they usually have an integrated barcode scanner.

To work with 1C on a PDA, you can use the 1C web extension (see below) - that is, a small website that works directly with 1C. However, specifically for PDAs with Windows Mobile 5.0 and above or Pocket PC 2003, there is a 1C client for PDAs.

The work of the 1C extension for PDAs is built as follows:

• PDA requests data from 1C (WiFi, GPRS, bluetooth)
• The PDA processes data using special forms under the PDA
• PDA prints data to a printer (communication in a similar way)
• The PDA saves data in 1C.

The 1C client for PDA allows you to use the configurator in a somewhat abbreviated form, which allows you to work with directories, documents, registers and their forms.

Web extension 1C and web services 1C (Web extension and services 1C)

The number of sites that work directly with 1C or that may need to work directly with 1C is growing. A simple example is an online store. Direct connection with 1C can be used to receive online balances, discounts, customer profile, save an order.

To integrate with the site, they usually use a periodic exchange (such as in CMS for Internet sites and online stores 1C Bitrix) or online connection with 1C. For the online operation of the site with 1C, you can use the 1C web extension or 1C web services.

Web extension 1C is an additional product that is supplied separately. It allows you to develop sites on the ASP .NET platform that work through a pool of COM connections with 1C. Creation of a queue of COM connections, their saving and manipulation is already written in the web extension engine for 1C.

1C web services are the capabilities of the 1C platform (1C server). To use them, you do not need to buy or install additional software from 1C.

Requires a web server (MS IIS or Apache) and its simple configuration (connecting the ISAPI extension). After that, 1C can publish its own web services. 1C web services allow you to both request data from 1C and write data to 1C.

Security is organized by the fact that no automatic functions, unlike a COM connection, are provided - the programmer himself prescribes the capabilities of the functions, respectively, if the programmer has not made a hole (universal notation), then it will not be.

The 1C web client is currently still a little raw and when working with it, you can encounter errors that interfere and annoy. This does not mean that you cannot work with it - the programmer can remove those places in the configuration that cause errors.

Of course, the 1C web client is the future of the 1C platform. It is independent of the operating system (Windows, Unix, Mac), browser (IE, Chrome, Safari, Firefox, Opera), and is not demanding on computer resources.

for platform 8.2:

for platform 8.3:

Comment. Automatic thin client update 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 a 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 way to verify the server certificate

Click "Finish"

Setting up automatic authorization on the web server

• Select the required IB in the 1C Thin Client and click the "change" button
• Click on the "Additional" 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 options" section, specify the line: where login is the login of the web server user, and password is his password.

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

More details about the settings of the Thin Client 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> - 1C Thin Client installation directory. 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/xxx where xxx is your web application path.

Click "Finish"

Setting up a 1C Thin Client to work with the 1C: Enterprise 8 platform of versions that are not included in the list of recommended

If you want to use a thin client version other than 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 using it, the data is transmitted in unencrypted form and can be intercepted by an attacker.

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

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

Set up 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/xxx where xxx is your web application path.

Click "Finish"

Installing and configuring Stunnel

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

In the window that opens, select the item "Configuration"

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

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

Most 1C users, in particular the G8, have repeatedly heard such frequently 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 on a daily basis, the difference between a thin and thick client is not felt, since such a user does not have to delve into the technical details of the processes performed by the computer, their algorithms. But at the same time, it will not be superfluous, at least at a primitive level, to understand 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 well be a situation where 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 a 1C thick and thin client?

Thick client 1C

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

Thin client 1C