Operation > 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
  1. 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.
  2. 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.
  3. 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
  1. 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.
  2. 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.

  3. 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 Topics Link IconRelated Information