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 |
|
- Integration Studio
- Integration Studio Overview
- Integration in a Multi-Tenancy Environment
- How to Work with Federated Data
- How to Work with Population Jobs
- How to Work with Data Push Jobs
- How to Set Up an Integration Point
- How to Save an Integration Point Configuration as an Adapter Default
- How to Remove Adapter Defaults
- How to Deploy a Package to a Remote Data Repository
- How to Configure Probe IP Ranges with Active Directory
- How to Increase the Number of Threads for Data Push Jobs
- Integration Studio User Interface
- Limitations
Integration in a Multi-Tenancy Environment
When executing integration queries or jobs in a multi-tenancy environment, all CIs and relationships that are federated or populated from the remote data source are assigned an owner tenant.
Note When executing integration queries or jobs in a multi-tenancy aware environment, the tenants defined in this environment must be a subset of the tenants defined in the data source environment (not multi-tenancy aware environment).
If the data source environment is multi-tenancy aware, when you run a query or a job, only the CIs and relationships of those tenants that you have permissions to view are federated or populated. The owner tenant value is brought in with all of the other attributes.
If the data source environment is not multi-tenancy aware, when you run the query or a job, UCMDB automatically assigns a specified owner tenant value to each of the federated/populated CIs and relationships. For details about selecting an owner tenant value to assign to federated/populated CIs and relationships, see New Integration Point/Edit Integration Point Dialog Box.
Scenario | Tenant Assignment Behavior |
---|---|
Single Tenant → Multi Tenant UCMDB | CIs are pushed to the tenant of the integration user(user default tenant). The target UCMDB tenant is assigned. |
Multi Tenant → Single Tenant UCMDB |
Note In a Single Tenant UCMDB the tenant properties can be made visible by setting Display Tenant Attributes in UI (display.tenant.attributes) to true from the Infrastructure Manager. |
Multi Tenant → Multi Tenant UCMDB |
Note If a CI's tenant is pushed to target UCMDB and the tenant does not exist, then the following error will be logged: ErrorCode [63507] Reconciliation DataIn Multi Tenant : trying to use tenant that does not exist.{<tenant name>}] |
Single Tenant > Single Tenant UCMDB | Not a tenant push scenario |