Skip to Content
These series of web blogs deals with transports of various components of KM. We are actually in the third part. For those who missed the first two parts feel free to refer from below, KM transports: Part IKM transports: Part II In KM transports II we saw how to create an export package. We actually created an export package and downloaded the package file to the local drive. Now we are gonna import this package in the destination system.  The import is to be done in the destination system with super admin rights. So we log in to the destination portal with an appropriate user. Unlike content package, the config package is always small in size. I have never seen a config package exceeding 1MB in size. So you can email or copy in a secondary storage device (Jump drive goes crazy in this country, seems like everyone has it except for me and I still hesitate to buy one! I don’t know whats the problem with me). But believe it or not for many content transports I did the transport package was minimum 475 MB. It might not be the case for everyone. Still I cant say you for sure a size estimate for content package.  Now its always a good practice that we take a backup of the existing system before we replace some of its properties. So we will first export the config of the destination system and save it as a back up, just in case. We already know how to do an export.. So lets  do an export in the destination system, create a config package that is intended to serve as a backup.  Then we get on to the work now. We will start importing the transport package by going to the path, System Administration >>System Configuration >>  Knowledge Management >> Content Management. Now click on “Actions” menu item, then click on “Import”. You would again see a server started for this operation that you can see in the picture below, image Now it will ask for the local drive config file to be imported. It is a file upload form wherein you have a brows option to isolate your file and submit button to confirm the file. Then it will show you the list of objects that will be changed. Something quite similar to the one below, image Confirm it after you verified. Now you have successfully transported the KM config across landscapes.  In the forth coming web blogs we will see more about content transports. 
To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Jasna Camper
    When my export file was created using the export proceedure it creates a file witht he extension ‘.ConfigCM’.  But when I attempt to import the file I receive the error ‘Enter a valid configuration archive name’.  You neglected to include this step in your process.  If you run into this issue rename the archive file with the extension ‘.configarchive’ and the file will import.
    (0) 

Leave a Reply