Client Side: It represents the applications which interact with the Cluster Framework. These applications can be in any technology like Flex, JSP, JSF, ASP.NET etc. Application Server: represents the container of LiveCycle server, the session manager, the engine to send JMS messages and the layer of each Application that exposes the objects permitted to be used remotely by LiveCycle and encapsulates sending messages to the NV core.
In this layer there is a proxy that interacts with a session manager to take care about the control of the session of each client and the permissions to use the application and methods of the core.
NV Middle Tier: Is the Core of the Framework. Allow communication being uncoupled, based on message services between the front-end and back-end. Ensures that all requests of the customers are served thank to a cluster-based infrastructure.
Business Logic Layer: Here is where the business logic of each one of the applications resides, and where the programmer can retrieve, insert, update, use, etc. data from the database. In this layer, the architecture follows the better habits of the Spring Framework even for the management of the pool connection with the database.
Data Base Cluster: This layer is not itself part of the framework, simply named to give a final idea of the architecture and reflect that it is possible to mount it into a cluster if the type of database supports it.