The following diagram shows a typical clustered scenario. On the left side you can see the users of a Projector based application. They connect to the application via their web browser. A load balancer is dispatching the requests to the different Projector servers to allow a highly scalable and failsafe application. The Apache web server works very well as a load balancer and can additionally do SSL encryption if needed.
The different Projector instances connect to the Slide server or and other compliant WebDAV repository via JCA. As the Slide server can also be clustered, a failsafe scenario can be achieved. The following diagram shows some more details of Projector. Projector itself is a J2EE based application that provides some services like a scheduler responsible for launching jobs when the specified conditions are met, a message manager that takes care of internationalization issues, the process manager that knows all available processors and their properties:
The main entry point for Projector is the process servlet that handles incoming HTTP-requests and invokes the corresponding processors. The result of the processor is delivered to the user as servlet response.