Data exchange, APIs and web technologies
An overview of the APIs (Application Programming Interface) available in WinCC OA.
This chapter describes the NextGen Archiver Backend API
Describes the NGA redundancy.
Release Notes, Update information, Certifications and Frequently Asked Questions.
Your first step into modern and powerful process visualization.
Topics, you need to know, before using WinCC OA.
Go beyond the norm in cybersecurity.
Powerful tools for easy or complex engineering tasks.
Classify, structure and archive your data.
Endless possibilities in data processing for your projects.
User interfaces, Trends and Reports for every purpose and device.
The process connection to the actual machines/sensors.
Your portal to the cloud or supervising systems.
The WinCC OA API (Application Programming Interface) offers a number of functions adding special Managers to this process control system.
This chapter provides an overview of the NGA system architecture.
Description of what is a backend.
The segments are used for NGA archiving. In order to keep the data manageable, NGA structures the data of each archive group into segments.
Contains the requirements for the NGA Backend API.
This chapter describes the project structure of the TemplateNextGenArchBackend project (lib, exe and plugin projects as well as the dplist directory).
Build steps contains the steps Create new project and Updating third-party libraries in an existing project.
The backend can work in various modes.
This chapter describes what classes you must implement to implement your backend.
The main aspect of NGA redundancy is to avoid losing historical data due to single hardware or software failures.
This chapter describes NGA redundancy for non-redundancy-capable databases.
This chapter describes NGA redundancy for redundancy-aware databases.
This chapter describes the backend lifetime consisting of the different steps for starting and stopping such as Create a CommonBackend instance and Get DatabaseParameters.
COM stands for Component Object Model, a specification for developing modular software components which can be used by each COM compatible application. COM components can be easily integrated in such applications and can even be removed from an application at run time. COM components can be programmed in various different programming languages although C++ is used mostly. The specifications OLE, ActiveX and DirectX are based on the COM technology.
The Prometheus interface (also referred to as Prometheus client) serves as a bridge between WinCC OA and Prometheus. It facilitates the retrieval, processing, and exposure of data from the WinCC OA system to a Prometheus-compatible format. This allows Prometheus to monitor and alert based on the data fetched from the WinCC OA system.
In increasingly dynamic automation environments and the merging of IT with OT, the SIMATIC PLC Discovery can help with the connection of newly added S7/S7+ devices by showing you all the devices in the network
The WinCC OA JavaScript Manager for Node.js is a manager that allows for the integration of the TypeScript/JavaScript runtime environment Node.js® into WinCC OA.
SIMATIC Unified AR is an industrial Augmented Reality app that allows to display and operate HMI screens (WinCC Unified) and web applications (WinCC OA Dashboard) in real production environments.
The HTTP Server integrates Internet technologies directly into WinCC OA . Implemented as an add-on for the Control Manager, possible applications are many and diverse. The HTTP Server can be used as a web server for static HTML pages including download facility or to generate dynamic HTML pages.
XML-RPC (Extensible Markup Language Remote Procedure Call) allows software on different operating systems to make procedure calls over the internet. XML-RPC uses HTTP for the transport and XML for the encoding. It sends the procedure call to a remote server through HTTP. The call is an XML document and it receives the response as XML.
The REST Reporting API is integrated into the Standard web server and can be activated via the config entry enabled in the [restReporting] section.
Distributed systems in WinCC OA allow to connect two or more autonomous WinCC OA systems via a network.
Configuring and maintaining a distributed system in WinCC OA requires a high amount of engineering effort due to a high number of settings and configuration steps that must be applied on several systems. The Dist-Management reduces the engineering effort and simplifies the necessary settings.
XMPP (formerly Jabber) is mostly used in chat (instant messaging) applications and allows near real time communication between two or more parties. It can, e.g., be used to push information from a WinCC_OA project server to one or more persons, even allowing the recipient to send a confirmation back to the server.
All about authorization, authentication and login-customization.
How to get your system uptime to the maximum.
Create state of the art project reports without limits.
Useful tools and enhancements for special demands.
Detailed and extensive content for special project adaptation.
Explore the capabilities of WinCC OA with our carefully selected collection of video tutorials and guides.
Basic information about terms and functions within the documentation.
A brief clarification of liability exclusions or legal notices.