This document describes the steps needed to install and configure the Denodo Platform on a Cloud environment like Amazon EC2, Azure Compute or Google Compute Engine.
1. When creating a new VM instance in EC2 the only additional step you need to do is add a firewall rule. In the Configure Security Group step, click on ‘Add Rule’ and select ‘Custom TCP Rule’ in the ‘Type’ column. Enter the value ‘9995-9999’ and ‘19995-19999’ in the ‘Port Range’ text box and give a source IP. You can also specify another custom rule for the Denodo web container (9090) and Solutions Manager web container (19090):
Similarly in Google Compute Engine, after creating a new instance add a new firewall rule for Denodo:
You can add the Google Cloud command that includes all ports :
gcloud compute --project=denodo4gcp-dev firewall-rules create denodo --description="Denodo Platform 8.0 plus ssh" --direction=INGRESS --priority=1000 --network=default --action=ALLOW --rules=tcp:9995,tcp:9996,tcp:9997,tcp:9998,tcp:9999,tcp:9090,tcp:19995,tcp:19996,tcp:19997,tcp:19998,tcp:19999,tcp:19090 --source-ranges=172.16.0.0/25
In Denodo 8.0, the JDBC driver, the administration tool and the new Design Studio connections now use only one port to communicate with Virtual DataPort (by default, 9999). In previous versions, the communication requires two ports (9999 and 9997). This change simplifies the configuration of firewalls.
2. Perform a headless installation of the Denodo Platform (See the Knowledge Base article Headless installation).
3. Next, you have to add an entry to the hosts file. First, get the local IP address with the below command:
$ ifconfig | grep 'inet addr:'| grep -v '127.0.0.1'
You will get an output like below, showing the internal IP address of the server:
inet addr:10.240.84.182 Bcast:10.240.84.182 Mask:255.255.255.255
4. Now you need to add an entry to the hosts file with the match between this IP address and the hostname that will be used for the connections from the clients. This hostname can be either resolvable by the client’s DNS (a public hostname) or a private one. To configure the hosts file follow these steps:
Example of entry with public hostname:
Example of entry with private hostname:
(replace <hostname> with the hostname used in the previous step)
5. Finally, regenerate the startup scripts and start the VDP server:
(replace <DENODO_HOME> with the path configured during installation)
In order for clients to be able to connect to this Denodo running in the Cloud server, they need to be able to resolve the hostname used during the configuration of the server.
If you have used a hostname that can be resolved by the client’s DNS (a public hostname) you do not need to do any additional configuration. However, if the hostname cannot be resolved by the clients, you need to add it to the hosts file of the clients.
As an example, if you are using a private hostname like denodovm, you can follow the next steps:
1. On the client side, you have to add an entry in the hosts file with the public IP of the instance. First, you need to identify the public IP address of your Cloud server. The procedure depends on the Cloud provider that you are using:
Finding the public IP in Google Compute Engine
Finding the public IP in Amazon EC2
2. Then you need to add this public IP address to the hosts file. For example, if the public IP is 220.127.116.11, you can add an entry like the one below:
(the hosts file location in Linux is /etc/hosts and in Windows: %SYSTEMROOT%\System32\Drivers\etc\hosts)
3. You can now connect to the VDP server using the Design Studio.
Headless installation of the Denodo Platform: Headless installation
Default Ports Used by the Denodo Platform Modules: Denodo Platform Ports
Default Ports Used by the Solution Manager Modules: Solution Manager Ports
Google Compute Engine: https://cloud.google.com/compute/
Amazon EC2: http://aws.amazon.com/ec2/
Azure Compute: https://azure.microsoft.com/en-us/services/virtual-machines/