Solutions for real-time systems from SCADA to manufacturing

RTA allows configuration of large projects that require distributed computing power via it's CLIENT - SERVER architecture.

The RTA-SERVER in the example below maintains the connection to the process and the database and at the same time shares it's RtDB data the RTA-CLIENTS. The clients can be visualization stations or blind-nodes and are connected to the server via TCP/IP. They can access all RtDB tables or specific ones and can have READ-ONLY or READ-WRITE access configured per table.

In a RTA SERVER-CLIENT configuration a maximum of 32 computers can be configured for shared RtDB access. The RTA internal Real Time Interprocess Communication mechanism (RtIpC) synchronizes all these computers. The synchronization is transparent for the application programer.

For RTA it does not matter if an application runs on the SERVER or on any of the CLIENTS, and neither does it for you. Thanks to RtIpC all data is replicated in real-time among ALL computers in the RTA network. This means you can run various applications on a single node or run the same applications, without changes, on different nodes. This makes it very easy to add additional computing power and it definitely saves your investment in software.

When you base your applications on RTA you get a fully SCALABLE system that can grow with your needs.

Of course the SERVER is the most crucial component in the system as it is the one that maintains the network-wide RtDB database. If the server fails the whole system shuts down. This is not acceptable in mission-critical environments, here availability and redundancy are required to ensure 24/7 operations.

How can RTA ensure high availability as required for mission-critical systems?

Step 4: The RTA CLIENT - SERVER Architecture for distributed computing power