Introduction

This document describes the hardware, software, and network configuration that needs to be in place before MettleCI can be deployed and configured in your environment. The platform delivered will include all MettleCI software, and will interface with your nominated non-production Information Server environment to enable the demonstration of all of MettleCI's capabilities.

The deployment topology of a MettleCI platform, whether being used for evaluation or production purposes, has been deliberately designed to be as simple as possible. The biggest difference between evaluation and production deployments of MettleCI is the selection of software components residing on the dedicated MettleCI Host that would be better deployed to separate servers. Alternatively, some components of the MettleCI stack could be delivered by integrating with existing solutions already in place in your organisation. While MettleCI is easily integrated with Customers' existing Jira, Git, and Bamboo instances, describing the full range of integration options available is beyond the scope of this document.

The delivered architecture will focus on evaluation purposes only, and has been designed for ease and speed of deployment. The evaluation will validate which parts of this architecture could be re-used for a MettleCI production deployment, and which may need to be re-deployed or reconfigured to meet your organisational requirements.

Whilst not representing our recommended production deployment of MettleCI, this MettleCI architecture assembles all of the software forming MettleCI's DevOps platform for Information Server into a single, pre-configured, easily deployed package. This optimises the time spent on the evaluation process.

See also

MettleCI Platform Components

The following high-level MettleCI architecture shows the key software components to be installed, and their communications between hosts. 

In-scope Hosts

Developer's Workstation: Where the Windows DataStage Designer client is typically run

Application Lifecycle Management Tools: One or more hosts running Work Item Management, Git, and Build services

Information Server Development Environment: Your development instance of Information Server, which may be deployed in any topology, and on any number of hosts.

Information Server Test Environment(s): Downstream Information Server environments sitting between Development and Production.

MettleCI Host: A Windows server hosting an IBM DataStage client tier which is used by your Azure Agent, in conjunction with the MettleCI Command Line Interface, to automate build and deployment activities.

Connections

1. here
2. here
3. here
4. here
5. here
6. here
7. here
8. here

Some points to note:

• MettleCI works with all Information Server deployment topologies, including High Availability, Grid, and Cluster environments, For clarity, this diagram shows each tier residing on its own, dedicated host.
• Application Lifecycle Management components can be co-hosted with the other tools on the MettleCI Host or located on another host (on-premise, cloud or SaaS).

Component Connections

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.