Preparing to install the management server on Linux

Obtaining the installation files and license key

Use the following procedure to obtain the installation files and a license key:

1. Go to Electronic Product Distribution (EPD) and log in.

2. Using the search bar, search for either BMC AMI Cloud Data or BMC AMI Cloud Vault. Both product files are composed with the same binaries.
3. Click the version that you want to download. 
4. On the Product tab, select the files and click Download.
5. Select the License Information tab and download the temporary license key.

6. To obtain a full license key, go to Support Central and select Case Management. 

7. Open a license key request by clicking on Create New Case and filling in the required information. 

   Important

   Supply the output of the z/OS command D M=CPU.

Installing the podman-plugins package

If you are using Podman as the container platform, install the podman-plugins package:

Configuring the local firewall

Configure your local firewall to allow connections to ports needed by the BMC AMI Cloud containers. For a list of required ports, see Firewall-and-network-connectivity-settings.

Alternatively, make sure that the local firewall is disabled by using by the following commands:

If the container solution is already installed, restart the container service by using the following command:

Verifying that the container platform is enabled and active

1. Run the following command to verify that the container platform is enabled:

   #When using docker
   sudo systemctl status docker
   
   #When using podman
   sudo systemctl status podman

2. Verify that enabled and active (running) are displayed in the output. Sample of enabled and active container platform in Docker 

   ● docker.service - Docker Application Container Engine
        Loaded: loaded (/lib/systemd/system/docker.service; enabled; vendor preset: enabled)
        Active: active (running) since Thu 2023-03-23 18:17:42 IST; 6 months 18 days ago
   TriggeredBy: ● docker.socket
          Docs: https://docs.docker.com
      Main PID: 698413 (dockerd)
         Tasks: 33
        Memory: 398.4M
        CGroup: /system.slice/docker.service

   Sample of enabled and active container platform in Podman 

   [root@ip-172-24-4-65 sivas]# sudo systemctl status podman
   ● podman.service - Podman API Service
      Loaded: loaded (/usr/lib/systemd/system/podman.service; enabled; vendor preset: disabled)
      Active: inactive (dead) since Tue 2023-10-10 14:14:46 IDT; 8s ago
        Docs: man:podman-system-service(1)
     Process: 854311 ExecStart=/usr/bin/podman $LOGGING system service (code=exited, status=0/SUCCESS)
    Main PID: 854311 (code=exited, status=0/SUCCESS)
   
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal systemd[1]: Starting Podman API Service...
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal systemd[1]: Started Podman API Service.
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal podman[854311]: time="2023-10-10T14:14:41+03:00" level=info msg="/usr/bin/podman filtering at log level info"
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal podman[854311]: time="2023-10-10T14:14:41+03:00" level=info msg="Not using native diff for overlay, this may cause degraded performance for building images: kernel has CONFIG_OVERLAY_FS_REDIRECT_DIR enabled"
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal podman[854311]: time="2023-10-10T14:14:41+03:00" level=info msg="Setting parallel job count to 7"
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal podman[854311]: time="2023-10-10T14:14:41+03:00" level=info msg="Using systemd socket activation to determine API endpoint"
   Oct 10 14:14:41 ip-172-24-4-65.ec2.internal podman[854311]: time="2023-10-10T14:14:41+03:00" level=info msg="API service listening on \"/run/podman/podman.sock\". URI: \"/run/podman/podman.sock\""
   Oct 10 14:14:46 ip-172-24-4-65.ec2.internal systemd[1]: podman.service: Succeeded.

3. If the container platform service is not enabled or active, use the following commands to enable and activate it: 

   #When using docker
   sudo systemctl enable docker
   sudo systemctl start docker
   
   #When using podman
   sudo systemctl enable podman
   sudo systemctl status podman

4. Make sure that the expected output of the container service is displayed, by issuing the following command:

   #When using docker
   sudo docker ps
   
   #When using podman
   podman ps

   The following output is expected: 

   CONTAINER ID    IMAGE      COMMAND     CREATED     STATUS     PORTS     NAMES 

Preparing your file system

The BMC AMI Cloud files should reside on a separate file system (other than the root file system) with enough free space to accommodate the BMC AMI Cloud management server and database. We recommend using the xfs filesystem type. To allocate adequate space and ensure it is mounted, contact your Linux administrator.

Uploading the installation files

Upload the model9-server-home zip installation file to the designated server in binary mode. Select one of the two available files according to your environment:

Where to go from here

See Performing-the-management-server-installation-on-Linux.