Another area of application for the “SOCKET” operating mode is the provision of web applications. The aim of a web application is to provide functions and display dynamic content. They form a user interface with which content is prepared for various end devices (desktop, tablet, smartphone, notebook).
This means that web applications work according to the client-server model. Data processing and evaluation takes place on a server and only the results are forwarded to the web application for visual processing.
Web applications are divided into platform-independent and dependent (native) applications. Both types have their advantages and disadvantages.
Platform-dependent web applications can be well optimized so that even complex and computationally intensive applications can be created. The application also has access to the built-in hardware (microphone, printer, camera, sensors, memory) which further extends the functionality of the application. One disadvantage is that a process must be created to distribute the application for installation. Also, a complex porting process is usually necessary when changing the platform.
With platform-independent web applications (e.g. Java, .NET, HTML browser), the applications run in a defined runtime environment. The more independent the runtime environment is from the underlying computer system (hardware, operating system), the easier it is to develop applications. The developer does not have to develop a separate client for each platform. This makes such applications cheaper and more flexible to create and maintain. One disadvantage is that it may be necessary to adapt all applications when updating the runtime environment. It is also more difficult to access hardware components or memory outside the defined runtime environment.
One of the best-known examples of platform independence is the web browser, where there is no need to install a client. Applications based on HTTP can be called up and used directly.
What are the advantages of designing a web application with conzept 16?
The SOA task is processed in the database. This means that the entire conzept 16 functionality is available to the SOA task, with the exception of restrictions for UI elements.
- Simpler infrastructure
No additional web server needs to be integrated into the system landscape and maintained. This reduces the complexity of the infrastructure and there are no new costs for familiarization with new software.
- Interface design
The elimination of an external web server also eliminates the need to create and maintain an interface to an external web server.
- Information transfer
Communication with the database is more efficient as we do not have to transfer data via an interface (REST, WSDL, ODBC).
Example: Monitoring water levels with conzept 16
Water level measuring stations have been set up at various locations to provide early warnings of flooding. If the water levels are to be read, the inspector can log in to a web application. All current information from the stations is retrieved and displayed within the web application.
A conzept 16 socket task waits for a connection. Once an inspector has successfully authenticated himself to the conzept 16 web application, all water levels of the various measuring stations are queried. The status is visualized and returned via the web application. If a measured value is exceeded, the inspector can select the measuring station with a mouse click in the web application and trigger an alarm. With the help of conzept 16, the alarm is forwarded to the relevant authorities by fax, SMS or e-mail.