Cross-Tenancy¶

Within Insights Hub, you can use the Cross-Tenancy functionality to share data between two independent Insights Hub environments. This functionality supports customers and service providers in creating a collaboration for data exchange as a base for data-driven business models.

For example, the maintenance of an asset or the sharing of asset configurations between different environments (tenants). When an asset is shared, the Cross-Tenancy function creates a copy of the static asset data, maintaining the same ID as the original asset. The dynamic asset data is not copied.

It is possible to change the static data (like name, description or geo-location) of a shared asset, although the changes are not propagated back to the original asset. Also, the changes made on the original asset after a sharing is completed are not applied to the copy.

The data is transferred as follows:

• Static data: All static data is copied.
• Inherited static data: Inherited static data is not copied, which leads to the auto-changing of this data.
• Dynamic data: Dynamic data is not copied. Instead, you can retrieve the original dynamic data of the shared asset.

You can request collaborations with other environments in the Settings application. This allows you to share your data in the Insights Hub with other environments by using the Cross-Tenancy functionality. For more information about how to create a collaboration, refer to the Settings documentation.

Once the collaboration is established, both environments can share various types of selected data based on assets via the Asset Manager application. For more information about the concept and how to share an asset, refer to the Asset Manager documentation.

Each action of data sharing requires active approval or rejection by the receiving tenant. Within a collaboration, the sharing tenant always remains the only and exclusive owner of the shared data.

Asset Manager and Insights Hub Monitor support the Cross-Tenancy shared asset function. The apps show the shared assets with a sharing icon. For example, you can display the aggregated data from the shared asset in the Aspects extension.

For more information about how to develop the Cross-Tenancy-Aware application, refer to the HowTo section.

Restrictions¶

The following restrictions currently apply when using Cross-Tenancy functionality:

General Restrictions¶

• Cross-Tenancy is only available for TenantAdmins.
• Sharing assets is only possible if a collaboration exists.
• Shared assets cannot be shared again from the receiver point.
• Sharing of assets derived from core.basicagent is not supported.
• Core plugins (such as MindConnectNano and MindConnectLib) on shared assets are not visible.
• Only single asset sharing is available.
• Shared assets cannot be moved below "normal assets".
• core.sharerenterprise assets cannot be updated.
• It is not possible to update or delete the shared types and aspects by the receiver and sharer tenant.
• Asset instances cannot be created from shared types.
• Sharing is an asynchronous process and therefore takes some time.

Insights Hub Monitor¶

• The plugins Attachments and Rules are not supported yet in Explore / Assets.

Asset Manager¶

• While using asset sharing, sharing of agent assets and updating or deleting core.sharerenterprise type assets must be avoided.

Web Components¶

• Shared asset IDs are not yet supported by the following Web Components: File View and Rule View.

For more information, refer to the Web Components documentation.

Except where otherwise noted, content on this site is licensed under the Development License Agreement.