STEP 1. Configuring IBM AD Configuration Server

About this task

The IBM® AD Configuration Server component can run with the default settings. If the default settings are not compatible with your environment, you can configure the component and overwrite the default settings.

Procedure

  1. Configure the settings in the <IBM ADDI Installation Folder>/IBM Application Discovery Configuration Service/conf/server.properties file.
    1. Configure the port that IBM AD Configuration Server listens on by setting the value of the server.port parameter.
      The default value is 2181.
    2. Configure the number of the snapshots and the corresponding logs that are retained by IBM AD Configuration Server. To configure the setting, set the value of the zookeeper.autopurge.snapRetainCount parameter.
      The default value is 4, and the minimum value is 3.
    3. Configure the time interval in hours for the purge task by setting the value of the zookeeper.autopurge.purgeInterval parameter.
      The purge task deletes old snapshots and the corresponding log files according to the time interval. The default value of the parameter is 24. To enable the purge task, you must set a value that is greater than 0.
  2. Configure the web server settings in the <IBM ADDI Installation Folder>/IBM Application Discovery Configuration Service/conf/log4j2.properties file.
    1. Configure the root logger level and the appenders by setting the log4j.rootLogger parameter with one of the following values:
      • OFF
      • FATAL
      • ERROR
      • WARN
      • INFO
      • DEBUG
      • TRACE
      • ALL
      The default log level is INFO. The default appenders are file, which indicates a rolling file appender, and stdout, which indicates a console appender.
      Example
      log4j.rootLogger=DEBUG
    2. Configure the file roller appender log level by setting the log4j.appender.file.threshold parameter with one of the following values:
      • OFF
      • FATAL
      • ERROR
      • WARN
      • INFO
      • DEBUG
      • TRACE
      • ALL
      Note: If you do not set the value of the log4j.appender.file.threshold parameter, the file roller appender log level is the same as the root logger level. To set the log4j.appender.file.threshold parameter, the value must be lower than or equal to the root logger level.
      Example
      log4j.appender.file.threshold=ERROR
    3. Configure the file roller appender location by setting the value of the log4j.appender.file.File parameter.
      Note: The value of the log4j.appender.file.File parameter must be a valid absolute or relative path.
      Example
      log4j.appender.file.File=/home/user/logs/server.log
    4. Configure the file roller appender minimum number of backup files to keep by setting the value of the log4j.appender.file.MaxBackupIndex parameter.
      Example
       log4j.appender.file.MaxBackupIndex=5
    5. Configure the file roller appender maximum file size by setting the value of the log4j.appender.file.MaxFileSize parameter.
      Example
      log4j.appender.file.MaxFileSize=100M
  3. Make sure that IBM Application Discovery Configuration Service Admin is up and running. If any error occurs, start the service manually:
    • On Windows
      1. Go to Start Menu > IBM Application Discovery and Delivery Intelligence and Launch IBM Application Discovery Configuration Service Admin.
      2. If the service does not start, check the server.log file under <IBM ADDI Installation Folder>/IBM Application Discovery Configuration Service/ folder.
    Important: For monitoring the IBM AD Configuration Server tasks, see Checking the log files of components.