As many probably know, the 1C Enterprise system supports two operating options. This:
- client-server;
- file version of work.
For client-server mode, you must install 1C: Enterprise Server.
In this article we will look at how to administer this server using the 1C 8.3 (8.2) Server Administration Console utility.
Immediately a service retreat - if upon startup the console displays the message “The client and server versions differ (8.3.х.х-8.3.х.х), client application: Cluster Console”, you need to register using the corresponding shortcut from the Start menu :
It does not have its own management interface. Administration is carried out using the 1C server console. The console is included in the 1C Platform delivery and is installed locally on the user’s computer. The Information Bases themselves can be hosted both locally and on remote computers or servers.
Get 267 video lessons on 1C for free:
Creating, editing and deleting databases on 1C Server
To create an information base on Server 1C, you must first create a Central Server and a Cluster to which the database will belong. On line 1C:Enterprise 8.3 Central Servers you need to “click” right click mouse and select “Create” in the context menu. In the window that opens, enter the server name and port number.
Now let's create a Cluster. We will also use the context menu and select “Create”. Let's fill in the cluster parameters.
In the “Information Bases” branch using context menu adding a new database. After filling out its parameters, click “Ok”. Information base ready to go.
Using the context menu, you can delete the database or edit its properties.
Actions in the console
How can the administration console be useful to us? It often happens that a user’s computer freezes, and the 1C program for a particular user does not start. A message appears that someone is already working under this user. The thing is that there are “non-working” sessions on the 1C server. These users even remain in the Active Users section. And when you need to perform operations in a program that require exclusive mode (for example, deleting objects marked for deletion), then if you ask all users to exit, the operation still cannot always be carried out.
Query console 1c- a convenient tool for building and debugging queries in 1C enterprise mode. Using the Query Console You can run a query to the 1C database and see the result of the query directly on the screen in 1C Enterprise. In this article we will look at two consoles, one for 1c 8.2 (regular forms), and the second can work in both regular and managed forms ah 1s 8.3.
Download the 1c query console
In order to start working with processing, you first need download 1c query console, below we will provide download links, but for now let’s note the fact that the 1c query console can be classified and assigned to one of the following types:
- For regular forms (1s 8.2)
- For managed forms (1s 8.3)
- Mixed (works on both 1s 8.2 and 1s 8.3)
In our article we will look at two consoles, the first works only on 1s 8.2 (regular forms), and the second works on 1s 8.3 (managed forms). They are slightly different from each other, we will talk about the differences further, but for now we note that in managed applications the console will work properly only in the “Thick Client” launch mode.
Download the 1c query console for the regular 1c 8.2 application
Below is a screenshot of the processing. You can download the 1c query console for regular application 1s 8.2
Download 1c query console for managed application 1c 8.3
And this is the second console, you can also see its screenshot on the screen below, using the link you can download the 1c query console for the managed application 1c 8.3
Description of the operating principles and main functionality of the 1c query console for a regular 1c 8.2 application
This 1s 8.2 query console for a regular application easy to use and does not require any special knowledge from the user. In the screenshot you can see a test field for writing a request; you can write a request in it either manually or using the constructor. Under number 1 in the figure you see the “Parameters” button; by clicking on it we will see a form for substituting parameters into the request, we will return to it later. Under number 2 you see the work area and the action panel with the request itself, here we can add requests, delete them, and also save them to a separate file on disk. Under the number 3 in query consoles 1s 8.2 there is a setting for displaying the result, it can be displayed in the form of a table or hierarchically in the form of a tree, the second option is used when we need to see the hierarchy as a result of the query. Point 4 shows us whether there are temporary tables in the request, if there are, then we can debug them and see the execution result that is placed in the temporary table.
Now let's look at some specific points in 1c query consoles.
Above you see a window in which parameters are entered into the request. By clicking on the "From request" button, we will receive the parameters that are specified in the request; now all we have to do is set the required values and close the form. By the way, if you are editing a request and your previously added parameters on the form are no longer used, they will be highlighted in gray. If there are a lot of such parameters, you can remove them from the window using the "Delete unused" button.
If you have temporary tables in your query, then you can debug them in separate subqueries and see the result of executing this subquery. If in the main window of the 1c query console we see that there are temporary tables, then click on the “Temporary tables” button (point 4 on the main console window). After clicking, the window that we saw above will appear, it shows all the temporary tables of the query, click “Debug” and see the following window.
Brief description of the functionality of the 1c query console for the managed application 1c 8.3
We got acquainted with the main functions query consoles 1s 8.2, now it's time to consider query console 1s 8.3. This processing We will not consider it in detail like the previous one, but will briefly go over the main parameters and settings.
Console Tool HTTP requests" is intended for generating HTTP requests using 1C: Enterprise, sending them and receiving responses for subsequent analysis. The console allows you to store lists of requests in an external file for their subsequent use in this processing.
Processing is suitable for experienced users and beginners (who want to quickly understand the principles of operation of HTTP mechanisms in 1C)
Below is information that is also located in the processing help.
Processing form areas
HTTP Request
In the HTTP request generation area, you specify the parameters on the basis of which the “HTTPRequest” and “HTTPConnection” program objects will be built. It is possible to specify the following parameters:
Address - In this field, an address line is formed, which will later be completed based on the entered parameters.
Request address - a field containing the final address generated based on the entered parameters, which will be used when generating an HTTP request. When unchecked "Add address" The line from the "Address" field will be copied into this field without further changes (the ability to send the request "as is").
Method- HTTP request method that will be called on the server.
Body- arbitrary text that will be placed in the body of the request.
Headers- a list of headers that will be inserted into the HTTP request. When creating a new request (adding to the request tree) or clicking on the button "Default" Headings that are generated by the platform by default will be added to the list.
Parameters- list of parameters that will be added to the address after the symbol "?" . You can also fill in the request body with parameters when you click on the button. "Fill with parameters" on the "Body" tab.
URL Parameters - list of parameters that will replace strings (name) in the address bar (by analogy with the use of configuration objects in url templates "HTTP request").
On the tab "Additionally" It is possible to set the following options:
OS Authentication - meaning of this field will be used when creating the HTTPConnection program object.
Sample - a value is entered into this field that will automatically be substituted in the address field instead of the string . When a new request is added to the list, this property is copied from the parent row.
Authentication - in the field you can select "Base" authentication. In this case, the data entered in the "User" and "Password" fields will be automatically transferred to the corresponding header in the form base64 lines.
Query tree
This element is used to manage a list of requests, which can later be saved to a file.
HTTP response
The HTTP response scope elements are filled with data from the response received from the server. The area contains the following elements
Response code- response code received from the server with an explanation
Body - the body obtained from the HTTP response as a string.
Headers - headers of the received HTTP response
HTML- a body obtained from an HTTP response as a string and placed in a field in the HTML document.
JSON- a string obtained by converting the response body to JSON and back to a string using the platform's JSON tools. In the field "Structure" the JSON structure is output in the form of a tree, if the conversion is successful.
Features and limitations
The request is sent on the client
The data stored in the tree includes the following fields: Body, Headers, Parameters, Autoredirect, Address, Authentication, Method, Template, URL Parameters
Converting HTTP response data into form fields is done the same way and does not depend on the contents of the response headers
Software requirements
- Processing is designed to work with the 1C:Enterprise platform starting from version 8.3.6. The "mode" must be used Managed Application"
- To access external HTTP services, you must have an Internet connection at the workplace from which processing is carried out. When accessing services on the internal network, you need access to these services in local network from this workplace.
Additional terms
- The validity period of the software license is unlimited
- The processing code is open and can be modified at the user's request.
- The processing is provided as a download link.
- Free period technical support- 3 months from the date of purchase.
ATTENTION!
Money back guarantee
Infostart LLC guarantees you a 100% refund if the program does not correspond to the declared functionality from the description. The money can be returned in full if you request this within 14 days from the date the money is received in our account.
The program has been so proven to work that we can give such a guarantee with complete confidence. We want all our customers to be satisfied with their purchase.
21/03/2016
Features of using the 1C:Enterprise server administration console of different versions
Introduction
In continuation of the previously published document, which describes the possibility of running several 1C services on one server, we would like to talk about the features of using the administration console of 1C:Enterprise servers different versions. The fact is that with a standard installation of this console, you will only be able to administer the 1C server of one version. If several versions of the platform are installed on one server and several 1C services are running, the question arises of how to administer 1C servers of different versions within one server?
Registration of 1C console
To register the administration console for 1C:Enterprise servers, 1C suggests using the RegMSC .cmd executable file located in the bin folder of the 1C server directory. This file can be launched from the Start menu in Windows: “1C Enterprise 8 -> Advanced -> [required version of the 1C platform] -> Registration of the 1C Enterprise server administration utility.”
The RegMSC .cmd file contains the following script:
regsvr32 /n /i:user radmin.dll
The purpose of this script is only to register the radmin .dll component. In practice use this script inconvenient, since every time before launching the administration console of 1C: Enterprise servers of the required version, you have to run the corresponding RegMSC .cmd file. Plus, this script is inoperative and needs to be improved (most likely, when you execute it, you will receive a message about successful registration of the component, but the console will not work).
So, we want to get a working script that will allow us to automate and perform the following actions in one click:
- Registration components radmin. dll of the required version;
- Launching the 1C cluster console.
We suggest changing the above script and creating a main universal script for registering components and launching equipment (consoles), as well as creating “starter scripts” for consoles required versions. Here's what we got:
rem %1 - full number version 1C:Enterprise
@echo off
This script should be saved in an executable file in .bat format (for example, “start _console .bat”). Let's look at this script in more detail. The following line is responsible for the correct registration of the radmin .dll component:
start /wait regsvr32 /s "C:\Program Files (x86)\1cv8\%1\bin\radmin.dll"
The version number of the 1C platform is passed to it as a parameter (%1). Next line is responsible for launching the MMC console with equipment for administering 1C:Enterprise servers:
start "C:\Windows\System32\mmc.exe" "C:\Program Files (x86)\1cv8\common\1CV8 Servers.msc"
start_console 8.3.7.1873
Since registering the radmin .dll component does not affect the operation of already running administration consoles for 1C:Enterprise servers, using this approach and the proposed scripts we can simultaneously launch administration consoles for 1C:Enterprise servers of different versions and work successfully in them, with our own cluster versions in each. Done, now you can administer several versions of 1C server on one server.
Please note that the suggested scripts use 32-bit versions of the components. When you try to register a 64-bit component in the same way, you will receive a message that it has been successfully registered, but then when you launch the 1C:Enterprise server administration console, you will most likely see an error like:
MMC could not create the snap in, Name: 1C:Enterprise (x86-64) Servers, CLSID:…
Bye this problem has not been resolved, the use of several 64-bit administration consoles for 1C:Enterprise servers within one server is not possible. If you have other information and know how to solve this problem, we will be happy to update the article.
Conclusion
In the article we described a method that allows you to use several administration consoles for 1C:Enterprise servers of different versions. This is necessary if you are working on a server with several working or test databases, for which the versions of 1C server used are different.
We hope you can easily complete the task you need and continue to enjoy using 1C products. Well, if something doesn’t work out for you, or you encounter some difficulties, we will definitely help!
The query console is very convenient to use when you need to debug some complex data or quickly obtain a sample of certain data.
You can find many different consoles on the Internet. For regular and managed forms, these are usually completely different consoles. From this you can download universal console requests 1C 8.3 and 8.2, which will work in both cases. Just keep in mind that the console is on managed interface It will only open in the thick client.
Working with the Query Console
In the 1C program, the query console opens in the same way as any external processing: menu “File” - “Open”, or using the hotkey combination “Ctrl + O”. At frequent use it can be added to external treatments the information base itself.
The left side of the request console displays the list of your requests. This allows you to store not just one request, but several at once. The query tree has a hierarchical structure, which is very convenient for grouping them.
By clicking on the “Add” button, you can add a new request, giving it a name yourself. Also, the built-in functionality allows you to create queries with copying, move up or down the list and much more.
The request text itself is displayed on the right side of the processing form. It can be written manually or using a query builder. The query builder only works in the thick client.
To the right of the designer button is the “Insert Query Statements” button. It will immediately add an empty query structure with condition, grouping, order and totals.
To the right are very useful buttons that will help if this request you use when developing solutions on 1C.
The button allows you to convert your written request into text. In our case it will look like the figure below.
You can save the requests themselves to a file or load them from it. This is very convenient for future use.
Before directly executing the request, you must set its input parameters (if any), then click on the “Run request” button. It is also possible to execute requests not as a whole, but separately as a package.
The viewing mode determines how the query result will be displayed: as a list, hierarchical list, or tree.
The execution result will be displayed at the very bottom of the request console. It also displays the number of rows received and the execution time. You can move query result rows if necessary.
Very often, users ask to select some data and save it in Excel. You may need this too. To complete the task, you just need to select “Display list” in the “More” menu. The program will prompt you to mark the required columns.
In addition to specifying a list of columns for output, you can also specify specific rows here. This is implemented by highlighting the rows in the query itself. Next, in the column selection form, just set the flag in the “Selected Only” setting.
In our example, we displayed all the query result data. Save them in external file, you can copy from the opened spreadsheet document, or using the hotkey combination “Ctrl+O”. There are many options for saving formats; we chose “*. xlsx".
As you can see, working in the query console is very convenient and useful, so we strongly recommend downloading it and putting it into practice.
