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.
Search for | Example | Results |
---|---|---|
A single word | cat
|
Topics that contain the word "cat". You will also find its grammatical variations, such as "cats". |
A phrase. You can specify that the search results contain a specific phrase. |
"cat food" (quotation marks) |
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. |
Search for | Operator | Example |
---|---|---|
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 | ^ (caret) |
cat ^ mouse
|
A combination of search types | ( ) parentheses |
|
- Integrating Multiple CMDBs
- Integrating Multiple CMDBs Overview
- Use Cases – Multiple CMDB Deployments: Discovery-CMS Solution
- Multiple Deployments with Version 9.x/10.x CMDBs Using Population
- Multiple Deployments with Version 9.x/10.x CMDBs Using Data Push
- Federation in Version 9.x/10.x CMDBs
- How to Perform Initial UCMDB-UCMDB Synchronization
- How to Configure Global ID Generation
- How to Use SSL with the UCMDB 9.x/10.x Adapter
- How to Set Up Integrations Between Multiple CMDBs
- How to Push Data from Authorized State to Actual State
- How to Protect CIs from Being Deleted on Target CMDBs during Data Push
- Troubleshooting and Limitations
How to Set Up Integrations Between Multiple CMDBs
The following steps describe how to create integration points and jobs to integrate between
-
-
Navigate to Data Flow Management > Integration Studio.
-
Click the New Integration Point button to open the New Integration Point Dialog Box. For details, see New Integration Point/Edit Integration Point Dialog Box.
Enter the following information:
Name (A-Z) Recommended Value Description Integration Name <user defined> The name you give to the integration point. Integration Description <user defined> Free text that describes the integration point. Adapter UCMDB 9.x or UCMDB 10.x The adapter that is used to integrate between multiple CMDBs. Is Integration Activated selected Select this check box to create an active integration point. Hostname/IP <user defined> The name or IP address of the remote CMDB machine.
Note: For a push synchronization, if the remote UCMDB machine is a High Availability environment, use the remote UCMDB Write-VIP URL.Port 8443 The port listened to by the UCMDB API. Web application Root Context
<user defined> The root context value of the remote CMDB. If no root context is defined on the remote CMDB, leave this field empty. Protocol HTTPS (SSL) Selects the protocol to be used for connecting to the remote CMDB. Valid values are:
-
HTTP
-
HTTPS (SSL)
Credentials ID Remote UCMDB If you must create a new credential protocol, use the Generic Protocol as a basis. For details, see Universal CMDB Discovery and Integrations Content Guide. Customer Name <user defined> The name of the remote UCMDB from which you want to retrieve data. Remote Machine State <user defined> The state with which you want to connect when integrating with multi-state CMDBs.
-
Actual
-
Authorized
Push Back Ids For Population <user defined> Introduced in version 10.21, allows you to schedule the pushback of global IDs after CIs are populated into UCMDB, without creating an integration point when using UCMDB 10.x adapter.
Valid values: Enabled, Disabled. Default: Disabled.
Push Back Ids For Push <user defined> Introduced in version 10.21, allows you to schedule the pushback of global IDs after CIs are pushed into UCMDB, without creating an integration point when using UCMDB 10.x adapter.
Valid values: Enabled, Disabled. Default: Disabled.
Data Flow Probe <user defined> Specifies which data flow probe will be used by the integration. Default Owner Name <user defined> The name of the owner tenant that should be assigned to the federated, populated, or pushed CIs and relationships.
Note
-
This field is displayed when creating a federation or population type integration point in a multi-tenancy environment only.
-
If no owner tenant is specified, but the Data Flow Probe selected for the integration point has an owner tenant, then the Data Flow Probe owner tenant is assigned to all discovered CIs.
-
The System Owner Tenant is assigned when:
- no owner tenant is specified, and no owner tenant is defined on the Data Flow Probe
- the data source is not a multi-tenancy environment
-
In case of push, the tenant assigned can be taken into consideration as explained in Tenant Assignment in a Multi-Tenant Scenario.
Additional Probes <user defined> Additional probes over which to run a federation-type integration. Click to select the additional probes.
When the integration runs, if additional Data Flow Probes are defined, the server uses the most available Probe.
-
-
Click Test Connection to ensure that the integration point has been successfully created, and then click OK.
-
Click OK.
You can use your integration point with any of the methods described below, population jobs, data push jobs, or federation.
-
-
Define and run a population job.
An out-of-the-box integration point already contains population jobs. This step is relevant only when creating additional population jobs.
Select the Population tab to define a population job that uses the integration point you defined above. For details, see New Integration Job/Edit Integration Job Dialog Box.
Note
-
When integrating between multiple CMDBs, population queries must be set up for the source CMDB.
-
Select the Allow Integration Job to delete removed data check box if you want your population job to allow deletion of CIs and links from the source CMDB.
-
By default, infrastructure CIs and containment relationships are deleted. All other CIs and relationships are retained.
-
For Multi-tenancy users: When running population with the Cmdb10xAdapter in a multi-tenancy environment, the tenants are automatically synchronized. To receive changes about the tenants (owner and user), Owner Tenant and Consumer Tenants must be defined in the TQL query layout.
-
-
Define and run a data push job.
Select the Data Push tab to define a data push job that uses the integration point you defined above. For details, see New Integration Job/Edit Integration Job Dialog Box.
Note
-
When integrating between multiple CMDBs, data push queries must be set up on the local CMDB.
-
Select the Allow Deletion check box for each query if you want your data push job to allow deletion of CIs and links from the remote CMDB.
-
By default, infrastructure CIs and containment relationships are deleted. All other CIs and relationships are retained.
-
For Multi-tenancy users: When running data push with the Cmdb10xAdapter in a multi-tenancy environment, the tenants are automatically synchronized. To receive changes about the tenants (owner and user), Owner Tenant and Consumer Tenants must be defined in the TQL query layout.
-
-
Select CI types and attributes to be federated.
-
Navigate to Data Flow Management > Integration Studio.
-
Click the Federation tab.
-
Select the CI types you want to federate from the source CMDB.
If desired, you can select only attributes to be federated. For details, see Federation Tab.
-
Click Save Integration Point .
-
We welcome your comments!
To open the configured email client on this computer, open an email window.
Otherwise, copy the information below to a web mail client, and send this email to cms-doc@microfocus.com.
Help Topic ID:
Product:
Topic Title:
Feedback: