TAPAS Demonstrator FAQ
From TAPAS Wiki
Contents |
What is PaP? and how is it related to TAPAS?
Plug and Play (PaP) is a term defined by the project TAPAS
What is PaP Demonstrator?
The TAPAS or PaP Demonstrator is a software implementation of the concept of Dynamic Plug and Play (PaP), as defined in the TAPAS Architecture. The demonstrator also implements a set of sample applications that makes use of the PaP principals for demonstration purposes. Dynamic Plug and Play, in contrast to static Plug and Play, has the property that only the PaP bootstrap software needs to be installed on a computer prior to execution of a PaP specific applications. All PaP specific software will be dynamically loaded from a web server and started when needed by the performing PaP application.
The PaP concepts definition is based on using the Theatre as a metaphor, where Repertoire, Play and Manuscript defines the behaviour of PaP applications, the Director and Actors and these are the real performers of the defined behaviour.
How is TAPAS platform implemented?
The implementation is based on the specification of the PaP Layered Reference Model, which defines how the PaP specific concepts (Repertoire, Play, Actor, Manuscript ...) should be implemented. In addition, the layered model also represents a common basis for designing and implementing PaP applications, and also specifies how software and hardware related concepts are handled in the PaP model. The application independent part of the PaP software is implemented as a Java package called TAPAS Support System. The interfacing (i.e. the PaP API) between the PaP Support System and the applications is mainly constituted by the ApplicationActor class in that Java package. Execution of PaP Applications requires the installation of the Java Runtime Environment (JRE) on all computers that will run PaP specific code, and the implementations of both the PaP Support System and the PaP Applications must be available at some web server.
How to develop TAPAS applications?
Development of TAPAS applications is based on the usage of the PaP API. Three example PaP applications have been developed and are used for demonstration purposes. They are the Tele-School, Watcher and TestPaP applications. Each of these applications may consist of one or more Plays,for instance, the TestPaP application consists of the two plays TestPaP and TestPlay. Each Play may define one or more Manuscripts, where each Manuscript defines the actual behaviour of an Actor assigned to that particular manuscript. The implementation of the example applications is written in pure Java code, designed according to the PaP API.
How to run TAPAS applications?
Installation and execution of PaP applications require a compiled version of both the generic PaP Support System and the specific PaP application to run. Compilation of Java source files into corresponding class files can be done by using the javac compiler from Java 2 Platform, Standard Edition (J2SE). The compiled PaP software must be available from a web server address (i.e. URL). In addition, the Java Runtime Environment (JRE), alternatively J2SE, must have been installed on any computer, that will run PaP software. The PaP Support System code can be installed on a web server, while the PaP boot code must be installed on the computer that runs the PaP applications. Also the example PaP application code may be downloaded and installed on the same or another web server than the location of the PaP Support System. The file pap.cnf, located in the PaP boot code, specifies the web server where the PaP Support System is located (codebase and policy), and the location, including the node name, where the default Director will run (homeinterface). The file pap.cnf must therefore be edited to adapt to a new installation.
A computer will become ready to run PaP applications when the PaP Node Execution Support (PNES) has been started. This can be done by running either of startPaP.bat or boot.bat located in the PaP boot code. A separat command/trace window should appear for PNES when started, and this window can be used to start applications (see Some user dialogue examples) by making use of the Debug and Trace facilities. A detailed debug command description has been defined. A set of demonstration examples, and a detailed specification of how to run these demonstrations has been defined.
How to do a quick TAPAS software check?
An installed and ready to use version of the PaP Support System software, and some sample PaP applications already exists at the web. Therefore, the only thing necessary to do to obtain a PaP demonstration is, if not already done, to install the PaP boot code any place locally at your computer, and eventuelly install the JRE if neither JRE nor J2SE has already been installed. Edit the pap.cnf file, according to what is said in the previous section, in the directory where the PaP boot code was installed. After installation, the PaP Node Execution Support (PNES) is simply started by executing the startPaP.bat file located in the directory where the PaP boot code was installed. PNES must always run when PaP applications are active. One of the sample applications is started by doing two simple command in the PNES command window. The PlayPlugIn will make a play available for execution (i.e. plugged into the Repertoire), and ActorPlugIn will start an Actor performing that play. Use the predefined list of commands in the PNES command window to select the desired play to run (select command by up/down arrows from keyboard). Some more detailes about running PaP applications is found in the previous section.
