Jetclouding Gateway has a lot of benefits. It can do a lot of features.
Gateway Tab
The Admin Tool Console enables you to configure Jetclouding, including the Gateway in its own tab:
Overview
A server can be set as the Gateway of your farm of servers.
- You can Add/Edit/Remove servers from your farm.
- You can assign one or several servers to a user / a local group / an Active Directory group.
According to his credential, the user will be able to choose which server he wants to access in the list of servers assigned to him.
If the farm is within a Domain, the Gateway will use his AD credentials and the user will connect with Single Sign-On (SSO). Otherwise, he must have the same local credentials on each server.
Choosing the role of the current server
Click on the “Server role” tile :
If you click on the “This server role is to be the Web Access Gateway Server” radio button the utility will be enabled. If you click in the “This server role is to be an Application server” radio button the utility will be disabled.
Managing the Servers of the Gateway
To manage the servers please click on the “Servers list Management” button. The window “Add, Edit or Remove Servers from you Gateway Portal” will open:
When you click on the “Add a new Server” button you can then add a Jetclouding Server by Display name and IP address (you can type an IP or a domain name, with or without a port number):
When you are done, please click the “Save” button to add the server to the Servers list.
To remove a server from the Servers list, click on the server you want to remove and then click on the “Remove Server” button. After a confirmation message, the server will then be removed from the list.
You can also edit a server by selecting it on the list and clicking on the “Edit Server” button.
The “Manage Users” button is explained in Managing Gateway Users.
* *
Recommended Architecture – All Servers have their own Public IP Address
This is the recommended architecture to use Jetclouding Gateway.
All your servers have public IP addresses and can be reached from the Internet.
This architecture follows best practices and allows the IT Administrator to industrialize its environment:
- every server has the same Jetclouding configuration
- every server has the same HTTP/HTTPS ports
- deploying a new Application server is only a matter of minutes (just add the server to the farm in the AdminTool on the Gateway server)
With this architecture, all access types are available without any specific configuration: Native, JAVA and HTML5 clients.
Of course, you can enable Load Balancing if you need it.
This architecture is described in the diagram below:
* *
Alternative Architecture – With only 1 Public IP Address
Jetclouding Gateway can also be set up with only 1 Public IP Address.
To enable this architecture, you will need to configure your router so it forwards two ports for each of your Application servers :
- one port for HTTP
- one port for HTTPS
Of course you can forward the HTTPS port only if you don’t want to use HTTP for security reasons.
You can enableLoad Balancing if you need it.
This architecture is described in the diagram below:
Every server only has a Private IP Address. The router forwards network streams depending on the port, and every server has its own ports on the unique Public IP Address.
When using this architecture, a special attention must be paid on the IP Addresses used in the AdminTool Gateway settings / Load Balancing settings :
- to use JAVA and/or Native access client : always use the Public IP Address with the specific port of each server
- 70.0.0.1:8082 for Server A
- 70.0.0.1:8083 for Server B (in the diagram example)
- to use HTML5 client : always use the Private IP Addresses of each server
- 192.168.0.2:8082 for Server A
- 192.168.0.3:8083 for Server B (in the diagram example)
