Downloading and deploying Monitoring Solutions

Where you are in the Installation process

The following steps summarize the process to deploy packages on PATROL Agents:

 

KM_push_user.png

Perform the following steps to import the Infrastructure Management repository, create and deploy packages.

To download the Repository files

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

To import the Infrastructure Management repository

BMC periodically releases new versions of the Infrastructure Management repository. Perform the following steps to import the latest version of the repository. You can import the repository using one of the following options:

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

Failed to execute the [excerpt-include] macro. Cause: [Error number 2 in 0: No wiki with id [confluencePage:page] could be found]. Click on this message for details.

To create a deployable package

As an administrator, you can select PATROL Agent and monitoring solutions to create a deployable package. The components can then be installed together using the deployable package. You can reuse the deployable packages, or deploy the packages to multiple computers. Ensure that you have reviewed the deployable packages best practices and have imported the Infrastructure Management PATROL repository before you start creating the deployable packages.

  1. Log on to the TrueSight console. In the navigation pane, expand Administration, select Repository, and select the Deployable Packages tab.
  2. ClickCreatePackage.PNGCreate Deployable Package.
    The Create Deployable Package wizard starts.
  3. On the Installation Package Solution Selection page, select the operating system for which you want to create a package, and then select a platform on which you want to install the package.
    The list of components in the repository that are supported on the specified operating system and platform is displayed.
  4. Select the components that you want to include in the package.

  5. From the Version list, select the version of the component that you want to include in the package.
    By default, the latest version available in the Presentation Server is selected. Select latest to automatically update the package with latest versions of components when they are imported to the Presentation Server.

    Important

    Deployment from the console is not supported if the deployable package contains the following components:

    • PATROL Configuration Manager
    • PATROL Classic console
    • Oracle JRE only

    If any of these components are present in the deployable package, the package is not seen in the Deploy and Install Packages screen.

  6. For monitoring solutions that contain sub-components, select the sub-components to be included in the deployable package.

    Tip

     To reduce the deployable package file size, choose only the sub-components that you will use.

    Package_Subcomponents.png


  7. Provide PATROL Agent related information:

    Note

    The following fields depend upon the components that are included in the deployable package. Not all fields may be displayed while creating a deployable package.  

    1. Specify the installation directory.
      Perform one of the following actions:
      • Proceed with the installation in the default directory.
      • Enter a different directory for installation.
      • Leave the field blank and proceed with the installation.
        You can leave the field blank if you do not know the location where the KM or PATROL Agent is installed. When you leave the field blank, the correct directory is automatically selected through the BMC_BASE variable.
    2. Specify the PATROL 3.x product directory.
    3. Follow the instructions in the Important Information section of the wizard.
    4. For UNIX operating system, provide the System Root account details.
      Note: You can continue the package process without the Root details but you will need to complete the root configuration at a later time for the selected component to run correctly.

    5. Provide the PATROL default account credentials.
      You must create this account manually before continuing with the installation. If you plan to use a domain account, type the following otherwise type the local account details:

      1. (Windows) DOMAIN_NAME\account name
      2. (Linux) DOMAIN_NAME\\account name
        Double slash before the account name ensures that the account name is parsed correctly. While editing the package, if the double slash is deleted, type it again.

      Note

      To allow the PATROL Agent to use the Local System account as the default account, leave the username and password fields blank.

    6. Select the security level.
      The default security level is appropriate for most environments.
    7. Specify the PATROL Agent port number.
      The port number is used by the PATROL Agent to communicate with the console. If you are installing a new version of the PATROL Agent over an existing one, ensure that you specify the same port number used by the earlier Agent.
    8. Provide the Infrastructure Management integration configuration:

      1. INTEGRATIONSERVICES variable: this variable is used for automatic registration of the PATROL Agent with Infrastructure Management.Enter one or more existing Integration Service(s) to connect to. Separate each entry by a comma and use the format Protocol:IntegrationServiceHostname:PortNumber. For example tcp:Integration Service Hostname:3183, where 3183 is the port on which the Integration Service host listens for an incoming PATROL Agent auto-registration connection.

        Note

        You can connect to the local integration service installed on the Infrastructure Management Server, or Downloading and installing a new instance of the Integration Service

      2. Central Monitoring Administration Tag(s):

        Provide comma separated tags that the PATROL Agent will use to get configuration from Central Monitoring Administration. Each tag follows the format TagName:Description. If there is a space in the description, enclose it with quotes. For example, WinOS:"Windows OS Monitoring".

      3. By default, Central Monitoring Administration manages the PATROL Agent(s) configuration. If you select No, you can enable policy management from Central Monitoring Administration later. For more information, see Managing-Infrastructure-Management-devices-from-the-TrueSight-console.

    9. (Optional) Provide the cell configuration details.
      Enter the Infrastructure Management encryption key and the cell details in the format Host/Port.

      You can choose to route events via an Integration Service.

      Note

      To route events via an Integration Service, the /EventSetup/Configuration/ForwardEventsToIS PATROL Agent pconfig variable must be set to Yes. 

      During the upgrade of earlier versions of the BMC PATROL Agent, ensure to provide the correct Cell name in the Infrastructure Management - Primary Cell and Infrastructure Management - Secondary Cell fields in the Infrastructure Management Performance Management Cell Configurations installation screen.

      Proceeding with the default value resets the Event Destination of the BMC PATROL Agent to localhost/1828.

      If /EventSetup/Configuration/ForwardEventsToIS is set to Yes and Infrastructure Management - Primary Cell is set to localhost/1828, then the PATROL Agent sends events to the local Cell of the Integration Service.

    10. (Optional) Provide the RTSERVERS variable details.
      BMC PATROL 7 products communicate with each other through one or more RTservers. For previously installed PATROL Agents (version 3.5 or later), you must set the RTSERVERS variable and restart the PATROL Agent. Provide comma separated RTSERVERS variables in the format protocol:hostname:port. For example, tcp:localhost:2059.
    11. Configure the firewall.
      You can choose to automatically add the components to the firewall exception list.

  8. Review the deployable package details.

    If you added a monitoring solution that contains sub-components, click the plus sign to view the included sub-components.


  9. In the Installation Package Details window, enter the following information:
    • Name: The name of the deployable package. Can contain only A-Z, a-z, 0-9, and underscore (_).
    • (Optional)Description: Enter a description of the package.
      The description is displayed in the list of deployable packages.
    • Format: The default file format for the operating system is automatically selected. Select a different format if required.

  10. Perform one of the following steps:

    A template of the package is saved to the installationDirectory\truesightpserver\data\pproxy\installer_templates folder and is listed in the Deployable Packages tab.

     Package_Save.png

    Tip

    Pop-up blockers might prevent downloading the deployable package when you select Save and Download. Turn off pop-up blockers or click the pop-up blocked icon in the browser navigation bar to start downloading the deployable package.

To deploy packages on PATROL Agents

As an administrator, you can deploy packages to PATROL Agents. The installation runs silently with the information entered during the package creation. The deployable package is copied to the file system of the targeted PATROL Agents, is extracted and installed. You can also upgrade a PATROL Agent to the latest version using the same functionality.

Tip

See Downloading and installing saved packages manually for the following scenarios:

  • To perform a fresh installation of a PATROL Agent
  • To deploy packages to PATROL Agents prior to version 10.0

You need to create deployable packages before you can deploy them. For more information, see Creating deployable packages.

Review the following compatibility matrix to determine the available deployment options:

PATROL Agent
version

Integration Service
version

Regular
deployment

Force
deployment*

10.0

10.5 or later

✅️

❌️

10.7 or later

10.5 or later

✅️

✅️

*Force deployment is the capability to overwrite an existing installed solution with the same version from the package.

The following validations are performed before deploying packages:

  • PATROL Agent version - Packages are deployed only to PATROL Agents version 10.0 and later. The PATROL Agent can be upgraded from version 10.0 to the later versions.

  • Monitoring solution version - Monitoring solutions in the deployable package that are of earlier versions than what are available on the PATROL Agent are not deployed.

    Click here to view examples
    • Scenario 1 - A more recent version of the monitoring solution is available in the package. The deployment is successful, and the installed version is upgraded.
    • Scenario 2 - An older version of the monitoring solution is available in the package. The deployment is unsuccessful.
    • Scenario 3 - A combination of a more recent and older version of monitoring solutions is available in the package. The deployment is partially successful, because the package contains a previous version for one of the monitoring solutions.

    • Scenario 4 - A combination of a more recent and same version of monitoring solutions is available in the package. The deployment is successful - One monitoring solution is upgraded and one is reinstalled.

      Note

      The capability to overwrite an existing installed solution with the same version (force deployment) has been made available with TrueSight Presentation Server 10.7 and later. With force deployment, you can install the same KM that you have installed earlier. You can later uninstall the KM by using the Infrastructure Management Administrator Console.

    Deploy_scenarios.png

  • Integration Service version - Packages are deployed only to PATROL Agents that are connected to Integration Services version 10.5 and later.
  • Operating system - Packages that do not match the operating system of the target PATROL Agents are not deployed.
  • Installation directory - During installation, if the directory is not specified or if an incorrect directory is specified, the correct directory is automatically selected through the BMC_Base variable.
  • Disk space - The Integration Service and PATROL Agent host must have sufficient disk space for deployment and installation.
    • The Integration Service must have free disk space of at least the deployable package size.
    • The PATROL Agent host must have free disk space of at least four times the deployable package size.

To deploy and install packages to PATROL Agents

  1. Log on to the TrueSight console. In the navigation pane, expand Configuration and select Managed Devices.

  2. Expand the entries list to display the PATROL Agents that you want to deploy and install the package to.

    Deploying a package to multiple PATROL Agent instances

    You can deploy monitoring solutions to multiple PATROL Agent instances that are running on the same host.

  3. From the action menu for the PATROL Agent, select Deploy and Install Packages.
     

    Notes

    • If you are simultaneously deploying the package to multiple PATROL Agents, you can use the action menu from the column heading to deploy the package to the selected PATROL Agents.
    • For deploying the package to 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.

  4. Select the packages that you want to deploy to the PATROL Agent and select Deploy and Install.

    Deploy_Install.png

    Note

    Deploying a package restarts the PATROL Agent.

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

    Note

    During a deployment, if an Integration Service is disconnected, the deployment continues when the Integration Service is reconnected.

  6. View the status in the Deploy Status column. For more information, see Viewing the deployment and installation summary.

To view the deployment and installation status

The icons in the Deploy Status column indicate the deployment and installation status. See the following table for a description of the icons and the status.

Note

The status of only the latest action (deployment or installation) is displayed in the Deploy Status column.

Icon

Deployment status

Description

DeployInProgress.PNG

Initiated

A deployment has been triggered on the PATROL Agent.

DeployInProgress.PNG

Deploy in Progress

A deployment is currently in progress on the PATROL Agent.

Hover over the icon to view details.

InstallInProgress.PNG

Install in Progress

A deployment or installation has been triggered on the PATROL Agent and is currently in progress.

InstallCompleted.PNG

Install Completed

The latest installation on the PATROL Agent was successful. Hover over the icon to view details.

InstallFailed.png

Deploy Failed

The latest deployment or installation on the PATROL Agent failed.

The same icon represents both deployment and installation status. Hover over the icon to view details.

InstallFailed.PNG

Install Failed

The latest deployment or installation on the PATROL Agent failed.

UninstallInProgress.PNG

Uninstall in Progress

The latest uninstallation of monitoring solution has been triggered on the PATROL Agent and is currently in progress.

Note: If you have installed a monitoring solution on a PATROL Agent without using the Deploy and Install option, you cannot uninstall the monitoring solution using the same option.

UninstallCompleted.PNG

Uninstall Completed

The latest uninstallation of monitoring solutions on the PATROL Agent was successful.

UninstallFailed.PNG

Uninstall Failed

The latest uninstallation of monitoring solutions on the PATROL Agent failed.

InstallAborted.PNG

Aborted

The latest deployment on the PATROL Agent was aborted.

InstallUnknown.PNG

Unknown

The status of the latest deployment or installation on the PATROL Agent is unknown.

This is the default status when a deployment job has not yet been triggered on a PATROL Agent.

 

Deploying packages to earlier versions of PATROL Agents

The deploy and install feature in the TrueSight console does not support PATROL Agents prior to version 10.0.

To deploy to such PATROL Agents, perform the following steps:

  1. Use the Save and Download option while creating a deployable package, as described in Creating deployable packages.

  2. Copy the deployable package to the PATROL Agent host and extract it.
  3. Run the following file in the bmc_products directory:
    (Windows) RunSilentInstall.exe
    (UNIX) RunSilentInstall.sh


Next step in the Installation process

Step 5 Phase C, Task 2 — Now that you have successfully downloaded and deployed the monitoring solutions, you must download and install the administrator console on remote computers.

 

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