Single Data Mover Host with Viewpoint Portlet
- Single Data Mover host with Data Mover daemon, single Data Mover agent
- Viewpoint host with Data Mover portlet
- Teradata Source/Teradata Target
- Embedded DSC on Data Mover host and ClientHandler on source or target Teradata TPA nodes
Host | Port | Connection Type | Notes |
---|---|---|---|
Data Mover | 61616 | TCP | If using embedded DSC on Data Mover host, the ClientHandler will connect to Data Mover host using port 61616. |
Viewpoint | 443 | HTTPS | If security is enabled, Data Mover will connect to Viewpoint host using port 443 (80 if using HTTP). |
Teradata Source/Teradata Target | 443/1025 | HTTPS/TCP | Data Mover will connect to Teradata Source/Teradata Target using HTTPS over port 443 if TLS 1.2 encryption is enabled. Otherwise TCP over port 1025 will be used. Viewpoint Data Mover portlet will connect to Teradata Source/Teradata Target using port 1025. |
Data Mover | 1443 | HTTPS | The Data Mover Viewpoint portlet will connect to the Data Mover host using Data Mover REST API port 1443. |
Server Management | 443/9981 | HTTPS | Data Mover will connect to Server Management using HTTPS using port 443 when using CMIC version 14.06.01 or later. Earlier versions of CMIC use port 9981. |
QueryGrid Manager | 9443 | HTTPS | Data Mover will connect to QueryGrid Manager for status on T2T jobs using HTTPS using port 9443. |
HA Data Mover Cluster
- Active Data Mover host with Data Mover daemon, single Data Mover agent
- Standby Data Mover host with offline Data Mover daemon, online single Data Mover agent
- Viewpoint cluster with each host having Data Mover portlet and Data Mover failover monitor
- Embedded DSC on both active and standby Data Mover host (only DSC on active Data Mover host online)
- ClientHandler on Teradata Source/Teradata Target TPA nodes
- Teradata Source/Teradata Target
If Data Mover failover occurs, the active and standby Data Mover host will switch roles. Therefore, when setting up ports, configure both active and standby Data Mover host in the same manner so that either can function as the active Data Mover host.
Host | Port | Connection Type | Notes |
---|---|---|---|
Active Data Mover Host | 61616 | TCP | If using embedded DSC on Data Mover host, the ClientHandler will connect to Data Mover host using port 61616. |
Active Data Mover Host | 22 | SSH | The Data Mover failover monitor running on Viewpoint hosts will connect to Data Mover host using port 22. The Data Mover cluster command running on standby Data Mover host will connect to Data Mover host using port 22. |
Active Data Mover Host | 5432 | TCP | The standby postgres sync running on standby
Data Mover host will connect to postgres logical sync
service using port 5432. The Data Mover failover monitor will run JDBC query to verify repo status by connecting to port 5432. |
Active Data Mover Host | 443 | HTTPS | The Data Mover Viewpoint portlet will connect to the Data Mover host using Data Mover REST API port 443. |
Active Data Mover Host | 9090 | HTTPS | Data Mover Agent on secondary Data Mover host will connect to DSA REST running on primary Data Mover host using port 9090. |
Standby Data Mover Host | 61616 | TCP | If using embedded DSC on Data Mover host, the Clienthandler will connect to Data Mover host using port 61616. |
Standby Data Mover Host | 22 | SSH | The Data Mover failover monitor running on Viewpoint hosts will connect to Data Mover host using port 22. The Data Mover cluster command running on standby Data Mover host will connect to Data Mover host using port 22. |
Standby Data Mover Host | 443 | HTTPS | The Data Mover Viewpoint portlet will connect to Data Mover host using DM REST API port 443. |
Standby Data Mover Host | 5432 | TCP | The Data Mover failover monitor will run JDBC query to verify repo status by connecting to port 5432. |
Standby Data Mover Host | 9090 | HTTPS | If failover occurs, external Data Mover Agent will connect to DSA REST running on secondary Data Mover host using port 9090. |
Primary Viewpoint Host | 443 | HTTPS | If security is enabled, Data Mover will connect to Viewpoint host using port 443 (80 if using HTTP). |
Primary Viewpoint Host | 22 | SSH | The Data Mover failover monitor running on secondary
Viewpoint host will connect to primary Viewpoint host using port 22. The Data Mover cluster command running on either active or standby Data Mover host will connect to Viewpoint host using port 22. |
Primary Viewpoint Host | 5432 | TCP | The Data Mover failover monitor will connect to Active Data Mover host to check whether repository is running using JDBC connection. |
Secondary Viewpoint Host | 443 | HTTPS | If security is enabled, Data Mover will connect to Viewpoint host using port 443 (80 if using HTTP). |
Secondary Viewpoint Host | 22 | SSH | The Data Mover failover monitor running on secondary
Viewpoint host will connect to primary Viewpoint host using port 22. The Data Mover cluster command running on either active or standby Data Mover host will connect to Viewpoint host using port 22. |
Secondary Viewpoint Host | 5432 | TCP | The Data Mover failover monitor will connect to standby Data Mover host to check whether repository is running using JDBC connection. |
Teradata Source/Teradata Target | 443/1025 | HTTPS/TCP | Data Mover will connect to Teradata Source/Teradata Target using HTTPS over port 443 if TLS 1.2 encryption is enabled. Otherwise TCP over port 1025 will be used. Viewpoint Data Mover portlet will connect to Teradata Source/Teradata Target using port 1025. |
Server Management | 443/9981 | HTTPS | Data Mover will connect to Server Management using HTTPS using port 443/9981.
|
QueryGrid Manager | 9443 | HTTPS | Data Mover will connect to QueryGrid Manager for status on T2T jobs using HTTPS using port 9443. |
Additional Configurations
Data Mover Command Line Running on External Client Host
- Data Mover CommandLine is installed on external client host and configured to connect to Data Mover host
- Host information has been added to the accept.host.list property. For more information on the Accept Host List, refer to the RESTFul API section of the Teradata® Data Mover User Guide, B035-4101
Host | Port | Connection Type | Notes |
---|---|---|---|
Data Mover | 1443 | HTTPS | The Data Mover CommandLine will connect to the Data Mover host (active or standby) using Data Mover REST API port 1443. |
Data Mover | 61616 | TCP | Data Mover REST and Data Mover daemon will connect to tdactiveMQ using port 61616. |
Client Calling Data Mover REST API from External Host
- The client is making REST calls to the Data Mover REST API from an external host
- Host information has been added to the accept.host.list property. For more information on the Accept Host List, refer to the RESTFul API section of the Teradata® Data Mover User Guide, B035-4101
Host | Port | Connection Type | Notes |
---|---|---|---|
Data Mover | 1443 | HTTPS | The client will connect to the Data Mover host using port 1443. |
Data Mover Using Embedded DSC
- Data Mover is configured to use embedded DSC running on Data Mover host
Host | Port | Connection Type | Notes |
---|---|---|---|
Data Mover | 61616 | TCP | DSA NC (network client), DSMain connecting to tdactiveMQ to communicate with DSC. |
Data Mover | 9090 | HTTPS | Internal connection in this configuration. Data Mover will connect to DSA REST on same server using port 9090. |
Data Mover | 1443 | HTTPS | Internal connection in this configuration. DSC will connect to DM REST on same server using port 1443. |
Teradata TPA Node | 15401 | TCP | DSMain connecting to DSA NC (assuming NC is
installed on TPA node). DSA NC connecting to other DSA NC on other TPA nodes (assuming NC installed on TPA node). |
Teradata TPA Node | 443/1025 | HTTPS/TCP | Data Mover will connect to Teradata Source/Teradata Target using HTTPS over port 443 if TLS 1.2 encryption is enabled. Otherwise TCP over port 1025 will be used. |
Data Mover Using External DSC
- Data Mover is configured to use external DSC running on an external host
Host | Port | Connection Type | Notes |
---|---|---|---|
Data Mover | 1443 | HTTPS | The external DSC will connect to Data Mover host using port 1443. |
DSC | 9090 | HTTPS | Data Mover will connect to the DSC host using port 9090. |
DSC | 61616 | TCP | DSA NC, DSMain connecting to tdactiveMQ to communicate with DSC. |
Teradata TPA Node | 15401 | TCP | DSMain connecting to DSA NC (assuming NC
installed on TPA node). DSA NC connecting to other DSA NC on other TPA nodes (assuming NC installed on TPA node). |
Teradata TPA Node | 443/1025 | HTTPS/TCP | Data Mover will connect to Teradata Source/Teradata Target using HTTPS over port 443 if TLS 1.2 encryption is enabled. Otherwise TCP over port 1025 will be used. |
Data Mover Using QueryGrid 2.x+
- Data Mover is configured to use QueryGrid 2.x and therefore is configured to call QueryGrid Manager on an external host
Host | Port | Connection Type | Notes |
---|---|---|---|
QueryGrid Manager | 9443 | HTTPS | Data Mover will connect to the QueryGrid Manager host using port 9443. |
Internal Connections on Data Mover Host
- Data Mover host with Data Mover daemon, single Data Mover agent
- Embedded DSC
Host | Port | Connection Type | Notes |
---|---|---|---|
Data Mover | 61616 | TCP | The Data Mover daemon, Data Mover agent, Data Mover TPT Executor, Data Mover REST, DSA REST, and DSC all connect to tdactiveMQ using port 61616. |
Data Mover | 5432 | TCP | The Data Mover daemon and DSC connect to the local Teradata repository using port 5432. |
Data Mover | 1443 | HTTPS | The DSC and Data Mover CommandLine connects to Data Mover REST using port 1443. |
Data Mover | 9090 | HTTPS | The Data Mover daemon and Data Mover agent connect to DSA REST using port 9090. |