...

Introduction

Components featuring on this page are described in MettleCI Topology Components.

A single MettleCI Agent Host for everything

This is the default (and simplest) topology to use when it’s permissible for a single MettleCI Agent host to connect to every DataStage environment and network zone.

• The Information Server environment can be deployed using a 1-tier, 2-tier, or 3-tier architecture. Common best practise places the Engine tier on a dedicated host, and the Services and Repository tiers together on a separate host.

• The MettleCI Workbench Service runs (in this topology) on a Unix-based DataStage Engine tier. This is because this service requires a shared filesystem with the MettleCI Unit Test Harness which can only be installed on the Engine tier.

• The MettleCI Agent host is a dedicated host reserved exclusively for use by your selected CI/CD build tool via the installed CD/CD agent. The MettleCI CLI is used by the CI/CD Agent to automate build and deployment activities. The MettleCI CLI and Agent need to be installed on a Windows host co-resident with a DataStage Client tier in order to enable the automation of the DataStage job compilation process, which requires the use of a Windows-based Client tier.

Separate MettleCI Agent Hosts per network zone

Separate MettleCI Agent Hosts per network zone

This topology is appropriate when it’s not permitted for a single MettleCI Agent host to connect to every DataStage environment and network zone. In particular, this topology is useful when a single instance of a CI/CD Agent is not permitted to access non-Production and Production environments/network zones.

Using a separate MettleCI Agent Host per network zone

Separate MettleCI Agent Hosts per DataStage environment

This topology is appropriate when each DataStage environment requires its own MettleCI Agent host, usually as a result of organizational security policies.

...