
You can move existing layout sets, and the configuration data of all objects used by layout sets, between portals.
For example, you can create a layout set in a test system and then transfer it to a productive system.
You can perform the transport either manually or use the enhanced Change and Transport System (CTS).
If you want to transport KM content using the CTS, you must set up the enhanced CTS beforehand. You must also have created the transport paths.
For more information see the documentation about non-ABAP transports in the documentation about the enhanced Change and Transport System (CTS).
Exporting a Layout Set
When you export a layout set, the system generates an archive file that contains the configuration data for all objects contained in the layout set in question (for example, the data for its collection renderer settings, command groups, and layout controllers). If a configuration object references other configuration objects, this data is also entered into the archive file.
The archive file only contains the configuration data for objects. The corresponding Java classes are not exported. If you have entered Java classes that are not contained in the standard delivery into the configuration of objects, you have to move these manually between portals.
We recommend that you create a copy of the layout set that you want to export before carrying out the export. Save this copy under a meaningful name (see Advanced Copying of Layout Sets ). If you use configuration objects with identical names in the configuration of different portals, conflicts may occur during the import. In some cases, configuration objects with identical names may be overwritten.
You can perform the export manually or use CTS.
To call up the overview of existing layout sets in the system, choose in the portal.
Select the layout set that you want to export, and choose Export . Choose OK .
To export a layout set manually, proceed as follows:
Choose File System , and then choose OK to complete the export.
Choose the link to the exported file and save it in the desired repository.
As soon as the system has generated the archive file you can transport the file to any portal and integrate the layout set there using Import .
To export a layout set via CTS, proceed as follows:
Choose CTS .
On the CTS tab page, the system displays the properties of the transport request. In the Note field you can enter a comment for the transport request.
To generate the transport request, choose Export via CTS .
In the Transport Organizer Web UI, release the transport request.
Importing a Layout Set
Depending on the export mode chosen, you import a layout set manually or use CTS.
If configuration objects with identical names to those in the archive file are already used in the system, these configuration objects are overwritten by those in the archive file.
If you are using your own JAVA classes in the layout set (ones that are not included in the standard delivery), copy them manually from one portal server to the corresponding directories on the other portal server.
Call up the overview of existing layout sets in the system. To do this, choose .
To import a layout set manually, proceed as follows:
Choose Import .
Select the file that contains the layout set to be imported.
Choose Upload .
To import a layout set via CTS, proceed as follows:
Log on to the CTS, and choose Transport Management System or call transaction STMS .
Choose Import Overview .
In the list with SAP systems, select the target system, and choose Display Import Queue .
The import queue of the target system appears.
Select your transport request, and choose
.