HTTP Server Requirements and Installation

Requirements

• WinCC OA base installation
• A valid HTTP Server license (required for both components)
• An HTTP browser (for example, Internet Explorer or Firefox).
• Network with TCP/IP communication.
• For the HTTPS (SSL) connection certificates are required. Create certificates via the Certificate authority (see Create a Certificate with a Certificate Authority) or create self-signed certificates (see Create a self-signed Certificate).
• Windows certificate store certificates can also be used for the HTTP server. Create CNG certificates with OpenSSL using the prime256v1 algorithm. See chapter CNG Provider - Create Certificates.

  In the chapter CNG Provider - Create Certificates, follow the steps under Create the Root Certificate and Create the Host Certificate. To use Windows Certificate Store certificates, you must convert the certificates to the Windows Certificate Store format. For instructions on how to do this, see chapter Create, Convert and Import Multiplexing Proxy Certificates for an example.

  After converting the certificates, add the necessary certificate configuration entries to your project configuration file - see chapter HTTP Server

Notes for using the HTTP Server

• The confg entries ip_allow and ip_deny must be used to set a list of allowed and restricted IP addresses for the Server access.
• The root certificate (CA) must be imported to a browser so that it is added to the trusted Certification Authorities and not blocked by the browser - see chapter Root Certificate & the Trusted Certification Authorities for Browsers.
• Note that the Desktop UI and the HTTP Server package can not be run over the same port at the same time.
• The behavior of the HTTP Server regarding connection management is different depending on the client HTTP/1.0 or HTTP/1.1.

  A 1.0 client expects a connection being closed unless it stated otherwise, a 1.1 client expects a connection being kept open unless stated otherwise.

• Note that a stepwise delay ( steps: 1, 2, 4, 8, 16, 32 and 60 seconds) is implemented when an invalid login is attempted. See also httpSetSecondaryAuthSuccess() and httpConnect() for more information.
• DNS Server response

  A slow response from the DNS server might cause delays and an unresponsive WebServer. If the DNS response is slow, a warning is shown indicating that the DNS response is unusually slow and that you should check the network settings.

  Under Linux, you can reduce the maximum DNS translation wait time by setting the following parameters:

  options timeout:1
  options attempts:1

  in /etc/resolv.conf file.

  See the man page for the resolv.conf file for more information.

Installation of the HTTP Server

Configure the following settings before starting a project to ensure that the HTTP Server works correctly:

1. Install the WinCC OA base package.
2. Start a CTRL Manager with the rs_http.ctl script:

    WCCOActrl rs_http.ctl

3. Copy the file config.http from the directory <wincc_oa_path>/config to<proj_path>/config.
4. In a browser, enter the name of the computer on which the HTTP Server is running (host name) or its TCP-IP address (for example, http://193.81.17.83). If the HTTP Server is installed on the local machine, enter http://localhost in the browser window.

Next, the login prompt will automatically be displayed. There are three ways of logging in to the HTTP Server depending on the settings in the base configuration config.http:

• Login as WinCC OA user. User name and password are the same as for WinCC OA login (User: root, PW: empty (no password) (see also HTTP base configuration, entry httpLogin).
• Login by entering an access code (see also HTTP base configuration, entry httpLogin and httpAccessCode).
• Access without login (see also HTTP base configuration, entry httpLogin).

The main HTTP Server directories are <proj_path>/data/http and <proj_path>/pictures/http. Save your HTML pages in the language directories under <proj_path>/data/http/<lang> and <proj_path>/data/http/<lang>/refs and your own images in <proj_path>/pictures/http. (see also Working with standard WinCC OA HTML pages).

The necessary directory structure will be created when you start the projects. The folders are created in the directory <proj_path>/data/http. By default, a multi-language project supports English 'en' and German 'de'. The standard pages are located in these directories and are available for immediate use.

For the use of Proxy/NoProxy settings see HTTP base configuration

Language properties

As usual on the web, there is no difference between en_US and en_GB. One page is available for both English options. Also only one page exists for de_AT and de_DE in German.

The language of the standard WinCC OA HTML pages cannot be changed directly in the address bar of the browser. To change the language, use the language selection button at the bottom of an HTML page.

Other languages are available, but the pages must be translated.

The following 30 languages are available: