Searching the Help
To search for information in the Help, type a word or phrase in the Search box. When you enter a group of words, OR is inferred. You can use Boolean operators to refine your search.
Results returned are case insensitive. However, results ranking takes case into account and assigns higher scores to case matches. Therefore, a search for "cats" followed by a search for "Cats" would return the same number of Help topics, but the order in which the topics are listed would be different.
|A single word||
||Topics that contain the word "cat". You will also find its grammatical variations, such as "cats".|
You can specify that the search results contain a specific phrase.
Topics that contain the literal phrase "cat food" and all its grammatical variations.
Without the quotation marks, the query is equivalent to specifying an OR operator, which finds topics with one of the individual words instead of the phrase.
Two or more words in the same topic
|Either word in a topic||
|Topics that do not contain a specific word or phrase||
|Topics that contain one string and do not contain another||
|A combination of search types||
- Migration Procedure
How to Migrate DDMI Server Configuration Data to Universal Discovery
To migrate DDMI server configuration data to Universal Discovery, do the following:
Export DDMI server configuration data
Locate the DDMIMigration.pl script on the UCMDB Server at the following location:
- Windows: C:\hp\UCMDB\UCMDBServer\tools\migration
- Linux: /opt/hp/UCMDB/UCMDBServer\tools\migration
Copy the script to any directory on each DDMI server that you want to migrate.
For each DDMI server, open a Command prompt and navigate to the directory where you copied the script. At the Command prompt, run the following command:
You can see the following message:
- By default, the data is archived in a file called DDMIMigrationData.zip.
- For options that are available for this script, see Server Configuration Data Export Script Resources.
- Maximum amount of device groups that can be imported is 20. If device groups exceed 20, remove some groups and run the script again. Then, create the remaining management zones in Universal Discovery manually.
For more information about the type of information that is migrated, see Results.
Import the data to Universal Discovery
Open the JMX Console, enter importMigrationDatafromDDMI in the quick search field and click the link that appears.
In the importMigrationDataFromDDMI method, the following parameters are displayed:
Note: It is recommended to import DDMI server configuration data to a clean probe because of IP Address conflict issues.
customerId. The customer ID that you want to migrate.
If you do not know the customerId parameter for the customer you are migrating, do the following:
- In UCMDB, go to Data Flow Management > Data Flow Probe Setup.
- In the Domains and Probes pane, select a Data Flow Probe and note the customer name at the top right of the window.
- Go to JMX Console > Customer and States > ShowAllCustomers method and note the customerId that maps to the customer name.
- True. Creates new activities in Management Zones. These activities contain the migrated data.
False. No activities are created. However, Management Zones are created.
primary|Secondary Call Home Address. The primary and the secondary Call Home IP addresses for the Data Flow Probe.
<UD_CallHomeIPAddressPrimary> , <UD_CallHomeIPAddressSecondary>
- If this field is left blank, the IP address of the Data Flow Probe is used.
- In some cases, data that is entered in these fields may not appear in the UCMDB Infrastructure activity. In these cases, reenter the data in the activity.
- The DDMI Call Home IP addresses are pre-populated, so it is not necessary to enter this information.
probeName. The name of the Data Flow Probe to which to map the data.
- configurationzipPackageName. The name of the archive file that was created in step 1.
- True. The XML Enricher global configuration file in UCMDB is overwritten by the DDMI configuration file.
- False. The XML Enricher global configuration file in UCMDB is not overwritten and the DDMI configuration file is ignored.
Specifies how to handle IP address range conflicts.
- True. If overlapping IP address ranges exist in DDMI and UCMDB, no IP address ranges are imported to UCMDB.
- False. If the same IP address range exists in UCMDB, only IP address ranges that are not in conflict are imported. Ranges that are in conflict are ignored. Additionally, Management Zones that contained the conflicted ranges are not imported.
- Success messages and warning messages are displayed.
- For some common issues that may occur, see Server Configuration Data Import Troubleshooting.
- In addition to the data that is contained in the archive file that was created in step 1, the following information is imported into UCMDB:
Deployment credentials. Credentials are imported and keys are regenerated automatically.
SNMP configuration profile.
- VMware configuration.
XML Enricher configuration file.
For details, see overrideGlobalConfig..
IP address ranges.
Additionally, the following resources are imported:
- Pre-scan and post-scan scripts
- Scanner configuration files (.cxz)
- User SAI files
- However, not all information exported from DDMI can work properly in Universal Discovery, further tuning is required. For details, see How to Configure Universal Discovery.
Basically, only the following information from DDMI is used for Universal Discovery without any change:
- Deployment credentials.
- SNMP configuration profile.
- VMware configuration.
- XML Enricher configuration file.
- Pre-scan and post-scan scripts.
- User SAI files.