Today I’ll leave a short post about setting up 1C 8.3 in terms of organizing access through the 1C WEB server and IIS 8 services.

Previously, I gave users access to 1C using the terminal server the old fashioned way. Then at my work I had a Windows 2003 server with 1C version 7, I had a terminal server license where the terminal server was deployed. I also once wrote an article on setting up this goodness. Everything was normal, but now we have new hardware (based on Intel Xeon CPU E3-1220 v3, 8gb of RAM), new 1C (v 8.3), new operating system (Windows Server 2012 r2).

From the beginning, our accounting department (8 PCs) worked on a network drive, but in this case the program works on the principle of uploading files over the network and it is very slow. It was decided to find a way to speed up the work.

I thought about a terminal server, but I don’t have a license for a terminal server (I couldn’t find it on the Internet, but they said it was expensive to buy). The solution was suggested by chance, it turns out that 1C has support for WEB server. Since I have experience with the same Apache and I know the principle of operation, I decided to master the 1C WEB server.

Installation and testing of all components

Let's start the setup by installing the 1C Web server components. Let's check that we have the 1C web server extension module installed. If not installed, install it.

Publish the database to the web server

We go into the 1C database in configurator mode. Next we go to the menu “Administration” - “Publishing on a Web Server”

Let's publish!

Setting permissions for 1C folders

The next step is to set permissions on the following folders:

Bin folder in 1C.

We set the rights as in the screenshot below in the security menu.

Connecting to the web server from client computers

To do this, create a connection to the 1C database - Write the name of the connection -> select On the web server -> then as in the picture below:

After this, you will be able to connect to 1C through the web server.

Errors I encountered:

1C8.3 IIS "Potentially dangerous Request.Path value detected" received from client

After setting up the 1C Web server, I encountered a problem: I can log into 1C via IP, I log in, but all the menus did not work, I could not open a single window except the 1C desktop. I struggled for a long time until I found a solution on the Internet.

What should be done:
1. Open IIS. Start - Run - find “IIS Service Manager”
2. Open our “site”
3. Go to the menu "Handler Mappings"
4. We are looking ISAPI-dll, and select change.
5. Change the request path from “*.dll” to “*”, Executable file (you may have a different version of 1C, please be more careful) - “C:\Program Files (x86)\1cv8\ 8.3.6.2390 \bin\wsisapi.dll".
6. Save.

7. Check.

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

Although 1C does not recommend using a web server in file mode (but only in server mode) - nevertheless, for small enterprises with 2-3 accountants, using a web server on new configurations with “managed forms” (Accounting 3.0, Salary 3.0, etc.) - allows you to organize fairly fast access to a database of network computers, even if they are essentially old junk. It is only important that the main computer with the databases and web server is decent (for example, Core I3, 8 GB of RAM and an SSD drive).

Step-by-step guide to setting up a 1C web server on Apache (including the file version of the database)

1. Download the Apache installer

For some reason, Apache stopped releasing all new versions (for example 2.4.25) as a self-extracting distribution. It is quite acceptable for us to use a non-latest distribution, 2.2.25, which allows us to get a convenient installer and avoid additional manipulations.

Please note that it is convenient for us to use the *.msi installer

Based on the user's recommendation (thanks, Vladimir), I am posting a link to Apache version 2.4 (www.apachelounge.com). Also from his words - if you download x64, then be prepared to install a similar x64 1c platform and edit the line LoadModule _1cws_module "C:/Program Files/1cv8/8.3.9.2016/bin/wsap24.dll" in httpd.conf.
But I myself do not recommend using 64-bit 1C, because, with a high degree of probability, enormous difficulties will arise when connecting commercial equipment, or some other third-party libraries.

We select the “no ssl” distribution if the databases will be opened only within our local network or the “ssl” distribution if the database will be opened on the Internet. You can read more about setting up ssl in the infostart article

In our example, we will configure a server without ssl for use only within the local network.

2. Run the downloaded installer

Fill in Network Domain: Localhost, Server name: Localhost

Press NEXT, Setup type: Typical NEXT, NEXT, INSTALL

3. Check if the web server has started

To do this, open any browser and specify the page address http://localhost

We should see a page that says It Works!

Let's find out the IP address of our computer on the local network. To do this, in the lower right corner (next to the clock) we find the local network icon, right-click on it and open “Network and Sharing Center”

Choose our network

And click the "Details" button

In my case, the computer address on the local network is 192.168.0.189

Now we return to the browser and check the availability of the It Works page at the IP address http://192.168.0.189 (in your case the numbers will be different)

If you see the familiar It Works page again, everything is fine,

4. Check the accessibility of the page from other computers and configure the firewall

Again we try to open the familiar page http://192.168.0.189 (your numbers are different) but from any other computer on the local network.

If, instead of a familiar page, you see “Cannot access the site” or a similar message, let’s configure the firewall. To do this, return to the computer where Apache is installed, go to “Control Panel” - “System and Security” - “Windows Firewall” and on the left side of the screen click on “Advanced settings”

Click on the “Rules for incoming connections” section, then on the right side of the window “Create a rule”

Check all three boxes

Specify an arbitrary name, for example “Web server port 80 for 1C”. Ready.

Again we go to other computers and make sure that now the browser shows the page we are familiar with at the IP address http://192.168.0.189 It Works

5. We publish our database on the web server.

Open our database configurator (Run 1C as administrator)

Publishing 1C:Enterprise 8.3 databases on the IIS web server in Microsoft Windows Server 2008/2012

In this article I will describe in detail the process of organizing web access to 1C:Enterprise databases 8.3 on the IIS (Internet Information Server) web server included with Microsoft Windows Server. For older versions of 1C:Enterprise ( 8.1 And 8.2 ) the algorithm for publishing databases is generally similar. The algorithm for setting up IIS for 1C:Enterprise will be discussed, and the process of publishing databases on a web server will also be described for both 32-bit, and for 64-bit web server extension module.

1. What you will need

1. A computer that meets the minimum system requirements for running a 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 kit for installing 1C:Enterprise components. To configure a 64-bit web server extension module, a distribution kit for installing a 64-bit 1C:Enterprise server. This example uses the version 8.3.4.389 . For older versions of 1C:Enterprise ( 8.1 And 8.2 ) the algorithm for publishing databases is generally similar.

2. Installing the IIS web server

We install the Internet Information Server web server, which is included by default with Microsoft Windows Server. When installing, be sure to select the components:

• Common HTTP Features
  • Static Content
  • Default Document
  • Directory Browsing
  • HTTP Errors
• Application Development
  • ASP.NET 3.5
  • .NET Extensibility 3.5
  • ISAPI Extensions
  • ISAPI Filters
• Health and Diagnostics
  • HTTP Logging
  • Request Monitor
• Management Tools
  • IIS Management Console

I wrote in detail about the process of deploying an IIS web server:

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

3. Installation of 1C:Enterprise components

On the same server where the IIS web server is deployed, we install 1C:Enterprise (32-bit components), making sure to select the components during installation:

• 1C:Enterprise
• Web server extension modules

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

• Web server extension module

4. Setting up the operating system

Now you need to set the necessary rights to the key folders used when using web access to 1C:Enterprise databases. For the storage directory for website files published on the web server (default C:\inetpub\wwwroot\) you need to give full rights to the group " Users"(Users). In principle, you can skip this step, but then to publish or change the publication of the database you will need to run 1C:Enterprise as an administrator. To configure the security of this directory, right-click on it and select “ Properties"(Properties).

In the properties window that opens, go to the “ Safety" (Security) and press the button " Change» (Edit...), to change existing permissions. The permissions window for this directory will appear. In the list of Groups or user names, select the group “ Users" (Users) and in the list of permissions for the selected group set the flag " Full 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 installed 1C:Enterprise files (by default C:\Program Files (x86)\1cv8\ for 32-bit expansion module and C:\Program Files\1cv8\ for 64-bit) group IIS_IUSRS. To do this, we perform actions similar to those described above, with the only difference that in order for the required group to appear in the list “ Groups or users" (Groups or user names) you must click the button located under the list " Add"(Add..), and in the window for selecting groups or users, click " Additionally"(Advanced...).

Then click the button on the right " Search"(Find Now), then select the required group IIS_IUSRS in the search results table and click “ OK».

Group IIS_IUSRS appears in the list of groups or users. We give it full rights to the selected directory and click “ Apply» (Apply) to save changes.

And finally, if publishing is performed for a file database, you must also give the group IIS_IUSRS full rights to the directory containing the files of this infobase.

5. Publishing the database on a web server

Let's move on to directly publishing the database on the web server. To do this, launch 1C:Enterprise in Configurator mode for the database that you want to publish. Then select “ Administration» — « Publishing to a web server...»

The window for setting up publishing properties on the web server will open. The main fields required for publication are already filled in by default:

• Virtual directory name - the name by which the database on the web server will be accessed. Can only consist of characters 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.
• Directory - The physical location of the directory in which the virtual application files will be located.
• Using the corresponding flags, you can specify the types of clients to publish, as well as indicate 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 by which this Web service will be accessed.
• It is also possible for the IIS web server to indicate the need to perform authentication on the web server using OS means by setting the appropriate flag.

Having selected the necessary publishing settings, click “ Publish».

If the publication went through without errors, we will see a corresponding message.

Publishing to the IIS web server is always done for the default website and the default application pool. It is worth keeping in mind that when publishing from the configurator, the 32-bit web server extension module will be registered, and the default application pool will be DefaultAppPool- Without configuration, it only works with 64-bit applications. Accordingly, further actions depend on the bitness of the web server extension module that you plan to use. For a 32-bit web server extension, you must enable the application pool to use 32-bit applications, or register a 64-bit web server extension. This will be discussed below

6. Configure IIS to use the 32-bit Web Server Extension Plug-in

Facilities"(Tools) - " Internet Information Services Manager

Default Web Site— a virtual directory transformed into an application appeared with the name that we specified when publishing the database. The only thing left to complete publishing is to enable 32-bit applications for the default application pool. To do this, go to the “ tab in the connection tree Application Pools"(Application Pools).

In the list of application pools we find a pool with the name DefaultAppPool. Right-click on it and select “ Extra options"(Advanced Settings).

In the application pool settings window that opens, in the group “ Are common"(General) find the item " 32-bit applications allowed» (Enable 32-Bit Applications) and set the parameter value to True. Then save the changes by clicking " OK».

7. Configure IIS to use the 64-bit Web Server Extension Plug-in

You can register the 64-bit web server extension module using the utility webinst.exe the corresponding version located in the directory bin, directory with the 1C:Enterprise program installed, or use the method below.

Let's launch Internet Information Services (IIS) Manager. This can be done from the Server Manager by selecting the “ Facilities"(Tools) - " Internet Information Services Manager» (Internet Information Services (IIS) Manager).

Here, expanding the tree in the connections window, we will see that for the default website - Default Web Site— a virtual directory transformed into an application appeared with the name we specified when publishing the database. To complete publishing, all that remains is to tell the application to use a 64-bit request processor. To do this, open the handler mapping settings page for this virtual directory by selecting “ Handler Mapping» (Handler Mappings) on the application home page.

In the table of handler comparisons we find the handler "1C Web-service Extension". Let's open this handler by double-clicking on the corresponding row in the table.

Let's edit the handler by replacing the path to the executable dll of the 32-bit web server extension module that is currently selected with the path to the 64-bit version of the library. In this example, we change the path from " C:\Program Files (x86)\1cv8\8.3.4.389\bin\wsisapi.dll" on " C:\Program Files\1cv8\8.3.4.389\bin\wsisapi.dll» using the selection button. After changing the path, click " OK» to save changes.

8. Connect to a published infobase via a web browser

Well, that seems to be all. To connect to a newly published database, launch Internet Explorer and enter a path like this in the address bar http://localhost/<Имя публикации информационной базы> . In this example it is http://localhost/DemoAccounting/.

You can also connect to this information base from any computer on the network by accessing the web server via its internal one (or if the port is forwarded 80 , by external) IP address.

In this case, for 1C:Enterprise to work correctly, the domain name being accessed (or IP address) must be added to trusted Internet Explorer sites, and pop-up windows must be allowed for it. Read more about setting up Internet Explorer for the 1C:Enterprise web client.

9. Connecting to a published information base through the 1C:Enterprise client

You can also connect to an information base published on a web server using the 1C:Enterprise thin client. To connect, open the “1C:Enterprise” launch window and click the “ Add» to add an information base.

In the window for adding an infobase/group, set the switch to “ Adding an existing infobase to the list" and click " Further».

Enter the name of the database as it will be displayed in the list of infobases (must be unique for this list), select the location type " On the web server" and click " Further».

Specify the launch parameters for the infobase and click “ Ready» to complete the wizard.

After which this information base will appear in the list of databases in the 1C:Enterprise launch window. Please note that the Configurator launch mode is not available for this type of connection. Click " 1C:Enterprise» to connect to the information base.

You can reduce system requirements for user machines as much as possible and make full use of the capabilities implemented in you by publishing 1C on a web server. This will allow you to organize work with the database not only using a thin client, but also using any browser, without installing additional components and applications.

Primary requirements

The minimum system requirements for the server side of the architecture can vary significantly and are highly dependent on:

1. Problems solved by the program;
2. Intensity of document flow;
3. Number of simultaneously connected users;
4. The size and number of published and registered databases.

However, it is simply impossible to do without two things when publishing 1C on a web server:

• A web server deployed in the system;
• An installed and running expansion module supplied by 1C.

Web server

This element of our structure can be either the Internet Information Server (IIS), supplied as part of operating systems from Microsoft, or the Apache server. Of course, there are paid analogues of these solutions, but we won’t talk about them.

An additional advantage of Apache products is the ability to run them from Linux-like operating systems.

We will consider the option with IIS, because... it does not require searching for and installing third party products.

Web server extension modules

Installation of these modules can be done by running the platform delivery file. Having reached the window, the appearance of which is shown in Fig. 1, you need to activate the installation of the corresponding component.

Naturally, in addition to the extensions, the 1C Enterprise platform itself must be installed on the computer, otherwise we will not have access to the Configurator, through which the main part of the publication is performed.

Having decided on the tools, let's move on to configuration.

Installing and starting a Web server

In order to start IIS on a computer with Windows installed, you need to perform the following sequence of actions (using Windows 7 as an example):

Fig.3

You can make sure that the web server is working by entering a line like “http://localhost” in the address bar of any browser and receiving a picture as in Fig. 4.

Fig.4

Fig.6.

In some cases (in particular, if the program operates in a 64-bit operating system), after publishing the database on the server, it may be necessary to further configure the work with the libraries used by the 1C platform. This can be done from the Sites submenu.

Having selected a specific, just published database in the list, you need to activate the “Handler Matching” utility (Fig. 7).
Fig.7

In our case, we will need to establish a correspondence between ISAPI-dll and the wsisapi.dll executable file located in the BIN folder of the installed version of the platform.

In principle, at this point the main part of the work with the server can be considered completed, let’s move on directly to publishing the database.

Publishing the database to the server

Setting up user rights

Having received the above window, we proceed to setting up access rules for users.

We need to allow full access to the IIS_USERS user:

• To the folder “C:\inetpub\wwwroot\Publication name”, where the resource is stored;
• To the folder with the version of the program in use, where the wsisapi.dll library is stored;
• To the place where the database is stored.

Having completed the above steps, we can check the functionality of our publication by entering a line like “localhoct/Publication name” in the browser window and finding a user identification form there.

Modern conditions, with the widespread use of mobile devices and accessible Internet, places new demands on the information systems of even small companies. If just a few years ago remote access was the lot of large organizations, today the ability to access information from anywhere is taken for granted. Today we will tell you how to quickly and cost-effectively organize web access to 1C:Enterprise databases working in file mode.

The traditional scheme for working with 1C:Enterprise in file mode implies shared access to infobase files via the SMB protocol (Microsoft network). In this case, one of the computers acts as a file server, while the others work with a publicly available information base.

However, this scheme has a number of significant drawbacks. The speed of operation is significantly influenced by both network bandwidth and the computing power of client computers. We discussed this issue in more detail in our material. This is especially true after the transition to managed application-based configurations, which are much more resource-demanding than previous generation configurations.

The issue with remote access is also acute; if it is still possible to organize remote access for remote computers via RDP, which, by the way, is not always available for small companies that do not have a dedicated server, then with mobile devices everything is quite sad.

At the same time, the managed application provides new features, such as web access to the infobase, including those working in file mode. This allows you to qualitatively change the way you work with the information system with virtually no additional costs.

On the computer with the infobase, an additional role is assigned to the web server on which the infobase is published. After which you can continue to work with it both in file mode and in web server mode.

In this case, it is not necessary to use a browser to operate; the platform can also access the database via a web server in thin client mode. This feature allows you to organize access not only for remote and mobile clients, but also improve work on insufficiently productive machines in the office, since all basic calculations will be performed on the server side and traffic transmitted over the network will be minimized, as will the load on the client’s computer .

And, of course, there are almost unlimited possibilities for remote access to the database: from anywhere, from any device, using a browser.

Below we will look at possible configurations for organizing web access to small databases running in file mode on client operating systems.

Currently, two main web servers are supported: Apache and IIS, and the platform must be installed on the machine with the web server and web server extension modules. You can always install them additionally by simply running the platform installation program again:

Windows and IIS

Internet Information Services (IIS) for unknown reasons is not popular among administrators and 1C users. But in vain, ignoring a standard solution in favor of some third-party software, even if it’s good, looks at least strange.

To install IIS on the client OS, in our case Windows 7 x64, go to Control Panel - Programs and Features - Turn Windows features on or off.

In the window that opens, select Internet Information Services, then expand the list and go to Internet Services - Application Development Components and check the box opposite ISAPI extensions, other parameters can be left as default.

After installing IIS, let's move on to setting it up, to do this, open Control Panel - Administrative Tools - Internet Information Services Manager.

In the tree on the left select Application Pools, right-click on DefaultAppPool - Additional parameters and allow 32-bit applications by setting the appropriate option in True.

Now let’s set the necessary rights for groups IUSR And IIS_IUSRS. We grant rights to the folder with the infobase Change And Read and execute:

To folder bin platforms - Read and Execute:

Then we launch 1C:Enterprise as an administrator and load the required infobase into configurator mode.

On the menu Administration choose Publishing to a web server. 1C:Enterprise will automatically detect the web server (IIS) and offer to place the web application in the root of the web server in a directory with the name of the infobase folder, which will also be the name of the publication; you can change these parameters if necessary.

Ready! To access the database we can use an address like http://host_name(address)/publication_name, in our case http://192.168.3.109/Acc30, launch the browser and check the work.

You can also configure the database to work with it through the platform; to do this, in the dialog for adding a new infobase, specify the location on the web server:

The next step is to enter the connection address:

After launching the infobase, you can make sure that it is running in web server mode and not in file mode:

Windows and Apache 2.2

If for some reason you do not want to use IIS, you can configure 1C to work with another popular Apache web server. Unfortunately, the Apache developers have stopped publishing binary assemblies for Windows, offering to contact their partners, so let’s go to the Apache Haus website and download the assembly 2.2.x x86 architecture, even if you have a 64-bit operating system.

Attention! To obtain the Apache build, you should use only reliable sources that are listed on the project website. The security of your web server and your data depends on it!

You will also need to install the Microsoft Visual C++ 2008 Redistributable Package, which is required for the Apache build to work properly.

Then unpack the downloaded Apache archive into an arbitrary directory, for example, C:\Apache22, from all the many folders we are interested in the folders bin And htdocs, the first contains the web server executable files, the second should contain the web content.

Open a command prompt with administrator rights and go to the directory bin web server:

Cd C:\Apache22\bin

Now let's install Apache as a service:

Httpd -k install

We do not pay attention to the warnings; for purposes of use with 1C, the default Apache configuration is suitable.

Since the service runs on behalf of the system account, there is no need to set rights to the folders with the database and platform.

Then, in the same way, we launch 1C as an administrator in configurator mode and proceed to publishing on the web server. Unlike IIS, in this case the platform itself cannot specify the path and create a folder, so we do it manually. The folder must be created inside the directory htdocs and its name must match the publication name:

In our case it is C:\Apache22\htdocs\Acc30\ By the way, you can create the desired directory directly in the folder selection dialog. Then we publish the information base.

The next point is that 1C does not know how to restart this Apache build, so we’ll do it manually through the snap-in Services:

After restarting the web server, the published database will become available at the same address as in the case of IIS, and working with it will be no different.

• Tags:

Please enable JavaScript to view the