Chapter 4. Running system components

<< Prev   Next >>

4.1. General information

When installing 1C:Enterprise, the following structure will be created in the Start – Programs menu (see example for Windows 10):

1C:Enterprise
1C:Enterprise 8 (folder)
1C:Enterprise (A.B.C.D)
ReadMe – Additional Information
Register server administration utility (A.B.C.D)
1C:Enterprise server administration
Start server (A.B.C.D)
Install protection driver
Remove protection driver

In the above list:

Item	Purpose
Install protection driver	Starts installation of the protection driver
Remove protection driver	Starts removal of the protection driver
ReadMe Additional Information	Additional information not included in the documentation
1C:Enterprise server administration	Server cluster administration utility (if any 1C:Enterprise server cluster access components are installed)
Start server (A.B.C.D)	Starts the 1C:Enterprise server as a service (if the Install 1C:Enterprise 8 server as Windows service check box was selected during server installation) or as an application (if the Install 1C:Enterprise 8 server as Windows service check box was cleared during server installation). In this case, server shutdown is identical to closing a regular application.
Register server administration utility (A.B.C.D)	Registers the 1C:Enterprise server administration utility (radmin.dll) for a specific version, so that you can connect to the servers of this version using the administration utility.

In this table:

• Specifying the name of an application without specifying a version means the application or file from the version that was installed latest.
• Specifying (A.B.C.D) next to an application name means that a separate menu item is created for each installed version, where A.B.C.D means the full number of the installed version. For example, if two versions are installed – 8.3.12.100 and 8.3.12 150, then the menu will have two lines: Starting the server (8.3.12.100) and Starting the server (8.3.12.150).
• If the 64-bit version of the 1C:Enterprise is installed, the name of the menu folder and names of items in this folder will contain x86-64.

When launching the 1C:Enterprise server components, the system command line interface is actively used. A detailed description of the device interface {HL: adm: TI000000832}.

If the 1C:Enterprise server is installed in the "for the user" mode, it cannot run as a Windows service.

4.2. Running the server agent

4.2.1. General information

To launch the 1C:Enterprise server cluster, you must start the server agent (ragent). All further actions will be executed by the system automatically. At startup, the server agent searches for a list of clusters registered on this computer.

If the cluster list is found, the server agent starts the specified cluster managers. Through these, it obtains information about the working processes that must be run in each cluster and starts these processes, with or without the help of agents of other working servers of the cluster.

If no list of clusters is found, the server agent creates a default cluster. If no list of clusters is found, the server agent creates a default cluster.

• Network port number: 1541
• Network port range: 1560: 1591
• When running in debug mode using the HTTP protocol, the debug server uses port 1550
• One working process is used; its port number is picked from the specified range

4.2.2. On Windows

4.2.2.1. Run as an application

The server agent can be run as an application. To do this, run the following command:

ragent /port <port> /regport <port> /range <range>
/seclev <level> /d <directory>
/pingPeriod <time> /pingTimeout <time>
/debug -<mode> /debugServerAddr <address> /debugServerPort <port> /debugServerPwd <password>

The start command can use the following commands:

The network port number of the server agent (ragent). This port is used by the cluster console to access the central server. The cluster agent port is also specified as the network port of the working server. The default value is 1540.

The network port number of the main cluster manager (rmngr) created by default on the first run of ragent. The default value is 1541.

Network port ranges for dynamic selection. Used as the initial value of the IP port ranges property of the working cluster server created by default when the server agent is first started (ragent). The default value is 1560:1591. Examples of range values: 4549:4567, 7072:7790.

The security level of the cluster agent process. Specifies the security level of connections established with the ragent process. Level can take values:

• 0 (default) – unprotected connections
• 1 – secure connections only for the duration of user authentication
• 2 – permanently protected connections

For details on the security level of a connection, see page.

The directory where the server cluster internal files are, or will be, stored (including the list of clusters and the list of cluster infobases). If this parameter is not specified, a default directory will be used: %USERPROFILE%\Local Settings\Application Data\1C\1cv8 (%LOCALAPPDATA%\1C\1cv8 for OS Windows Vista or later). If the directory path contains spaces, the path must be enclosed in quotes, for example:

/d "c:\Server data\cluster 2"

The period of checking the connection tracking system, milliseconds (see page).

The default value is 1000.

Timeout checking the connection tracking system, milliseconds (see page).

The default value is 5000.

Running a server cluster in configuration debugging mode. The <mode> parameter specifies a protocol for the debugger on this server cluster:

• -tcp – TCP/IP protocol
• -http – HTTP protocol

The default value is -tcp.

Specifies the address of the computer on which the debug server is running. It is recommended to use this key in the case when several network cards are installed on the computer.

If the key is not specified, then an arbitrary network address will be used that belongs to the computer where the debug server is running.

Specifies which port should be used by the debug server. The default port is 1550.

Specifies the password that the client application will need to use when establishing a connection with the debugging server of this server cluster.

By default, no password is set.

Stop the server agent running as an application by pressing the Ctrl + C keys.

4.2.2.2. Run as a service

If during installation of the server cluster the option of starting the central server agent as a service was chosen, then this service will be started automatically during the installation process and will also be started at the start of the operating system.

If the agent of the central server was installed as an application, then it is possible to register the service manually and then launch it.

The service name differs in 32 and 64-bit versions of 1C:Enterprise:

1C:Enterprise version	Service name
32-bit version	1C:Enterprise 8.3 Server Agent
64-bit version	1C:Enterprise 8.3 Server Agent (x86-64)

Service registration is performed by the following command:

ragent /instsrvc|/rmsrvc /usr <name> /pwd <password>
/start|/stop
/port <port> /regport <port> /range <range>
/seclev <level> /d <directory>
/pingPeriod <time> /pingTimeout <time>
/debug -<mode> /debugServerAddr <address> /debugServerPort <port> /debugServerPwd <password>

Register a cluster agent as a Windows service. If ragent is running with this key, it will register in the list of Windows services and exit.

The / instsrvc switch is incompatible with the / rmsrvc switch.

Unregistering the cluster agent as a Windows service. If ragent is started with this key, it will cancel its registration in the list of Windows services and end.

The / rmsrvc switch is incompatible with the / instsrvc switch.

Run ragent registered as a Windows service. Runs ragent, previously registered as a Windows service, and then terminates.

Stop ragent registered and running as a Windows service. Stops ragent, previously registered and running as a Windows service, and then terminates.

The name and password of the Windows user on whose behalf ragent should be launched as a Windows service. Can only be used with the / instsrvc switch when registering ragent as a Windows service.

The network port number of the server agent (ragent). This port is used by the cluster console to access the central server. The cluster agent port is also specified as the network port of the working server. The default value is 1540.

The network port number of the main cluster manager (rmngr) created by default on the first run of ragent. The default value is 1541.

Network port ranges for dynamic selection. Used as the initial value of the IP port ranges property of the working cluster server created by default when the server agent is first started (ragent). The default value is 1560:1591. Examples of range values: 4549:4567, 7072:7790.

The security level of the cluster agent process. Specifies the security level of connections established with the ragent process. Level can take values:

• 0 (default) – unprotected connections
• 1 – secure connections only for the duration of user authentication
• 2 – permanently protected connections

For details on the security level of a connection, see page.

The directory where the server cluster internal files are, or will be, stored (including the list of clusters and the list of cluster infobases). If this parameter is not specified, a default directory will be used: %USERPROFILE%\Local Settings\Application Data\1C\1cv8 (%LOCALAPPDATA%\1C\1cv8 for OS Windows Vista or later).

The period of checking the connection tracking system, milliseconds (see page).

The default value is 1000.

Timeout checking the connection tracking system, milliseconds (see page).

The default value is 5000.

Running a server cluster in configuration debugging mode. The <mode> parameter specifies a protocol for the debugger on this server cluster:

• -tcp – TCP/IP protocol
• -http – HTTP protocol

The default value is -tcp.

Specifies the address of the computer on which the debug server is running. It is recommended to use this key in the case when several network cards are installed on the computer.

If the key is not specified, then an arbitrary network address will be used that belongs to the computer where the debug server is running.

Specifies which port should be used by the debug server. The default port is 1550.

Specifies the password that the client application will need to use when establishing a connection with the debugging server of this server cluster.

By default, no password is set.

The default service is started automatically when you turn on the computer. You can also manually start the service from Windows: My Computer – Management – Services and applications – Services – Agent of 1C:Enterprise 8 server (My computer – Manage – Computer Management – Services and Applications – Services – 1C:Enterprise 8 Server Agent). You can also manually stop the service from Windows.

To stop the service, run this command:

ragent /rmsrvc

4.2.3. On Linux

4.2.3.1. General information

The installer sets up the server processes so that they are started in daemon mode, that is, without binding them to any specific control terminal. If necessary, the server agent can be started with command-line parameters.

4.2.3.2. Running the server agent

To start the server agent, use the following command-line parameters:

./ragent /daemon
/port <port> /regport <port> /range <range>
/seclev <level> /d <directory>
/pingPeriod <time> /pingTimeout <time>
/debug -<mode> /debugServerAddr <address> /debugServerPort <port> /debugServerPwd <password>

This parameter allows you to start the server agent in daemon mode, that is, as a background application that does not interact with the terminal used to start it. Running a server agent with this parameter does not auto start the server agent after a system reboot.

The network port number of the server agent (ragent). This port is used by the cluster console to access the central server. The cluster agent port is also specified as the network port of the working server. The default value is 1540.

The network port number of the main cluster manager (rmngr) created by default on the first run of ragent. The default value is 1541.

Network port ranges for dynamic selection. Used as the initial value of the IP port ranges property of the working cluster server created by default when the server agent is first started (ragent). The default value is 1560:1591. Examples of range values: 4549:4567, 7072:7790.

Optional. The security level of the cluster agent process. Specifies the security level of connections established with the ragent process. Level can take values:

• 0 (default) – unprotected connections
• 1 – secure connections only for the duration of user authentication
• 2 – permanently protected connections

For details on connection security level, see page 

The directory where the server cluster internal files are, or will be, stored (including the list of clusters and the list of cluster infobases). If the parameter is not specified, the default directory is used: ~/.1cv8. If the directory path contains spaces, the path must be enclosed in quotes, for example:

/d "~/cluster data"

The period of checking the connection tracking system, milliseconds (see page).

The default value is 1000.

Timeout checking the connection tracking system, milliseconds (see page).

The default value is 5000.

Running a server cluster in configuration debugging mode. The <mode> parameter specifies a protocol for the debugger on this server cluster:

• -tcp – TCP/IP protocol
• -http – HTTP protocol

The default value is -tcp.

Specifies the address of the computer on which the debug server is running. It is recommended to use this key in the case when several network cards are installed on the computer.

If the key is not specified, then an arbitrary network address will be used that belongs to the computer where the debug server is running.

Specifies which port should be used by the debug server. The default port is 1550.

Specifies the password that the client application will need to use when establishing a connection with the debugging server of this server cluster.

By default, no password is set.

Stop the server agent running as an application by pressing the Ctrl + C keys.

4.2.3.3. Running the server agent using a script

A dedicated script srv1cv83 is intended to manage the 1C:Enterprise server agent. The script is located in a directory with a specific version and bitness. The script always starts the server in daemon mode. The script uses the following command-line parameters:

srv1cv83 start|stop|restart|info|status

Starts the server. The script runs a single instance of 1C:Enterprise server.

Stops the server. The script only stops the server that was previously started by this script (see the start command above).

Restarts the server. Same as the sequence of commands stop and start.

Displays information about server settings: ports specified at startup, cluster directory, configuration debug mode status, connection security level.

Displays server status information (enabled or disabled, running or stopped).

To specify the startup parameters for the 1C:Enterprise server agent, use the configuration file that is located in the directory containing the system start script. For description of parameters of the configuration file {HL:adm:TI000000417:refer to the book}.

An example of configuration file:

#------------------------------------------------------------
# 1C:Enterprise Server configuration parameters
#------------------------------------------------------------
# 1C:Enterprise Server keytab file.
# default - usr1cv8.keytab file in 1C:Enterprise Server
# installation directory
#SRV1CV8_KEYTAB=
# Number of the cluster port created by default during first
# launch of ragent
# default - 1540
SRV1CV8_PORT=1540
# Number of cluster agent main port. This port is used by the
# cluster console to address the central Server. Cluster agent
# port is also specified as the IP port of the working Server.
# default - 1541
SRV1CV8_REGPORT=1541
# Port range for connection pool
# example values:
# 4549:4567,7072:7790
# default - 1560:1691
SRV1CV8_RANGE=1560:1691
# 1C:Enterprise Server configuration debug mode
# 0 - default - off
# 1 - on
SRV1CV8_DEBUG=0
# Path to directory with claster data
# default - $HOMEDIR/.1cv8/1C/1cv8
SRV1CV8_DATA=$HOMEDIR/.1cv8/1C/1cv8
# Security level:
# 0 - default - unprotected connections
# 1 - protected connections only for the time of user
# authentication
# 2 - permanently protected connections
SRV1CV8_SECLEV=0
#------------------------------------------------------------
# end of config
#------------------------------------------------------------

4.2.3.4. Enabling auto start for 1C:Enterprise server

In order for the 1C:Enterprise server to automatically start at OS startup, run the following command:

• Copy the srv1cv83 file from the directory with a specific bitness and version, and then paste it to the /etc/init.d directory. Make sure that the script has a unique name within the /etc/init.d directory. For example, you can name the script according to its full version. In that case, a script for version 8.3.18.100 will be named srv8-3-18-100.
• Copy the src1cv83.conf configuration file from the directory with a specific bitness and version, and then paste it into the following directory:
  • For RPM systems: /etc/sysconfig
  • For DEB systems: /etc/defaults

    The name of the configuration file that you pasted must match the name of the script for auto start. This configuration file will contain parameters for starting the server with the same name. In the example described above, the configuration file must be named srv8-3-18-100.conf.

• Add the script for starting the server to the system start script:
  • For RPM systems:

chkconfig --add <UniqueScriptName>
chkconfig <UniqueScriptName> on

• For DEB systems:

update-rc.d <UniqueScriptName> defaults
update-rc.d <UniqueScriptName> start

In these commands, <UniqueScriptName> stands for the name of the script for auto start (and of the configuration file) that you picked upon copying the srv1cv83 file into the /etc/init.d directory.

As a result, the server with a specific version and bitness will be added to the list of automatically started services.

4.3. Collaboration between server processes

4.3.1. General information

In the total majority of use cases, one server agent runs per working server.

When multiple clusters are created under the control of a single server agent, the server agent ensures that their network ports do not conflict. If clusters are created under the control of different server agents, you need to take additional efforts to ensure there are no conflicts between the network ports of the cluster managers.

You should always take efforts to ensure there are no conflicts between the network ports of working processes on the server (provided that the server is used in different clusters), even when such clusters run under the control of the same server agent.

The situation when two or more server agents run on a computer at the same time, each agent managing a set of clusters, is rare but not abnormal. For example, this may be necessary when you need to use multiple versions of the 1C:Enterprise server on the same computer.

To ensure the parallel operation of two server agents processing different clusters, you need to meet the following conditions:

• Server agents must have different network ports
• Server agents must have different internal file directories
• Server clusters created for each server agent must have different network ports
• Network port ranges used by working processes on this server must not overlap (if this server is used in different clusters)

4.3.2. On Windows

4.3.2.1. General information

This section explains how to start a second instance of the 1C:Enterprise server on a computer.

Please note that the installer does not allow changing the network ports of the server, so a new instance of the server will not be able to function directly after installation.

The following examples assume that the 1C:Enterprise server runs on an OS of the same bitness (a 32-bit server on a 32-bit OS, or a 64-bit server on a 64-bit OS). If you run 32-bit 1C:Enterprise server on 64-bit Windows, replace path C:\Program Files with C:\Program Files (x86) in all examples in the following sections.

4.3.2.2. Running multiple servers with different 1C:Enterprise versions

4.3.2.2.1. As a service

To start a 1C:Enterprise 8.3 server as a Windows service when a 1C:Enterprise 8.1 server is already running:

• Go to the bin directory of the installed 1C:Enterprise 8.3 server. In this example, 1C:Enterprise 8.3.3.150 is used.

c:
cd "c:\Program Files\1cv8\8.3.3.150\bin"

• Delete registration of the 1C:Enterprise 8.3 server.

ragent /rmsrvc

• Delete contents of the cluster registry directory. The directory location depends on how the installation of the 1C:Enterprise 8.3 server was performed (for details, see page ).

rmdir /s /q "c:\Program Files\1cv8\srvinfo"

• Register the service with different network port values.

ragent /instsrvc /port 2540 /regport 2541 /range 2560:2590 /usr .\usr1cv8 /pwd UsrPwd8 /d "d:\DbData\srvinfo"

In this example, the following port values are used:

• Serial port number of server agent is 2540.
• Serial port number of cluster manager is 2541.
• Diapason of ports for dynamic selection is 2560:2590/.
• Cluster registry data is located in directory D:\DbData\srvinfo.
• The user on whosebehalf the service of 1C:Enterprise,  usr1cv8 is performed.
• The password on the behalf of which the service of 1C:Enterprise server,  UsrPwd8 is performed.
• If you need to enable debugging mode for the registered service, add the /debug parameter to the command line.
  • Start the 1C:Enterprise server.

ragent /start

4.3.2.2.2. As an application

To change network ports for a 1C:Enterprise server started as an application:

• Shut down the running server instance by pressing Ctrl + C in the console window of the server.
• Go to the bindirectory of the installed 1C:Enterprise 8.3 server. In this example, 1C:Enterprise 8.3.3.150 is used.

c:
cd "c:\Program Files\1cv8\8.3.3.150\bin"

• Delete contents of the cluster registry directory. The directory location depends on how the installation of the 1C:Enterprise 8.3 server was performed (for details, see page ).

rmdir /s /q "%USERPROFILE%\Local Settings\Application Data\1C\1cv8"

• Start the 1C:Enterprise server with new values of network ports and other data.

ragent /port 3540 /regport 3541 /range 3560:3590 /d "d:\DbData\srvinfo"

In this example, the following port values are used:

• Number of network port of server agent is3540.
• Number of network port of cluster manager is3541.
• Diapason of ports for dynamic selection is 3560:3590.
• Cluster registry data is located in directory D:\DbData\srvinfo.
• If you need to enable debugging mode for the registered service, add the /debug parameter to the command line.
• On subsequent starts, use exactly the same startup command string. For convenience, you can save it to a Windows batch file.

4.3.2.3. Running multiple servers with identical 1C:Enterprise versions

4.3.2.3.1. As a service

1C:Enterprise has no standard functionality for registering multiple instances of the 1C:Enterprise server service with the same version. You should use the sc utility instead. Service names, network port numbers and cluster directory addresses used by the service instances must be different.

Let us review an example of the batch file that performs the registration of the server service.

Register-service.bat:

@echo off
rem %1 – 1C:Enterprise full version
rem%2 – first two digits of the port numbers. For ports 1540,1541,1560:1591, use 15.
rem %3 – directory with cluster registry data
 
set SrvUserName=<user name>
set SrvUserPwd=<user password>
set RangePort=%260:%291
set BasePort=%241
set CtrlPort=%240
 
set SrvcName="1C:Enterprise 8.3 Server Agent %CtrlPort% %1"
set BinPath="\"C:\Program Files\1cv8\%1\bin\ragent.exe\" /srvc /agent /regport %BasePort% /port %CtrlPort% /range %RangePort% /d \"%~3\" /debug"
set Description="1C:Enterprise 8.3 Server Agent" Parameters: %1, %CtrlPort%, %BasePort%, %RangePort%"
 
if not exist "%~3" mkdir "%~3"
 
sc stop %SrvcName%
sc delete %SrvcName%
sc create %SrvcName% binPath= %BinPath% start= auto obj= %SrvUserName% password= %SrvUserPwd% displayname= %Desctiption% depend= Dnscache/Tcpip/Tcpip6/lanmanworkstation/lanmanserver

Before using this batch file, make sure it contains actual user data (name and password) you want to use for starting the server cluster service(see lines set SrvUserName= and set SrvUserPwd=). This batch file registers the specified version of 1C:Enterprise server. The service name is a string containing the following information:

• 1C:Enterprise 8.3 Server Agent
• Network port number of the main cluster manager
• Full version number of 1C:Enterprise

When registering server version 8.3.3.100 with main cluster manager port 2540, the service name will look like this: 1C:Enterprise 8.3 Server Agent 2540 8.3.3.100.

Example:

register-service 8.3.3.100 25 "c:\cluster_data\cluster 1"
register-service 8.3.3.100 35 "c:\cluster_data\cluster 2"

In this example, the first line registers the server service with the following parameters:

• Service name: 1C:Enterprise 8.3 Server Agent 2540 8.3.3.100
• Server ports: 2540, 2541, 2560:2591
• Directory containing cluster registry data: C:\cluster_data\cluster 1
• Service description: 1C:Enterprise 8.3 Server Agent. Parameters: 8.3.3.100, 2540, 2541, 2560:2591

The second line registers the server service with the following parameters:

• Service name: 1C:Enterprise 8.3 Server Agent 3540 8.3.3.100
• Server ports: 3540, 3541, 3560:3591
• Directory containing cluster registry data: C:\cluster_data\cluster 2
• Service description: 1C:Enterprise 8.3 Server Agent. Parameters: 8.3.3.100, 3540, 3541, 3560:3591

To unregister the server service, you can use the following example batch file.

Unregister-service.bat:

@echo off
rem %1 – 1C:Enterprise full version
rem%2 – first two digits of the port numbers. For ports 1540,1541,1560:1591, use 15.
 
set SrvcName="1C:Enterprise 8.3 Server Agent %240 %1"
 
sc stop %SrvcName%
sc delete %SrvcName%

Example:

unregister-service 8.3.3.100 25

This batch file stops the service and deletes its registration. The service name is formed according to the same rules as when registering a new (non-standard) 1C:Enterprise server service.

4.3.2.3.2. As an application

You can start multiple server instances of the same version, working as an application, from the command line. In this case, the command line parameters should differ not only in the numbers of network ports, but also in the addresses of the cluster directories.

start "Server 1" "C:\Program Files\1cv8\8.3.3.100\bin\ragent.exe" /port 2540 /regport 2541 /range 2560:2590 /d d:\ClusterData\Srv1
start "Server 2" "C:\Program Files\1cv8\8.3.3.100\bin\ragent.exe" /port 3540 /regport 3541 /range 3560:3590 /d d:\ClusterData\Srv2

In the example, two instances of the 1C:Enterprise server are started with the following parameters:

• The first server has Server 1 window title, uses network ports 25xx and stores cluster data at D:\ClusterData\Srv1.
• The second server has Server 2 window title, uses network ports 35xx and stores cluster data at D:\ClusterData\Srv2.

4.3.2.4. Changing the network ports used by a running 1C:Enterprise server instance

You cannot change network ports used by an already running instance of the 1C:Enterprise server. If such a need arises, you should:

• Create a new server instance with the required network port values and other parameters.
• Register existing infobases on the new server.
• Transfer users to the new server.
• Stop and delete the old instance of the 1C:Enterprise server (along with the cluster data).

4.3.3. On Linux

4.3.3.1. General information

This section explains how to start a second instance of the 1C:Enterprise server on a computer.

Please note that the installer does not allow changing the network ports of the server, so a new instance of the server will not be able to function directly after installation.

4.3.3.2. As daemon

To change the network ports of a running server instance:

• Stop the 1C:Enterprise server.

/etc/init.d/srv1cv83 stop

• Delete the cluster directory.

rm -rf /home/usr1cv8/.1cv8

• Change the startup parameters of the 1C:Enterprise server by specifying the required for network ports values and other parameters (including the cluster registry directory). For description of the configuration file {HL:adm:TI000000417:refer to the book}.
• Start the 1C:Enterprise server.

/etc/init.d/srv1cv83 start

4.3.3.3. As an application

To change the network ports for a 1C:Enterprise server running as an application:

• Shut down the running server instance by pressing Ctrl + C in the console window of the server.
• Delete contents of the cluster registry directory. Typically, this is the .1cv8 directory located in the home directory of the user on whose behalf the server is running.

rm -rf /home/<ServerUser>/.1cv8

• Go to the directory with 1C:Enterprise binary files.

For the 32-bit version:

cd /opt/1cv8/i386/A.B.C.D

For the 64-bit version:

cd /opt/1cv8/x86_64/A.B.C.D

• Start the 1C:Enterprise server with new values of network ports and other data.

./ragent /port 2040 /regport 2041 /range 2060:2090 /d /home/usr1cv8/dbinfo/.1cv8

In the example, server is started with the following port values:

• Number of network port of server agent –2040
• Number of network of cluster manager – 2041
• Diapason of ports for dynamic selection – 2060:2090
• Cluster registry data is located in the /home/usr1cv8/dbinfo/.1cv8 directory
• If you need to enable debugging for the registered service, add the -debug parameter to the command line
• On subsequent starts, use exactly the same startup command string. For convenience, you can save it to a Linux command file.

4.3.3.4. Changing the network ports used by a running 1C:Enterprise server instance

You cannot change network ports used by an already running instance of the 1C:Enterprise server. If such a need arises, you should:

• Create a new server instance with the required network port values and other parameters.
• Register existing infobases on the new server.
• Transfer users to the new server.
• Stop and delete the old instance of the 1C:Enterprise server (along with the cluster data).

<< Prev   Next >>