Configuring using PATROL Configuration Manager

In addition to using the AWS Account Configure menu command, you can also use the PATROL Configuration Manager to configure AWS accounts by using the following methods:

Before using PATROL Configuration Manager to change the configuration of a Knowledge Module (KM), BMC recommends that you ensure that PATROL Configuration Manager is set up to save or backup the configuration.

To enable backups in PATROL Configuration Manager

  1. From the main menu, select File > Configure > Application.
  2. In the Configure: Application dialog box, select the Archives tab to open the Backup Settings.
  3. Ensure that the Save Backup Before Apply option is selected.
  4. Click OK to save the settings.

Configuring an Amazon Web Services account using the PATROL Configuration Manager menu commands

  1. In PATROL Configuration Manager, right-click the agentHostName where you are monitoring Amazon Web Services.
  2. Right-click agentHostName and select Configuration > Get.
    The account status is displayed in the Job Status Information dialog box. When PATROL Configuration Manager completes the transfer of the configuration variables from the selected host, the line that represents the host becomes green and OK is displayed in the Status field for the host.
    The Configuration > Get command copies the pconfig variables from the Agent, converts them into rules, and pastes them into PATROL Configuration Manager in the following folder: 

    RuleSets\PCM\backup\agentHostName\agentHostName\date-timestamp 

    The following figure shows the Configuration > Get menu command in the left panel of the PATROL Configuration Manager. An example of the rules is displayed in the right panel after the Configuration > Get command finishes importing the configuration variables from the Agent. Each rule in PATROL Configuration Manager contains a configuration variable. A RuleSet is the entire set of rules for an Agent.  
  3. Select the directory with the most recent timestamp, at the bottom of the list.
  4. To add an Amazon Web Services account, complete the following steps:
    1. Right-click the directory with the most recent timestamp and select New Rule
    2. In the RuleSet dialog box, double-click the highlighted space in the Variable column and add the AWS/acct_name/displayName variable.

      The value of the displayName variable does not support blank spaces and special characters such as /, \, &, and @.

    3. In the Operation column, select the REPLACE option.
    4. Double-click the highlighted space in the Value column and enter the value of the DisplayName variable.
    5. Click OK
    6. Repeat #step a to #step efor the following variables:
      • /SecureStore/AWS/acct_name/AccessKey
      • /SecureStore/AWS/acct_name/SecretKey 

        For information about the description and values of these variables, see PATROL Agent configuration variables.
  5. To modify an Amazon Web Services account, complete the following steps:
    1. Right-click the rule containing one of the following variables and select Edit Rule:
      • /AWS/acct_name/displayName
      • /SecureStore/AWS/acct_name/AccessKey
      • /SecureStore/AWS/acct_name/SecretKey 

        BMC recommends you to not modify the account name in the displayName variable because you might end up lose all data history related to the original account name of the Amazon Web Services instance. If you change the account name with which you are monitoring an Amazon Web Services instance, PATROL Agent treats the new name as a new Amazon Web Services account instance.

        For information about the description and values of these variables, see PATROL Agent configuration variables.

    2. In the RuleSet dialog box, modify the value of the variable as required.
    3. Click OK.
  6. To delete an Amazon Web Services account, right-click the rules containing the following variables and select Delete:
    • /AWS/acct_name/displayName
    • /SecureStore/AWS/acct_name/AccessKey
    • /SecureStore/AWS/acct_name/SecretKey 

      For information about the description and values of these variables, see PATROL Agent configuration variables.
  7. If you have modified or added an AWS account, drag the new RuleSet onto the agentHostName in the left pane.
  8. Click the Apply Configuration icon in the PATROL Configuration Manager menu bar.

Adding or modifying pconfig variables manually

Some configuration variables are not automatically available, and cannot be activated by using a menu command. You must enter these variables manually by using the PATROL Developer console.You must be sure to enter valid values because PATROL Configuration Manager does not verify or notify you if the value you enter is invalid. All of the variables and their valid values are listed under the topic PATROL Agent configuration variables.

To add, modify, or delete a pconfig variable manually

  1. Right-click the host, and select Development > Agent Configuration.
  2. To add a variable, complete the following steps:
    1. From the main menu, select Edit > Add Variable to display the Add Variable dialog box.
    2. In the Variable field, enter the instance name (if required) and then the variable.
    3. In the Value field, enter the value you want to apply to the variable.
      For more information about valid values, see PATROL Agent configuration variables.
    4. To save the configuration, select File > Save.
  3. To modify the value of a variable, complete the following steps:
    1. Select the variable you want to modify.
    2. From the main menu, select Edit > Modify Variable to display the Modify Variable dialog box.
    3. Double-click the entry from the Change Entries list.
    4. In the Value field, modify the value of the variable.
      For more information about valid values, see PATROL Agent configuration variables.
    5. To save the configuration, select File > Save.
  4. To delete the value of a variable, complete the following steps:
    1. Select the variable you want to delete.
    2. From the main menu, select Edit > Delete Variable.
    3. The values for the selected variable is deleted.
    4. To save the configuration, select File > Save.

For instructions on how to add a variable or RuleSet using PATROL Configuration Manager, see the PATROL Configuration Manager User Guide.

Configuring Amazon Web Services accounts by using the PATROL Configuration Manager CLI 

The PATROL Configuration Manager CLI processes a script file that contains commands regarding RuleSets.

To configure an Amazon Web Services account by using the PATROL Configuration Manager RuleSets, you must set the values for the pconfig variables in the pllrulesets.cfg file. After modifying the file, you can apply those changes to the configured PATROL Agent by using the PATROL Configuration Manager CLI. For a list of configuration variables, see PATROL Agent configuration variables.

PATROL for AWS creates the pllrulesets.cfg file at the following location:

  • (UNIX) $PATROL_HOME/../pll/rulesets
  • (Windows) %PATROL_HOME%\pll\rulesets

When you apply RuleSets to the configured PATROL Agent, the PATROL Agent automatically configures all the accounts for which the RuleSets have been created.

Copy the pllrulesets.cfg file to any directory under the %BMC_ROOT%/pconfmgr/rulesets directory and use the following command to apply the RuleSets:

  • (Windows) pcm.cmd -f scriptFileName
  • (UNIX) pcm.sh -f scriptFileName

The scriptFileName variable represents the script file that contains commands to be executed for applying RuleSets. For example, to apply RuleSets, enter the following command in the script file:

apply -a agentName RuleSetsFileName

The RuleSetFileName variable represents the name of the RuleSets file.

Note

In the preceding command:

  • Specify the path as relative to the RuleSets directory.
  • Do not add the extension while specifying the file name.

For more information about the commands and options that can be used in a script file, see the PATROL Configuration Manager User Guide.

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

Comments