The following diagram is one possible configuration, and is presented as an example for further architecting. The number of IS environments, for example, and how many tiers they use, is notional
| Gliffy | ||||||||||
|---|---|---|---|---|---|---|---|---|---|---|
|
In-scope Hosts
Jenkins Host: Where the Jenkins controller (providing build/deploy services as part of ALM) is run
Developer's Workstation: Where the Windows DataStage Designer client is typically run
Application Lifecycle Management Tools: One or more hosts running Work Item Management, and Git services
Information Server Development Environment: Your development instance of Information Server, which may be deployed in any topology, and on any number of hosts.
Other Information Server Environment(s): Downstream Information Server environments, including testing and (optionally) Production. These environments can be MettleCI deployment targets without requiring the deployment of any MettleCI components.
MettleCI Host: A MettleCI-dedicated Windows server hosting an IBM DataStage Client tier which is used by your Build system's agent, in conjunction with the MettleCI Command Line Interface, to automate build and deployment activities.
Connection descriptions
# | Summary | Description | Technical |
|---|---|---|---|
1 | MettleCI Workbench Service (Engine Tier) ↔︎ Your Work item Management system | The MettleCI workbench is configured to perform a dynamic lookup of work items as part of the Git Commit process. Currently supported work item management systems are listed here. | The Workbench service on your DataStage Engine tier needs to be able to use your Work Item Management system’s query API, over whatever protocols/ports it requires. |
2 | MettleCI Workbench Service (Engine Tier) ↔︎ Your Git Repository | The MettleCI Workbench application running on your DataStage Engine tier needs to performs a commit to your Git platform | |
3 | Jenkins Host ↔︎ Your Git repository | Jenkins can keep pipeline definitions (as jenkinsfile files) in a repo so they can be versioned the same as the artifacts | |
4 | Jenkins Host ↔︎ DataStage designer client (developer workstation) | Web access to Jenkins by developers | |
5 | Jenkins Host ↔︎ DataStage designer client (MettleCI host) | Jenkins controller issues commands to the Jenkins Agent to perform MettleCI related tasks such as code movement, and DataStage deployment (project manipulation, job compliation) | |
6 | Developer Workstation ↔︎ IS/DS Service/Engine tiers | Normal developer activity such as editing jobs, test compilations, etc | |
7 | |||
8 | |||
9 | |||
10 |