If you want to prevent the custom content from becoming a system-scope content, you can export the custom objects and resources as a package and delete them from the Orchestrator server before enabling the multitenancy feature. After enabling multitenancy, you can import these objects to a particular tenant or tenants.

Note:

You can import the same package to multiple tenants independently. You cannot import to a tenant a package that exists in the system scope and you cannot import to the system scope a package that exists as a tenant-specific content.

Prerequisites

Verify that multitenancy is not enabled on your vRealize Orchestrator 7.4 .

Procedure

  1. Log in to the Orchestrator client as an administrator.
  2. Create a package for export.
  3. Export the package.
  4. Delete the exported package from the Orchestrator server.
  5. Enable multitenancy.
  6. Log in to the Orchestrator client as a tenant administrator to import the package to the particular tenant.
  7. Import the package.