Default language.

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

  1. In the BMC Helix Operations Management console, navigate to Administration > Repository > Deployable Packages and click Create.
  2. 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.

  3. Select the components and their versions for the package, and click Next.

    Important

    If you have selected the PATROL Agent Patch for Windows or PATROL Agent Patch for Unix and Linux component, make sure that the base image of the respective PATROL Agent is already installed.

    The PATROL Agent for Unix and PATROL Agent patch for Unix and Linux components support all Unix and Linux flavors, which include Linux, Solaris, AIX, and HP-UX.

  4. In the BMC Software Products Installation Directory field, type in the installation directory for the components that you selected.

    Important

    If a PATROL product was previously installed, type in the PATROL installation directory. For example, if PATROL3.4 was previously installed, type in /opt/patrol as the installation directory.

  5. Perform one of the following steps:
    1. If you have selected the PATROL Agent as one of the components, provide the Root or Sudo user credentials for the PATROL Agent and click Next.
    2. If you have not selected the PATROL Agent as one of the components, provide the Root user credentials and click Next.
  6. In the PATROL 3.x Product Directory field, type in the installation directory for the PATROL products.
    If a PATROL product was previously installed, type in the PATROL product directory as the installation directory. For example, if PATROL3.4 was previously installed, /opt/patrol is the BMC software products installation directory, and PATROL3.4 is the PATROL 3.x product directory.
  7. If you have selected the PATROL Agent as one of the components, perform the following steps:
    1. Provide the login credentials for the PATROL Agent and click Next.
    2. Select a security option and click Next.
      The security level is the default level of security for the PATROL Agent to communicate with the Integration Service. The communication is over TLS 1.2.
      The following options are available:
      • No Certificate Validation
      • Certificate Validation
  8. Add the PATROL Agent port number, choose to restart the PATROL Agent automatically or manually, and click Next.
  9. If you have selected the PATROL Agent as one of the components, perform the following steps:
    1. Select a level of access control and click Next.
      If you select the Restricted Access Control (default) action, access to the PATROL Agent from pconfig and PatrolCli is restricted only to the default account. We recommend this option.
      If you select the Full Access Control option, all users can use pconfig and PatrolCli to access the PATROL Agent.
    2. Enter the following details:
      1. The streaming endpoint details for the PATROL Agent. If you have not configured a streaming endpoint for the PATROL Agent, leave this field blank.

      2. Tags to associate the PATROL Agent with the monitoring policy.
        We recommend tagging Agents when you want to apply a monitor policy to an Agent. You can tag Agents to provide precise Agent selection criteria when you create and assign a policy to an Agent. With the correct tags, the policy is automatically applied to an Agent when the Agent checks into BMC Helix Operations Management.

        Click here to see an example

        Consider an environment that has the following databases or platforms to be managed:

        • Oracle databases running on Red Hat Enterprise Linux
        • Microsoft SQL Server databases running on Windows
        • Apache running on Windows and Red Hat Enterprise Linux
        • WebLogic running on Windows and Red Hat Enterprise Linux

        Create packages and tags as listed below:

        Linux/UNIX Agent, Linux/UNIX OS Knowledge Module

        LinuxOS, OracleDB

        Tags

        SQLWin

        Windows Agent, Windows OS Knowledge Module

        WinOS, SQLDB

        ApacheWin 

        Windows Agent, Windows OS Knowledge Module 

        WinOS, Apache

        ApacheRHEL

        Linux/UNIX Agent, Linux/UNIX OS Knowledge Module 

        LinuxOS, Apache

        WebLogicWin

        Windows Agent, Windows OS Knowledge Module

        WinOS, WebLogic

        WebLogicRHEL

        Linux/UNIX Agent, Linux/UNIX OS Knowledge Module

        LinuxOS, WebLogic

        Oracle

        Oracle Database Knowledge Module

        N/A

        SQLServer

        SQL Server Database Knowledge Module

        N/A

        Apache

        Internet Server Manager Knowledge Module

        N/A

        WebLogic

        WebLogic  Knowledge Module

        N/A

      3. If you want to manage the PATROL Agent configuration by using a monitoring policy, click Yes. Else, click No.
      4. 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 for naming a package

    • 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.





 

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