Configure and Register Data Gateway for Reporting

Perform these optional steps to enable remote connectivity for Classic features such as analyses and dashboards.

If you're only deploying for data visualization (for example, Oracle Analytics Cloud Professional Edition), then you don't need to follow these steps.
Before you start, follow the configuration steps in Configure Data Gateway for Data Visualization.
  1. On the machine where you've installed a Data Gateway agent, obtain the machine name and port number.
    In a server deployment:
    1. Execute the command /<Data Gateway install folder>/domain/bin/status.sh.
    2. In the command output, note the machine name contained within the URL displayed under Data Gateway Status, and note the Data Gateway Jetty HTTP Port value.
    In a personal deployment:
    1. Open the file: %localappdata%\Temp\DataGateway\ports.properties.
    2. Note the machine name and port number.
  2. Start the Data Gateway agent.
  3. If you want to model your data before you start connecting to it remotely, use Semantic Modeler or Model Administration Tool (if the database isn't supported by Semantic Modeler) to edit your semantic model.
  4. If you're using Model Administration Tool, load the Java data source metadata.
    1. In Model Administration Tool, from the File menu, click Open, then In the Cloud, and use the Open in the Cloud dialog to specify the details of your semantic model.
    2. From the File menu, click Load Java Data Sources.
    3. At the Connect to Java Datasource Server dialog:
      • In the Hostname field, enter the machine name that you noted in Step 1. Fully qualify the hostname. For example, if you noted machine in Step 1, you might specify machine.us.example.com.
      • In the Port field, enter the port that you noted in Step 1. For example, 51811.
      • In the Username and Password fields, enter dummy or any string (these credentials aren't validated because this is a public call to discover the capabilities advertised by the Data Gateway).
  5. If you're using Model Administration Tool, set up a physical database connection:
    1. In the Physical layer, create a local (not remote) connection to your data source using the standard call interface appropriate for your data source, and model the data as required.
    2. When you're ready to make a remote connection to your semantic model and publish it back to the cloud, edit the connection that you created.
    3. On the General tab, in the Call interface field select JDBC (Direct Driver), and in the Connection String field, specify the JDBC string and credentials in the semantic model connection. See JDBC and JNDI Templates and Examples below for a list of supported JDBC strings and driver classes.
    4. On the Miscellaneous tab, in the Use SQL Over HTTP field enter true, and in the RDC Version field enter 2, and specify the JDBC driver class.
    5. Publish the semantic model to the cloud.
You're now ready to test your deployment by connecting remotely to an on-premises database.

JDBC and JNDI Templates and Examples

When you set up remote connectivity for analyses and dashboards, you might have to specify JDBC strings and driver classes, and JNDI connection details and context details.

JDBC String Patterns and Driver Classes
JNDI Templates for Native Drivers
JNDI Templates for DD Drivers

Add a JDBC Driver to Data Gateway

Add a JDBC driver to your Data Gateway installation so that you can model data in an on-premises database.

Before you start, ensure that Data Gateway and Model Administration Tool are installed on the same Windows computer in your on-premises environment.
  1. Download the JDBC driver that you want to deploy.
    For example, to model data in a Snowflake database, download the latest Snowflake JDBC driver (for example, in file snowflake-jdbc-3.9.0.jar).
  2. Copy the downloaded JDBC JAR file to the Data Gateway installation folder.
    • In a server deployment, copy the JAR file into: <Data Gateway install_location>/domain/jettybase/thirdpartyDrivers.
    • In a personal deployment on Windows, copy the JAR file into: <Data Gateway_extract_path>\thirdpartyDrivers.
    • In a personal deployment on MacOS, copy the JAR file into: <Application->Show Package Contents>Resources->app.nw-> thirdpartyDrivers.
  3. Re-start Data Gateway. See Maintain Data Gateway.

DSN Formats for Specifying Data Sources

In Oracle Analytics you can model your on-premises data for many database types. Oracle Analytics supports direct access to some on-premises data sources through the semantic model. When you create the database connection using Model Administration Tool, in the Data source name field on the Connection Pool dialog (General tab) you use the appropriate DSN format for the database type you're connecting to. 

Amazon Redshift:
       DRIVER=Oracle 7.1 Amazon Redshift Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"]
      SSL: DRIVER=Oracle 7.1 Amazon Redshift Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"];EM=6;CPV=TLSv1.2,TLSv1.1,TLSv1, SSLv3, SSLv2;VSC=0
Apache Drill:
       DRIVER=MapR Drill ODBC Driver;Host=["host-name"];Port=["port"];CastAnyToVarchar=true;ExcludedSchemas=sys,INFORMATION_SCHEMA;AuthenticationType=Basic               Authentication;ConnectionType=Direct
Aster:
       DRIVER=Aster ODBC Driver;SERVER=["host-name"];PORT=["port"];DATABASE=["service-name"]
DB2:
      DRIVER=Oracle 7.1 DB2 Wire Protocol;IpAddress=["host-name"];PORT=["port"];DB=["service-name"]
      SSL:  DRIVER=Oracle 7.1 DB2 Wire Protocol;IpAddress=["host-name"];PORT=["port"];DB=["service-name"];EM=1;VSC=0
Greenplum:
       DRIVER=Oracle 7.1 Greenplum Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"]
Hive:
       DRIVER=Oracle 8.0 Apache Hive Wire Protocol;HOST=["host-name"];PORT=["port"]
      SSL: DRIVER=Oracle 8.0 Apache Hive Wire Protocol;HOST=["host-name"];PORT=["port"];EM=1;VSC=0
Impala:
       DRIVER=Oracle 7.1 Impala Wire Protocol;HOST=["host-name"];PORT=["port"]
     SSL:  DRIVER=Oracle 7.1 Impala Wire Protocol;HOST=["host-name"];PORT=["port"];EM=1;VSC=0
Informix:
       DRIVER=Oracle 7.1 Informix Wire Protocol;HOSTNAME=["host-name"];PORTNUMBER=["port"];DATABASE=["service-name"]
MongoDB:
       DRIVER=Oracle 8.0 MongoDB;HOST=["host-name"];PORT=["port"];DB=["service-name"]
MySQL:
      DRIVER=Oracle 7.1 MySQL Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"]
PostgresSql:
       DRIVER=Oracle 7.1 PostgreSQL Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"]
Spark:
      DRIVER=Oracle 8.0 Apache Spark SQL;HOST=["host-name"];PORT=["port"]
      SSL:  DRIVER=Oracle 8.0 Apache Spark SQL;HOST=["host-name"];PORT=["port"];EM=1;VSC=0
SQL Server:
     DRIVER=Oracle 7.1 SQL Server Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"]
     SSL:  DRIVER=Oracle 7.1 SQL Server Wire Protocol;HOST=["host-name"];PORT=["port"];DB=["service-name"];EM=1;VSC=0;CryptoProtocolVersion=TLSv1.2,TLSv1.1,TLSv1,SSLv3,SSLv2
Sybase:
       DRIVER=Oracle 7.1 Sybase Wire Protocol;NA=["host-name"], ["port"];DB=["service-name"]
Teradata:
       DRIVER=Oracle 7.1 Teradata;DBCName=["host-name"];port_name=["port"]