GXportal has two components:
GXportal Backend: is made up by the management systems used to design it and to manage its contents and everything to be published in the portal. Those users with Backend roles access this system through a browser, either connected through Internet or connected within their own Intranet.
GXportal Frontend: is the group of web pages and security components accessed by end users while browsing through the portal.
Architectures
GXportal may be installed setting it up in multiple servers or in only one server. Basically, the components required to bring GXportal into operation are the web Server where the Backend and Frontend system will be published, the Database server where all portal contents and information reside and the FTP server through which all images, audio and video files to be used in the portal will be stored.
Let’s see the different alternatives as regards the architectures over which GXportal can be brought into operation:
Minimum architecture
In this case, the web server, the database server and the FTP server are setup on the same server. That is to say, the Backend and the Frontend are in the same server.
Standard architecture
In this architecture, the database Server has been separated and the web Server and the FTP Server remain in the same PC. In this case, the Backend and the Frontend are also in the same server.
Optimal architecture
This is the case where all components are separated. That is to say, each component has a different Server and, at the same time, there are different FTP servers, one for each file type to be stored (audio, video or image). As shown in the next figure, the Backend and the Frontend are separated in different web servers.