1c web server is used for. Setting up web servers to work with 1C: Enterprise. Publishing Settings in IIS Manager
31/05/2016
Configuring the Microsoft Internet Information Services (IIS) web server to work with 1C: Enterprise platforms
General information about publications
As you know, the publication of 1C databases can be carried out both from the configurator and using the webinst utility. The publication algorithm is described in more detail on the ITS, for example, at this link.
It should be noted that publishing for a 64-bit server is possible only from the configurator in Linux OS or using the webinst utility. In some of our load tests, 64-bit IIS web servers performed slightly better, so unless there are other restrictions, we recommend using them.
If you plan to use a 32-bit IIS web server, then do not forget to enable the launch of 32-bit applications: in the “Application Pools” list, for each required pool, right-click, in context menu select " Extra options... ”(“ Advanced Settings ”), then set“ Enable 32-bit Applications ”to“ True ”.
The documentation also describes several important points regarding working with the IIS web server. To quote them: when publishing to an IIS web server, remember that:
- Publishing is always done for the Default Web Site.
- Publishing is always done to the default application pool (DefaultAppPool).
- .NET support must be disabled for the application pool used for 1C: Enterprise operation. To do this, set the application pool property "Environment Versions." NET Framework"(" .NET Framework Version ") to" No Managed Code ".
The information on the first two points is important in itself, and especially in the context of the issue under consideration, since it will be useful to us in the future. The third recommendation, in our experience, is not required and the IIS web server works successfully in the use mode of the version, for example, .NET Framework v4.
Configuring IIS for different versions of the 1C platform
In order to use several web server plug-ins, which differ only in the third and fourth digits of the version, it is necessary to use different application pools (this is not possible within the same application pool). Accordingly, as many application pools must be created in the web server as there are different versions of plugins to be used, and then each virtual application must be manually linked to the desired application pool.
So, for example, let's create two additional application pools (in the general case, there may be more of them), for convenience we will indicate in the pool name the version of the platform with which we plan to use them (we indicated the version in abbreviated form - "8.3.6", but it may be more convenient for you use full version, for example, "8.3.6.2237", or generally divide application pools according to the application criterion, for example, "test cluster pool"). Let's set the recommended parameters (the version of the environment, the sign of using 32-bit applications). As a result, you should see the following list of IIS web server application pools:
Next, launch the configurator (do not forget to perform this action on behalf of the administrator) and publish. As indicated in the documentation, a new site entry appears (or is updated if the publication has already been performed before) in the "Default Web Site" group. The additional parameters for this publication will specify the default application pool, "DefaultAppPool". To change it, you can call the "Additional parameters ..." or "Basic settings ..." dialog. We call the main ones:
We replace the default application pool ("DefaultAppPool") with the application pool corresponding to the version of the 1C platform of the published database ("AppPool 1C 8.3.6" or "AppPool 1C 8.3.7").
If you need to change the handler for web server extensions (for example, after publishing from the configurator from 32-bit to 64-bit), we can do it here:
We proceed in the same way for another infobase and another version of the 1C platform.
This completes all the necessary settings! We check and enjoy the simultaneous work with 1C web applications different versions within one web server:
Conclusion
In the article, we described a method that allows you to use multiple publications information bases within one IIS web server for 1C: Enterprise infobases of different versions. This is necessary if you work on a server with several working or test bases for which the versions of the 1C platform used differ.
We hope you can easily complete the task you need and continue to enjoy using 1C products. Well, if something doesn't work out for you, or you run into some difficulties, we will definitely help!
In order for a website to appear on the Internet, it must be hosted on a server connected to the network and having an IP address. The server is a computer on which a special softwarewhich in turn is also called a web server. Exists a large number of web servers, and the most popular of these is Apache.
Apache is a full-featured, open source, extensible web server that meets almost all of the needs of modern web development. Apache is cross-platform, i.e. supports many operating systems - Microsoft Windows, Linux, BSD, Mac OS, Novell NetWare, BeOS. Its main functions are: support for the http protocol, the ability to connect external modules, the use of a DBMS for user authentication and processing of configuration files.
Fig. 1 Apache functions
Before Apache is configured for 1C and the publication itself on the web apache server base 1C, you need to download it. There are no binary assemblies for Windows now, which means that we download an earlier version for example - 2.2.25, using the search.
Fig. 2
Run the downloaded file and follow the installation.
Fig. 3
Fig. 4
Fig. 5
Next, we indicate information about our server. If the server is in the local network, and the enterprise does not have its own domain, we indicate any information, and the server name is Localhost, which means that the server will work on local computer... In the next field, fill in the address email, to which server responses will come (we have an arbitrary one, for example).
We choose one of two settings: Apache will start automatically or manually, only for the current user. Let's leave the recommended settings.
Fig. 6
For combined use with the 1C program, the recommended installation of the Apache configuration is sufficient.
Fig. 7
Fig. 8
Fig. 9
Fig. 10
After the installation is complete, the server starts working automatically. The program icon will appear at the bottom of the panel.
Fig. 11
The easiest way to check if our web server is working is to open any browser and specify http: // localhost in the address bar.
In the window we should see the message “It works!”.
Fig. 12
(localhost) is a computer on computer networks, a standard, officially reserved domain name for private IP addresses. Recall that when installing Apache, we specified it in the "Server Name" field.
Fig. 13
The second way to determine the health of our web server is by IP address.
Let's define the IP-address of our PC in the LAN. Clicking in the left corner on the "Network" icon, go to the "Network and Sharing Center" menu.
Fig. 14
In the window that opens, select the item "Wireless network connection", ie. our network, and in the window that appears, click the "Details" button. There we see the IP address of our computer on the network. In our case - 192.168.0.102.
Fig. 15
To check the operation of the web server, open any browser and enter - htpp: //192.168.0.102. If we see the inscription “It works!” In the browser window again, everything works.
Fig. 16
If you open it from another PC in the LAN, the result should be the same.
Open 1C: Enterprise in the configurator as administrator and load the required infobase.
Fig. 17
In the "Administration" select the function we need.
Fig. 18
If a window appears:
Fig. 19
... you need to install the web service extension modules.
To do this, go to the "Control Panel-Programs and Features", find "1C: Enterprise" and click "Change".
Fig. 20
Select "Web Service Extension Modules" and click "Next" until we get to "Finish".
Fig. 21
Fig. 23
In the window that opens, specify the name, select the web server (the program automatically saw the installed Apache) and an arbitrary folder for publication (the folder name must be written in Latin letters).
After the release of new 1C platforms (for example, already in 8.3.11.2867) on 64-bit Windows systems, Apache version 2.0, 2.2 stops working. There is a way out to go to 2.4. Its installation is somewhat more complicated than the usual one - there are no installation files, so everything needs to be started and configured manually. Considering that I was interested in using IIS, I decided to write an article at the same time.
- For Windows x64, you will need a 1C x64 distribution kit (this applies to both the server and client applications)
- Installing the IIS web server
Install the Internet Information Server web 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
- Correction and diagnosis (Health and Diagnostics)
- HTTP Logging
- Request Monitor
- Management Tools
- IIS Management Console
4. Then we give the rights for the IIS_IUSRS and IUSR users to the folders:
- folders with the installed platform;
- folders with database publications;
- the folders of the databases themselves (in the case of the file version).
6. Configuring IIS to Use the 32-Bit Web Server Extension
Facilities"(Tools) -" Internet Information Services (IIS) Manager
Default Web Site - a virtual directory converted into an application appeared with the name that we specified when publishing the database. All that remains to complete publishing is to enable 32-bit apps for the default app pool. To do this, go to the " Application pools"(Application Pools).
In the list of application pools, find a pool named DefaultAppPool... Click on it right click mouse and in the context menu select the item " Extra options"(Advanced Settings).
In the opened application pool settings window, 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 we save the changes by clicking " OK».
7. Configuring IIS to Use the 64-Bit Web Server Extension
You can register the 64-bit Web Server Expansion Module using the utility webinst.exe the corresponding version located in the directory bin, directory with installed program "1C: Enterprise", or use the method below.
Let's start the Internet Information Services (IIS) Manager. This can be done from the Server Manager by selecting the item " Facilities"(Tools) -" Internet Information Services (IIS) 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 converted into an application appeared with the name that we set when publishing the database. To complete the publication, it remains only to indicate this application use a 64-bit request handler. To do this, open the page for configuring the mapping of handlers for this virtual directory by selecting the item " Handler mapping"(Handler Mappings) on the application start page.
In the table of handler mappings, we will find the "1C Web-service Extension" handler. 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 that is selected in this momentto the path to the 64-bit version of the library. IN this example change path c " C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.?. ?? \\ bin \\ wsisapi.dll" on " C: \\ Program Files \\ 1cv8 \\ 8.3.?. ??? \\ bin \\ wsisapi.dll»Using the selection button. Changing the path, click " OK»To save changes.
Today I will leave a small post-note about setting up 1C 8.3 in terms of organizing access through the 1C WEB server and IIS 8 services.
I used to give access to users to 1C by means of a terminal server in the old fashioned way. Then I had a Windows 2003 server with 1C version 7 at my work, I had a terminal server license, where the terminal server was deployed. I also once wrote an article on setting up this good,. Everything was normal, but now we have new hardware (on intel based Xeon CPU E3-1220 v3, 8gb RAM), new 1C (v 8.3), new operating system (WIndows Server 2012 r2).
From the beginning, our accounting department (8 pc) worked on a network drive, but in this case the program works on the principle of downloading files over the network and it is sooo slow. It was decided to find a way to speed up the work.
I thought about a terminal server, but I do not have a license for a terminal server (I did not find it on the Internet, but they said it was expensive to buy). The way out was suggested by chance, it turns out that 1C has support for the 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.
Install and check all components
Let's start the setup by installing the 1C components Web server... Let's check that we have installed the 1C web server extension module. If not installed, install.
We publish the database to the web server
We go to the 1C database in the configurator mode. Next, go to the menu "Administration" - "Web Server Publishing"
We publish!
We set the rights to folders 1C
The next step is to set the rights to the following folders:
The bin folder in 1C.
We set the rights as in the screenshot below in the security menu.
We connect to the web server from client computers
To do this, create a connection to the 1C database - Write the name of the connection -\u003e select On the web server -\u003e further as in the picture below:
After that, you will be able to connect to 1C already through the web server.
Errors encountered:
1C8.3 IIS "Potentially dangerous Request.Path value detected" received from client
After setting up the 1C Web server, I ran into a problem: I can log into 1C by IP, I log in, but all the menus did not work, I could not open a single window except the 1C desktop. I steamed for a long time until I found a solution on the internet.
What should be done:
1. Open IIS. Start - Run - find "IIS Manager"
2. We open our "site"
3. Go to the menu "Handler Mappings"
4. Looking for ISAPI-dll, and choose to change.
5. Change the request path from "* .dll" to "*", Executable file (you may have another version of 1C, please be more careful) - "C: \\ Program Files (x86) \\ 1cv8 \\ 8.3.6.2390
\\ bin \\ wsisapi.dll ".
6. We save.
7. Checking.
That's all for now. If you have any questions, I will try to help.
