You can transport room templates and room part templates within your system landscape, for example, from the test system through the consolidation system to the production system.
You cannot transport rooms and room content. You can only transport room templates and recreate rooms based on those templates.
Data in a Template
To transport room templates and room part templates to a new system, the following basic objects in the room templates and room part templates are relevant:
Every room template and room part template is based on a workset that defines the layout of the pages in the room or room part. The worksets for the templates are stored in the Portal Content Directory (PCD).
Specific properties are defined for each template. These specific properties are stored differently for room templates and room part templates and therefore require different transport procedures.
Room template properties are stored in the portal as configuration data.
Room part template properties are stored in the Portal Content Directory (PCD).
You must make sure that you export and import both the workset and the associated template properties for each template.
The data for the template must be complete in the target system. If the data is incomplete, the following problems can occur:
The system does not display the transported templates.
Rooms based on the template in question function incorrectly.
Export and Import of Worksets for Room Templates and Room Part Templates
Use the PCD export and import functions to transport worksets. You can group the worksets required in one transport package.
The system saves worksets that are assigned to the room templates and room part templates under the name of the respective template in the following folders in the PCD.
These worksets are copies of the original worksets. They are uniquely assigned to the templates in question.
If necessary, you can transfer worksets that are not assigned to the target system for test purposes or to create further templates. These worksets do not affect existing templates. They are stored in the following folders in the PCD:
Export and Import of Room Part Template Properties
The room part template properties are stored in the PCD, like the worksets.
You can either use the transport object for the workset or create a new transport object to transport the properties of room part templates. In either case, make sure that for each template both the workset and the associated template properties are transported to the target system.
To add the transport objects to a transport package, proceed as follows:
In the transport package, delete all transport objects for the room part templates that you do not require in the target system. Transporting unchecked transport objects for other room part templates could overwrite room part template properties in the target system.
Export and Import of Room Template Properties
The room template properties are stored as configuration data. Therefore, you must export all configuration data for the room templates and import it to the target system, in addition to the worksets.
The iView com.sap.portal.runtime.config.ieu.component.ImportExportUI provides the functions for exporting and importing configuration data. For more information, see Transporting Configuration Data .
In the portal, you can launch the configuration data as follows:
This includes all configuration objects in subordinate folders whose name contains the same template name as the primary configuration object. For example, this includes extensions, parameters, parameter assignments, paths to Content Management folders, room roles, page permissions, and so on.