This documentation space contains information about PATROL Agents when deployed in a TrueSight Operations Management environment. If you are a BMC Helix Operations Management user, see PATROL Agent 22.4 for BMC Helix Operations Management. Open link

Installing in a TrueSight Operations Management environment

To install PATROL Agent, you create a deployable package that contains the imported PATROL Agent. You then deploy the package to the host computer from where you want to collect data.

setup.exe utility is deprecated

From 20.02, the setup.exe utility has been discontinued. Use deployable packages to install PATROL Agent.

Before you begin

Before installing PATROL Agent, perform the following:

  1. Create a PATROL default account.
    For more information, see PATROL default account. Open link
  2. Ensure that you have the base repository imported to your TrueSight console.
    For downloading instructions, see Downloading the Repository. Open link
    If you do not have the base repository, perform the following actions:
    1. Download the PATROL Agent files from the Electronic Product Distribution (EPD) website:

      VersionEPD linkComment
      PATROL Installation Utility

      EPD link to download PATROL Installation Utility Open link

      PATROL Agent 22.3.01

      EPD link to download PATROL Agent Open link

      • Windows -
      • Linux/Unix - PIA_ALL_22301.tar

    2. Import the downloaded file to the repository by performing the following steps:

      1. Log in to the TrueSight console.
      2. Click Administration > Repository > Installation Components.
      3. Click  Import.
      4. In the Import a Repository or Solution dialog box, select Single Solution.

      5. Click Browse to browse and select the downloaded files (PATROL Agent and PATROL Installation Utility).
        The selected files are displayed in the File Selected box.

      6. Click Import.
        The selected archive file is imported to the repository and extracted. You can close the window during the import process.

Step 1: Create a deployable package

  1. In the TrueSight console, click Administration > Repository > Deployable Packages .

  2. Click Create Deployable Package.
    The Create Deployable Package wizard is displayed.

  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 one of the following PATROL Agent components and any monitoring solutions that you want to install with PATROL Agent:

    • PATROL Agent for Windows
    • PATROL Agent for UNIX
  5. From the Version list, select the version of the component that you want to add to the package.
    If you select latest, latest version of the solution is added to the package automatically and the package is updated with the latest versions of these solutions when their new versions are added to the repository.

  6. Enter PATROL Agent configuration details:


    Enter the installation directory by performing one of the following actions:

      • Proceed with the default installation directory.
      • Enter a different directory location for installation.
      • Leave the field blank and proceed with the installation.
        When you leave the field blank, the correct directory is automatically selected by using the BMC_BASE variable.

    If you are using other BMC products, it can use the same default installation directory, which may cause uninstallation issues. For more information, see the Knowledge Article, Open link


    Specify the PATROL 3.x product directory, and click Next.


    (UNIX only) Enter the root account password.


    Using root account might create security risks.

    If you do not want to enter the root password, leave the field blank. You must run the hostname_port_install.log_rootscripts script file post installation. For more information, see post installation steps.


    Enter the PATROL default account or local account credentials.


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

    To use domain account, enter any of the following:

    • (Windows) DOMAIN_NAME\account name
    • (UNIXDOMAIN_NAME\\account name
      Note the double slash before the account name that are used to ensure that the account name is parsed correctly. When you are editing the package and the double slash is deleted, enter it again.


    Select one of the following security options:

      • No Certificate Validation(default)- PATROL Agent uses TLS 1.2 communication channels, but PATROL Agent does not validate the certificate.
      • Certificate Validation - PATROL Agent uses TLS 1.2 communication channels, and PATROL Agent validates the certificate received from server.

    For more information, see Security certificate options. Open link


    Enter the PATROL Agent port number.
    The default port number is 3181.


    Select whether you want to restart PATROL Agent automatically or manually, and click Next.


    Enter the streaming endpoint details in the following format:
    tcp:<IP address or FQDN of the Integration Service>:<port_no>

    This information will be used to register PATROL Agent with TrueSight Operations Management.


    Enter a comma-separated list of tags to associate PATROL Agents to infrastructure policies.
    PATROL Agents use the specified tags to get configuration details from TrueSight Operations Management.

    For example,  WinOS:"Windows OS Monitoring"


    Select whether you want to manage the PATROL Agent configurations via monitoring policy, and click Next.


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

    You can opt to route events via an Integration Service.

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

    Ensure you 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 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.


    Configure the firewall.
    You can opt to add the solutions to the firewall exception list automatically.

  7. Review the deployable package details.
    If you added a monitoring solution that contains sub-components, view the included sub-components by clicking the plus sign.

  8. 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 — Select a file compression format for the installation package.
  9. Click Save and Download.
    To save the package for future installation on the current or other hosts, click Save and download it later from Repository> Deployable package.
    A template of the package is saved to the  installationDirectory\truesightpserver\data\pproxy\installer_templates  folder and is listed in the  Deployable Packages tab.

Step 2: Deploy the package

  1. Log in to the host computer by using the PATROL default account on which you plan to install the PATROL Agent.
    If you are using your host computer username, ensure that you have administrator privileges.
  2. Copy the package that you downloaded to a temporary directory location.
  3. Extract the package.
    It is extracted to the <PA_EXTRACTED_PACKAGE>\bmc_products  directory.
  4. From the bmc_products directory, run one of the following commands:

    • Windows: RunSilentInstall.exe

    • UNIX: ./

          Installation status is displayed.

Step 3: (UNIX only) Post upgrade steps Run hostname__install.log_rootscripts

When deploying the package silently, if you did not enter the root password, you need to run the <hostname>_<port>_install.log_rootscripts script and make some other small modifications. 

  1. Stop the PATROL Agent process if it is running:
    For more information, see Starting and stopping the PATROL Agent . Open link
  2. Navigate to the unpacked installation files directory:
         cd <installation_directory>/log/<date_time_of_install>_install/
         Example: /opt/bmc/log/2021_07_08_05_57_59_install/
  3. Switch to the root user by using the following command and entering the root password:
  4. As root user, rename the <hostname>_<port>_install.log_rootscripts file to <hostname>_<port> by running the following command:
         mv <hostname>_<port>_install.log_rootscripts <hostname>_<port>
         Example: mv myhostname_3181_install.log_rootscripts
  5. As root user, assign the permissions to run the <hostname>_<port> file:
          chmod 755 <hostname>_<port>
          Example: chmod 755
  6. As root user, run <hostname>_<port>
    Example: ./
  7. Run to load environment variables:
    1. Navigate to Patrol3 directory:
      cd <installation_directory>/Patrol3
      Example: cd /opt/bmc/Patrol3
    2. Run
      . ./
  8. Navigate to the Patrol Agent’s bin directory and run
    1. Navigate to the Patrol bin directory:
      cd $PATROL_HOME/bin
    2.  Run the script:
  9. Verify the PatrolAgent/snmpmagt binaries are owned by the root account and that the sticky bit is set:
          ls -tl PatrolAgent
    The following output is displayed:
          -rwsr-xr-x 1 root patrol 12641000 Feb 10 10:39 PatrolAgent
     The S indicates the sticky bit is set successfully on the PatrolAgent binary. (Same for the snmpmagt binary, if present.)

    Learn more about the S bit Open link

  10. Ensure the access file is owned by the default account:
      sudo chown <default_account>:<default_account> <install_directory>/common/security/keys/access
    Example: sudo chown patrol:patrol /opt/bmc/common/security/keys/access
  11. As the default account, start the PATROL Agent.
     For more information, see Starting and stopping the PATROL Agent . Open link

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