Uploaded image for project: 'Solution Center'
  1. Solution Center
  2. SOL-339

Enable internet access for Exasol Community Edition

    XMLWordPrintable

    Details

    • Solution:
      Hide

      Scope

      By default, an Exasol virtual machine (VM) is configured to use a host-only network. This configuration allows to access the database and the EXAoperation management interface locally from the host machine. Nethertheless, this configuration prevents the use of publically available hosts and services in the internet from the virtual machine. This How-To provides information about configuring Exasol to be able to access the internet and enables users to:

      • use DNS to access publicly reachable servers for making backups or in database IMPORT/EXPORT statements
      • use LDAP servers of your choice for database or EXAoperation accounts
      • use standard repositories for the installation of UDF packages
      • use the Exasol Version Check (only if this feature has not been disabled)

      1. Configuration of VM network

      1. If not already done, import the Exasol OVA file into the VM tool of your choice (in Virtualbox: File -> Import Appliance). Accept the "End User License Agreement" and the "Privacy Statement" and wait until the image has been successfully loaded.
      2. Now, a new VM has been created. Change its network settings to use NAT (in Virtualbox: right click on VM -> Settings -> Network -> Adapter 1 -> Attached to NAT) and define port forwardings to guest ports 8563 (database) and 443 (EXAoperation management interface) (in Virtualbox: Adapter 1 -> Port Forwarding -> Add rule -> Host Port 8563 and Guest Port 8563 -> Add rule -> Host Port 4443 and Guest Port 443). The port forwarding rules will enable you to use the VM from the physical host machine.
      3. Start the VM and wait until Exasol is up and running.

      2. Configuration of DNS server

      1. Browse to EXAoperation and login.
      2. Go to Network. In the System tab, click on "Edit".
      3. Add one or two DNS servers reachable from the VM (e.g. "8.8.8.8" for an environment that can reach internet DNS servers) and click "Apply".
      4. Log out.

      Troubleshooting

      • Firewalls and/or company proxy servers may block or restrict traffic to internet hosts.
      Show
      Scope By default, an Exasol virtual machine (VM) is configured to use a host-only network. This configuration allows to access the database and the EXAoperation management interface locally from the host machine. Nethertheless, this configuration prevents the use of publically available hosts and services in the internet from the virtual machine. This How-To provides information about configuring Exasol to be able to access the internet and enables users to: use DNS to access publicly reachable servers for making backups or in database IMPORT/EXPORT statements use LDAP servers of your choice for database or EXAoperation accounts use standard repositories for the installation of UDF packages use the Exasol Version Check (only if this feature has not been disabled) 1. Configuration of VM network If not already done, import the Exasol OVA file into the VM tool of your choice (in Virtualbox: File -> Import Appliance). Accept the "End User License Agreement" and the "Privacy Statement" and wait until the image has been successfully loaded. Now, a new VM has been created. Change its network settings to use NAT (in Virtualbox: right click on VM -> Settings -> Network -> Adapter 1 -> Attached to NAT ) and define port forwardings to guest ports 8563 (database) and 443 (EXAoperation management interface) (in Virtualbox: Adapter 1 -> Port Forwarding -> Add rule -> Host Port 8563 and Guest Port 8563 -> Add rule -> Host Port 4443 and Guest Port 443). The port forwarding rules will enable you to use the VM from the physical host machine. Start the VM and wait until Exasol is up and running. 2. Configuration of DNS server Browse to EXAoperation and login. Go to Network. In the System tab, click on "Edit". Add one or two DNS servers reachable from the VM (e.g. "8.8.8.8" for an environment that can reach internet DNS servers) and click "Apply". Log out. Troubleshooting Firewalls and/or company proxy servers may block or restrict traffic to internet hosts.
    • Category 1:
      Cluster Administration

      Attachments

        Activity

          People

          • Assignee:
            CaptainEXA Captain EXASOL
            Reporter:
            CaptainEXA Captain EXASOL
          • Votes:
            1 Vote for this issue
            Watchers:
            2 Start watching this issue

            Dates

            • Created:
              Updated: