Transport of Room Templates and
Room Part Templates 
Use
You can transport room templates and room part templates from one system to another. To do this, you use the corresponding functions for exporting and importing objects.
Integration
To transport room templates and room part templates to a new system, the following fundamental objects in the room templates and room part templates are relevant:
● Worksets
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).
● Template properties
Specific properties are defined for each template. These specific properties are stored different for room templates and room part templates and therefore require different transport procedures.
○ Room template properties
Room template properties are stored in the portal as configuration data.
○ Room part template properties
Room part template properties are stored in the Portal Content Directory (PCD).
Activities
You must make sure that for each template both the workset and the associated template properties are exported and imported.
If the data for a template is not complete in the target system, the template might not be displayed and the behavior of the rooms based on the template might be incorrect.
The special points to follow during transport of worksets and template properties are described below:
Activity |
Description |
Export and import of worksets for room templates and room part templates |
To transport worksets, use the corresponding export and import function in the PCD. You can group the worksets required in one transport package. Transport of worksets that are assigned to templates: ●
Folder for
assigned worksets for room templates: ●
Folder for
assigned worksets for room part templates: These worksets are copies of the original worksets. They are uniquely assigned to the templates in question. Optional: Transport of worksets that are not assigned to
templates: ●
Folder for
initial worksets for room templates: ●
Folder for
initial worksets for room part templates: |
Export and import of room part template properties |
The room part template properties are stored in the PCD, like the worksets. You can 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: ... 1. In the PCD Export iView, choose Portal Content ® com.sap.ip.collaboration ® RoomPartTemplates 2. Choose Add all objects to transport package.
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 In the portal, you can launch the configuration data as follows: ... 1. Choose System Administration ® System Configuration ® Knowledge Management ® Collaboration ® Room and Room Part Templates. 2. Start the export mode by choosing Actions ® Export ® Start. Under Topics, the template link is displayed. 3. Choose template. The primary configuration data for each room template is stored under template. The name of the respective object comprises the template name and the version information, for example, template_&VER&3. This naming convention applies only to newly created and copied templates. In addition to the primary configuration data, you must also add the secondary configuration data to the transport request. 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. |
exporting and
importing configuration data