The dmanager.conf file is a configuration file used to configure the environment for activities performed on the Manager. The dmanager.conf file is also responsible for setting up the communication ports between the Manager and any other underlying services within BDA.
The following figure shows the basic level configurations of the ports responsible for communication between the Manager and the Agent:
# # This is the dmanager configuration file # # Statistics poll port to listen on poll_port=7001 # Listen for initial node information on this port node_init_port=7002 # Listen for initial node information on this port (encrypted) node_init_ssl_port=7003 # SSL Certificate file ssl_cert_file=/app/clarity/dmanager/etc/server.pem # SSL Private Key (must be PEM formatted) ssl_privatekey_file=/app/clarity/dmanager/etc/server.key debug=off # Manager state file state_file=/app/clarity/dmanager/var/dstate # Manager IP manager_vip=0.0.0.0 dont_import_postgres=true # Configure log rotation max_log_size=10485760 max_number_logs=3 service=static DmanagerMgmtAsyncTask "-t 16" service=static DmanagerMgmtTask "-t 8" service=static DmanagerMgmtAcceptor "-t 1" service=static PollCollector "-t 1" service=static StatsCollector "-s 0 -u 500000" # This is for CMDB service=static CMDBSerializer "-t 1 -n /app/clarity/dmanager/var/cmdb/new -x /app/clarity/dmanager/var/cmdb/proc -p /app/clarity/dmanager/var/cmdb/pend -e /app/clarity/dmanager/var/cmdb/error -i 86400" # transport_layer_backward_compatibility_mode # valid values: true, false # default: false # # If it is set to true, transport_layer_backward_compatibility_mode gives the # manager permission to use older SSL transport layer protocols which are # vulnerable to POODLE or BEAST when communicating with agents and clients that # do not support the latest, most secure, protocols. If you need to communicate # with BDA agents 8.9.00 or older, you need to have this parameter set to true. # # This parameter and comment block are added automatically when a manager is # updated to a new version and the dmanager.conf and mtd.conf files do not # contain a reference to the parameter. If you want to turn off this backward # compatibility mode and not have it re-enabled the next time you upgrade, # please either set the parameter to 'false' or comment out the parameter. transport_layer_backward_compatibility_mode=false
The following table describes each parameter of the dmanager.conf file:
The port where polling operations are performed on the dmanager.
The default value is 7001.
The port where BDA listens for the initial node (agent) information.
The default value is 7002.
The SSL port through which BDA listens for the initial node (agent) information.
The default value is 7003.
This parameter shows the path to the secured signed certificate file.
The default path is:
This parameter shows the path to the secured signed key file.
The default path is:
This parameter enables traces of debugging on the dmanager logs. Valid values are on and off.
The default value is off.
This parameter shows the path to the file containing information about all BDA artifacts. This includes Node(s) information, Objects (DB, Instance) information against the nodes, and the full structure of the Manager artifacts excluding patches, templates and actions.
The default path is:
This parameter shows the Private IP address for the Manager.
The default value usually is 0.0.0.0 for continuous communication.
This parameter shows the maximum size of the log file generated by the Manager, after which the log file gets compressed and a new log file is generated. This parameter enables you to easily administer log files, which are generated in large numbers by the Manager. It also allows automatic rotation, compression, and removal of log files.
The default size is 10,485,760 bytes.
This parameter shows the maximum number of log files that can be generated for a specific service. Once the limit reaches, the oldest one gets deleted, and a new one is created.
The default value is 5.
This is a part of the dmanager service which usually maintains the stack for maximum number of threads assigned. Each thread performs asynchronous task on their respective targets within the dmanager service.
For example, when the threads are 16 (specified by -t 16), the stack container size is set to 16, which allows a limit of 16 child jobs against the activities within the dmanager service. The dmanager can run maximum of 16 threads asynchronously, which means it can trigger only 16 child jobs, and rest of them wait for the stack to be refreshed again. In other words, if you are executing an activity, each job is spawned into their child jobs against each activity.
The default value is 16 and the maximum value is 32.
This is a part of the dmanager service which is responsible for management tasks (such as approving nodes, forgetting nodes, removal of database, and node refresh), mostly performed when the command is executed directly from the backend.
This sample command is executed when you perform any of the mentioned management tasks on the GUI.
The default and the maximum number of threads that can be executed is 8, which is controlled by -t parameter.
Also, if you have set the value of this parameter to 8 and if there are 9 nodes to be approved, then the 9th node will have to wait till the queue gets reduced.
This parameter shows the queue size (maximum number of threads) to create sockets for continuous communication between the Manager and the Agent.
The default value is 1.
This parameter shows the polling queue (maximum number of threads) for communication between the Manager and the Agent.
The default value is 1.
This parameter shows the time interval after which to collect the dmanager statistics for PollCollector, dmanagerMgmtAsyncTask, and system resources.
The default time interval to collect the statistics is 500,000 microseconds.
Valid values are true and false (default).
If you set the value to true, the Manager has the permission to use the older SSL transport layer protocols which are vulnerable to POODLE or BEAST when communicating with Agents and clients that do not support the latest, most secure, protocols.
If the Manager needs to communicate with an Agent version 8.9.00 or earlier, set this parameter to true.
This parameter and comment block are added automatically when the Manager is upgraded to a newer version and the dmanager.conf and mtd.conf files do not contain reference to this parameter.
If you want to turn off the backward compatibility mode and not have it re-enabled, the next time you upgrade, either set the parameter to false or write a comment for this parameter.