BMC AMI AI Services integration workflow

This topic explains the workflow for integrating various services within the BMC AMI AI Platform, focusing on the interaction between the BMC AMI DevX space, BMC AMI Ops Insight, and BMC AMI AI Services. The BMC AMI DevX space includes client applications such as BMC AMI DevX Workbench for Eclipse, BMC AMI DevX Workbench for VS Code, and BMC AMI Common Enterprise Services (CES), with CES acting as middleware.

The integration service provides access to all the generative AI features in BMC AMI products. For more information about BMC AMI AI Services, see BMC-AMI-AI-Services-overview.

Integration consists of the provisioning process and the usage process.

Provisioning process

After you complete the installation, you start the provisioning process. The provisioning process involves deploying AI services to the environment and configuring access for users. After AI services are deployed, they become visible in the UI environment, allowing administrators to manage them through the BMC AMI AI Manager console. The Discovery Service automatically detects features such as the Code Insights Explain service. When the Code Insights Explain integration is running, the system can discover it, and the BMC AMI AI Manager console displays its availability.

To enable access to the BMC AMI AI Manager console and other integrations, administrators must provision the service. This process generates an access token and URL for connecting to the integrations.

For more information, see Managing-the-platform-in-the-BMC-AMI-AI-Manager-console.

Usage process

This topic describes the usage process with or without CES after completing the provisioning process.

Usage process with CES

CES facilitates provisioning for any AI services integration and manages access through the generated URL and token. This integration allows client applications such as BMC AMI DevX Workbench for Eclipse to interact with CES without requiring configuration changes because CES automatically provides the necessary information.

The usage process is as follows:

From the BMC AMI AI Manager console, in the integration settings, you select an integration card that you want to provision.
During the provisioning process, the gateway URL and access token are sent to CES.
BMC AMI DevX Workbench for Eclipse communicates with CES. It passes the code snippet to explain to CES, which passes it on to the Platform.

This process ensures secure and efficient communication between the user, the AI services, and the client applications.

The following figure displays the workflow and the integration among the BMC AMI AI Services by using CES.

Usage process without CES

The usage process without CES is as follows:

From the BMC AMI AI Manager console, in the integration settings, you select an integration card that you want to provision.
During the provisioning process, the access token is generated internally.
From the AI Manager console, you download the connection details. These details are used to connect with BMC AMI AI Services.

These steps ensure secure and efficient communication between the user, the AI services, and the client applications.

The following figure displays the workflow and the integration between the BMC AMI AI Services without using CES.

You can now start using BMC AMI AI Services and the following products:

BMC AMI DevX Workbench for Eclipse—Using Code Insights Explain
BMC AMI DevX Workbench for VS Code—Using Code Insights Explain
BMC AMI Ops Insight—Enabling BMC AMI Assistant

Where to go from here

For more information about BMC AMI AI Services, see Getting-started.

To prepare for installation, see Planning.