Overview of Universal Connector architecture

This section provides information about the following topics:

• Integrating Universal Connector with Azure DevOps
• Integrating Universal Connector with GitHub Actions
• Integrating Universal Connector with GitLab CI/CD

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:

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. 

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:

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.

Integrating Universal Connector with GitLab CI/CD

(BMC.DB2.SPE2504)

To integrate Universal Connector with GitLab CI/CD, use the UC application image in the GitLab CI/CD 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 GitLab CI/CD application:

This process involves the following steps:

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