Overview of Universal Connector architecture

(BMC.DB2.SPE2304)

The BMC AMI DevOps Universal Connector (UC) application is a containerized application that is designed for easy integration with continuous integration (CI) applications. CI applications support the running of the pipeline or workflow in a container environment by any agent or runner, including a self-hosted agent or runner. The UC application image name is defined in the CI pipeline or workflow configuration file. A self-hosted agent or runner is installed and configured for the CI application in a VM that has access to the CI application server and z/OSMF server.

Related topic

Getting-started

This section provides information about the following topics:

Integrating Universal Connector with Azure DevOps

The UC application image can be used in the Azure DevOps pipeline configuration. The pipeline creates the container and runs UC application steps inside the container. The following figure depicts the process for integrating UC with the Azure DevOps application:

UC CI application.drawio.png

This process involves the following steps:

  1. Run the Azure DevOps pipeline by committing any change in the Git repository file, or other Azure DevOps supported repository file, via a trigger or manual run. 
  2. The pipeline service gets the self-hosted agent and pipeline information from the pipeline configuration file in the Git repository.
  3. The pipeline service assigns the self-hosted agent to run the pipeline execution.
  4. The self-hosted agent connects to the Container Registry server that hosts the image.
  5. The self-hosted agent pulls the Container image from the Container Registry.
  6. The self-hosted agent creates the Container from the pulled image.
  7. The self-hosted agent checks out (downloads) all files from the Git repository to the Container workspace.
  8. The self-hosted agent runs UC application steps as defined in the pipeline configuration. The UC application communicates with the z/OSMF server and performs the required operation. 

(BMC.DB2.SPE2307)

Integrating Universal Connector with GitHub Actions

The UC application image can be used in GitHub Actions workflow configuration. The workflow creates the container and runs UC application steps inside the container. The following figure depicts the process for integrating UC with GitHub Actions application:

UC GHA CI application.drawio.png

This process involves the following steps:

  1. Run the GitHub Actions workflow by committing any change in the GitHub repository file, via a trigger or manual run. 
  2. The workflow service gets the self-hosted runner and workflow information from the workflow configuration file in the Git repository.
  3. The workflow service assigns the self-hosted runner to run the workflow execution.
  4. The self-hosted runner connects to the Container Registry server that hosts the image.
  5. The self-hosted runner pulls the Container image from the Container Registry.
  6. The self-hosted runner creates the Container from the pulled image.
  7. The self-hosted runner checks out (downloads) all files from the Git repository to the Container workspace.
  8. The self-hosted runner runs UC application steps as defined in the workflow configuration. The UC application communicates with the z/OSMF server and performs the required operation.

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*