12.04 - Setting Up Teradata ServiceConnect - Server Management

Teradata Server Management Web Services User Guide

prodname
Server Management
vrm_release
12.04
created_date
January 2017
category
User Guide
featnum
B035-5350-017K
Make sure your site ID is configured before starting this procedure. Contact Teradata Customer Service if you need assistance.
  1. From the Teradata Viewpoint portal page, click .
  2. Open the Server Management portlet.
  3. From the Configure list, click ServiceConnect.
  4. Log in to Teradata ServiceConnect. The Teradata ServiceConnect details appear. If the system was previously set up with a site ID, the SiteID box is populated.
  5. Do one of the following:
    ServiceConnect Description
    If ServiceConnect has not been configured
    1. Click Create Connection.

      A connection is created, devices are configured, and an alert is generated. If no SM_LOG alert action set is defined, one is created for all times (Core, Evening, Weekend) and includes the log action in the Alert Viewer portlet. If no ALL alert is defined for Server Management, one is created and enabled for all SiteIDs, and sends a notification when updates occur.

      After you create a connection, the connection is tested as part of the process so there is no need to click Test Connection afterwards.

    If ServiceConnect is configured
    1. Click Test Connection.

      An Asset Baseline and Alert Escalation Test is run.

      • If the test connection is successful, verify an email was received.
      • If the Asset Baseline fails, contact Teradata Customer Support.
      • If the Alert Escalation fails, verify all nodes are in an operational state and test the connection again. If it fails a second time, contact Teradata Customer Support.
  6. [Optional] If you require outgoing connections to go through a proxy server, click Advanced options and do the following: If you enable Proxy Auto-Configuration, you cannot enable the HTTP Proxy or SOCKS Proxy. However, you can complete the authentication fields for either if the .pac file points to a proxy server that requires this information. If you have a *.pac file at a known URL, you can configure it, along with any authentication for the HTTP and SOCKS servers, if required.
    Proxy Options Description
    Auto-Configuration
    1. Under Proxy Auto-Configuration, select Enable if you have an automatic proxy configuration script.
    2. In the URL box, type the IP address of your proxy server.

      The format is http://proxy server IP Address/*.pac file path .

    HTTP
    1. Under HTTP Proxy, select Enable.
    2. In the Host IP Address box, type the IP address of the HTTP proxy host.

      The IP address must be a valid IPv4 or IPv6 address. If it is IPv4, it is pinged to ensure the connection is valid.

    3. In the Port box, type the port number for the HTTP proxy.
    4. If credential authentication is required, click Authenticate using the following information, and type the log-in credentials.
    SOCKS
    1. Under SOCKS Proxy, select Enable.
    2. In the Host IP Address box, type the name or address of the SOCKS proxy host.

      The IP address must be a valid IPv4 or IPv6 address. If it is IPv4, it is pinged to ensure the connection is valid.

    3. In the Port box, type the port number for the SOCKS proxy.
    4. If credential authentication is required, click Authenticate using the following information, and type the log-in credentials.
  7. Click Apply.
  8. [Optional] From the Configure list, click Alerts to further configure the alerts. Action sets that are configured in the Alert Setup portlet are displayed in the Alert Actions list in the Server Management portlet.
  9. Click Close.