BDNA Data Platform 5.5
ADDM provides functionality to export native data to an RDBMS or CSV format. The following instructions show how to export ADDM data into either of these formats.
| 1. | In the ADDM console, navigate to Administration > Export |
| 2. | Create a new Mapping Set: |
| a. | Select the “Mapping Sets” tab. |
| b. | Create a new Mapping Set named “normalize-mapping-set”. |
Note • Normalize requires a specific set of fields from ADDM. Several of those fields are not in the standard “extended-rdv-mapping-set”
|
OBJECT_NAME |
COLUMN_NAME |
Used by |
In Standard |
|
HOST_CI |
DOMAIN |
Yes |
Yes |
|
HOST_CI |
HOST_HOSTNAME |
Yes |
Yes |
|
HOST_CI |
HOST_KEY |
Yes |
Yes |
|
HOST_CI |
HOST_KEY_HASH |
Yes |
Yes |
|
HOST_CI |
LAST_UPDATE_SUCCESS |
Yes |
Yes |
|
HOST_CI |
MODEL |
Yes |
Yes |
|
HOST_CI |
NUM_LOGICAL_PROCESSORS |
Yes |
Yes |
|
HOST_CI |
NUM_PROCESSORS |
Yes |
Yes |
|
HOST_CI |
OS |
Yes |
Yes |
|
HOST_CI |
OS_EDITION |
Yes |
Yes |
|
HOST_CI |
OS_VERSION |
Yes |
Yes |
|
HOST_CI |
PARTITION |
Yes |
No |
|
HOST_CI |
PROCESSOR_SPEED |
Yes |
Yes |
|
HOST_CI |
PROCESSOR_TYPE |
Yes |
Yes |
|
HOST_CI |
RAM |
Yes |
Yes |
|
HOST_CI |
SERIAL |
Yes |
Yes |
|
HOST_CI |
VENDOR |
Yes |
Yes |
|
HOST_CI |
VIRTUAL |
Yes |
No |
|
PACKAGE_CI |
PACKAGE_DESCRIPTION |
Yes |
No |
|
PACKAGE_CI |
PACKAGE_KEY_HASH |
Yes |
Yes |
|
PACKAGE_CI |
PACKAGE_NAME |
Yes |
Yes |
|
PACKAGE_CI |
PACKAGE_OS |
Yes |
Yes |
|
PACKAGE_CI |
PACKAGE_VERSION |
Yes |
Yes |
|
PACKAGE_CI |
VENDOR |
Yes |
No |
|
PACKAGE_HOST_REL |
HOST_KEY_HASH |
Yes |
Yes |
|
PACKAGE_HOST_REL |
PACKAGE_KEY_HASH |
Yes |
Yes |
|
SI_CI |
EDITION |
Yes |
Yes |
|
SI_CI |
PUBLISHERS |
Yes |
No |
|
SI_CI |
SI_KEY_HASH |
Yes |
Yes |
|
SI_CI |
SI_TYPE |
Yes |
Yes |
|
SI_CI |
SI_VERSION |
Yes |
Yes |
|
SI_HOST_REL |
HOST_KEY_HASH |
Yes |
Yes |
|
SI_HOST_REL |
SI_KEY_HASH |
Yes |
Yes |
Mapping Set tab
| 3. | Import the following files into the new mapping set: |
| • | host.xml |
| • | si.xml |
| • | package.xml |
Note • The .xml files listed here are included with this .pdf file as Attachments. For those viewing the online help, the .xml files can be obtained from the .pdf version of the BDNA User Console User Guide.
| 4. | Create a new ADDM SQL Server database. |
| 5. | Execute the following script on the new SQL Server database: |
| • | Normalize-ADDM-Exporter-(MSS).sql |
Note • The .sql file listed here is included with this .pdf file as an Attachment. For those viewing the online help, the .xml files can be obtained from the .pdf version of the BDNA User Console User Guide.
| 6. | Select the “Adapter Configurations” tab. |
Adapter Configurations tab
| 7. | Click Edit to edit the Adapter Configuration. |
| 8. | Select the Microsoft SQL Server (JTDS Driver) in the Database Driver drop-down. |
For more information about adding new drivers, click here: http://discovery.bmc.com/confluence/display/83/RDB+adapter+-+Adding+a+new+JDBC+driver
| 9. | Enter a Connection URL using the required syntax. For example: |
jdbc:jtds:servertype://server[:port][/database][;property=value][;property=value]
Editing the adapter configuration
| 10. | Select the “Exporters” tab. |
| 11. | Create a new Exporter named “Normalize”. |
Exporters tab
| 12. | Select the new Adapter Configuration and the new “normalize-mapping-set”. |
Adapter Configuration and Mapping Set
| 13. | Run the Normalize Exporter. |
BDNA Data Platform 5.5 Administration Help Library02 August 2016 |
Copyright Information | Flexera |