While installing the next Accounting update I received the error “I only work on 8.3.4”, well... it's time to install 8.3.4. So:
I won’t describe the process of downloading and installing the new platform, everything is simple.
Server Agent Service 1C
By default it is installed on port 1540, and there I have 8.2 running, so we change it in the registry branch
HKEY_LOCAL_MACHINE\SYSTEM\CurrentControlSet\Services\1C:Enterprise 8.3 Server Agent ImagePath Parameter
change the port numbers by adding an offset: "C:\Program Files\1cv8\8.3.4.365\bin\ragent.exe" -srvc -agent -regport 1741 -port 1740 -range 1660:1691 -d "C:\Program Files\ 1cv8\srvinfo"
Launch the Agent and open the Administration console of 1C servers and create a cluster 8.3
Specified the server name and configured it on port 1740 (8.2 runs on 1540)
We create a cluster + optimized it a bit (I only have ONE small server, so I indicate the restart interval for work processes and the amount of memory. Because I have one server - the fault tolerance level is 0) 
Now in more detail:
1. Restart interval: 86400 sec (24 hours). The moment of restart is not regulated, apparently from the moment the parameters are set or the application server is started.
2. You can also specify the allowed amount of memory: 3,000,000 KB (3 GB) - For a server with 4 GB of RAM, If it is less, then do not fill in this option!.
3. Memory overrun interval is a continuous period of time when the permissible amount of memory is exceeded, after which the server will restart the process. If 0 seconds is specified, it will wait forever.
4. The number of Work Processes is calculated automatically based on your settings
5. Fault tolerance level You can set the cluster fault tolerance level as the number of working servers that can simultaneously fail, and this will not lead to abnormal termination of users. Backup services are launched automatically in the amount necessary to ensure the specified fault tolerance; In real time, the active service is replicated to the backup ones.
6. Load distribution mode, which can be used either to increase the performance of the system as a whole, or use the new “memory saving” mode, which allows you to work “with limited memory” in cases where the configuration used “likes to eat up memory.”
Working server
My server is simple, 2 Gb of RAM in total and there will be only 2 databases on it, so I’ll configure it like this: 
I set the Number of information security per process parameter to 1, i.e. I want each information security to run its own process - this will reduce mutual influence both in terms of reliability and performance. You configure it to the characteristics of your server!
Information base
I add IB: 
In the starter peeing the database: 
Functionality assignment requirements
I don’t set this up myself, but I think I should say about it:
Cluster management means that the administrator determines the composition of computers (working servers) on which the cluster is located. In addition (if necessary), he can determine the “requirements” for them: which services and connections to infobases should run on each of the working servers. Cluster managers and worker processes are launched automatically based on assigned "requirements". “Requirements” for production servers can be specified interactively, from the cluster administration console, or programmatically, from the built-in language.
So on a laptop with a security key, in order not to launch users on the cluster server, you need to add “requirements” for the requirement object “Client connection to information security” - “Do not assign”, i.e. deny worker processes of this server handle client connections. Even more interesting is the ability to run “background jobs only” on the cluster’s production server without user sessions. This way you can move highly loaded tasks (code) to a separate machine. Moreover, you can run one background task “closing the month” via “Additional parameter value” on one computer, and the background task “Updating the full-text index” on another. Clarification occurs through the indication “Value of the additional parameter”. For example, if you specify BackgroundJob.CommonModule as a value, you can limit the work of the working server in the cluster to only background jobs with any content. The BackgroundJob.CommonModule..- value will indicate the specific code.
Security Profiles
Security profiles serve to prohibit an application solution from performing actions that could be potentially dangerous to the functioning of a server cluster.
The cluster administrator can assign any information base one of the security profiles existing in the cluster. And then potentially dangerous functionality application solution will be limited to the extent described in this profile.
By default, once created, a security profile prohibits all potentially dangerous actions:
-appeal to file system servers;
-launching COM objects;
-use of external 1C:Enterprise components;
- launching external processing and reports;
-launching applications installed on the server;
- access to Internet resources.
Thus, protecting yourself from unwanted actions of an unfamiliar application solution is very simple: you need to create an empty security profile and assign it to the information base. Further, if necessary, you can expand this profile by describing in it the actions that the application solution is allowed to perform.
Location of cluster manager service files in 1C Enterprise 8.3
If when installing the system! "1C:Enterprise" has chosen the option of launching the "1C:Enterprise" server as a service, then the first launch of the server agent will be performed during the system installation process. In this case, the service will be launched on behalf of the user selected in the system installation dialog, but the server cluster service files will be located in the directory<каталог установки системы 1С:Предприятие>\srvinfo (the launch key -d will be explicitly specified in the service parameters).
If, when installing the 1C:Enterprise system, you selected the option to launch the server as an application, then the server is not launched during the system installation process; The server agent must be started independently after the system installation is completed. Moreover, if the start switch -d is not specified, the server cluster service files will be located in the default directory: %USERPROFILE%\LocalSettings\ApplicationData\lC\lCv8 (%LOCALAPPDATA%\lC\lCv8 for Windows Vista and older).
ATTENTION! If a cluster has already been created on this central server, then when changing the option for launching the server agent (service, application) or when changing the user on whose behalf the server agent runs, you should always take care to correctly specify the path to the directory of service files of the server cluster. If the server agent does not find a list of clusters during startup, it will create a new cluster on this server.
In the operating room Linux system server cluster service files will be located in the /home/usrlcv8/.lcv8/lC/lcv8 folder (or a shortened version - ~/.1cv8/1C/1cv8).
For various reasons, access to the 1C:Enterprise server may be lost, and then when we try to launch the cluster console, we will see a prompt to enter authentication data, but we will not be able to do anything:
We will not discuss the reasons that led to this. Let's start solving the problem. We need to restore access to the server in any way. It doesn’t matter whether we reset the password or select authentication data.
Let's take the fastest route. We have administrator rights on the server, so we can do it with the least amount of effort.
Solution
First of all, let's stop the "1C:Enterprise 8.2 Server Agent" service. For this purpose in command line let's do:
Sc stop" 1 C:Enterprise 8 . 2 Server Agent"
The same can be done through the graphical utility "Services":
Based on the file data, it can be judged that an “Adm” administrator was added to the server with a certain password. We can either replace the data with the user we need with the “correct” password, or delete the entry about the server administrator. Let's choose last method. This is what the contents of the file now look like:
Let's start the server service. The next time you start the 1C:Enterprise server cluster console, the program will not ask for authentication data.
Bottom line
The article describes a method for resetting the administrator account for a 1C:Enterprise 8.2 server. It should be taken into account that Accounts administrators can be added for each information base separately. In this case, look at the file "1CV8Reg.lst", which is usually located in the directory:
" C:Program Files (x86) 1 cv82srvinforeg_1541"where "reg_1541" is the cluster settings directory, the directory name of which depends on its settings.
This file stores infobase settings, as well as authentication data of cluster administrators.
The authentication data of each IS coincides with the corresponding authentication data of the users of this information base. In order to open the properties of the database in the cluster, you need to enter the login and password of an information security user with administrative rights.
Now you already know what you need to do. Under no circumstances should you consider the described method of resetting 1C:Enterprise server administrator accounts as hacking, since without administrator rights nothing like this (stopping the server service, accessing the server settings directory, etc.) can be done.
If you are interested, here are some articles on a related topic, namely on the selection/recovery of passwords for users of the 1C:Enterprise 8.2 information base:
"The lighter the password, the easier it is"
"Entry without invitation"
"Resetting accounts. We are writing a universal program in the .NET Framework"
In this article I will talk about how to add new or existing databases to the 1C:Enterprise server. 8.3 (for other versions of the platform - 8.1 And 8.2 actions are similar). Options for adding an information base both from and through the 1C:Enterprise server administration program (in Windows OS) will be considered. Some issues of administering information bases in a 1C:Enterprise server cluster are also touched upon.
1. Adding an infobase from the 1C:Enterprise launch window
Let's create a new database on the 1C:Enterprise server from a standard configuration. To do this, launch “1C:Enterprise” and in the launch window click “ Add…» to add an information base.
The wizard for adding an information base will start, select the item “ Creation of a new information base" by setting the appropriate switch and clicking " Further».
In the list of installed configuration templates, select the template we need and click “ Further».
Let's enter the name of the database as it will be displayed in the list of infobases, specify the location type " On the 1C:Enterprise server" and click " Further».
On the next page you need to specify the parameters of the created infobase, namely:
(IN in this example parameters were selected in accordance with the 1C:Enterprise server installation parameters adopted in the article)
- Server cluster name 1C:Enterprise— as a rule, it matches the network name of the computer where the 1C:Enterprise server is installed (the central cluster of the server);
- Name created base in a cluster— the name by which the information base will be accessed. Must be unique within a given cluster;
- Secure connection- disabled by default;
- Type of DBMS on which the database will be stored- in this example MS SQL Server;
- Database server name— as a rule, it consists of the network name of the computer where the database server is installed and the name of the server instance (if any), separated by the “\” sign;
- Name of the database on the database server— for convenience, we will adhere to the rule that the name of the database must match the name of the infobase in the cluster. In addition, in the case of using MS SQL Server, the first character in the database name can only be a letter of the Latin alphabet or the symbol “_”, subsequent characters can only be a letter of the Latin alphabet, a number or the symbols “_” and “&”, the name must be unique within a given database server instance and not exceed 63 characters. If the database already exists on the server, the current database will be used, if not and the flag " Create a database if it doesn't exist", a new database will be added to the database server.
- Database user— a DBMS user who will become the owner of the database on the server if a new database is created or who has rights to work with an existing one;
- User password— the password of the user on whose behalf the database will be accessed;
- Date offset— 0 or 2000. This parameter determines the number of years that will be added to dates when they are saved in the database Microsoft data SQL Server and subtracted when retrieving them. The point is that the DATATIME type used Microsoft SQL Server, allows you to store dates in the range from January 1, 1753 to December 31, 9999. If, when working with an infobase, there may be a need to store dates preceding the lower limit of this range, the date offset should be selected as 2000. In addition, if the application solution uses accumulation registers or accounting registers (and most likely this will be the case), also in the “field date offset must be set to 2000.
- Set blocking of scheduled tasks— setting the flag allows you to prohibit the execution of scheduled tasks on the server for this information base. It should be installed in the case of creating test information bases, where the implementation of routine tasks does not carry any practical load.
Having set all the information base parameters, click “ Further».
And finally, specify the launch parameters for the database being created and click “ Ready» to start the process of creating a new information base. At the same time, a new information base will be created on the 1C:Enterprise server, if necessary, created new base data on the database server, and data will also be loaded from the configuration template.
If all of the above actions are completed successfully, the wizard will complete its work, and we will see the newly created database in the list of infobases in the 1C:Enterprise launch window.
2. Adding an information base from the 1C:Enterprise server administration console
Now let’s add another infobase to the server cluster, but through the “ Administration of 1C:Enterprise servers"(previously). You can find it:
Well, in any case, the snap-in can be launched by executing the file “ 1CV8 Servers.msc"located in the 1C:Enterprise installation directory in the subdirectory " common».
If the equipment " " is launched on the same computer where the 1C:Enterprise server is installed, then in the tree on the left, in the branch with the network name of the current computer, we should see this cluster of servers called " Local cluster" Expanding the tab " Information bases"we will see all the infobases in this server cluster (for example, the database created through the 1C:Enterprise launch window in the previous step). To add a new information base, click right click mouse on this tab, in the context menu select “ Create» — « Information base».
The parameters window for the created infobase will open. The list of parameters is the same as that described above in paragraph 1 of this instruction. After filling out all the parameters, click “ OK» to start the process of creating a new information base. In this case, a new information base will be created on the 1C:Enterprise server and, if necessary, a new database will be created on the database server.
If all of the above actions are completed successfully, the parameters window will close, and we will see the newly created database in the list of infobases of the current cluster.
And if you go to the “Wednesday” program SQL Server Management Studio" and connect to the current instance of MS SQL Server, you can see the databases created in the previous steps.
3. Properties of the infobase
To view or change the parameters of a specific infobase, you need to use the " Administration of 1C Enterprise servers", in the list of infobases, right-click on it and select " Properties" To authenticate in the administration console, you must use administrators in the corresponding infobases. In other words this check is similar to authentication when connecting to an infobase through the 1C:Enterprise client.
As you can see, the following have been added to the list of parameters already familiar to us:
- Session start blocking is enabled— a flag that allows you to enable blocking of the start of sessions with the infobase; if the flag is set, then:
- Existing sessions can continue running, establish new connections, and also run background jobs;
- Establishing new sessions and connections to the infobase is prohibited.
- Start And End— duration of session blocking;
- Message— text that will be part of the error message when trying to establish a connection with a blocked infobase;
- Permission code— the string that should be added to the parameter /UC when starting 1C:Enterprise to connect to the infobase despite being blocked;
- Blocking options— arbitrary text that can be used in configurations for various purposes;
- External session management— a string describing the parameters of the external session management Web service;
- Mandatory use of external control— if the flag is set, then if the external session management Web service is unavailable, an error occurs and establishing a connection to the infobase is impossible;
- Security Profile— if you specify a profile name, the application solution begins to work taking into account the restrictions imposed by the specified security profile;
- Security Profile safe mode - the same as the security profile, but restrictions will be imposed on fragments of the application solution operating in safe mode.
By changing required parameters click " Apply" to save changes or " OK» to save and close the infobase properties window.
4. Adding an existing infobase to the list of infobases in the 1C:Enterprise launch window
And finally, all we have to do is add the one created using the “ Administration of 1C Enterprise servers» infobase to the list of infobases in the 1C:Enterprise launch window. Why in this window click “ Add…" and in the wizard that starts adding an infobase/group, select the appropriate item and click " Further».
Enter the name of the infobase as it will be displayed in the list, select the type of infobase location " On the 1C:Enterprise server" and press " again Further».
Enter the address of the 1C:Enterprise server cluster and the name of the infobase, as it is defined in this cluster. Click " Further».
And finally, set the parameters for launching the infobase and click “ Ready» to complete the wizard.
Our database has appeared in the list of information databases. You need to understand that this is an empty (clean) database, and then you should load data into it from a template, or from a pre-loaded data file.
Did this article help you?
Hello dear readers.
Today we'll talk about funds Server administration 1C:Enterprise.
1C:Enterprise supports the following:
Client - server version of work
File version of work
When working in client-server mode, a three-level architecture is used using a cluster of 1C:Enterprise servers, through which communication between the client part of 1C:Enterprise and the DBMS is carried out.
Server 1C does not have its own user interface; various tools can be used to control it; let’s consider the standard Client-server administration utility, it can be installed at .
Utility server administration 1C:Enterprise or 1C server console
The main tasks of the 1C server console:
- Creating, deleting and changing production servers;
- Creation of administrators;
- Creating and deleting cluster worker processes;
- Creating and deleting information security
- Forced termination of the session;
- Blocking new connections.
Let's briefly consider the main points of the 1C servers administration console:
Create a Central 1C server
To add a new Central Server We will use 1C:Enterprise 8.2 context menu having previously selected the line Central servers 1C
A window will appear where you need to enter the name of the 1C server or its IP address.
Creation of 1C server administrators
IN branches Administrators server administrators are added. Administrators have rights to administer only their own server; you do not need to be an administrator to manage a cluster. If no Administrator has been added, then everyone who logs in will be able to manage the server.
Creating 1C cluster workflows
Working servers This is where worker processes are added and removed, allowing you to influence the performance of user sessions by distributing them across worker processes.
If you look at the process properties, you will see the following:
Performance: a number up to 1000 is indicated, the default value is 1000. New sessions are attached to the process that has the maximum performance and once every N minutes the system itself looks at the actual processor load and rearranges the performance number.
Property Enabled: here the activity of the process is monitored and can take the following values: Use, Don't use, Use as backup
Creating and deleting information security
In the thread Information bases connected databases are visible, it is possible to delete a database or create a new one.
If we look at the properties of the database, we will see the following:
Session start blocking is enabled– sets a ban on connecting to this database.
Message– issued when trying to join while blocked.
Permission code– allows connection to be made when connections are blocked.
Ending a 1C user session
In general Sessions branch you can view the list of sessions for the entire cluster; to view sessions for a separate infobase, you need to select the desired information security and view its Sessions.
Loading...
