IT support
Setting up 1C web publishing, connecting cash register equipment
1. Setting up a web server in IIS
Install the Internet Information Server web server, which is included in the delivery by default 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
- Correction and diagnosis (Health and Diagnostics)
- HTTP Logging
- Request Monitor
- Management Tools
- IIS Management Console
2. Publications of the base in 1C
On the same server where the IIS web server is deployed, install 1C: Enterprise (32-bit components), making sure to select the following components during installation:
- 1C: Enterprise
- Web Server Extension Modules
If you plan to configure a 64-bit web server extension module, you must additionally run the 64-bit server setup program from the corresponding 1C: Enterprise delivery and install the component:
- Web Server Extension Module
Now you need to install necessary rights to the key folders used when working with web access to 1C: Enterprise databases. For the directory for storing files of websites published on the web server (by default: C: \ inetpub \ wwwroot \), you must give full rights to the group "Users"(Users). In principle, you can skip this step, but then in order 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, click on it with the right mouse button and in context menu choose "Properties"(Properties).
In the properties window that opens, go to the tab "Security"(Security) and press the button "Change"(Edit ...) to change the current permissions. A window for permissions for this directory will appear. In the list of Groups or user names, select the Users group and in the list of permissions for the selected group, set the flag "Full access"(Full control). Then press Apply(Apply) to save the 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" (by default: C: \ Program Files (x86) \ 1cv8 \ for a 32-bit expansion module and C: \ Program Files \ 1cv8 \ for 64-bit) group IIS_IUSRS... To do this, we perform the actions similar to those 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 the button below the list "Add"(Add ..), and in the window for selecting groups or users, click "Additionally"(Advanced ...).
Then press the button on the right "Search"(Find Now), after which we select the required group IIS_IUSRS in the search results table and click "OK".
And finally, if publishing is to a filebase, you must also give the group IIS_IUSRS full rights to the directory with the files of this infobase.
Let's move on to publishing the database directly to the web server. To do this, run 1C: Enterprise in the Configurator for the base that you want to publish. Then select from the menu "Administration" - "Publishing on a web server ..."
The window for configuring the properties of the publication on the web server will open. The main fields required for publication are already filled in by default:
- The name of the virtual directory is the name used to access the database on the web server. It can only consist of characters from the Latin alphabet.
- Web server - is 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 where the virtual application files will be located.
- The corresponding flags can be used to specify the types of clients to publish, and also to indicate the ability to publish Web services. In the table below, you can edit the list of Web services that will be published, as well as in the "Address" column, change the synonym by which this Web service will be accessed.
- Also, for the IIS web server, it is possible to specify the need to perform authentication on the web server using the OS by setting the appropriate flag.
By choosing required settings publications, click "Publish".
If the publication was successful, we will see the corresponding message.
2.3 Connecting to a published infobase via a web browser
To this information base you can also connect from any computer on the network by accessing the web server via its internal (or if port 80- by external) IP-address.
3. Creating a free Let's Encrypt SSL certificate on IIS
The presence of an SSL certificate for the site allows you to protect user data transmitted over the network from attacks man-in-the-middle and guarantee the integrity of the transmitted data.
Let’s Encrypt Is a non-profit certification authority that allows you to automatic mode issue free SSL / TLS certificates via API. Only domain validation certificates with a validity period of 90 days are issued, which is not a problem due to the built-in automatic certificate re-issue capability, which ensures continuity of protection.
The following describes a way to obtain an SSL certificate from Let’s Encrypt using the console utility LetsEncrypt-Win-Simple... It is a simple wizard that lets you select one of the sites running on IIS and automatically issue and bind an SSL certificate to it.
3.1 Generating an SSL Certificate
Download the latest client release from the project's GitHub page https://github.com/PKISharp/win-acme/releases
Let's unpack it to a directory on the server with IIS: c: \ inetpub \ letsencrypt
An interactive wizard will start, which will first ask you to specify your e-mail, to which notifications about problems with the certificate renewal will be sent, and agree to the user agreement.
Then you will need to choose that you need to create a new certificate ( N: Create new certificate) and select the type of certificate (in our example, there is no need to use a certificate with multiple SANs), so just select the item 1.Single binding of an IIS site.
The next step is to perform domain validation. Several validation options are available: TLS, DNS entry, or HTTP). The easiest option is to select the item 4 Create temporary application in IIS (recommended)... In this case, a small application will be created on the web server through which the Let’s Encrypt servers can validate.
Note. When performing a TLS / HTTP check, your site must be accessible from the outside by its full DNS name using the HTTP (80 / TCP) and HTTPS (443 / TCP) protocols.
After validation, the utility letsencrypt-win-simple will automatically send a request to generate a certificate, download it (all the necessary files, as well as the private key are saved to the C: \ Users \ User \ AppData \ Roaming \ letsencrypt-win-simple directory) and create a binding on the IIS website. In the event that an SSL certificate is already installed on the site, it will be replaced with a new one. In addition, a rule will be created in the scheduler Windows jobs that runs every day and automatically issues and installs a new certificate every 60 days.
3.2 Creating a separate pool and a site connected with an SSL certificate.
Create a separate IIS pool for letsencrypt
We add the site to the new pool. We indicate the port 443 (or another to which we will later forward to port 443).
Specify the new certificate in " SSL certificates»:
Configure a link to our site:
Checking.
4. Connection of cash register equipment. COM port forwarding over TCP / IP using Virtual Serial Ports Emulator (VSPE).
4.1 Configuring VSPE on the server
Start the VSPE program. Click on the "Create a new device" button.
After that, you need to create virtual ports (there is a port for each checkout). It is better to take the port numbers lower in order to avoid problems.
In the window that opens, in the drop-down menu, select TcpServer... Press the button "Further".
Set the local tcp port number to listen on. Select the COM port to which the equipment is connected via the interface converter. Press the button "Settings".
To make it work, you need to do the following:
1. Install the IIS module.
1.1. Control Panel - Programs and Features - Turn Windows features on or off
1.2. We put down the checkboxes:
- "IIS Web Kernel Injectable",
In the section "IIS Services" - "Application Development Components" put the checkboxes "ISAPI Extension" and "ISAPI Filters"
In the section "IIS" - "Web site management tools", put the checkbox "IIS Management Console"
Then click OK and wait until everything is downloaded and installed. On this point, I would also like to clarify that the components necessary for the operation of 1C have been supplied, I did not need anything other than this yet. This set was installed on both WIN 7 and WIN10
2. Initial configuration of IIS.
2.1. Give IIS access to:
Sites directory (C: \ inetpub),
Platform1C (C: \ Program Files (x86) \ 1cv8),
Base1C here is the exact path, everyone does not have his own.
To do this, on each of the folders, right-click Property-Security - Change - Add -IIS_IUSRS; IUSR and tick boxes full access... After clicking on OK, "Access Denied" errors may appear, click "Continue" and that's it.
2.2. Allow IIS to work with 32-bit applications. (This item is needed if you have WIN 64-bit and 1C 32-bit, so almost everyone) Go to Control Panel - Administrative Tools - IIS Manager,
in the window that opens, open the "Application Pools" section in the right window, find the "DefaultAppPool" pool, right-click - Extra options, well, in the window that opens, change "Allowed 32-bit applications" to "True" and also check the ".NET Framework version" so that it is either "v2.0" or "Without managed code" (I did not see the difference, but v4.0 - not worth it as there will be a problem in generating reports)
3. Publishing the database
3.1. Installation of the platform is mandatory with the checkbox "Web server extension module" checked
3.2. We launch 1C under administrator rights in the Configurator - Administration - Publishing on a web server mode.
And that's it, nothing else is needed.
There is one piece of advice: If the database will be available through 1C, it is not superfluous to publish it with a name that will mean nothing to provide additional security. Better in general with a random set of letters and numbers (qAdsfslj- for example), users, even if they work through a browser, go to the link, and you have additional peace of mind, but with this approach there is a minus, if you removed the base from publication, for example, to update, then the name will change to the name of the database folder, and if you have not saved this name somewhere, then you start looking for this link, and okay, if there is one or two databases, and if there are several dozen of them, then you can get confused. Having hit it a couple of times, I did the following "D: \ Bases1C \ Buh \ qAdsfslj" - where "Buh" is the name I understand, but "qAdsfslj" is the name of the database when publishing.
If after installing and configuring IIS + 1C 8.3 (everything worked on the APACH) inside local network everything is fine, but when you enter via the Internet, everything seems to be fine, but strange things happen when a spreadsheet document is formed, instead of the report grouping icons, a "torn piece of paper" appears, and you cannot select a cell in the report (although the decryption works when you double-click), and the screen has no pictures and barcodes in spreadsheet document(report) but if the same report is saved in Excel or printed, everything comes out as it should. It means that you "got" just like me (I was looking for a solution for a very long time, which is why I am writing this article).
I tried all the proposed settings on the Internet, it did not help, changed Windows (7.10, 2008), computer, version 1C and IIS (7.0, 7.5, 10) does not help. At the same time, it is necessary to take into account also such a moment that one IIS + 1C server is already running on the same network and everything works as it should.
And the fact was that after I started the server, I immediately made a port forward through the router to the outside, and since there was already a server running on port 80, I forward it to the alternative (444, 98, 90, etc. there were a lot of reinstallations ). and got a sad result. And you had to first make a direct forwarding 80-80 to go to 1C via the Internet. and then you can change the port to any. This option has been tested several times.
I will be glad if someone can help, and will not allow you to lose a lot of time and nerves.
Today we will learn with you install IIS web server v operating system Windows Server 2016 in several ways, namely using graphic tool and of course with using Windows PowerShell.
What is IIS 10?
IIS (Internet Information Services) Is a set of services designed to implement a web server in an operating room Windows system with support for HTML sites and applications on ASP.NET or ASP. On Windows Server, it is distributed as a separate role with sufficient big amount role services. Earlier in the article "Description and Purpose of Server Roles in Windows Server 2016" we looked at a brief description of all server roles and their services, including the role " Web Server (IIS)"Therefore, repeat now, i.e. I will not describe each of the role services.
The current version of the server operating system Windows Server 2016 also contains the most a new version web server, namely IIS 10.
IIS web server versions
| IIS version | Operating system version |
| 10 | Windows 10; Windows Server 2016 |
| 8.5 | Windows 8.1; Windows Server 2012 R2 |
| 8.0 | Windows 8; Windows Server 2012 |
| 7.5 | Windows 7; Windows Server 2008 R2 |
| 7.0 | Windows Vista; Windows Server 2008 |
| 6.0 | Windows Server 2003 |
| 5.1 | Windows XP Professional |
| 5.0 | Windows 2000 |
Installing the IIS 10 Web Server
So, let's move on to looking at the installation process, and for example, let's just install the basic components that are necessary for the functioning of the web server and its administration ( controls), and also place on it plain HTML page, i.e. essentially an HTML site to test the web server. If you need to host applications, for example on ASP.NET, then you need to also install the corresponding role services from the section " Application Development».
Installing the IIS web server using the wizard
First, let's walk through the process of installing an IIS 10 web server using “ Server manager", And more specifically" Add Roles and Features Wizards».
Step 1
Open the server manager " Start -> Server Manager».
Then we run " Add Roles and Features Wizard", Menu" Management -> Add Roles and Features».
Step 3
Then we select the installation type “ Installing Roles or Features", Click" Further».
Step 4
Then select the target server and click " Further».
Step 5
At the step of choosing roles, mark the role “ Web Server (IIS)". You will be automatically prompted to install the component " ", We agree and click" Add components».
Step 6
Everything necessary components we have already noted, so at this step we also immediately press “ Further».
Step 7
Now we need to configure the installation of the role " IIS web server", First press" Further».
And then we select the necessary role services, by default the minimum number of services will already be selected, but if you need something else, then tick them. For our test problem, i.e. host a simple static HTML site, the default services will be enough, click " Further».
Step 8
We check the selected roles, services and components and click " Install».
The installation will complete as soon as a message appears.
Installing the IIS web server using Windows PowerShell
To install the IIS web server using PowerShell, start Windows PowerShell and enter the following commands ( the commands below will install all the same services that we installed using the wizard just above).
Default document
Install-WindowsFeature -Name "Web-Default-Doc"Catalog overview
Install-WindowsFeature -Name "Web-Dir-Browsing"
Http errors
Install-WindowsFeature -Name "Web-Http-Errors"
Static content
Install-WindowsFeature -Name "Web-Static-Content"
Filtering requests
Install-WindowsFeature -Name "Web-Filtering"
Http logging
Install-WindowsFeature -Name "Web-Http-Logging"
Install-WindowsFeature -Name "Web-Stat-Compression"
Internet Information Services Management Console
Install-WindowsFeature -Name "Web-Mgmt-Console"
Hosting HTML site on IIS web server
The first thing to do is to create the root directory of our test site, for this in the directory C: \ inetpub \ create a folder TestSite and add the index.html file with the following content to it for checking, for example
<Н1>Test site
Then we open “ Internet Information Services (IIS) Manager", This can be done, for example, from the server manager" Tools -> IIS Manager».
Then we right-click on the item " Websites -> Add Website».
A window for adding a website will open, fill in the required fields and click " OK» ( TestSite in my case is the name of the site).
Now we can check the operation of the web server and the newly created site, for this we open any web browser and go to the TestSite site ( just remember, in order for you to open a site by name just like mine, it must be added to DNS server(A record was created) or at least for tests an entry was added to HOSTS file local server).
Removing the IIS web server using the wizard
To remove the IIS web server, open the server manager, then click on the menu " Management -> Remove Roles and Features».
As a result, “ Remove Roles and Features Wizard", Where we do almost the same thing as during installation, only we do not check the boxes, but remove them.
Removing the IIS web server using PowerShell
To remove the IIS web server on PowerShell, start the Windows PowerShell shell and use the cmdlet Uninstall-WindowsFeature... To remove the following IIS Web Server Role Services, you can use the following commands:
Default document
Uninstall-WindowsFeature -Name "Web-Default-Doc"
Catalog overview
Uninstall-WindowsFeature -Name "Web-Dir-Browsing"
Http errors
Uninstall-WindowsFeature -Name "Web-Http-Errors"
Static content
Uninstall-WindowsFeature -Name "Web-Static-Content"
Filtering requests
Uninstall-WindowsFeature -Name "Web-Filtering"
Http logging
Uninstall-WindowsFeature -Name "Web-Http-Logging"
Compressing static content
Uninstall-WindowsFeature -Name "Web-Stat-Compression"Internet Information Services Management Console
Uninstall-WindowsFeature -Name "Web-Mgmt-Console"
Here we are with you and learned how to install and remove the IIS web server in the Windows Server 2016 operating system, and that's all for now!
A web server is some kind of program (service) that accepts HTTP requests from clients, usually from web browsers, which processes these requests and gives them a response, usually together with an HTLM page (site), image, file, media stream or other data. Below we will take a closer look at the installation process of such a service, namely the IIS 8 (Internet Information Server) web server included in the delivery.
1. Installing the IIS web server
Launch Server Manager. It can be launched from the shortcut on the taskbar, or by running the command servermanager.exe(To do this, press the key combination Win + R, in the window that appears in the field “ Open"(Open) write the name of the command and press" OK»).
In the server manager, in the menu located on the right upper corner windows, select " Control"(Manage) -" Add roles and components»(Add Roles and Features)
The Add Roles and Features Wizard will launch. Click " Further»(Next) on the start page.
Installation Type, mark “ Installing Roles or Features"(Role-based or feature-based installation) and click" Further"(Next).
We select the current server from the server pool (Select a server from the server pool) and again click “ Further"(Next).
In the next step, select the role that you want to install. In our case, this is the role “ Web Server (IIS)"(Web Server). We mark it in the list.
In this case, the wizard will offer us to add the components required for the Web server, namely “ Internet Information Services Management Console"(IIS Management Console). We agree to install additional components by clicking " Add components"(Add Features) and click" Further"(Next).
Leaving the list of components unchanged, press “ Further"(Next).
After reviewing the information about the role of the web server, click again " Further"(Next).
Next, you need to select the role services to install for the web server. This set depends on the specific tasks that the IIS server will perform.
Also, this site can be viewed from any other computer on the network by typing in the IP address of the computer where the IIS web server is installed.
The files of this site, like the files of all other sites added later, are located by default in the directory C: \ interpub \ wwwroot.
Well, and accordingly, so that sites located on this web server are accessible from the Internet by an external IP address or domain name (how to bind Domain name to the IP address), you need to perform forwarding on the router 80 port to the computer with the IIS web server installed.
2. Restarting the IIS server
Sometimes it is necessary to restart the IIS web server. This can be done both from the IIS Manager by right-clicking on the server in the connections window or from the menu “ Actions»(Action)
so and from command line by running the command
Iisreset / noforce<имя_компьютера>
- parameter / noforce is optional and is used to protect against data loss when Internet Information Services (IIS) cannot be stopped within a one-minute time-out period.
- parameter <имя_компьютера> also optional when working on local computer... When remote administration IIS server as parameter<имя_компьютера>specifies the NetBIOS name of the computer on which IIS is being restarted.
When you restart the IIS web server, the following services are restarted (if they were installed during the installation of the IIS component):
Did this article help you?
This document walks you through the process of installing an IIS web server and configuring it to serve static content. Static content is a web page (HTML) that is delivered to the user as it is stored. Conversely, dynamic content is rendered by a web application such as ASP.NET, a classic ASP application, or PHP application... Static content displays the same information for all users; dynamic content can display information about a specific user, such as the user's name.
Static Content Web Server is the simplest IIS configuration to support HTML websites. A static content web server can be used to host internal or external (public) websites. Installing IIS 8 installs by default all IIS modules required to support static content web servers. The default installation includes the ability to serve static HTML files, documents, and images. IIS 8 supports default documents, directory browsing, logging, and anonymous access for a server with static content.
