There are different options for configuring a GAS installation depending on your network.
A Web server is required and security needs to be considered.
A Web server:
Enables load balancing.
Handles HTTPS.
Handles authentication. You can use the Web server to handle authentication.
Alternatively, you can use a Single sign-on solution.
Installation example 1: all-in-one machine
You can have the Genero Application Server on the same machine as the Web server.
Installation example 2: database on separate server
You can have the GAS installed on the same machine as the Web server and the database on a
separate server as shown.
Installation example 3: behind frontal web server
If you already have a Web server (server A) on the internet (in a non-protected area /
inside a DMZ) and do not want to have Genero on this server, you will need to add another Web server
(shown in Server 1 in the drawing) to manage the GAS.
Note:
If you are using the isapidispatch
dispatcher, it is bound to the Web server and therefore
needs to be on the same host. Installations using fastcgidispatch can be on the
same host as the Web server, but may also be installed on a separate host. See Installation example 4
for an example of this installation.
This second Web server needs to be protected and therefore sits in the protected network.
The frontal Web server forwards application requests to the internal Web server on server 1
as shown.
Installation example 4: GAS on a separate server to the Web server (fastcgidispatch
only)
If your installation uses the fastcgidispatch dispatcher, you can install
the GAS on a separate server to the Web server.
The Web server forwards application requests to the GAS on server 1 as shown.
It is recommended that the configuration for production environments be supervised by a Web
specialist to avoid security issues.
