Today I will leave a small post-note about setting up 1C 8.3 in part of the access organization via the Web server 1C and IIS 8 service.

Previously, I gave access to 1C to the Terminal Server to users. Then I had Windows 2003 Server C 1C version 7 at work, there was a terminal server license where the terminal server was deployed. An article on setting up this good I also once wrote. Everything was rules, but now we have a new iron (based on Intel Xeon CPU E3-1220 V3, 8GB RAM), new 1C (V 8.3), new operating system (Windows Server 2012 R2).

From the beginning, our Accounting (8 PCs) worked on a network disk, but in this case the program works on the principle of downloading files over the network and it is sooo slowly. It was decided to find a way to speed up the work.

I thought about the terminal server, but I do not have a license to the terminal server (I did not find it on the Internet, and I said expensive to buy). The output was suggested by chance, it turns out to be 1C support for the Web server. Since experience with the same Apache I have and I know the principle of work, I decided to master the Web server 1C.

Installing and checking all components

Let's start setting up from the installation of the 1C Web server components. Check that we have installed the 1C web server module. If not installed.

We publish the database to the web server

We go to the database 1c in the configurator mode. Next, go to the menu "Administration" - "Publication on a web server"

We publish!

Exposing the rights to folders 1C

The next step is to set the rights to the following folders:

BIN folder in 1C.

Rights put on the screen below in the Security menu.

Connect to the web server from client computers

To do this, create a connection to the database 1c - write the connection name -\u003e Select on the web server -\u003e Next, as in the picture below:

After that, you will have a connection to 1C already through a web server.

Errors with whom met:

1C8.3 IIS "The potentially dangerous value of Request.path has been detected" received from the client

After setting up the 1s server's Web, I ran into a problem: I can log in in 1C, I log in, but all menus did not work, you could not open a single window except desktop 1C. Long batted until I found a solution in the internet.

What should be done:
1. Open IIS. Start - Perform - Find "IIS Service Manager"
2. Open our "site"
3. Go to the menu "Comparison of handlers"
4. Looking for Isapi-DLLand choose change.
5. Change the query path from "* .dll" to "*", executable file (you may have another version of 1C, please be attentive) - "C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.6.2390 \\ bin \\ wsisapi.dll. "
6. We save.

7. Check.

That's all. If you have questions, I will try to help.

Publication of databases "1C: Enterprises" 8.3 on the IIS web server in Microsoft Windows Server 2008/2012

In this article, I will describe the process of organizing web access to the databases "1C: Enterprise" 8.3 On the IIS web server (Internet Information Server) in the delivery of Microsoft Windows Server. For older versions "1C: Enterprise" ( 8.1 and 8.2 ) The database publication algorithm is generally similar. The IIS configuration algorithm to work "1C: Enterprise" will be considered, and the process of publishing databases on a web server is described as for 32-bitand for 64-bit Web server extension module.

1. What do you need

1. Computer meets minimal system requirements for the web server running one of the operating systems:
   • Microsoft Windows Server 2012 (R2)
   • Microsoft Windows Server 2008 (R2)
2. Local administrator rights on this computer.
3. Distribution for installation Component "1C: Enterprise". To configure a 64-bit web server extension module, distribution to install a 64-bit server "1C: Enterprise". This example uses version 8.3.4.389 . For older versions "1C: Enterprise" ( 8.1 and 8.2 ) The database publication algorithm is generally similar.

2. Installing IIS Web Server

Install the Internet Information Server web server, which is the default in the delivery of Microsoft Windows Server. When installing, we definitely select the components:

• Common Http Features (Common Http Features)
  • Static content (Static Content)
  • Default document (Default Document)
  • Directory Review (Directory Browsing)
  • HTTP Errors (HTTP Errors)
• Application Development (Application Development)
  • ASP.NET 3.5.
  • Extensibility.net 3.5 (.NET EXTENSIBILITY 3.5)
  • ISAPI Extensions (ISAPI Extensions)
  • ISAPI filters (ISAPI Filters)
• Correction and diagnostics (Health and Diagnostics)
  • HTTP logging (HTTP Logging)
  • Request Monitor (Request Monitor)
• Management Tools (Management Tools)
  • IIS Management Console (IIS Management Console)

In detail about the IIS web server deployment process:

• In Microsoft Windows Server 2012 (R2) -. IIS version 8, after installation, you should see the Default Web Site Page:

3. Installation of Component "1C: Enterprise"

To the same server where the IIS web server is deployed, install "1C: Enterprise" (32-bit components), be sure to select the component when installing:

• 1C: Enterprise
• Web Server Extensions Modules

If you plan to configure a 64-bit web server extension module, you must additionally launch the 64-bit server installation program from the corresponding delivery "1C: Enterprise" and install the component:

• Web Server Extension Module

4. Setting the operating system

Now you need to install the necessary rights to key folders used when working for web access to the databases "1C: Enterprise". For the storage directory of web site files published on the web server (default C: \\ inetpub \\ wwwroot \\) It is necessary to give full rights to the group " Users"(Users). In principle, this step can be skipped, but then to publish or change the database publication, you will need to run "1C: Enterprise" on behalf of the administrator. To configure the security of this directory, click on it with the right mouse button and select the context menu " Properties"(Properties).

In the properties window that opens, go to the " Safety"(Security) and press the button" Change"(Edit ...), to change the valid permissions. The permissions window will appear for this directory. In the list of groups or users (Groups or User Names), select the group " Users"(Users) and in the list of permissions for the selected group set the flag" Puty access"(Full Control). Then click " Apply"(Apply) To record changes and close all windows using the" button " OK».

Next, you need to give full rights to the directory with the installed files "1C: Enterprise" (default C: \\ Program Files (x86) \\ 1cv8 \\for a 32-bit expansion module and C: \\ Program Files \\ 1CV8 \\ for a 64-bit) group IIS_IUSRS.. To do this, we perform similar to the action described above, with the only difference that in order for the necessary group to appear in the list " Groups or users"(Groups or User Names) You must click on the button" Add"(Add ..), and in the group selection window or users click" Additionally"(Advanced ...).

Then press the button located on the right. Search"(Find Now), after which they choose the necessary group IIS_IUSRS. In the search results table and click " OK».

Group IIS_IUSRS. It will appear in the list of groups or users. Giving her full rights to the selected directory and click " Apply"(Apply) to save changes.

Well, finally, if the publication is executed for the file base, it is also necessary to give a group IIS_IUSRS. Full rights to the directory with the files of this information base.

5. Publication of the database on a web server

Go to directly publishing a database on a web server. To do this, launch "1C: Enterprise" in the configurator mode for the base you want to publish. Then select " Administration» — « Publication on a web server ...»

The Publishing Property Setup window opens on a web server. The main fields necessary for the publication are already filled with default:

• The name of the virtual directory - the name for which will occur to the database on the web server. It may consist only of the symbols of the Latin alphabet.
• Web server - selected from the list of web servers found on the current computer. In our case, this is Internet Information Services.
• Catalog is the physical location of the directory in which the virtual application files will be located.
• You can specify customer types to publish, as well as specify the possibility of publishing Web services. In the table below, you can edit the list of Web services that will be published as well as in the column " Address»Change the synonym for which it will appeal to this WEB service.
• Also, for the IIS web server, it is possible to specify the need to perform authentication on a web server using the OS tools by setting the appropriate flag.

By selecting the necessary publication settings click " Publish».

If the publication has passed without errors, see the appropriate message.

Publication on the IIS web server is always executed for the default website and for the default application pool. It is worth keeping in mind that when publishing a configurator, a 32-bit web server extension module will be registered, and the default application pool is registered - DefaultAppPool- Work without setting only with 64-bit applications. Accordingly, further actions depends on the bit of the web server expansion module, which is planned to be used. For a 32-bit web server extension module, you must allow the application pool to use 32-bit applications, or register a 64-bit web server extension module. This will be discussed below

6. Setting up IIS to use a 32-bit web server expansion module

Funds"(Tools) -" IIS service dispatcher

Default Web Site. - A virtual directory with the name is converted to the application, which we set when publishing a database. To complete the publication, it remains only to resolve 32-bit applications for the default application pool. To do this, let's move in the Connection Tree to Pools applications"(Application Pools).

In the list of application pools, find the pool named DefaultAppPool. I click on it with right mouse button and in the context menu select the item " Extra options"ADVANCED SETTINGS).

In the application pool parameters window that opens, in the group " General"(General) Find the item" 32-bit applications are allowed"(Enable 32-bit Applications) and set the value of the parameter to equal True.. Then save the changes by clicking " OK».

7. Setting up IIS to use a 64-bit web server extension module

Register a 64-bit web server extension module using a utility webinst.exe. Relevant version located in the catalog bin., Catalog with the installed program "1C: Enterprise", or use the method below.

Run IIS Manager (Internet Information Services (IIS) Manager). You can make it from the Server Manager (Server Manager) by selecting the item " Funds"(Tools) -" IIS service dispatcher"INTERNET INFORMATION SERVICES (IIS) MANAGER).

Here, by turning the tree in the connections window, we will see that for the default website - Default Web Site. - A virtual directory was converted to the application with the name that we set when publishing a database. To complete the publication, it remains only to specify this application to use a 64-bit query handler. To do this, open the handlers' mapping settings page for this virtual directory by selecting " Comparison of handlers"Handler Mappings) on the initial page of the application.

In the table of comparisons of processors, we find the handler "1C Web Service Extension". Open this handler by clicking 2 times on the corresponding line in the table.

We edit the handler, replacing the path to the 32-bit 32-bit web server expansion module, which is currently selected, on the path to the 64-bit version of the library. In this example, change the path C " C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.4.389 \\ bin \\ wsisapi.dll" on the " C: \\ Program Files \\ 1CV8 \\ 8.3.4.389 \\ Bin \\ wsisapi.dll"Taking advantage of the selection button. By changing the way click " OK»To save changes.

8. Connecting to a published information database through a web browser

Well, it seems to be all. For connections to just published database, run Internet Explorer, and in the address bar We enter the path of the view http: // localhost /<Имя публикации информационной базы> . In this example, it is http: // localhost / demoaccounting /.

You can also connect to this information database from any computer on the network by contacting the web server according to its internal (or if the port is procined 80 , on an external) IP address.

In this case, for the correct operation of "1C: Enterprise", the domain name for which the appeal (or IP address) must be added to the secure Internet Explorer nodes, and pop-up windows must be allowed for it. For more information about configuring Internet Explorer to work "1C: Enterprise" to work.

9. Connecting to a published information database through the client "1C: Enterprises"

The information base published on the web server can be connected with the help of a thin client "1C: Enterprises". To connect, open the startup window "1C: Enterprise" and click the " Add"To add an information base.

In the Add information database / group window, we set the switch to " Adding to the list of an existing information base"And click" Further».

We introduce the database name, as it will be displayed in the list of information bases (must be unique for this list), the type of location will choose " On a web server"And click" Further».

Indicate the startup parameters for the information base and click " Ready»To complete the wizard.

After that, this information base will appear in the list of the launch window of "1C: Enterprise". Note that the startup mode configurator is not available for this type of connection. Click " 1C: Enterprise»To connect to the information base.

After the release of the new 1c platforms (for example, already in 8.3.11.2867) on the 64-bit windows of Windows Apache version 2.0, 2.2, it stops working. There is a way out to go to 2.4. Its installation is somewhat more complicated than the usual - there are no installation files, so everything needs to be started and adjusted manually. Taking into account the fact that I was interested to use IIS, I decided to write an article at the same time.

1. For Windows X64, the 1C X64 distribution will be required (this also applies to both the server and client applications)
2. Installing IIS Web Server

Install Internet Information Server Web Server. When installing, we definitely select the components:

• Common Http Features (Common Http Features)
  • Static content (Static Content)
  • Default document (Default Document)
  • Directory Review (Directory Browsing)
  • HTTP Errors (HTTP Errors)
• Application Development (Application Development)
  • ASP.NET 3.5.
  • Extensibility.net 3.5 (.NET EXTENSIBILITY 3.5)
  • ISAPI Extensions (ISAPI Extensions)
  • ISAPI filters (ISAPI Filters)
• Correction and diagnostics (Health and Diagnostics)
  • HTTP logging (HTTP Logging)
  • Request Monitor (Request Monitor)
• Management Tools (Management Tools)
  • IIS Management Console (IIS Management Console)

4. Then we give the rights for users of IIS_IUSRS and IUSR on the folder:

• folders with the installed platform;
• folders with database publications;
• folders of the databases themselves (in the case of a file version).

6. Setting up IIS to use a 32-bit web server extension module

Funds"(Tools) -" IIS service dispatcher

Default Web Site. - A virtual directory with the name is converted to the application, which we set when publishing a database. To complete the publication, it remains only to resolve 32-bit applications for the default application pool. To do this, let's move in the Connection Tree to Pools applications"(Application Pools).

In the list of application pools, find the pool named DefaultAppPool. I click on it with right mouse button and in the context menu select the item " Extra options"ADVANCED SETTINGS).

In the application pool parameters window that opens, in the group " General"(General) Find the item" 32-bit applications are allowed"(Enable 32-bit Applications) and set the value of the parameter to equal True.. Then save the changes by clicking " OK».

7. Setting up IIS to use a 64x discharge web server extension module

Register a 64-bit web server extension module using a utility webinst.exe. Relevant version located in the catalog bin., Catalog with the installed program "1C: Enterprise", or use the method below.

Run IIS Manager (Internet Information Services (IIS) Manager). You can make it from the Server Manager (Server Manager) by selecting the item " Funds"(Tools) -" IIS service dispatcher"INTERNET INFORMATION SERVICES (IIS) MANAGER).

Here, by turning the tree in the connections window, we will see that for the default website - Default Web Site. - A virtual directory was converted to the application with the name that we set when publishing a database. To complete the publication, it remains only to specify this application to use a 64-bit query handler. To do this, open the handlers' mapping settings page for this virtual directory by selecting " Comparison of handlers"Handler Mappings) on the initial page of the application.

In the table matching table, find the 1C Web Service Extension handler. Open this handler by clicking 2 times on the corresponding line in the table.

We edit the handler, replacing the path to the 32-bit 32-bit web server expansion module, which is currently selected, on the path to the 64-bit version of the library. In this example, change the path C " C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.? ?? \\ bin \\ wsisapi.dll" on the " C: \\ Program Files \\ 1CV8 \\ 8.3.? ??? \\ bin \\ wsisapi.dll"Taking advantage of the selection button. By changing the way click " OK»To save changes.

Large corporations using 1C software products in their remote branches are often faced with the problem of the absence of the possibility of installing 1C in separate employee jobs. Sometimes outdated computers can be the cause of this, sometimes remoteness, sometimes the absence of IT staff. The 1C developers solved this problem in the platform version 8.2, integrating a special web client in it. The organization of work in this form of the client will significantly save on the upgrades of computers and the content of administrators 1C.

Externally, the web client does not differ from a thin client, except that the 1C interface opens in the browser. To launch Web Customers 1C need a web server publication and the availability of the Internet at workplaces. For the connection of the database and user interface of the web client, the web server and DHTML and HttpRequest technologies are responsible. At the time of work, the data is transmitted via HTTP to the web server, compiled, and directly execution occurs on the client side, in the Internet browser environment.

Sufficient popularity of the 1C Web Customer Mode is explained by the list of benefits:

• Lack of need to set the client part 1c in the workplace;
• Ensuring 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 worldwide network;
• Technical simplicity, as you just need to start the browser and correctly dial the address;
• Special data exchange mode with a web server at low Internet speed.

In addition, the web client mode has certain disadvantages:

1. Web server vulnerability that becomes affordable anywhere in the world;
2. Certain limitations on the exchange of data and operation of the file system;
3. Availability only for configurations using a managed application type and a subtle client;
4. Inaccessibility of local licenses.

If you firmly decided that the Web client 1C is great for users, then you will have to configure and publish a web server. As an example, consider setting up the standard IIS embedded in Windows.

If your computer is installed on your computer, you can do without third-party programs. This will help you with a built-in IIS server, to configure a fairly initial knowledge of the system. It should be noted that the installation of the server on a weak computer will make it difficult to launch Web customers 1C and the performance of the entire system will be threatened. 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 the server setting, go to "Control Panel" -\u003e "Programs and Components" -\u003e "Enable or Disable Components". Find the Branch of IIS / Internet Service and Slip the following daws in the tree.

• In the "Common HTTP" section:
  • "View directory";
  • "Default document";
  • "Static content";
  • "HTTP errors."
• "Checking performance and diagnostics":
  • "HTTP Magazine";
  • "Query Monitor".
• "Application Development Components":
  • "ASP";
  • "ASP.NET";
  • "ISAPI extension";
  • "Extensibility.net";
  • ISAPI filters.
• "Management tools":
  • "IIS Management Console".

To publish a configured server, you must install the 1C Web Server Expansion Modules. To do this, during the 1C installation process, you must mark the corresponding item in the installation of the installation method and install the components. Then run 1c in the configurator mode with administrative rights and click on the "Administration" menu -\u003e "Publication on the web server ...". The 1c platform will independently detect a configured web server, and you will only need to set the name of the base and its location.

After you click the "Publish" button, the server must be restarted. Now you can check the execution of the work, making the web client to 1C, speaking in the browser the string: "http: imaging / name". It is necessary to envisage that all users have access to the location of the database for reading and writing. Otherwise, the 1c web client configuration at the workplaces will not give results.

Web client 1C is a convenient tool for users, the performance of the jobs of which leaves much to be desired. Thanks to a simple setup, minimal differences in the application interface and the list of various advantages, the web client won some popularity in companies of various caliber.