The following table describes which interactions take place between the software components listed above, and which functions those interactions support. Note that if a component or protocol isn't specified then it’s either irrelevant to MettleCI, or MettleCI can re-use whatever your infrastructure dictates.
Connection |
First Host - Application |
Second Host - Application |
Protocol(s) |
Authentication |
Related MettleCI Function(s) |
Comments |
|---|---|---|---|---|---|---|
1 |
DataStage Development Engine Tier - MettleCI Workbench Service |
Git Host - Git service |
SSH (default), HTTP(S) |
Git user credentials. See relevant build tool pages here. |
Commit |
See Configuring MettleCI Workbench to communicate with Git over HTTPS |
2 |
DataStage Development Engine Tier - MettleCI Workbench service |
Work item Management Host - Work Item Management service |
Work item Management service-dependent |
Work item Management service’s API. See relevant pages here. |
Dynamic Work item lookup during Commit |
'Work Item Management service' means Jira, Service Now, etc. The ports and protocols depend upon your selected tool. See these pages for more details. |
3 |
Developer Workstation - Web browser |
Git Host - Git service |
HTTP(S) |
Git user credentials |
Git tasks |
|
Developer Workstation - Web browser |
Work item Management Host - Work Item Management service |
HTTP(S) |
Work Item Management user credentials |
Work Item Management tasks |
||
Developer Workstation - Web browser |
Build Host - Build Tool controller |
HTTP(S) |
Build tool user credentials |
Build tasks |
||
4 |
Developer Workstation - Web browser |
DataStage Development Engine Tier - MettleCI Workbench Service |
HTTP(S) |
DataStage user credentials |
|
Ports are configurable in the MettleCI configuration file. |
Developer Workstation - Web browser |
DataStage Development Engine Tier - MettleCI Workbench Service |
SSH |
DataStage Development Engine Tier O/S user credentials |
|
OPTIONAL |
|
5 |
Developer Workstation - Remote Desktop |
MettleCI Agent Host - Microsoft Windows |
RDP |
MS Windows |
Configuration and diagnostics |
OPTIONAL Required during setup, but Developers shouldn’t require this access on a day-to-day basis. |
6 |
Built Host - Build Tool Controller |
MettleCI Agent Host - Built Tool Agent |
Build tool dependent |
Build tool dependent |
Build Controller can execute pipelines requiring a ‘MettleCI Command Line Interface’ capability |
See the documentation of your chosen build tool |
7 |
MettleCI Agent Host - Built Tool Agent |
DataStage Development Engine Tier |
DataStage (IBM-specified), SCP, SSH |
DataStage user credentials. Various authentication mechanisms required by each MettleCI Commands. See this page for details on each command. |
|
This link will use the same ports and protocols that the customer uses for its standard installation of the DataStage Client on end-user hardware, as well as SCP and SSH for certain MettleCI Commands. |
MettleCI Agent Host - DataStage Client Tools |
DataStage Development Services and Engine Tiers |
DataStage (IBM-specified) |
IBM-specified |
Normal DataStage Client operations |
This link will use the same ports and protocols that the customer uses for its standard installation of the DataStage Client on end-user hardware. |
|
8 |
MettleCI Agent Host - Built Tool Agent |
DataStage Testing (and potentially Production) Services and Engine Tiers |
DataStage user credentials. Various authentication mechanisms required by each MettleCI Commands. See this page for details on each command. |
|
This link will use the same ports and protocols that the customer uses for its standard installation of the DataStage Client on end-user hardware. |
