Installing zAdviser Enterprise On-Prem as a single node on on-premise Linux Ubuntu
Download the file BMC-AMI-ZADVISER-X86.zip from BMC Electronic Product Distribution (EPD) and extract the files.
Create a folder for all your zAdviser resources. Give the Read and Write access by running:
chmod 777 -R <path to the folder created>To store all your data in folder/home/bmc/zAdviser, run the following command:
chmod 777 -R /home/bmc/zAdviser
Download and install the Secure Copy Protocol (SCP) client by using WinSCP for a Windows or Cyberduck for a MacOS. You can find them online.
- Connect your SCP application to the Virtual Machine (VM) by using the following host and port:
- Hostname: VM’s public IP
- Port number: 22
- Enter the user name and password for the Linux server.
- Move the downloaded files zAdviserDeployment-Ubuntu-Prod.yml and compose.yml from the left column (your local machine) to the right column (the VM).
Task 2: To install Python on the VM
- Connect to the Linux VM by using SSH.
- Log in to the VM.
- To check the python installation, run the python command.
- If the following response is displayed, skip the remaining steps of this task.

- To exit the Python shell, enter the exit() command.
- If the following response is displayed, skip the remaining steps of this task.
Run the following commands in sequence:
sudo apt updatesudo apt install python- Run the python --version command to verify the Python installation.

Task 3: To Install Ansible on VM
- To check the Ansible installation, run the ansible -–version command.
If the following response is displayed, skip the remaining steps in this task.

To install Ansible on the VM, run the following commands:
sudo apt-add-repository ppa:ansible/ansible
sudo apt update
sudo apt install ansible- To verify Ansible installation, run the ansible -–version command .

Task 4: To Install BMC AMI zAdviser Enterprise On-Prem services on VM by using the Ansible playbook
- Connect to the Ubuntu VM with SSH.
- Log in to the VM.
- Run the following command:
ansible-galaxy collection install community.docker - The following are the steps to install BMC AMI zAdviser Enterprise On-Prem services using non-LDAP authentication.
- Run the following commands in sequence from the folder where you copied all the installation files:
sysctl -w vm.max_map_count=262144
ansible-playbook zAdviserDeployment-Ubuntu-Prod.yml -e
'{"ES_PORT":"9200", "user":"<EDP user>", "pass":"<base64
encoded EPD token>", "KIBANA_PORT":"5601",
"ELASTIC_PASSWORD":"<Password for ElasticSearch>",
"KIBANA_PASSWORD":"<Password for ElasticSearch>",
"zadviser_config_folder":"<folder path to folder
created>", "zadviser_app_port":80,
"zadviser_app_port_https":443,"zadviser_kibana_proxy_port":3001,"mcp_server_port":8001}' The description of each parameter is as follows:
Parameter
Description
user
EPD user name
pass
Download the EPD token and convert to base64 encoded.
ELASTIC_PASSWORD and KIBANA_PASSWORD
Passwords set initially for accessing Elasticsearch and for future use. Choose your preferred password.
zAdviser_config_folder
Path to the folder where you keep all the zAdviser data. For more information, see Task 1: To move the downloaded files from EPD to the server by using the SCP tool .
mcp_server_port Http port on which mcp server runs to generate application analysis reports. Default value: 8001. The following response is displayed:

If following error message is displayed, log in with your personal Docker Hub credentials and rerun the Ansible command.

- Run the following commands in sequence from the folder where you copied all the installation files:
Task 5: To verify the installation
- Run the docker ps command. Verify that the following five services statuses are displayed as up and running:

- Visit the following IP address to check the installation:
- BMC AMI zAdviser Enterprise Administration—https://serverIP:443
- BMC AMI zAdviser Enterprise—http://serverIP:5601. The user name is elastic and the password is provided in elastic_password playbook command field.
BMC AMI zAdviser MCP Server: http://serverIP:8001/health. Use this endpoint to verify that the MCP server is up and running.