Skip to Content
Information

This site will undergo a brief period of maintenance on Friday, 18 December at 12:30 AM Central/12:00 PM IST. During a 30 minute window, site availability may be intermittent.

Installing BMC AMI Ops Console Management

You can use the following methods to install BMC AMI Ops Console Management:

  • RPM method: The RPM method is used for installing the BMC AMI Ops Console Management package on a new environment or on top of an existing RPM installation. The RPM installation requires users to have system root privileges.

  • Tarball method: The Tarball method is for users with non-root privileges. This is an alternate way to install BMC AMI Ops Console Management. This method has a different set of requirements and security restrictions that are mentioned below.

    Warning

    Important

    If upgrading from 4.0.xx or earlier, we recommend the RPM installation method.

    Make sure that the installation methods are not mixed, as the installation may result in unexpected behavior.

Related topics

Planning and installing

Before you begin

  • Before you start the installation, you must choose which method to use. We provide separate packages on Electronic Product Distribution (EPD). You only need to install the package for your chosen method.

  • We recommend that all users clear their browser cache and cookies after installing, updating, or restoring BMC AMI Ops Console Management.

RPM installation for root users (recommended)

The RPM installation method requires you to have root privileges. RPM administration is necessary to install any missing prerequisite system or install files.

The software package is named BMC_AMI_OPS_Console_Management-v.v.vv.tgz, where v.v.vv is the version number of the software.

Perform the following steps to install BMC AMI Ops Console Management using the RPM method:

  1. Download the BMC AMI Ops Console Management installer package from BMC Software’s EPD site.
  2. Copy the installer package to a directory on your Linux server. We recommend you copy the file in /root directory (the root user’s home directory) as most installations are done on a dedicated Linux server.
  3. Log into the Linux server using an ssh client, such as PuTTY.
  4. Change the directories to the directory, where you copied the file. Execute the ls command to view the BMC_AMI_OPS_Console_Management-v.v.vv.tgz file.

  5. Unpack the installer package using the following command: 

    tar xvf BMC_AMI_OPS_Console_Management-v.v.vv.tgz

    This will create a directory named BMC_AMI_OPS_Console_Management-v.vv.vv.

  6. Change directory into the new directory.

  7. Run the following command: 

    ./run-me-first.sh

    This command verifies that all the system requirements are fulfilled. If there are any errors, you must correct them before continuing with the installation.

  8.  Run the following command: 

    ./install.sh
    1. This prompts you to accept a license agreement.
    2. If you are performing an upgrade, the previous version is upgraded to the new version installed in the same directory.
  9. The installer creates the user iocadmin and group iocgroup. These are initially used for file ownership but can also be used if you want to operate the software in the unprivileged mode by running the /opt/bmc/ami_cm/iocinst/bin/mvcm_reconfigure.sh script after installation.
  10. Reboot the Linux server using the reboot command. This ensures that all system services initiate in the proper order.

Other supported installation - Tarball for non-root users

The tarball method does not require the user to be root. However, this method consists of some additional tasks and limitations.

Linux uses a package called systemd to start daemons (processes) at system boot time. If you try to install the product as a non-root user, you need to configure systemd later as root, or run it in the systemd user mode.

When the system daemons are not running as root, they cannot open up network sockets that listen on ports less than 1024. This means that a URL like https://hostname.example.com/index.html, must be changed to use a port greater than or equal to 1024 like https://hostname.example.com:1443/index.html.

If you find this inconvenient, you can avoid this by using port-forwarding using Linux firewall rules.

The installer for the tarball method is contained in the file named BMC-AMI-OPS-ConsoleManagement-v.v.vv.bin, where v.v.vv is the version number of the software.

Perform the following steps to install BMC AMI Ops Console Management using the tarball method:

  1. Download the BMC AMI Ops Console Management installer package from BMC Software’s EPD site.
  2. Copy the installer package to a directory on your Linux server. We recommend you copy the file in /root directory (the root user’s home directory) as most installations are done on a dedicated Linux server.
  3. Log into the Linux server using an ssh client, such as PuTTY.
  4. Change directories to the directory where you copied the file:

    1. Run the following command: 

      chmod a+x BMC_AMI_OPS_Console_Management-v.v.vv.bin
    2. This prompts you to accept the license agreement if you haven't accepted it already.
    3. The software is extracted into a subdirectory named: BMC_AMI_OPS_Console_Management-v.v.vv.
  5. Change the directory to the new subdirectory.

  6. Run the following command:

    install.sh
    1. If you are performing an upgrade from a previous install, the previous version is uninstalled and the new version is installed in the same directory. 
    2. If you are performing a new installation, the installer prompts you to select the directory, where the software is going to be installed. Alternatively, you can enter the directory on the command line.
    3. If the user is root, the systemd daemon is configured automatically.

If you are installing with a non-root account, you need to ensure that the AMI-CM bootstrap daemon gets started up properly. The bootstrap daemon is responsible for starting up all the other daemons. To enable the bootstrap daemon run the command: 

<install location>/bootstrap/amicm_install_bootstrap.sh <username>

This script assumes you have root privileges when it is executed. The script takes a single parameter, which is the user ID that should own the processes. 

 

 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*

BMC AMI Ops Console Management, BMC AMI Ops Console Automation, and BMC AMI Ops SecureHMC 4.1