Configuring the BMC AMI Platform service

This topic describes how to configure different Ansible files for installation.

To configure the Ansible files

Open each Ansible file.
Configure the required values for your system.

BMC AMI AI Platform Service Configuration

The following table displays the values you must add before you install BMC AMI AI Services:

Field	Description
Gateway host configuration
app_http_domain	This is required when you have a load balancer or application gateway. You must provide a domain name that points to the load balancer or application gateway.
(Required) gateway_host	If app_http_domain is set, assign its value to amiai_gateway. If app_http_domain is not set, use the IP address or hostname of the BMC AMI AI Services machine.
CES configuration Important For licensing purposes, you must provide CES configuration. During the feature provisioning, the CES details are provided to store BMC AMI AI Services access information. The CES details are also used with BMC AMI DevX Workbench applications to access BMC AMI AI Services.
ces_scheme	Protocol of CES instance
ces_host	Host name or IP address of CES instance
ces_port	Port of the CES instance
(Optional) ces_username	If the CES instance requires a user name, then provide it.
(Optional) ces_password	If the CES instance requires a password, then provide it.
Management console user configuration Important We require user credentials to access the BMC AMI AI Manager console. In the BMC AMI AI Manager console, there are two ways to configure users: zos_host admin_user_id Note that all users are admin users.
zos_host	Host name or IP address of zos machine Important Set the mainframe machine's host or IP address in zos_host. The use of zos_host is to authenticate users. All authenticated users can access the BMC AMI AI Manager console.
admin_user_id	Set the administrator user name The default is admin.
admin_password	Set admin user password. Before setting a password, encode the password in base64 encoding. The default set value is base64 encoded of amiaiadmin—YW1pYWlhZG1pbg==
Logs configuration
deployment_platform	It can be non-cloud or AWS. For non-cloud, the following fields are blank. For AWS, you must specify the following fields.
aws_region	Specifies the geographical area where AWS resources are hosted and managed. You must set this field when the deployment_platform is AWS.
aws_access_key_id	A unique identifier for an AWS account that is used for API authentication. This field is set to select automatically if an instance has access. You can set it up manually if the auto selection is not configured.
(Optional) aws_secret_access_key	The secret key is paired with the access key ID for secure AWS API access. This field is set to select automatically if an instance has access. You can set it up manually if the auto selection is not configured.
aws_session_token	The temporary token is used for session-based authentication in AWS and is often part of temporary security credentials. This field is set to select automatically if an instance has access. You can set it up manually if the auto selection is not configured.

BMC AMI AI model configuration

The following table displays different configurations for model installation. These configurations vary based on the selected infrastructure and model.

Field	Description
Model instance configuration
llm_host	The default value is set as amiai_llm. It works when BMC AMI AI Platform services and a model are installed on the same machine. If a model is deployed in a different instance, then set the value as the IP address of the instance where the model is deployed.
discovery_host	The default value is set as amiai_discovery. It works when BMC AMI AI Platform services and a model are installed on the same machine. If a model is deployed in a different instance, then set the value as the IP address of the instance where the BMC AMI AI Services is deployed.
no_of_threads	no_of_threads impact the model performance. We have different values according to the instance configuration. It's documented in all the infrastructure documents.
Logs Configuration
deployment_platform	It can be non-cloud or AWS. For non-cloud, the following fields are blank. For AWS, you must specify the following fields.
aws_region	Specifies the geographical area where AWS resources are hosted and managed. You must set this field when the deployment_platform is AWS.
aws_access_key_id	A unique identifier for an AWS account is used for API authentication. If the instance has access, the system automatically selects this field. If automatic selection isn't configured, you can set it manually.
(Optional) aws_secret_access_key	The secret key pairs with the access key ID to provide secure AWS API access. If the instance has access, the system automatically selects this field. If automatic selection isn't configured, you can set it manually.
aws_session_token	A temporary token provides session-based authentication in AWS and is often part of temporary security credentials. If the instance has access, the system automatically selects this field. If automatic selection isn't configured, you can set it manually.

Where to go from here

After you edit the Ansible files, install the services on your platform. For more information, see one of the following sections:

Automated-installation for automated installation on the AWS Cloud or Azure Cloud platform
Manual-installation for the x86, AWS Cloud, or Azure Cloud platform