The AGE Web Apps are special kind of applications managed by the AGE's Web Server. These applications can generate and provide content to your Web-browser, or to another application. The Web Apps are processing standard HTTP(S) requests, then perform some particular business logic and data processing, and finally provide the result back to the requester as a standard HTTP responses. The technology behind the Web App development is based on the Model-View-Controller (MVC) software design pattern in order to provide flexibility, code reuse and simultaneous development of application components for business logic, data persistence, connectivity, grid processing and user interface visualization. This is a server-side technology for Web development. The Web Apps can work as a single-site solution, similar to other technologies on the market, however, these Apps are working also within the AGE node, and could be a native part of complex grid or cloud infrastructure. In other words, with AGE Web technologies you can create and deploy scalable web-based grid or cloud solutions without special efforts, just like adopting an existing Erlang, C++ or C# stand-alone applications. Furthermore, your Web Apps can use the API of all system services and plug-ins provided by the AGE IT ecosystem in order to create amazing and functionally rich solutions to your Web-clients. By design, the AGE Web Apps can be developed on multiple server-site programming languages. This documentation will explain the principles of software development and deployment using JavaScript and Erlang together. More examples and tutorials on other programming languages shall be provided additionally. |
1)The age_web_service must be loaded. This could be setup on Node's start-up, or loaded manually by age:start_services/2; 2)The age_web.config file should be configured in order all Web controllers of the respective Web Apps to be invoked correctly; 3)Your make_app.config file is deployed in the root (trunk) directory of your Web solution. For better understanding and support, we shall use the same directory structure as suggested for standard Erlang solution, however, our Web App will be developed and deployed under config/web/apps/ directory. |
Model-View-Controller (MVC) for AGE Web Apps
|
AGE Solution with Web Projects
|
Template for AGE/Erlang Web Solution Configuration file (make_app.config)
Compile Web application and model controllers
Compile Web view and language controllers
Deploy the compiled Web solution
|