Skip to end of metadata
Go to start of metadata

You are viewing an old version of this page. View the current version.

Compare with Current View Page History

« Previous Version 5 Next »

An example topology for an environment using the following technologies:

  • Citrix desktop virtualisation

  • Atlassian Bitbucket Git repository

  • Atlassian Jira work item management platform

  • Jenkins build tool

Components connections

  1. The Citrix client running on your Developer Workstation presents a virtualised DataStage Designer client to your Developer

  2. Depending upon your Citrix configuration, the MettleCI menu items in the virtualised DataStage client invoke the MettleCI Workbench interface in a virtualised browser window served by Citrix, or…

  3. .. in a native browser window on your Developer Workstation. In either case this communicates (over ports you configure) with the MettleCI Workbench Service running on your DataStage Engine.

  4. Your Git tool (e.g. Atlassian Bitbucket) can be accessed from your Developer Workstation by configuring network access to the the relevant host ports.

  5. Your work item management tool (e.g. Atlassian Jira) can be accessed from your Developer Workstation by configuring network access to the the relevant host ports.

  6. Your build tool (e.g. Jenkins) can be accessed from your Developer Workstation by configuring network access to the the relevant host ports.

  7. The virtualised DataStage Designer client running on Citrix will need regular access to DataStage Service and Engine tiers, as documented by IBM.

  8. Your MettleCI Workbench will need network access to your Jira server to perform Work item lookup from the Workbench’s Git Commit page.

  9. Your MettleCI Workbench will need network access to your Bitbucket server to commit work to your Git repositories.

  10. The Jenkins Controller running on your Jenkins host will need network access to your Bitbucket instance to poll for, and retrieve, changes to your Git repositories

  11. The Jenkins Controller running on your Jenkins host will need network access to the Jenkins Agent running on the MettleCI Agent Host.

  12. The Jenkins Agent, MettleCI CLI, and DataStage Client programs running on the MettleCI Agent Host will require network access to the DataStage Service and Engine tiers.

  • No labels