Deploying and installing packages


This topic provides instructions on downloading, deploying packages, aborting their deployment, and uninstalling them. To understand the concepts of deployable packages and installation components, see Deployable packages.

You must be a tenant administrator to deploy packages.

Downloading deployable packages

On the BMC Helix Operations Management console, on the Administration > Repository > Deployable Packages tab, do the following:

  • Click the Download  icon against a package.
  • From the package menu, select Download.

You can deploy the packages using the action menu or the API key, which is a unique identifier of the tenant.

Even if a monitoring solution is already installed on a PATROL Agent, you can force deploy the same version of the monitoring solution on the same PATROL Agent. This is useful if the first deployment is not successful.

Deploying packages using the action menu

On the BMC Helix Operations Management console, on the Configuration > Managed Devices page:

  1. Do one of the following:
    • To deploy and install packages on a single device, click the device action menu.
    • To deploy and install packages on multiple devices, select the devices by holding the Shift key, and click the action menu from the column heading.

      Note: Supported instances for multiple package deployment

      For deploying the package on multiple PATROL Agents or when upgrading PATROL Agents, only the instance or service names that contain the word "PatrolAgent" are supported. The instance or service names are not case sensitive.

  2. Click Deploy and Install Packages.
    You can hover your mouse over the icon in the Deploy Status column to view the current installation status.

If a package deployment fails in validation, an error message is displayed. The remaining compatible packages, if any, are deployed and installed to the PATROL Agent.

Deploying packages using the Copy Install Script option

Use the Copy Install Script option to deploy pre-defined and custom packages.

On the BMC Helix Operations Management console, on the Administration > Repository page do the following:

  1. Determine whether the package contains a PATROL Agent. Pre-defined packages contain a PATROL Agent.
    To do this, click the package and view its summary.
  2. If the package contains a PATROL Agent, do the following:

    1. From the package menu, click Copy Install Script.
    2. Go to the computers where you want to deploy the package, and create a new PATROL Agent user.
    3. In the home directory of the new user, create a directory.
    4. Provide read/write/execution permission to the PATROL user for the directory.
    5. Paste and run the install script in this directory. For pre-defined packages, the default directory is:
      (Windows) <installation_directory>\BMC Software
      (Linux) /opt/bmc.
      Note: Use PowerShell version 5 or later.
    6. Provide the following information when prompted:
      • (Linux) Root login name and password
      • PATROL default account login name and password
  3. If the package does not contain a PATROL Agent, do the following:
    1. In the package menu, click Copy Install Script.
    2. Go to the computers where you want to deploy the package.
    3. In the directory that has read/write/execute permission for the PATROL user, paste and run the install script.

Deploying packages using the API key 

Use this procedure for deploying predefined and custom packages by using the API key. On the BMC Helix Operations Management console, on the Administration > Repository page, do the following:

  1. Retrieve the API key of the package that you want to deploy. Do the following:
    1. Click Copy API Key. The API key is copied to the clipboard.
    2. Paste the API key in a text file. You will require this key when you run the installation utility.
  2. Download and copy the package.
  3. Go to the computer where you want to install the package.
  4. If the package contains a PATROL Agent, ensure that the PATROL user directory has the read/write/execution permission. Pre-defined packages contain a PATROL Agent.
    (Linux) For pre-defined packages, the default directory is /opt/bmc.
    (Windows) For pre-defined packages, the default directory is <installation_directory>\BMC Software.
  5. Paste and extract the package.
  6. From the bmc_products directory, run the following command:
    • Custom package with PATROL Agent:  

      #Syntax - Windows
      runRunSilentInstall.exe -apikey=<apikey> -proxyserver=<FQDN of the PATROL Agent forward proxy server>:<port> -proxyuser=<Proxy Username> -proxypasswd=<password for the proxy server>
      
      #Syntax - Linux
      RunSilentInstall.sh -apikey=<apikey> -proxyserver=<FQDN of the PATROL Agent forward proxy server>:<port> -proxyuser=<Proxy Username> -proxypasswd=<password for the proxy server>
      
      #Example
      RunSilentInstall.exe -apikey=a1236789-123f-1d23-12d4-1234abc12345 -forwardProxyServer=proxyServer.bmc.com:3128 -forwardProxyUser=user1 -forwardProxyPasswd=user123

      API key

      The API key in this command is the key that you retrieved earlier. PATROL Agents use the API key to encrypt message requests sent to BMC Helix Operations Management. You can set the API key when you install PATROL Agents as shown in the preceding example. Alternatively, you can set the API key after installing PATROL Agents. For more information, see Support for HTTP communication.

      Proxy server

      You can configure PATROL Agents to communicate with BMC Helix Operations Management through a forward proxy server to create an additional layer of security. Setting up a proxy server is optional. For more information, see Configuring PATROL Agents to support a forward proxy server

    • Custom package without PATROL Agent:
      • (WindowsRunSilentInstall.exe
      • (LinuxRunSilentInstall.sh
      Note: Do not use the API key and proxy server options to deploy a package that does not contain a PATROL Agent.
  7. Provide the following information when prompted:
    • Linux - If the package contains a PATROL Agent
      Root login name and password
      PATROL default account login name and password
    • Windows
      PATROL default account login name and password

Aborting deployment of packages to PATROL Agents

You can abort deployment of a package to PATROL Agents if:

  • The package is not in the Install in Progress status.
  • The assembly of the deployable package on the PATROL Agent is not complete and the installation has not started.

Where do I find the package deployment status?

To view the deployment status of a package, follow these steps:

  1. In the BMC Helix Operations Management console, go to Configuration > Managed Devices.
  2. Click the Managed Devices menu and click View Deployment and Installation Summary.


    You can see the package deployment status on the Deployment and Installation Summary page.

When you abort a deployment, it applies to all PATROL Agents that the deploy and install process was initiated on.

For example, you deploy and install deployable package PKG1 on PATROL Agents PA1 and PA2. The Deployment and Installation Summary page lists PKG1. If you abort PKG1, deployment to both PA1 and PA2 is aborted.

In the BMC Helix Operations Management console, on the Configuration > Managed Devices page, follow these steps:

  1. Click the Managed Devices action menu and select View Deployment and Installation Summary.

    Tip: Viewing the latest deployment status before aborting

     Refresh the Deployment and Installation Summary page before you abort a deployment so you can view the latest deployment status.

  2. Click the action menu for the deployment you want to abort and click Abort Deployment
    To abort multiple deployments, select the deployments you want to abort, click the action menu in the table header, and click Abort.



  3. In the confirmation window, click Yes.
    On the Deployment and Installation Summary page, the Status column displays Aborted if the deployment was successfully aborted; else it displays the In Progress status.
  4. If you want to view the detailed status of the abort process, in the PATROL Agents Applied To column, click the PATROL Agent count and see the PATROL Agent Details page.

Uninstalling packages and monitoring solutions

On the BMC Helix Operations Management console, on the Configuration > Managed Devices page, do the following: 

  1. From the PATROL Agent menu, click Uninstall Monitoring Solutions. For monitoring solutions that contain sub-components, you can select specific sub-components to uninstall.
  2. Click Uninstall. The PATROL Agent restarts.
    You can view the uninstall status in the Deploy Status column.

    IconDeployment statusDescription

    Uninstall in Progress

    An uninstall has been triggered on the PATROL Agent and is currently in progress.

    Uninstall Completed

    The latest uninstall on the PATROL Agent was successful.

    Uninstall Failed

    The latest uninstall on the PATROL Agent failed.

The uninstall log is available at <install_directory>\tmp\ Uninstall_Log\<yyyy_mm_dd_hh_mm_ss_job_id>

Tip: Uninstalling a monitoring solution

After you initiate the uninstallation of a monitoring solution using the BMC Helix Operations Management console, do not attempt to manually uninstall it from the PATROL Agent host computer.


Uninstalling PATROL Agents

You can uninstall PATROL Agents using the command line option. For more information, see  Uninstalling PATROL Agents.



Was this page helpful? Yes No Submitting... Thank you

Comments