Show TOC

Transporting KM ContentLocate this document in the navigation structure

Use

You use the transport function to transport KM content from one system to another (for example, from a test system to a production system).

The system can handle the transport of the following KM content:

  • Collections

  • Resources

  • Links

Note

Links are transported, but target items are not. If the target item of a link does not exist in the target system, the link does not work.

The following metadata associated with the KM content can be transported:

  • Standard properties such as file size, creation date, last changed by, and so on

  • Custom properties

  • Access Control Lists (ACLs)

  • Globally Unique Identifiers (GUIDs)

You specify the KM folders or files you want to transport in the transport package.

Note

The system does not transport application properties, and therefore it does not transport metadata based on KM application properties, except for the data specified in the Repository Services Data table below. The transport of metadata based on other persistent storages is also not supported.

The system only transports the values of predefined properties. If you want to use the predefined properties of the source system in the target system, you have to transport the property definitions from the configuration before transporting KM content. More information Transporting Configuration Data .

The following table explains the scope of the transported repository services data:

Data

Transportable

Ratings

No

State Management

Yes

Time-Dependent Publishing

Yes

Layout Service

No

Access Statistics Service

No

Service ACL

Yes

Discussions

No

Subscriptions

Yes

Feedback

No

Comments

No

Personal Notes

No

Versions

Only the current version is transmitted in each transport.
Prerequisites

If you want to enable the scheduling and automate the import of pending KM transport packages, you must have the system administrator portal role assigned to your user.

Procedure

To transport KM content from one system to another, proceed as follows:

  1. Optional: If you want to perform a transport more than once or regularly, create an export template. For more information, see Creating a KM Export Template .

  2. Create a new transport package in the source system, selecting all items that you want to transport. You can perform the transport either manually or using the Change and Transport System (CTS). For more information, see Exporting KM Content .

  3. Import the transport package to the target system. This makes the KM content from the source system available in the target system. For more information, see Importing KM Content .

  4. Optional: You can schedule and automate the import of pending transport packages. For more information, see Automating the Import of Pending Transport Packages .

You can use status overviews and log files to see whether or not an import or export was successful or had errors. For more information, see Monitoring Exports and Imports .