Best Practices for Publishing WinCC Web Navigator Graphics in SIMATIC PCS 7

In SIMATIC PCS 7 with WinCC Web Navigator, graphic modifications published directly on the Web Server are overwritten and lost during the next OS download from the Engineering Station (ES). To ensure persistence and proper display on Web Clients, always execute the Web View Publisher directly on the Engineering Station inside the OS project, and then download the project to the Web Server using the standard PCS 7 OS download mechanism. Finally, refresh the Web Client browser cache.

Architecture of WinCC Web Navigator in PCS 7 Client-Server Topologies

In SIMATIC PCS 7 process control systems, the WinCC Web Navigator option enables operators, plant managers, and remote engineers to view and operate process screens over standard intranet or VPN connections via Internet Explorer or the Web Navigator standalone client application.

The Web Navigator engine functions by converting native WinCC graphics files (.pdl), ActiveX faceplates, and scripts into optimized, web-compliant formats (compressed XML/PDL structures and web scripts) using the Web View Publisher tool.

A recurring operational frustration occurs when an engineer makes graphic adjustments, logs into the dedicated Web Server PC, and runs the Web View Publisher locally:
1. The web changes appear briefly on remote clients.
2. Several days later, an engineering change is made in CFC or Graphics Designer on the Engineering Station (ES).
3. The ES compiles and downloads the OS project to the Web Server.
4. All web publishing is completely wiped out, reverting the Web Clients back to outdated screens.

This happens because the Engineering Station is the single point of truth in PCS 7. Any files published locally on the Web Server reside in target runtime folders that are completely overwritten during the next ES download.

Web Publishing Workflow and File Persistence Matrix

Understand where web publishing assets must be authored, published, and stored:

Web Navigator Lifecycle StepExecution LocationFile System PathRisk / Consequence if Executed IncorrectlyAuthoring Graphic ScreensEngineering Station (ES)<ProjectPath>\GraCS\*.pdlMaster graphics must originate on the ESExecuting Web View PublisherEngineering Station (ES)<ProjectPath>\WebNavigator\*Publishing on Web Server results in overwrite during next ES downloadProject OS DownloadEngineering Station -> Web ServerNetwork share transfer to Web ServerTransfers compiled master graphics and published web data atomicallyWeb Client AccessRemote Web Client PCInternet Explorer / Web Client CacheCached ActiveX controls prevent viewing published screen updates

System standard: Never author or publish graphics directly on runtime Web Servers.

Executing the Web View Publisher on the Engineering Station

Follow this verified procedure on the Engineering Station:

Complete Graphic Modifications in Graphics Designer:
* Open the OS project on the Engineering Station.
* Make and save all process screen modifications in Graphics Designer.
Launch Web View Publisher on the ES:
* In WinCC Explorer on the ES, expand the navigation tree.
* Right-click Web Navigator and select Web View Publisher (or launch from Tools > Web Navigator > Web View Publisher).
Configure Publishing Scope:
* In the wizard, select the language versions to be published.
* Under Select Pictures and Functions:
- Select All pictures (or check Publish modified pictures only for fast incremental publishing).
- Ensure standard PCS 7 faceplates and Basic Process Control functions are selected.
- Click Publish: The wizard parses all .pdl files, converts scripts, and places the web-ready output into the project's local WebNavigator directory on the ES.

Downloading to Web Server and Managing Web Client Browser Caches

To deploy the published assets to the runtime environment:

Download OS to Web Server from SIMATIC Manager:
* In SIMATIC Manager on the ES, select the Web Server OS object.
* Select PLC > Download.
* Scope: Changes only (or Entire OS if structural changes occurred).
* The download routine transfers both native graphics and the compiled WebNavigator web payload to the physical Web Server PC atomically.
Refresh Remote Web Client Sessions:
* On the remote Web Client computer, close the active browser window.
* Open Internet Explorer, press Ctrl + Shift + Delete, and clear Temporary Internet files and website files.
* Reconnect to the Web Server URL: http://<WebServer_Name>/.
* The Web Navigator client downloads the newly published screen packages and renders the updated process graphics.

Verification

Verify end-to-end web publication:
1. Make a distinctive visual modification (e.g., add a text label Web_Test_V1) to a process screen on the ES.
2. Run Web View Publisher on the ES, then download changes to the Web Server.
3. Open the Web Navigator client from an external workstation.
4. Confirm that Web_Test_V1 appears on the web screen immediately upon login.
5. Execute a subsequent OS change compile and download from the ES: Confirm that Web_Test_V1 remains persistent on the Web Client.

Limitations and Operational Precautions

Not all standard WinCC ActiveX controls and complex third-party .NET controls are supported in Web Navigator; always check controls against the Web Navigator compatibility catalog.
WinCC Web Clients require Internet Explorer 11 or the Siemens WinCC WebViewer standalone application; standard consumer browsers (Chrome, Edge, Firefox) require the HTML5-based WinCC WebUX option.
Remote client connections must be secured using HTTPS (SSL/TLS certificates) when traversing corporate networks.

Engineer FAQ

Can I publish web pictures directly on the Web Server for urgent testing?

You can publish locally on the Web Server for immediate testing, but you MUST repeat the publishing on the Engineering Station immediately afterward; otherwise, the next ES download will permanently overwrite your work.

Why do Web Clients see old values after a successful publish?

The local browser cache on the client PC is holding the old PDL graphics. Clear the browser cache or configure Internet Explorer to 'Check for newer versions of stored pages: Every visit to the webpage'.

What is the difference between Web Navigator and WebUX in PCS 7?

Web Navigator provides full-featured SCADA client functionality using ActiveX in Internet Explorer or WinCCViewerRT. WebUX provides platform-independent HTML5 visualization for mobile devices and non-Windows browsers.