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 3 Next »

A description of how you can configure multiple MettleCI Agents Hosts when you need to segregate agent access by DataStage environment or network zone.

A single MettleCI Agent Host for everything

  • 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

Using a separate MettleCI Agent Host per network zone

Separate MettleCI Agent Hosts per DataStage environment

Configuring pipeline activity to the appropriate Agent host

The following links describe how various build tools provide support for specifying which pipeline activities are assigned to which build Agent/Runner.

  • No labels

© 2015-2024 Data Migrators Pty Ltd.