3.20.2. <point> (root element)

<< Prev   Next >>

<point> is the root element of the configuration file. It defines the virtual resource settings. It can contain one instance of each item: <zones>, <ws>, <pool>, <debug>, <openid>, <openidconnect>, <exitURL>, <standardOData>, <analytics>, and <progressiveWebApplication>. In this case, several nested <point> elements are allowed in the <ws> element, and several nested <zone> elements are allowed for the <zones> element:

<point...>
<ws...>
<point>...</point>
<zones>
<zone>...</zone>
<zone>...</zone>
</zones>
<point>...</point>
</ws>
<httpServices>
<service>...<service/>
</httpServices>
<pool.../>
<debug.../>
<openid>
<rely... />
<provider>
<lifetime>...</lifetime>
</provider>
</openid>
<openidconnect.../>
<exitURL>
...
</exitURL>
<standardOData.../>
<analytics.../>
<progressiveWebApplication.../>
</point>

Example:

<?xml version="1.0" encoding="UTF-8"?>
<point xmlns=http://v8.1c.ru/8.2/virtual-resource-system xmlns:xs=http://www.w3.org/2001/XMLSchema xmlns:xsi="http://www.w3.org/2001/XMLSchema-instance"
base="/demo"
ib="Srvr=&quot;tcp://Server&quot;;Ref=&quot;demo&quot;;"
enable="false"
allowexecutescheduledjobs="force"
<ws>
<point name="OperationalData" alias="OperData"/>
<point name="AnalyticalData" alias="AnalytData"/>
</ws>
<httpServices>
<service name="OperationExample" enable="true"/>
</httpServices>
<pool size="50" maxAge="10" attempts="2"/>
<debug enable="true" protocol="tcp" url="tcp://localhost"/>
<zones>
<zone value="8214" safe="true"/>
<zone value="last" specify="true" />
</zones>
</point>

The root element of the default.vrd file may contain the following attributes:

The base element points to a relative path (relative to the website root directory) to the virtual application directory.

Example:

base="/demoMA"

Contains the connection string to 1C:Enterprise infobase. Remember that different connection strings are used for the file and client/server modes.

File infobase example:

ib="File=c:/bases/demo;"

Client/server infobase example:

ib="Srvr="tcp://myServer";Ref="mybase";"

In the connection string you can specify user login and password. In this case, the connection to the infobase will be performed on behalf of the specified user. In the following example, the connection will be established on behalf of the Seller user:

ib="Srvr="tcp://myServer";Ref="mybase";Usr=Seller;Pwd=123;"

However, if you specify a login and password at the command line for the client application, the connection will be performed with the parameters specified in the command line.

Responsible for operations with the published infobase using a thin and a web client. If the attribute is true, operations with the published infobase using thin clients and web clients are allowed. The connection string will look like this (for example, at the beginning of the section):

http://host/demo

Otherwise (the attribute is set to false), operations using the thin client and the web client are not allowed.

Default value: true (thin client and web client operations are allowed).

Allows you to specify a temporary files directory for the web server extension (wsisapi.dll, wsap22.dll, wsapch2.dll) or for the infobase file mode. If the attribute is not specified:

• The file infobase uses the 1Cv8Tmp subdirectory of the directory that contains the infobase file.
• In other cases, the temporary file directory of the user on whose behalf the request is performed is used.

If the attribute contains a reference to a directory used as a temporary file directory for the web server extension operation, the user on whose behalf the web server extension is started must have full access to that directory and its contents.

The attribute value specifies the full URL of the client application distribution package file to be downloaded and installed in the event of a mismatch between the client application and server versions. This URL must be accessible from outside the computer on which the distribution package is located. Attributes contain paths to distribution packages of the corresponding client applications:

Dialog box	default.vrd file	Description
Linux x32	pubdstlin32	32-bit thin client for Linux
Linux x64	pubdstlin64	64-bit thin client for Linux
macOS x64	pubdstmac64	64-bit thin client for macOS
Windows x32	pubdstwin32	32-bit thin client for Windows
Windows x64	pubdstwin64	64-bit thin client for Windows

If the client application distribution package is obtained over an HTTPS connection, the computer receiving the distribution package will verify the certificate of the server from which the distribution package is being received using the root certification authority certificates obtained from the root certificate store of the operating system used. The installation will use the parameters specified in the 1cestart.cfg file (similar to the regular installation of the client application).

The client application distribution package must be placed in an archive. An exception is the RUN file from the Linux installer that cannot be archived. Archive type: zip. Archive requirements:

• Archive file structure:
  • On Linux: thin client installer file (RUN file). setup-fhin-A.B.C.D-arch.run, where A.B.C.D is the full number of 1C:Enterprise version and arch is the used architecture of the client application.
  • On macOS: .dmg.
  • On Windows: no hierarchy or directories, only the distribution package files of the client application.
• Features of the distribution package files:
  • Distribution package on macOS: all archive files with the .pkg extension must be digitally signed.
  • Distribution package on Windows: all files with the .msi, .cab, and .mst extensions located in the archive must be digitally signed. If OS Windows XP is unavailable in a list of client operating systems (managing installation of 1C:Enterprise), there is no need to archive a file with _xp name suffix, such as 1CEnterprise8_xp.msi and 1049_xp.mst, and so on.
• Digital signatures of the files included in the distribution package should be checked on the computer where the installation will be executed.
• When using IIS web server, you might need to specify a MIME type for the .zip extension.

Example:

pubdstwin32="http://www.myhost.ru/files/client-win-32.zip"
pubdstmac64="http://www.myhost.ru/files/client-mac-64.zip"
pubdstlin64="http://www.myhost.ru/files/setup-fhin-8.3.20.100-x86_64.run"

If the server version is changed, you only need to replace the client application archive file.

The attribute controls the ability to execute scheduled jobs by the web server extension for the infobase file mode.

The attribute can take the following values:

• off. In this case, the web server extension will not perform scheduled jobs. In this case, the client application (if there is any) that connects to the infobase directly, without the use of a web server, will perform scheduled jobs.
• force. In this case, the web server extension will perform scheduled jobs.

Default value: not specified. In this case, the scheduled jobs will be run by the application that established the first connection to the infobase.

<< Prev   Next >>