To view the latest 11.3.x version, see  PATROL Agent 11.3.02 Open link .

Installing in a ProactiveNet Performance Management environment

With Central Monitoring Administration, administrators select monitor installation components and the PATROL Agent to create an installation package. You can reuse the installation packages, or deploy the packages to multiple computers.

The ProactiveNet Central Monitoring Repository is a requirement on the ProactiveNet Central Server where Central Monitoring Administration is enabled. The Central Monitoring Repository includes the current versions of BMC components that you can use with ProactiveNet.

After creating a component installation package, administrators can save the package to the Monitoring Installation Packages list for future use, or download the package on the current host without saving the package. For saved packages, administrators can download and install the package on any host, or edit a package.

Before you begin

To create an Agent installation package

  1. For PATROL Agent package creation, follow the instructions in Provide details for a PATROL Agent installation package.

    The installation wizards for the products that you selected are displayed, and they vary depending on the products or components that you selected to include in the package. To complete the installation wizards, follow the instructions for creating a component installation package in the installation documentation for the selected products.

Provide details for a PATROL Agent installation package

  1. Specify the installation directory.
    Note that the PATROL products are installed one level below the BMC products installation directory.
  2. Specify the PATROL 3.x product directory.
    Follow the instructions in the Important Information section.
  3. 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.
  4. 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, enter DOMAIN_NAME\account name; otherwise, enter the local account. To allow the PATROL Agent to use the Local System account as the default account, leave the username and password fields blank.
  5. Select the security level.
    The default security level is appropriate for most environments. For more information, see The BMC PATROL Security User Guide.
  6. 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.
  7. Provide the ProactiveNet integration configuration:
    1. INTEGRATIONSERVICES variable: this variable is used for automatic registration of the PATROL Agent with ProactiveNet.

      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.

    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 PATROL agents from Central Monitoring Administration.
  8. Provide the ProactiveNet cell configuration details.
    The ProactiveNet cell is used to auto-register the PATROL Agent with ProactiveNet.
    Enter the ProactiveNet encryption key and the cell details in the format Host/Port.

    You can choose to route events via an Integration Service.

    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 PATROL Agent to version 9.5, ensure to provide the correct Cell name in the ProactiveNet - Primary Cell and ProactiveNet - Secondary Cell fields in the ProactiveNet Performance Management Cell Configurations installation screen.

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

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

  9. Provide the RTSERVERS variable details.
    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.
  10. Configure the firewall.
    You can choose to automatically add the components to the firewall exception list.
  11. Provide the installation package details like name and file format.

To edit a component installation package

You can edit any part of an existing component installation package except the operating system and platform.

  1. In the navigation pane of Central Monitoring Administration, click the Repository drawer and select Deployable Package Repository.
  2. (Optional) To filter the list of packages, select an operating system from the Filter by Operating System list.
  3. Select the row for a package and click Edit .
  4. From the Available components list, add or remove components, and click Next.
  5. Perform one or more of the following actions, depending on your requirements:
    • Edit the installation details of existing components.
    • Add installation details for new components.
    • Click Finish Update to skip to the Installation Package Details window.


      If you add a component to the package, you must complete the configuration process. The Finish Update button shows an explanatory tooltip and does not skip to the Installation Package Details window.

  6. In the Installation Package Details window, modify the following information as needed:
    • Name: To save your changes to the same package, do not change the name. To save the package under a unique name, change the name.
    • (Optional) Description: Enter a description of the package.
      The description is displayed in the Monitoring Installation Packages list on the Deployable Package window.
    • Format: Select a file compression format for the installation package.
  7. Perform one or both of the following actions:
    • To save the package for future installation on the current host or other hosts, click Save Installation Package.
      The package is available through the Monitoring Installation Packages list.
    • To download the installation package immediately, click Download.


      If you click Download and do not click Save Installation Package, the changes are not saved in the Monitoring Installation Packages list for later use or editing.

  8. When you are finished, click Close.


On non-English Linux computers, if you use the Firefox browser, in the Add/Edit Component Installation Package page, when you click Cancel, a confirmatory message is displayed with the black background. On other browsers, the confirmatory message is properly displayed.

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