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 4 Current »

No.

MettleCI has no requirement or mechanism to ‘phone home’ over the internet to any Data Migrators owned or managed services or infrastructure. It also doesn’t contact any other services outside of its own hosts (within the customer’s infrastructure) or the customer’s DataStage Engine and Services Tier hosts. The only exceptions are:

  • Where a customer wants MettleCI to integrate with a SAAS provider of Git services (e.g. Bitbucket Cloud, Gitlab)

  • Where a customer wants MettleCI to integrate with a SAAS provider of work item management services (e.g. Atlassian Jira Cloud, Azure DevOps).

In both those cases that would be a conscious decision by the customer requiring the necessary acknowledgment of all parties as to responsibilities for data flowing between infrastructure component. This isn’t the case with NJ Courts as those functions will be provided but the Atlassian software we install in there infrastructure (i.e. not on the IBM Cloud).

Install/Upgrade

To perform MettleCI installation customers must download the relevant installation packages from the relevant Data Migrators website and copy them to the relevant target hosts within their infrastructure. There is no external calling required or performed either during or after the installation.

Licensing

MettleCI licenses are provided as files attached to a registration email. MettleCI components use this file to understand which MettleCI functions should be exposed to users, and when access to those functions expire. At no point does the licensing process require access to the internet, with the exception of your MettleCI administrator receiving a refreshed licence email.

  • No labels