The task is to raise the IIS web server built into Windows and publish a 1C database on it on the 8.3 platform. There is nothing complicated about it.

We have a 2008 r2 enterprise server spinning on a virtual machine. Local administrator rights to it. Platform 1C 8.3.6.2041. We will create an empty information base. And so let's get started. Join our group on VK! Get it repaired! Smart workshop!

Installing the webserver role (IIS)

First you need to install the webserver role. Opening Server Manager, select the branch on the left Roles, click on the right Add a role.

We get to the step of selecting Server Roles and check the box next to Web Server (IIS). Click next. Now you need to correctly select the services of the installed role. Check the boxes exactly as in the screenshot below.

We complete the installation. The Add Role Wizard should tell us after a certain time that the role and all role services have been successfully installed:

Now we need to check if everything worked out well. Open any browser and go to the address http://localhost. We should see a happy picture like this:

installation of the 1c platform and components

This means that our web server has started up correctly and everything is working fine. So let's move on to 1s now. It is necessary to install a platform. The only caveat when installing the platform is to choose:

• 1C:Enterprise

• Web server extension modules

setting access rights

First of all, we need to configure the rights of the folder where our web server root directory is located. If you haven't changed anything, then by default it is C:\inetpub\wwwroot. Go to the folder C:\inetpub\ select a folder wwwroot, Right-click on it and go to properties. Go to the tab Safety. By clicking on the change button, we go directly to setting up permissions. We find it in the list Groups and users, group Users, and by clicking on it put it in the column below Group Permissions, missing checkmarks in the column Allow.

Now you need to give rights to the folders with 1c installed. Let's move on to them, by default for the 32-bit version 1c is in the folder C:\Program Files (x86)\1cv8 for 64-bit in the folder C:\Program Files\1cv8. Also select the folder 1cv8 go to its properties, go to the tab Security -> Edit. But instead of selecting a group from the list, we need to add it there first. To do this, press the button Add, in the window that appears, press the button Additionally.

Next, click on the button Search and look in the result list IIS_IUSRS, adding it with a double click returns us to the window Selecting Users or Groups but with the group already included in the list. Click OK and return to the window Group Permissions We put all the checkboxes in the allow field for the newly added group.

Having set permissions for folders with 1c files, we are left with the last thing. Give permissions to the group IIS_IUSRS folder where we have the 1C database itself.

The necessary preparations have been made. Now let's move on to publishing.

Publishing 1c on a web server

You need to launch 1c in configurator mode, selecting the database you need to publish. In my case, this is an empty database and there is only one.

In 1c configurator mode, go to the menu Administration -> Publishing to a web server.

After looking at the parameters and making sure that, in essence, everything suits us, we click Publish. If your publication went through without errors, let's move on to the last step.

setting up IIS to work with a 32-bit 1C web server extension module

Let me remind you that we used a 32-bit platform and a web server extension module from 1c, respectively. Therefore, in this case, we still need to allow the default application pool to run - DefaultAppPool run 32-bit applications. It's not difficult to do. Let's go Server Manager -> Roles -> Web server(IIS) -> Service Manager (IIS) -> Application Pools -> DefaultAppPool. Right click on DefaultAppPool call the context menu and select from it Additional options.

We are looking for a line 32-bit applications allowed and on the contrary we put TRUE

CONFIGURING IIS TO WORK WITH A 64-BIT 1C WEB SERVER EXTENSION MODULE

If we used a 64-bit platform and a web extension module, respectively, then we need to do the following manipulations:

Let's go Server Manager -> Roles -> Web server(IIS) -> Service Manager (IIS)-> And select the application converted from the virtual directory with the name that we specified when publishing the database. In the right field go to the section Handler Mappings. Publication of 1c 8.3 on the iis web server Publication of 1c 8.3 on the iis web server

Join our group on VK!

Large corporations that use 1C software products in their remote branches often face the problem of the inability to install 1C at individual employee workstations. Sometimes this can be due to outdated computers, sometimes remoteness, sometimes lack of IT staff. 1C developers solved this problem in version 8.2 of the platform by integrating a special web client into it. Organizing work in this type of client will allow you to significantly save on upgrading computers and maintaining a staff of 1C administrators.

Externally, the web client is no different from the thin client, except that the 1C interface opens in the browser. To launch 1C web clients, you need to publish a web server and have the Internet at your workplace. The web server and DHTML and HTTPRequest technologies are responsible for connecting the database and the user interface of the web client. At the time of operation, the data is transmitted via HTTP to the web server, compiled, and execution itself occurs on the client side, in the Internet browser environment.

The sufficient popularity of the 1C web client mode is explained by the list of advantages:

• There is no need to install the 1C client part on workstations;
• Providing access to the database from anywhere in the world with Internet access;
• Support for any browsers and, accordingly, any operating systems and all gadgets with access to the World Wide Web;
• Technical simplicity, since the user simply needs to launch the browser and type the address correctly;
• A special mode for exchanging data with a web server at low Internet speeds.

In addition to the advantages, the web client mode also has certain disadvantages:

1. Vulnerability of a web server that becomes accessible anywhere in the world;
2. Certain restrictions on data exchange and file system operation;
3. Available only for configurations using a managed application type and a thin client;
4. Unavailability of local licenses.

If you firmly decide that the 1C Web client is great for users, then you will have to configure and publish a web server. As an example, let's look at setting up the standard IIS built into Windows.

If your computer has a Windows operating system installed, then you can do without third-party programs. The built-in IIS server will help you with this; to configure it, a basic knowledge of the system is enough. It should be noted that installing a server on a weak computer will make it difficult to launch 1C web clients and the performance of the entire system will be at risk. Therefore, it is recommended to configure IIS only on those configurations where the operating system functions without delays and there is a large supply of resources.

To start setting up the server, go to “Control Panel” -> “Programs and Features” -> “Turn features on or off.” Find the “IIS Services/Internet Services” branch in the tree and check the following boxes:

• In the "Common HTTP Features" section:
  • “Browse directory”;
  • "Default Document";
  • "Static content";
  • "HTTP Errors".
• “Performance check and diagnostics”:
  • "HTTP Logging";
  • "Request Monitor".
• "Application Development Components":
  • "ASP";
  • "ASP.NET";
  • "ISAPI extension";
  • ".NET Extensibility";
  • ISAPI filters".
• "Controls":
  • "IIS Management Console".

To publish the configured server, you must install 1C web server extension modules. To do this, during the 1C installation process, you need to check the appropriate box in the window for changing the installation method and install the components. Then launch 1C in configurator mode with administrative rights and click “Administration” -> “Publish on a web server...” in the menu. The 1C platform will automatically detect the configured web server, and you will only have to specify the name of the database and its location.

Once you click Publish, the server should restart. Now you can check the progress of the work by launching the 1C web client and entering the line in the browser: “http:ServerName/BaseName”. It is necessary to ensure that all users have read and write access to the database location. Otherwise, setting up the 1C web client at workstations will not produce results.

The 1C web client is a convenient tool for users whose workplace performance leaves much to be desired. Thanks to simple setup, minimal differences in the application interface and a list of various advantages, the web client has gained some popularity in companies of various sizes.

Print (Ctrl+P)

Configuring web servers to work with 1C:Enterprise

1. General information

This article describes the mechanism for configuring web servers to work with a web client and Web services, as well as setting up support for OpenID authentication. Once published, the published components will be accessed as follows:
● Access to the web client. To launch the web client, you must use an address that is formed according to the following rules: <Имя хоста веб-сервера>/<Имя виртуального каталога> . If the name of the virtual directory is DemoCfg , then to start the web client you should type the following URL (to access from the local machine): http://localhost/DemoCfg.
● Contacting a Web service. To gain access to the Web service, you must use an address that is formed as follows:
<Web server hostname>/<Имя виртуального каталога>/ws/<Имя Web-сервиса> or <Имя хоста веб-сервера>/<Имя виртуального каталога>/ws/<Адрес Web-сервиса> .
So, if the virtual directory has the name DemoWS, the name of the Web service in the configurator is specified as DemonstrationWorkWS, and DemoWorkWS is specified as the address, then the Web service can be accessed simultaneously at two addresses (to gain access from the local machine):
http://localhost/DemoWS/ws/Demonstration of WS or http://localhost/DemoWS/ws/DemoWorkWS.
Read more about Web services.
● Calling an HTTP service. To gain access to the HTTP service, you must use an address that is formed as follows:
<Имя хоста веб-сервера>/<Имя виртуального каталога>/hs/<путь к ресурсу>.
For more information about HTTP services, see here.
● OpenID authentication is performed automatically by the system.
Web servers of the Internet Information Services (hereinafter referred to as IIS) family are supplied with the operating system, and to make it easier to understand which web server you are using, here is a table of correspondence between the version of the web server and the operating system:

IIS version Operating system version
IIS 5.1 Windows XP Professional
IIS 6.0 Windows Server 2003 or Windows XP Professional x64 Edition
IIS 7.0 Windows Vista or Windows Server 2008
IIS 7.5 Windows 7 or Windows Server 2008 R2
IIS 8.0 Windows 8 or Windows Server 2012
IIS 8.5 Windows 8.1 or Windows Server 2012 R2
IIS 10.0 Windows 10

The Apache web server distribution (for both Windows and Linux OS) can be obtained from the project website: http://httpd.apache.org/download.

2. General requirements

The computer on which you publish must have a supported web server installed and configured. To install the Internet Information Services web server, you may need a distribution package for the operating system you are using. When installing a web server, you must install support for ISAPI extensions. Installing a web server requires administrative privileges on the computer on which the desired web server will be installed. Publishing can be done in two ways:
● Using the publishing dialog on a web server, if the computer with the web server has the ability to launch the configurator of the required bit depth.
● Using the webinst utility. (Call the webinst utility from the bin directory of the 32-bit version of 1C:Enterprise)

To publish to web servers, you must have administrative privileges on the computer where you are publishing:

● For Windows Vista and older, to publish, you must launch the configurator using the item Run as administrator context menu of an application or launcher. If publishing is performed using the webinst utility, then either the utility itself or the Windows command line interpreter must be launched as an administrator.
● For Linux OS, to publish, you must become a superuser (root user) using the su command or run the application that publishes using the sudo command.

When you try to publish, the system checks to see if you have the necessary privileges to perform the operation. If the current user's privileges are not sufficient to perform the publication, then:

● When publishing from the configurator, the user is asked whether to continue publishing. The dialogue indicates the reason for the occurrence (of the dialogue) and contains recommendations on how to obtain the necessary privileges.
● When publishing using the webinst utility, the user receives a diagnostic message, but publishing continues.

Publishing is possible only if 1C:Enterprise is located on a computer with a web server.
For IIS 7.x and later web servers, publishing is not supported if the Directory property (or the webinst utility's dir parameter) points to a directory %SYSTEMDRIVE%\Inetpub\wwwroot.
NOTE. To work with the configuration via the web server, the configuration must not be empty.

3. Types of publication

3.1. General publication scheme

The general publication scheme is as follows:

● the request processing module (web server extension module) corresponding to the web server is registered;
● a virtual application is registered on the web server;
● a virtual application directory is created, and the default.vrd file is placed in it and configured;
● users are assigned rights to the directory with the database file (only for the file option).

To publish a web client, you should use the version of 1C:Enterprise that is used to work with the infobase that you plan to access using the web client. If two versions are installed on your computer, for example, 8.3.3.100 and 8.3.3.150, and the 1C:Enterprise server version 8.3.3.150 is running, then for publication you should use the configurator or webinst utility of exactly the same version.
When publishing, remember that the bitness of the registered web server extension must match the bitness of the web server itself.

When publishing to an IIS web server, be aware that:
● Publishing is always performed to the Default Web Site;
● Publishing is always performed for the default application pool (DefaultAppPool);
● For the application pool used to run 1C:Enterprise, support for the .NET environment must be disabled. To do this, set the .NET Framework Versions application pool property to No managed code.
To publish from the configurator, you must use the publishing dialog ( Administration – Publishing to web server…).

Rice. 1. Publishing on a web server

Then you should do the following:
● Enter the name of the virtual directory in the Name field; the name of the virtual directory can only consist of Latin characters.
● In the Web server field, specify the type of web server for which you are publishing.
● In the Directory field, specify the physical location of the directory in which the files describing the virtual directory will be located. When using the Apache web server, the directory name must contain only Latin characters.
● Select the checkboxes depending on the need Publish thin and web client and Publish Web services.
● For the IIS web server, you can specify whether to authenticate to the web server using the OS.
● If necessary, select the Web services that you want to publish. The Address column can be changed. This column specifies the synonym for the Web service. You can access a Web service either by name or by synonym.
● If necessary, configure other publishing parameters.
● Clicking the Publish button starts the publishing process. Clicking the Disable button removes the publication from the selected web server.

After publishing, you will be prompted to restart the web server in the following cases:
● the version of “1C:Enterprise” has changed;
● the path to the web server extension module has changed;
● a new publication has been made for the Apache web server;
● publishing has been disabled.
When using anonymous authentication and a file infobase, when publishing, the user on whose behalf anonymous access has access rights to the infobase directory is checked. If the user does not have the necessary rights, a warning is issued about the impossibility of working with this infobase through the web server. It is recommended to either grant rights to the directory with the infobase, or check the Use operating system authentication on the web server checkbox.
If publishing from the configurator is not available (for example, when using a 64-bit Windows OS), publishing can be done using
webinst command line utility, which is available on Windows and Linux in both bit sizes. The publishing dialog will be described in detail below.
command line switches for the webinst utility.

3.2. Publishing dialog

The publish dialog is used to create a publication or prepare a template file for publication using the webinst utility (using the -descriptor command line parameter).
All parameters that can be edited when creating a publication are located on two tabs. Let's take a closer look at them.

3.2.1. Dialogue buttons

The Publish button publishes to the web server. When publishing, a directory is created on disk and the specified web server is configured to work with 1C:Enterprise. Remember that publishing to the IIS web server is always done for the default website (Default Web Site) and the default application pool (DefaultAppPool).
Under Linux OS the following actions are performed:
● For the directory in which the default.vrd file is located, the owner group is set to the group of the user on whose behalf the web server runs;
● The default.vrd file is set to read access for the group that includes the user on whose behalf the web server is running.
In the case of publishing a file infobase, for the directory with the infobase file, the owner group is set to the group of the user on whose behalf the web server operates, and inheritance of the owner group is configured to ensure work with the infobase.

Rice. 2. Publishing on a web server

The Disable button removes the application from the web server and publishing directory, if necessary.
The Save button saves the parameters specified in the publishing dialog on the web server to a file. When saving, the system requests the name and location of the file into which the save will be performed. Saving will be done in the default.vrd file format. Using this command, you can create template files that will be used as the -descriptor parameter of the webinst utility. The values ​​of the ib and base attributes of the point element will contain the parameters of the infobase from which the file is saved.
The Load button allows you to load an arbitrary default.vrd file for editing. When loading, the ib and base attributes of the point element of the loaded file are ignored.
The Close button closes the dialog.
The Help button opens a window with help information about the publish dialog.

3.2.2. “Basic” tab

3.2.2.1. General Settings

Rice. 3. Publishing on a web server. Basic

On this tab you can set basic publishing parameters.
Name. Specifies the name of the publication. When publishing using the webinst utility, it is described by the -wsdir parameter. In the default.vrd file, corresponds to the base attribute of the point element.

Web server. Indicates which web server is being published to. Apache web servers are added to the list if they are detected on the computer. When publishing using the webinst utility, the web server used is specified by one of the parameters iis, apache2, apache22, or apache24. When running on Linux, publishing is only possible for the Apache web server.
If the system could not unambiguously determine the version of the Apache web server installed on the computer (2.2 or 2.4), both versions of the web server will be present in the list. It should be taken into account that for the Apache web server versions 2.2 and 2.4 the changes made in the web server configuration file differ. Therefore, incorrectly specifying the web server version will result in the publication not working.

Catalog. Specifies the physical directory on disk where the default.vrd file will be located and where the web server virtual directory will be mapped. The directory must exist. When publishing using the webinst utility, it is described by the -dir parameter.

Publish thin and web client. Responsible for the ability to work with the published information base using a thin and web client. If the checkbox is checked, it is possible to work with the published infobase using a thin and web client. In the default.vrd file, corresponds to the enable attribute of the point element.

Publish standard OData interface. Responsible for the ability to gain access to the standard OData interface of the application solution. The mechanism of the standard OData interface is described in more detail in the book 1C:Enterprise 8.3. “Developer's Guide”. In the default.vrd file, corresponds to the enableStandardOData attribute of the point element.

Publish distribution. Determines whether a client application can be obtained and installed if the versions of the client application and the server do not match. A zip archive is used as a distribution, the full name of which is specified as the value of the Location of the published distribution property. In the default.vrd file, these properties correspond to the pubds t attribute of the point element. The archive should
the distribution kit of the client application is located. The installation will use the installation parameters specified in the 1cestart.cfg file (same as a normal client application installation).

Use operating system authentication. Allows the system to set the OS authentication capability to the IIS web server.

Transition address when the web client ends allows you to specify the URL to which the transition will be made after the web client ends. In the default.vr file, d corresponds to the exitURL element.

3.2.2.2. Web services tab

Rice. 4. Publishing Web services

Publish Web Services. Selecting this checkbox will cause the Web services created in the configuration and listed in the table below the checkbox to be published. In the default.vrd file, corresponds to the enabl e attribute of the ws element. If the flag is cleared, this is equivalent to either not having a ws element in the default.vrd file, or having a ws element with the enable attribute set to true.

Publish Web Services by Default. Responsible for the possibility of using Web services in this information base that are published without explicit permission for use. In the default.vrd file, corresponds to the pointEnableCommon attribute of the ws element.
Table below checkbox Publish Web Services contains a list of published Web services and allows you to manage the publication of each Web service. The first column controls the publication of a specific Web service. If the checkbox is cleared, this Web service will be prohibited from use (it cannot be called). In the default.vrd file, corresponds to the enable attribute of the point element.
The second column (named Name) contains the name of the Web service, as it was specified during creation. A description of Web services is given in the book 1C:Enterprise 8.3. “Developer's Guide”. In the default.vrd file, corresponds to the name attribute of the point element.
The last column of the table (named Address) contains an alias for the name of the published Web service. You can access a Web service either by name or by alias. The Web service alias can be edited in the publish window. In the default.vrd file, it corresponds to the alias attribute of the point element.
Web services that are located in connected extensions are not displayed in this table and can only be published by manually editing the default.vrd file.
Publish extension Web services by default. Responsible for the ability to use Web services that are supplied in configuration extensions. In the default.vrd file, corresponds to the publishExtensionsByDefault attribute of the ws element.

3.2.2.3. HTTP services tab

The HTTP services tab is intended to control the ability to access the application solution using HTTP services.

Rice. 5. Publishing HTTP services

Selecting this checkbox will cause the HTTP services created in the configuration and listed in the table below the checkbox to be published. In the default.vrd file, corresponds to the publishByDefault attribute of the httpServices element. If the flag is cleared, then this is equivalent to the absence of an httpServices element in the default.vrd file or the presence of an httpServices element with
with the publishByDefault attribute set to false .

Table below checkbox Publish HTTP services by default contains a list of published HTTP services and allows you to manage the publication of each HTTP service. The first column controls the publication of a specific HTTP service. If the checkbox is cleared, this HTTP service will be prohibited from use (it cannot be called). In the default.vrd file, corresponds to the enable attribute of the service element.
The second column (named Name) contains the name of the HTTP service as it was specified during creation. A description of HTTP services is given in the book 1C:Enterprise 8.3. “Developer's Guide”. In the default.vrd file, corresponds to the name attribute of the service element.
HTTP services that are located in connected extensions are not displayed in this table and can only be published by manually editing the default.vrd file.

Publish extension HTTP services by default. Responsible for the ability to use HTTP services that are supplied in configuration extensions. In the default.vrd file, corresponds to the publishExtensionsByDefaul t attribute of the httpServices element

3.2.3. “Other” tab

Rice. 6. Other publishing options on a web server

On this tab you can change auxiliary publishing parameters.

Temporary files directory. Allows you to specify the directory of temporary files for running the web server extension or file version of the infobase. In the default.vrd file, corresponds to the temp attribute of the point element.

Connection pool group. Describes the pool element of the default.vrd file. Read more here. Also, the parameters of this group control the operation of the connection loss tracking system.

Debugging group. Describes the debug element of the default.vrd file.

OpenI D group. Describes the openid element of the default.vrd file.

Data separation. Describes the zones element of the default.vrd file. Let's take a closer look at the structure of a table with delimiters.

The table includes all independent delimiters that exist in the configuration or loaded file. The first column (without a name) determines whether to create a zone element for the selected separator. It should be remembered that element matching is performed not by the name of the separator, but by its ordinal position in the list. If the first separator is disabled, then it makes sense to disable all the others, since the parameters of the zones element will be applied by the system to other separators.
The Name column contains the name of the separator, as specified in the properties of the general attribute. The checkbox in the next column determines whether the separator value in the zone element will be set or not. If the checkbox is checked, then the value from the Value column will be used as the value of the value attribute.
The checkboxes in the Specify and Safe columns are responsible for the safe and specify attributes (respectively) of the zone element of the default.vrd file.
The Background jobs in the file version parameter describes the possibility of using background jobs in the file version of the infobase (the allowexecutescheduledjobs attribute of the root point element).

Briefly and succinctly, all the information necessary for administering 1C is: installation, updating, backup.

Stream format error 1 C - what to do

This article will explain the causes, types and methods of eliminating the “Stream Format Error” 1C.

How to clear the cache of a 1C Enterprise 8.3 server

If, after updating the configuration, your forms float, the report stops working, and error windows pop up, then most likely the problem can be solved by clearing the cache.

Software protection 1C

Services for ensuring protection and information security of databases and modules 1C: Enterprise 7.7 and 8, setting up 1C server protection. Protection of information in 1C from failures, hacking, copying at the software and hardware levels to ensure business resiliency

Enterprise server maintenance

Administration of Windows servers, including remotely or with on-site specialists. Professional, highly qualified service and configuration of Windows servers in St. Petersburg is our specialty. Sign a service agreement and get 4 services for free!

Database server configuration

Integrus specialists provide outsourced database server administration services. Proper configuration and administration of a database server is no less important for business than high-quality hardware and software. The main thing in administering database servers is the correct settings and organization of database storage. Proper organization of database servers allows employees to effectively manage and use information...

Cloud virtual PBX and 1C

Services for deploying a virtual PBX in an organization, connecting and setting up a cloud PBX and IP telephony, recommendations in choosing a provider, implementing the integration of a cloud PBX with CRM, 1C and other services.

Placing servers in a data center

To create a scalable and fault-tolerant IT infrastructure, an organization often needs its own data center, corporate data center or mini-data center. Offers a full cycle of turnkey construction of corporate data centers - from design to installation and maintenance.

As you know, with the release of 1C 8.3 configurations written entirely in managed forms, it became possible to publish these configurations on a web server.

Publishing 1C 8.3 on the IIS web server differs only in the installation of the server part.

Installing Apache Web Server

First you need to download the server distribution. It is located at http://www.apache.org. Download the latest version of the distribution for Windows and start the installation.

Click “Next” until the following window appears:

In the first two fields we will enter “localhost” (or 127.0.0.1). This means that the server will run on your local computer. In the third field, enter your email address; server responses will be sent to it.

It should be noted that Skype can also use port 80. Therefore, if you use it, disable port 80 in the settings.

Click “Next”.

In the next window, I suggest choosing a standard installation. This will install all the components necessary for operation.

We will also leave the installation directory as default. Click “Install”. The installation process will begin.

Get 267 video lessons on 1C for free:

After installation is complete, the server should start automatically. An icon will appear in the system tray. This means that the server has started successfully. If you double-click on this icon, the following window will open:

Publishing a web client and web services in 1C 8.3 (8.2) on the Apache server

The server is running. Now let's move on to the 1C program. Let's launch the Configurator.

In the Configurator, select the “Administration” menu, then “Publish on a web server”.

The settings required here are minimal. Basically everything should be defined by default.

You just need to select a directory, you can use any empty one. “Name” must be specified in Latin characters.

You can choose as you wish. You can turn it off completely. The main thing is to go to the HTTP services tab. Here you need to make the same settings as on the previous tab: