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	`AND` `and` `+` (plus symbol) `&` (ampersand)	`cat AND dog` `"cat food"+milk` `"cat food"&"dog food"`
Either word in a topic	`OR` `or` `\|` (pipe)	`cat OR dog` `cat \| dog`
Topics that do not contain a specific word or phrase	`NOT` `not` `!` (exclamation point)	`NOT cat` `! dog`
Topics that contain one string and do not contain another	`^` (caret)	`cat ^ mouse`
A combination of search types	`( )` parentheses	`cat + (dog \| mouse)` `cat \| dog + (! mouse)`

Configuration Management System (CMS)2018.05

Use > Data Flow Management > Integrations > Integration Studio > Integration in a Multi-Tenancy Environment

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.

Tenant Assignment in a Multi-Tenant Scenario
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	If tenant owner property is defined in integration TQL layout then the CI tenant will be pushed. In this case the source UCMDB tenant is assigned. If the tenant owner property is NOT defined in integration TQL layout and there is a Default Owner Name integration point property defined, then this tenant will be assigned in the target environment. In this case the source UCMDB tenant is assigned. No tenant property if cases 1 and 2 from above are not met. 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	If the tenant owner property is defined in the integration TQL then the CI tenant will be pushed. In this case the source UCMDB tenant is assigned. If the tenant owner property is NOT defined in integration TQL layout and there is a Default Owner Name integration point property, then this tenant will be assigned in the target environment. In this case the source UCMDB tenant is assigned. If both tenant owner property is NOT defined in the integration TQL layout and Default Owner Name integration point property in NOT defined then the tenant of the integration user(user default tenant) will be assigned to the pushed CIs. The target UCMDB tenant is assigned. 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

Related Information

Send Help Center feedback