The extended RDB mapping set
The Extended RDB mapping set provides a set of mapping files for exporting the main BMC Discovery inferred nodes, except for Host Based Adapters (HBAs).
In version 10.2, the host.xml mapping file was modified: the interface_name, interface_speed, interface_duplex, and interface_negotiation are no longer exported with the Network Interface CI information by default.
If you need to export the mentioned details, customize the Extended RDB adapter mapping set by uploading the host.xml file (for more information on customizing a mapping set, see Managing mapping sets).
When importing data to the external database, you need to modify the default database scripts used for initial configuration on the RDB side to match the introduced changes in the export schema. You can download a sample customized scripts for Oracle, MySQL, and for SQLServer: SQLServer.sql and SQLServer.osql.
This mapping set was developed to serve as the basis of a best practice, used to export BMC Discovery data to RDBMS. It is not intended to be the only best practice, nor does it cover all use cases.
The extended RDB Mapping set is designed in such a way that it can be used to form a modular export. That is, the user can pick and match any of the mapping files in the mapping set to decide what they want to export. Each mapping file contains a main node and relevant relationships to other nodes. The exception to this (no relationships) is the Host mapping, as this is expected to form the basis of any export set.
As an example, the BAI mapping file exports to a BAI table, as well as to a BAI-to-Host relationships table. If you include only the Host and BAI mapping files then they will export all data related to both nodes and the relationship links. If you want to include SI in your exports, then this will export the SIs and relationships to BAIs and Hosts.
The idea behind this is to allow flexibility in the export schema while maintaining consistency. If a new node is to be added to the export, then the same process should be applied.
All mapping files will only export data that has been modified since the last export date. This functionality can be overridden by de-selecting the Export Changed Items flag when defining the Exporter.
The Extended RDB mapping set is made of the mapping files as described below.
BAIs, relationship to Hosts, Cyclic dependencies to: Contained BAIs, DependedOn BAIs
BAI: bai_key, name, description, type, version
bai_ci, bai_contained_bai_rel, bai_dependedon_bai_rel, bai_host_rel
Hosts, Network Interfaces and related Subnet
Host: host_key, host_hostname, host_name, description, domain, model, serial, ram, max_ram, workgroup, vendor, os, os_edition, os_version, os_eos, os_eoes, num_processors, num_logical_processors, processor_type, processor_speed, cores_per_processor, power_watts, btu_h, u_size, hw_eos, hw_eoes, host_created_date, host_modified_date, last_update_success
Switches, Switch Ports, relationships to Network Interface and Hosts
Switch: switch_key, switch_name, description, status, model, ostype, osversion
switch_ci, switch_host_rel, switch_interface_ci
Software Instances: relationships to Hosts and BAIs; Cyclic dependencies to: peer-to-peer communicating SIs, client-server communicating SIs, Contained SIs, DependedOn SIs
Software Instance: si_key, si_name, si_type, si_version, product_version, prod_release, edition, service_pack, build, patch, revision, si_eos, si_eoes
si_ci, si_host_rel, si_client_server_comms_rel, si_contained_si_rel, si_dependedon_si_rel, si_peer_to_peer_comms_rel, si_bai_rel
Packages and Hosts with those packages installed
Package: package_key, package_name, package_version, package_revision, package_os, package_created_date, package_modified_date
Patches and Hosts with those patches installed
Patch: patch_key, patch_name, patch_os, patch_created_date, patch_modified_date
Files and relationships to SIs and Hosts
File: file_key, file_path, file_size, file_md5sum, file_last_modified, file_created_date
file_ci, file_host_rel, file_si_rel
Clusters and relationships to member Hosts
Cluster: cluster_key, cluster_name, cluster_type, cluster_created, cluster_modified
Virtual Hosts and related Physical Hosts
SI running virtualisation software: v_instance_key, v_instance_name, v_product_name, v_product_version, v_product_last_update_success, v_product_created, v_product_modified
Export Host Containers and their Host relationships
Host container: host_container_key, host_container_name, host_container_type, host_container_created, host_container_modified
Extended RDB mapping schema
The following diagram provides a description of the target schema.
Configuration on the RDB side
To create this schema, the Extended RDB mapping set is provided with the following database specific scripts in the $TIDEWAY/java/integrations/mappings/extended-rdb directory:
There are also generic SQL statements in each of the mapping (xml) files for reference.
In the MySQL command line client:
In a command window:
sqlplus <user>/<password>@<SID> -d <databasename>
In a command window:
osql -S <hostname>[,<port>] -U <user> -P <password> -i <file>