Creating a batch configuration file


Use this task to apply the same configuration settings to multiple PATROL for DB2 UDB consoles by creating a batch template file. Use either of the subtasks described in this task to create the batch file.

Before you begin

The PATROL account for the operating system must have read and write permissions to the $PATROL_INSTALL/db2/conf directory. Also, this account must have write permission in pconfig.

To create a batch configuration file from the PATROL console

  1. Use the PATROL console and configure the KM settings as needed.
  2. Right-click the DB2_SETUP icon (or DB2EEE_SETUP for PATROL for DB2 UDB EEE) and select Configuration > Create Batch Template.
     The $PATROL_INSTALL/db2/conf/db2_batch_conf.tpl file is generated.
  3. Open the db2_batch_conf.tplfile, and then edit it, as follows:
    1. Change the default account entries. Passwords (the configuration_value for DefaultAccount entries) in encrypted or unencrypted format can be entered in the db2_batch_conf.tpl file.
    2. If you are using this file for another host name, change the hostname entry field. Do not remove the colon character because it is required as a column separator.
    3. Edit the other keywords, as required. For information about the keywords, see Keywords to be used as configuration variables.
  4. Save the file as a text-only file using one of the following file names:
    • db2_batch_conf.conf
    • db2_batch_conf portNumber.conf

      Warning

      Note

      The db2_batch_confportNumber.txt file will be processed only by the PATROL Agent running with that port number. Use this file name in situations where several PATROL Agents are running on one computer or where the $PATROL_INSTALL directory is mounted across several computers running the PATROL Agent.

      When DB2_SETUP or DB2EEE_SETUP discovery runs, if a db2_batch_conf portNumber.conf file is found, the file will be processed. If a matching db2_batch_conf portNumber.conf file does not exist, and a db2_batch_conf.conf file does exist, that file will be processed. Be aware of the following changes that occur to the file name during processing:

  • During processing, the file name suffix changes to configuring.
  • If processing completes with no errors, the suffix changes to done.
  • If processing completes with errors, the suffix changes to errs.
Information
Example

During processing, db2_batch_conf.conf changes to db2_batch_conf.configuring, and then to db2_batch_conf.done (no errors) or db2_batch_conf.errs (with errors).

All valid lines are processed, even if errors are found on some lines. After processing, passwords are encrypted. If the file is renamed again, the passwords must be changed to plain text.

To create a batch configuration file outside PATROL

  1. Use a text editor to open the following file located in the $PATROL_INSTALL/db2/conf directory:
    db2_batch_conf.sample

    Warning

    Note

    You can open the file in a word processing program, but the word processing program must allow you to save the file in a text only or MS-DOS text format.

  2. Add line formats describing configurationVariableName that you want to configure for a specific computer HOSTNAME. For information about the keywords that you can use as configurationVariableName, see Keywords to be used as configuration variables.
  3. Save the file in the $PATROL_INSTALL/db2/conf directory as a text-only file using one of the following file names:
    • db2_batch_conf.conf
    • db2_batch_conf portNumber.conf (for a particular PATROL Agent). Be aware of the file name changes that occur during processing as described in step 4. All valid lines are processed, even if errors are found on some lines. After processing, passwords are encrypted. If the file is renamed again, the passwords must be changed to plain text.

 

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

BMC PATROL for DB2 Universal Database 9.0