Application Server Configuration

Extensibility
Extensibility covers the mechanisms by which you, as the user or developer, can extend the functionality of the Teradata Database, for example with the use of User Defined Functions, or UDFs.
Teradata Employee

Application Server Configuration

This section describes configuration of the application server.

Overall Process

  1. Setup JDBC Connection.
  2. Setup Source JMS Queue or Topic for Loader (optional)
  3. Setup Target JMS Queue or Topic for Extractor (optional)
  4. Deploy the war file or ear file.

JDBC Connection

The JDBC Connector consists of two parts:

  1. JDBC Connector Driver
  2. JDBC Connector DataSources

Both parts must be configured for this application to work.

Note: The JDBC Connector Driver must be setup prior to configuring your DataSources. 

JDBC Driver Installation

  • Download the JDBC driver package.
  • Unzip the contents of the package.
  • Follow the "How-To" Guide for your specific application server.

JDBC Connector DataSources

Prerequisites

This guide assumes that you have downloaded and setup the Teradata JDBC driver in your Application Server (see above).

Setting Up the Data Source for the System Repository.

  • The JNDI Name for the system repository must be jdbc/com.teradata.terajmsa.MetaDS.
  • JNDI names are case sensitive.
  • User ID and Password will be required to create jdbc/com.teradata.terajmsa.MetaDS.
  • Meta data tables will be created as below where “Database” field is specified when the JMS Universal Connector is deployed
    • TERAJMS_STATUS
    • TERAJMS_ALIAS
    • TLOADER_ALIAS_MAP
    • TLOADER_PROPERTIES_MAP
    • TLOADER_SERVICE_MAP
    • TROUTER_ALIAS_MAP
    • TROUTER_PROPERTIES_MAP
    • TROUTER_SERVICE_MAP

Database Account Permissions for the Administration UI

  • TD user id is required to login to the Administration UI and this user id needs to have the “select” permission on the system repository, which is the database accessed by the data source, jdbc/com.teradata.terajmsa.MetaDS.

Database Account Permissions for the Loader and the Extractor

  • Each loader and extractor service can have their own data source.
  • For the loader services, the user account in the data source needs to have the “Select” and “Insert” permissions on the database referenced by this data source.
  • For the extractor services, the user account in the data source needs to have the “Select” and “Delete” permissions on the database referenced by this data source.

Special attention for User permissions in WebLogic and Tomcat

  • Please refer to WebLogic User and Password Configuration in the Using the Administration UI. (See Page 29)
  • Please refer to Deployment on Apache Tomcat Application Server. (See Page 39)