Skip to Content
0

Export FSDB repository from Knowledge Management

Mar 02 at 07:45 AM

30

avatar image

Hi,

we need to export documents from CM Repository configured as FSDB (File System for files; Database for Metadata and properties).

We have a huge volume of data so we have doubts about exporting/importing timeouts and size limits.

How should one face this? With ICE, CTS?

What about timeouts? Should we separate in smaller folders or is it possible to export/import all the repository together?

Is there any size limit for exporting files?

Thanks.

10 |10000 characters needed characters left characters exceeded
* Please Login or Register to Answer, Follow or Comment.

1 Answer

Cathal Kelly
Mar 12 at 09:20 PM
0

Hi Iker,

There are several options available for you through which you could export or transport this content. The most straightforward would probably be the standard KM Transport Service -

https://help.sap.com/saphelp_nw73/helpdata/en/49/b4dfbadcfc6bf9e10000000a421937/frameset.htm

This can be configured to use either CTS or the file system. As outlined in the above documentation, the following prerequisite is in place should you wish to use CTS -

"If you want to transport KM content using the Change and Transport System (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 CTS."

If using the File System option, a .kmc transport package will be created on the file system and this may then be imported using the KM Transport service in the destination system.

The Content Exchange Service or ICE as it's better known may also be used to transport this content. This can be performed either online or offline and both methods are described in greater detail here -

https://help.sap.com/saphelp_nw73ehp1/helpdata/en/4c/3ad89b093c5791e10000000a15822b/frameset.htm

The online option (distributing content using HTTP) would typically be used if performing regular scheduled transports of content in a specific location between portal environments. It requires the configuration of both a syndicator and subscriber.

Regardless of which method is used, we would generally recommend keeping transport packages to a size of no more than 2GB if possible. When transporting a large volume of content, we would recommend breaking the content into multiple packages of approximately 2GB at most and transporting these one at a time.

Kind regards,

Cathal

Share
10 |10000 characters needed characters left characters exceeded