Configuring zAdviser Enterprise On-Prem as a single node in On-prem Linux Ubuntu

Task 2: To obtain an Elastic certificate file for the configuration

1. Use the SCP tool to navigate to installationFolder/certs/ca/ on your installation server.
2. Copy the crt file to the VM machine. This certificate is used to configure the zAdviser.
   

Task 3: Elastic and Kibana configuration

Use the following details to configure connections to Elasticsearch and Kibana. Ensure that the domain part of the URL remains unchanged, and do not modify it to include extensions such as .bmc.com.

Task 4: LDAP Configuration

This section explains how to configure the LDAP connection parameters required to integrate the application with your organization’s directory service. The configuration enables centralized user authentication and access management through LDAP. Ensure that all required fields marked with an asterisk (*) are completed before saving the configuration.

Task 5: To configure SMTP server for generative AI reporting

1. In the zAdviser Enterprise administration pane, expand Generative AI reporting.
2. Select Email.
   

3. Enter the following details:

   Field	Description
   Host	SMTP server address
   Port	Appropriate port for your setup
   Start with TLS	Select based on your servers security settings
   Username	SMTP user name
   Password	SMTP password
   From address	Email address used to send emails
   Recipient(s)	One or more recipient email addresses (comma-separated for multiple addresses)

4. To save the configuration, click Apply.

Task 6: To configure LLM for generative AI reporting

1. In the zAdviser Enterprise administration pane, expand Generative AI reporting.
2. Select Large language model (LLM).
   
3. Select a Platform: BYOLLM (Bring Your Own LLM) or AMI Platform

4. Provide the required configuration details based on the selected deployment platform.

   BYOLLM configuration

   Field	Description
   URL	The endpoint for the LLM.
   Model	LLM name
   Token	An authentication token required to access the LLM.
   Headers	Specify any additional custom headers to be included.

   AMI Platform configuration

   Field	Description
   Integration Path	Specify the AMI Platform Integration Path.
   Integration Key	Enter the AMI Platform Integration Key.
   Integration ID	Provide the AMI Platform Integration ID.

5. To save the configuration, click Apply.

Task 7: To configure Git Settings

To configure Git settings, provide the required information in the Git Settings page. These settings establish a secure connection between your Git repository (such as GitHub, GitLab, or Bitbucket) and the application, enabling integration for version control, issue tracking, and automation.

Task 8: Jira Configuration

The JIRA Settings page enables integration between the application and your JIRA instance for issue tracking and workflow synchronization.
Depending on your environment, you can connect to either JIRA Server/Data Center or JIRA Cloud.

The following are the steps to configure your JIRA connection:

Step 1: Select Connection Type

On the JIRA Settings page, select your JIRA instance type:

• Server / Data Center : Select this option if you are using a self-hosted JIRA Server or JIRA Data Center instance.
  
• Cloud: Select this option if you are using Atlassian-hosted JIRA Cloud.
  

Step 2: Enter Base URL

In the Base URL field, enter the base URL of your JIRA instance.
Examples:

• For JIRA Cloud: https://your-domain.atlassian.net
• For JIRA Server/Data Center: http://your-jira-server

This URL allows the application to communicate directly with your JIRA instance.

Step 3: Provide Authentication Details

Depending on your selected connection type:

• For JIRA Cloud:

  • Enter your Email Address associated with your Atlassian account.
  • Enter your Personal Access Token (API token) generated from your Atlassian account.

• For JIRA Server/Data Center:

  • Enter the Personal Access Token generated and provided by your JIRA administrator.

Step 4: Specify the JIRA Project

Enter the JIRA Project key or name that you want to connect to. Although optional, providing a project name is recommended for better integration and filtering of issues.

Step 5: Review Additional Configuration Guidelines

Before applying your settings, ensure the following prerequisites are met:

• If your proxy restricts API calls, whitelist the User-Agent "zadviser".
• The configured JIRA user must have permission to browse the project.
  Required Permission: Browse Projects

Step 6: Save Configuration

Once all fields are completed:

1. Click Apply to save your JIRA configuration.
2. If you wish to discard the changes, click Cancel.

After successful configuration, your JIRA connection is ready for use.

Task 9: To configure LPARs

On the configuration page, navigate to LPAR Definitions section and enter all relevant information about the LPARs used by your organization.

You can update the LPAR settings at any time.

Task 10: To enable zAdviser Enterprise On-Prem support

1. Apply PTF CXSK99A (included in the October 2024 maintenance for ECC).

2. If you are using BMC AMI DevX Code Pipeline, apply the following PTF for a smooth and successful startup:

   Version	PTF
   22.01	IWH265A
   18.02	IWG531A

3. Make the following changes to your BMC AMI PARMLIB:

   Purpose	Action
   Enable the on-premises mode	ZADVISER = ON_PREM
   Set the on-premises IP address	ZADVISER_ONPREM IP = ipAddress Replace ipAddress with your zAdviser Enterprise On-Prem instance (for example, 127.0.0.1).
   Configure the port number	ZADVISER_ONPREM_PORT = portNumber Replace portNumber with the port number for sending zAdviser data to zAdviser Enterprise On-Prem. .

Task 11: Configuring Application Analysis

The Application Analysis feature enables you to generate comprehensive zAdviser reports for multiple programs associated with a specific LPAR, Application ID, and Sub-Application ID. The tool also provides enriched insights powered by your configured LLM.

The following are the steps to configure Application Analysis:

1. Log in to the BMC AMI zAdviser Enterprise Administration interface.
2. Navigate to Configuration > Application Analysis.

   The Application Analysis page is divided into the following sections:

   • Generate Report panel
     

   • Instructions / Status panel
     

3. In the Generate Report panel:

   • Select the LPAR on which the application programs are running (for example, CW01).

   • Enter the App ID that identifies the primary application (for example, APP01).

   • Enter the Sub App ID associated with the application (for example, SUBAPP01).

   • In the Programs field, select one or more programs from the available multi-select list.

4. Click Generate to submit the Application Analysis request.

5. Monitor the request progress in the Instructions / Status panel.
   After processing completes, view or download the generated report.

   Note:

   • Verify all field values before submitting the request.
   • Select only relevant programs to ensure meaningful analysis results.
   • Keep the browser session active until the request is accepted for processing.
   • LLM-based requests might incur usage charges depending on the configured model.
   • For large datasets, use a paid, high-token LLM model for improved insights.
   • Ensure that at least three months of application usage and SCM activity data is available for optimal results.

6. (Optional) Click Cancel to clear all field selections or stop a request that has not yet started processing.

7. After the request is processed successfully:

   • You receive an email notification confirming that the report has been generated.
   • The completed report is available in the designated section on the zAdviser Kibana dashboard home page.
     
     
     

Troubleshooting Application Analysis

Use the following information to resolve common issues:

• Generate button is disabled
  Ensure that all required fields are populated.
• Programs are not displayed
  Verify that the required application-to-program mappings are configured.
• Report generation is delayed
  Backend processing might take additional time, depending on the data volume.
• Report content is incorrect
  Verify the selected LPAR, application, and program details.

For further assistance, contact your zAdviser Administrator or BMC Support.

Task 12: Configuring AMI Assistant

The AMI Assistant Configuration page allows you to enable onboarding with the AMI Assistant, which integrates zAdviser Enterprise with the AMI Platform for AI-powered insights and assistance.

The following are the steps to configure AMI Assistant:

1. Navigate to Administration -> AMI Assistant Configuration.
   

2. In the AMI Assistant Onboarding section, enter the following details:

   • API URL 
     Enter the AMI Platform API URL that connects zAdviser Enterprise to the AMI Assistant service.
     For example,  https://api.platform.bmc.com/amiassistant

   • API Key 
     Enter the API key generated from your AMI Platform account. This key authenticates communication between zAdviser Enterprise and the AMI Assistant.
     Click the eye icon to view or hide the entered key.
3. Click Apply to save the configuration or Cancel to discard the changes.