Configure ServiceConnect | Test ServiceConnect | Teradata Vantage on Azure (DIY) - Configuring or Testing ServiceConnect - Teradata Vantage on Azure

Teradata Vantageā„¢ on Azure (DIY) Installation and Administration Guide

Product
Teradata Vantage on Azure
Release Number
2.2
Published
September 2021
Language
English (United States)
Last Update
2021-09-24
dita:mapPath
djf1623284042771.ditamap
dita:ditavalPath
fon1623285509395.ditaval
dita:id
B035-2810
lifecycle
previous
Product Category
Cloud
Prerequisite You must have a site ID to configure or test Teradata ServiceConnect.
[Enterprise, Advanced, Base tiers only] Teradata ServiceConnect allows Teradata Services to connect to your site. Use the Server Management portlet in Teradata Viewpoint to configure ServiceConnect.
  1. Open a Teradata Services incident with a synopsis of Validation Request for Teradata Server Management on Azure Teradata Configuration.
    Teradata Services obtains permission to access your Azure configuration, confirms that connectivity is functioning, and closes the incident.
    This process can take up to five days.
  2. From the Azure portal, note the private IP address of the first CMIC.
  3. Open a browser and go to the Web Client.
    https://<hostname or the IP address CMIC>:9981
    Any CMIC can be used.
  4. In the Web Client, select "" > Settings > General.
  5. Verify the SiteID and update as needed.
  6. Click Configure. The following occurs:
    • One or more CMICs are selected to have gateways configured.
    • The connection is tested on each CMIC to make sure the Axeda Enterprise can be reached.
    • File uploads are tested by running commands to generate files.
    When ServiceConnect is not configured on a CMIC, you will see the Configure button. After the first ServiceConnect gateway is configured, the Add Gateway button appears, allowing you to add more gateways to your configuration.
  7. If unable to reach the Axeda Enterprise, you will see a red indicator letting you know there is no connection. This is most likely because the CMIC does not have a network path to the Enterprise. You can choose to resolve this now, or remove any non-functional gateways.
  8. When one or more gateways have been configured, you can do the following: