Configuring the BMC Database Automation adapter
You configure an adapter in Grid Manager. The configuration provides information about how the adapter interacts with the BMC Database Automation application. While each adapter must have a unique name, you can create multiple adapters with the same adapter type to allow for different configuration properties.
To configure the actor adapter
- Log on to the BMC Atrium Orchestrator Grid Manager.
- Access the adapters page, by clicking the Manage tab; then click the Adapters tab.
- In the Adapters in Repository list, select the bmc-adapter-bmc-database-automation-actor check box.
- Click Add to Grid to include the adapter in the Adapters on Grid list.
- Click Configure corresponding to the newly added adapter.
- On the Add an Adapter Configuration page, perform the following substeps to configure the adapter using the form view or jump to step 7 to configure the adapter using the XML view:
- Enter a name for the adapter.
- Enter a description for the adapter.
- Under Properties, enter or select values for the configuration elements.
The configuration elements for each adapter are described in that adapter's section. Include all required elements indicated with an asterisk (*).
- (optional) Configure the adapter in the XML view using the following substeps:
- Enter a name and a description for the adapter.
- Click Switch to XML View.
- On the Warning message that appears, click Switch View.
Copy the configuration elements from the XML sample into the Properties text box, and then click OK.
- On the Warning message that appears, click Save.
This saves the adapter configuration with settings in the XML view permanently. The newly configured adapter is now listed in the Adapters on Grid list.
The following table describes the node elements required to configure the actor adapter.
Node elements required to configure the actor adapter
The following figure shows an XML sample for configuring the actor adapter.
XML sample for configuring the actor adapter
<use-ssl-certificate>true</use-ssl-certificate>
<install-certificate>true</install-certificate>
<allow-unsigned-certificate>true</allow-unsigned-certificate>
<signature-properties mode="key-files">
<private-key-file>D:\User1\ssl\BBDA_client_certs\server.key</private-key-file>
<certificate-file>D:\User1\ssl\BBDA_client_certs\server.pem</certificate-file>
</signature-properties>
</config>
Enabling custom logging
To enable custom logging for the adapter, you must specify a log file name. You can also provide additional parameters for logging.
- Log File Name: Provide a name for the log file.
This file will be stored in the AO_HOME/tomcat/logs directory. If Log File Max Backup Index value is greater than 0, the log file name is suffixed with the backup index. For example, if the parameter value is a.log, backup log files will have names, such as a.log.1, a.log.2. - Log File Size: Specify a size limit for the log file.
If the value specified for Log File Max Backup Index is greater than 0, when the specified size is reached, the current file is renamed with the suffix .1. Otherwise, the log file will be reset and over-written. The default value is 10MB. The available units are KiloBytes (KB), MegaBytes (MB) or GigaBytes (GB). - Log File Max Backup Index: Enter the maximum number of backup files allowed. The default value is 10.
- Log File Append: Select this option to append new log information to the existing information in the file. If unselected, the file will be overwritten with new log information.
Log Level: Enter the logging level using one of the following choices:
Logging level
Description
DEBUG
The most detailed logging level; logs low-level messages, normal execution, recoverable erroneous conditions, and unrecoverable erroneous conditions
INFO
(default)
Logs normal execution, recoverable erroneous conditions, and unrecoverable erroneous conditions
WARN
Logs recoverable erroneous conditions and unrecoverable erroneous conditions
ERROR
The least detailed logging level; logs only error conditions that are not usually recoverable