This documentation supports the releases of BMC Helix Operations Management up to December 31, 2021.To view the documentation for the latest version, select 23.1 from the Product version picker.

Configuring deployable packages

A deployable package consists of KMs and PATROL Agent that you can select and deploy together. These components are also called installation components. You can reuse deployable packages on a single or multiple computers. For example, to monitor your Windows environment, create a package that contains PATROL Agent and PATROL for Microsoft Windows Servers.

The following deployable packages are available out-of-the-box:

  • Predefined_Package_For_Linux_x64
  • Predefined_Package_For_Windows_x64

You can deploy a package on the host computer or push it to multiple computers in your system. You can view the deployment status on the Agents page in the Configuration menu. 


To create deployable packages

Navigate to the Administration > Repository > Deployable Packages tab, click Create, and follow these steps:

  1. Select the operating system and platform for which you want to create a package.
     The list of platforms changes according to the operating system that you select.
  2. Select the components and their versions for the package, and click Next.

  3. If the monitoring solutions contain subcomponents, select the subcomponents to be included in the package, and click Next.

    Can I reduce the package size?

    To reduce the package file size, select only the subcomponents that you will use.

  4. Specify the installation directory for the package, and click Next.
  5. Enter the PATROL Agent product directory, and click Next.
  6. Verify the PATROL Agent name, and enter the PATROL Agent account credentials.
  7. Add the PATROL Agent port number, choose to restart the PATROL Agent automatically or manually, and click Next.

  8. (Optional) To start the PATROL Agent automatically, select the option and click Next.

  9. Add the components to your firewall exceptions list, and click Next.

  10. Add a name and description for the package, and select the format.
    The maximum number of characters for the package name is 100.

    Best practices

    • Provide a meaningful name.
      Add the information with the maximum impact at the beginning of the package name. For example, for a basic package to monitor Red Hat Enterprise Linux (RHEL) operating systems that would be deployed to most of the RHEL systems in your environment, use the name “RHELOSBasic”.
    • Do not use special characters in package names.
    • Enter complete descriptions in every package description field. Add the most important information at the beginning of the description, so that it is readily visible without you having to hover the mouse over it.
  11. Save the deployable package.


To view and filter deployable packages

Navigate to the Administration > Repository > Deployable Packages tab to view the package details:

  1. Click the package name.
  2. (Optional) To filter the list of deployable packages, click the operating system names for which packages are created.

    view_deployable_package.png
  3. To perform various actions on a deployable package, click the action menu for the package:

    DeploymentPackages.png

    The following options for the package are available in the package menu:
    • Edit: You can edit only those deployable packages that you created. You can edit any part of these packages except the operating system and platform. To edit out-of-the-box packages, save them with a different name, and then edit them.
    • View: This action is similar to clicking the name of the package.
    • Delete: This action deletes the package from the server.
    • Download: This option is used when you are deploying the package. 
    • Copy Install Script: This option is used when you want to silently install the package. For more information, see Deploying-packages.