Exporting and Importing Tenants 

Use

You can transport a tenant and its content from one SAP NetWeaver Portal to another; for example, when moving from a test or staging environment to a production environment.

You use the standard Package Export Editor on the source portal to create a transport package containing the relevant folders and objects for each tenant. You then use the Package Import Editor on the target portal to import the contents of the transport package. After importing the package, you need to perform some additional procedures to fully configure the tenant on the target system.

For general information about transporting packages, see Transport of Portal Objects.

 

Prerequisites

On the source portal:

·        If any objects you want to export are direct delta links to source objects located in the Content Provided by SAP folder, you need to change the ID prefix of the delta link objects so that they do not contain com.sap.pct or com.sap.portal. Objects with these IDs are automatically filtered from the export.

Note that this requirement refers to unit or standalone objects only. For example, if the framework page embedded in a portal desktop contains the ID com.sap.portal, you do not need to change the ID of the framework as it is an embedded object, not a unit object.  

On the target portal:

·        You have enabled multitenancy portal support in the UME on the target system. See Enabling UME to Support a Multitenant Portal.

 

Procedure

Exporting a Transport Package

All steps for exporting a transport package are documented in detail the Portal Administration Guide in the section: Creation of an EPA Archive for the Portal Export.

The basic process flow for exporting a package in a multitenant portal includes the following steps:

...

       1.      Use the Package Export Editor in the portal to create a new transport package; at this point the package is empty.

       2.      Populate the transport package with content you want to export.

For each tenant, we recommend you choose the following tenant-specific folders and objects:

¡        The unique portal tenant system object.

¡        The tenant's folder in the Portal Catalog (Portal Content/Tenants/<Tenant name>).

¡        Portal themes.

Additional folders and objects not included in the tenant's folder should also be considered; however, depending on the configuration of your multitenant portal, you may decide to exclude them from the transport package and recreate them manually on the target portal following the import. For example:

¡        Tenant-specific rule collection objects specifying display rules for portal desktops. If all rules are defined in the Master Rule Collection (main_rules) object, then you may want to export it, as well (see Master Rule Collection).

¡        Additional system objects relevant for connectivity to content-based backend systems.

       3.      Select the option to include personalization data with export content, if it exists. Optional.

       4.      Perform the export to create an Enterprise Portal Archive (EPA) file on the server of the source portal.

       5.      Check the status of the export using the log file.

Note the following:

·        You can create Software Deployment Archive (SDA) and Software Component Archive (SCA) files to include applications, such as PAR applications and Web Dynpro applications, in your transport package. For more information, see Creation of SDA and SCA Archives.

·        The Package Export Editor allows you to include the permissions assigned to selected folders and objects. We do not recommend using this option; rather reassign all permissions manually on the target portal.

Importing a Transport Package

All steps and rules for importing a transport package are documented in detail the Portal Administration Guide in the section: Importing EPA Archives.

The basic process flow for importing a package to a multitenant portal includes the following steps:

...

       1.      Copy the exported EPA archive created during the export to any import directory on the target portal.

       2.      Use the Package Import Editor in the portal to import the EPA archive.

To deploy SDA or SCA archives to the portal, use instead the SAP Software Deployment Manager.

       3.      Redeploy the PAR file containing customized branding images for the tenant.

       4.      Assign portal permissions to the tenant's folders in the Portal Catalog so that each tenant has access to its content only. Permissions also need to be applied to other folders that are not in the tenant's folder.

Refer to "Permissions" in Initial Folders, Content, and Permissions for Tenants as a guideline for assigning permissions.

For additional information, see Creating Content and Assigning Permissions.

Make sure the new content is not available to other tenants.

       5.      In the Tenant Management screen, open the tenant for editing and then save it.

This step is important for reconnecting the new portal to the ABAP client of the user store. When you save the tenant, the status of the tenant changes to Connected if the connection to the user store is successful.

       6.      Test the portal tenant; this includes:

                            a.      Logging on to the portal as a tenant using its specific portal alias.

                            b.      Checking access to the user store.

                            c.      Checking functionality of tenant-specific content.

 

Result

The objects and folders in the transport package are created in the same Portal Catalog folders in the target portal as in the source portal. The target portal is able to connect to the ABAP client of each tenant's user store.