However, despite of the simplicity of the user interface, the architecture which lies behind is not simple at all. In this article, I will briefly explain the different parts of the architecture.
A PTAnywhere installation looks like the following image shows.
There is a web server where the PTAnywhere API is deployed. Additionally, it might also serve the web application with the HTML widgets which use the API. The PTAnywhere API uses a Redis database to handle students’ sessions. It also relies on one or more PT managers to handle Packet Tracer instances. Each manager can handle several concurrent instances. Optionally, the API can also record interaction details in a Tin Can API compatible Learning Record Store (LRS).
In the next section, I briefly explain how to install PTAnywhere. However, if you are interested in a specific part of the architecture you can go directly to its explanation clicking in any of the following links: