Import Wizard: Data Source tab
The Data Source tab of the Import Wizard is the first tab shown when adding a new data source or editing an existing data source. The Data Source tab contains four sub-tabs:
From the General sub-tab, the user is able to specify the name of the Data Source; this will be the name displayed in the Data Import Management page when the data source has been created or amended.
The user should select the Audit Tool that will be providing the inventory data for import; this is selected in two stages. The user selects the Inventory Type from the Inventory Type drop-down list.
This list contains a number of options to choose from, namely:
- ADDM (Oracle)
- Capacity Plan
- ComplianceConsole (Legacy)
- License Optimizer Generic
- Ivanti Discovery
- Oracle ReviewLite 12.3
- Tivoli configuration Manager
Upon selecting an option from the Select Audit Tool drop-down list, the File Types pane is updated to display the file types that the user may choose to include in the data source. With the example shown above, the available file types are the Hardware File and Software File file types. If the user wishes to include either of the file types in the data source, the user should check the Active checkbox for the file type that they wish to include.
When file types are made active, the General sub-tab is updated to show any relevant additional properties (based on the file types made active). In the example shown above, the user is prompted to specify:
•Whether hardware records should be automatically generated for any software records that have no matching hardware record
Software records cannot exist in License Optimizer without a related hardware record. This option tells License Optimizer how to handle software records where the hardware detailed by the software record does not already exist:
•If the user checks the checkbox to have License Optimizer create hardware records in such cases, License Optimizer will create a hardware record and link the software record to it.
•If the user does not check the checkbox, License Optimizer will ignore the software record. (The log file will report records that have been ignored by the import).
•How hardware records should be identified.
Hardware records must have one field which can be used to identify each item; this is usually done with a unique ID. However where a unique ID is not available, License Optimizer can take the name of the OSI and combine it with the Business Unit to identify each item; this prevents License Optimizer from importing duplicate hardware records multiple times.