Add a Target Connector | QueryGrid - Adding a Target Connector - Teradata QueryGrid

QueryGrid™ Installation and User Guide - 3.06
Deployment
VantageCloud
VantageCore
Edition
Enterprise
IntelliFlex
Lake
VMware
Product
Teradata QueryGrid
Release Number
3.06
Published
December 2024
ft:locale
en-US
ft:lastEdition
2024-12-07
dita:mapPath
ndp1726122159943.ditamap
dita:ditavalPath
ft:empty
dita:id
lxg1591800469257
lifecycle
latest
Product Category
Analytical Ecosystem
  1. Under Fabric Configuration, select Fabrics and select a fabric to which you want to add a connector.
  2. Select the Connectors tab.
  3. Select the "" next to Connectors.
  4. Enter a name, up to 256 characters.
  5. Enter a description, up to 1,000 characters.
  6. In the System list, select a system to add this connector to.
  7. Next to Allowed OS users, select "" to add the allowed OS user.
    For more OS users information, see the information found under QueryGrid Security.
  8. Do one of the following:
    Option Description
    Select an existing connector software version
    1. From the Software Name list, select an existing software version.

      The list contains the connector software packages you uploaded earlier.
    Upload a new connector software version
    1. Next to the Software Name list, select "".
    2. Browse to the file and select Upload.
    3. From the Software name list, select the uploaded version.
    4. Select Save.
  9. In the Server box, enter the hostname of the server.
  10. Select "" next to Connector Software.
  11. In Select Connector Properties, do one or more of the following:
    Option Description
    Customize
    1. Select the check box to customize the values for a connector property.

      When the check box is cleared, QueryGrid uses the default values for a property.

    Teradata recommends focusing on correctly filling out the required connector properties as well as the security-related connector properties so that connections with the target data engine can be established and tested using the connector diagnostic check. For more information, see the target connector security guidelines in this guide for each type of target connector. The link can be further customized as more advanced connector properties are needed at both the connector and the link levels.
    Overridable
    1. [Optional] Select this check box for the connector property values to be overridden when a user initiates queries during individual processing sessions.
    After designating a property as overridable at the connector level, the property setting stays in effect even if you do not designate it as overridable at the link level in the Links tab.

    In order to disable the setting for an initiator or target connector, you must clear the check box at both the link level and connector level.

    For these reasons, consider designating a property as overridable only at the link level in the Links tab, depending on the requirements specific to the link.
  12. Select OK to save the configuration.
    Under Connector Software, all properties you set to customize appear.
  13. Modify each setting to govern how the connector operates.
    For complete descriptions of all properties for each connector type, see:
  14. Under Driver Nodes, do one of the following to designate where driver nodes are available:
    Option Description
    Make available on all nodes
    1. Select Make available on all nodes.
    Make available on selected nodes only
    1. Select Make available on selected nodes only.
    2. Choose Select Nodes.
    3. In the Available nodes filter box, enter the text and one or more wildcards to get a subset of the available nodes to display in the Available nodes list.
    4. Select "" to move the nodes you want from the Available nodes list to the Selected nodes list.
    5. Select Save.
    Use the following guide when making node selections:
    System Description
    Teradata Any Teradata node can be used as a driver node. Teradata recommends using the Limit the number of driver nodes to option when setting up the driver node.
    Hive For a node to be used as a driver node, the node must have the Hive Client package installed. When using EMR, only master nodes can be used as driver nodes.

    For HDI clusters where auto-scaling may occur on worker nodes, Teradata recommends choosing at least one non-worker node as a driver node. It is recommended to use the Limit the number of driver nodes to option when setting up the driver node, provided that the Hive Client requirement is met by all nodes that join the system in the future.
    Spark For a node to be used as a driver node, the node must have the SPARK_HOME environment variable set. When using EMR, only master nodes can be used as driver nodes.

    For HDI clusters where auto-scaling may occur on worker nodes, Teradata recommends choosing at least one non-worker node as a driver node. It is recommended to use the Limit the number of driver nodes to option when setting up the driver node, provided that the node requirement is met by all nodes that join the system in the future.
    Presto Any Presto node can be used as a driver node. Teradata recommends using the Limit the number of driver nodes to option when setting up the driver node.

    Consider the following if not using the dynamic driver nodes feature: For Presto clusters in the cloud where auto-scaling can occur on worker nodes, Teradata recommends choosing at least one coordinator node as driver node. Coordinator nodes can be destroyed and recreated under certain circumstances, in these situations Teradata recommends choosing the option Make available on all nodes to avoid any future QueryGrid outages.
  15. [Optional] From the Associated Viewpoint system list, select a Viewpoint system to associate with this connector.
    This association links Viewpoint monitored systems to QueryGrid queries in portlets, such as Query Monitor.
  16. Select Save.