Teradata users must map a JDBC data source to a relational database in the ais.cfg file in order to use the XML Import/Export feature of Integration Services. Teradata requires JDBC Type 3 .
To map a data source, edit the ais.cfg file (located in products/Essbase/eis/server/bin) using any text editor. If the ais.cfg file does not exist, use a text editor to create and edit it, and then save it in products/Essbase/eis/server/bin.
Multiple OLAP Metadata Catalogs can be mapped under the [JDBC DSN] heading. If you want to comment out certain data sources in a list of data sources, insert the pound sign (#) as the first character in a line. (See the data source mapping examples that follow.)
The following syntax provides usage examples for editing ais.cfg to connect to a Teradata or an Oracle relational data source.
Syntax
[JDBC DSN] <Teradata ODBC DSN>:<Gateway Host>/<Port # on Gateway>/<Server Host> oracle:<tnsname | oname>:<host name>:<port #>:<SID>
Command | Description |
|---|---|
[JDBC DSN] | (Required) Available by default |
For Teradata: | |
Teradata ODBC DSN | The name of the Teradata data source used as the OLAP Metadata Catalog in Integration Services |
Gateway Host | The host on which the Teradata JDBC Type 3 driver is configured and the Jserver is running |
Port # on Gateway | Port number of the Gateway host |
Server Host | The host on which the Teradata server resides |
For Oracle: | |
tnsname | The name of the Oracle Net Service Name (found in $ORACLE_HOME/network/ admin/tnsnames.ora) used as the OLAP Metadata Catalog in Integration Services |
oname | The Schema Name used to connect to an Oracle database if you are using onames instead of tnsnames This is the database identifier that you use when you are using SQL *Plus to connect to the database. |
host name | The host on which the Oracle server is installed and running |
port # | Port number of the host on which the Oracle server is configured |
SID | The server identifier for Oracle on host <host name> |
In the following examples for mapping a JDBC data source for Teradata and Oracle, note that the pound sign (#) at the beginning of a line indicates that the line has been commented out.
Example of JDBC Type 3 Settings for Teradata
[JDBC DSN] td_catalog_dsn:labmachine1:6063/teradataServer #tbc_md:labmachine1:6063/tera1 td_tbc_md:labmachine1:6063:tera1/
Example of JDBC Type 4 Settings for Oracle
[JDBC DSN] oracle:ora_tbc_md:labmachine2:1521:orasid #oracle:tbc_md:labmachine2:1521:orasid
When using Oracle with tnsnames, if the definitions for tnsname, host name, port #, and SID elements do not match the corresponding elements of a Net Service Name stanza in the tnsnames.ora file, a Java environment error results. The preceding JDBC settings example is built using the elements in the following tnsnames.ora stanza:
ora_tbc_md = (DESCRIPTION = (ADDRESS_LIST = (ADDRESS = (PROTOCOL = TCP)(HOST = labmachine2)(PORT = 1521)) (CONNECT_DATA = (SERVICE_NAME = orasid) )
When using Oracle with onames, in the example above, ora_tbc_md is the Schema Name used to connect to an Oracle database. This is the database identifier that you use when you are using SQL*Plus to connect to a database.