Application manager Sample Clauses

Application manager. The application manager was developed to allow developers to easily and quickly test their applications. In the application manager developers can use three different pages. The first (overview) page shows the applications that are currently active on the server. This means that the application has been opened at least once. Furthermore the current number of screens and connected users can be viewed and logging information is available. Also there is the possibility to locate all the screens. By pressing the related button an audio signal will be played on all connected screens so developers can find all their devices. The second page shows all the applications available on the server including versioning. From here it is possible to deploy new applications, define if the application is a development or production version and configure if new uploads should be auto deployed as development or a production version. The third page allows for user management where users can be added and altered. An impression of the pages from the application manager can be seen in Figure 4. Demo applications are provided with an Ant3 build file that will pack the application together with the client side resources (images, style sheets, client side scripts) in a war file. However unlike normal war files that are deployed directly on a J2EE web server the war file needs to be uploaded through the application manager that is part of the SMT. When an application is uploaded the application manager moves the resources to the correct locations and keeps track of different versions. For every application a limited amount of versions is kept, at least one version per month, week and day is kept so that developers can always roll back to a previous version if needed. Updated applications are directly available to use after deployment.