/
KGS Migration4ArchiveLink (MIG)

KGS Migration4ArchiveLink (MIG)

Introduction

KGS Migration4ArchiveLink is a Java-based software application which allows you to migrate the contents of any SAP ArchiveLink® compliant document storage and archiving system.

Ever since archiving solutions exist, document migrations have been required. KGS Migration4ArchiveLink allows you to define and control migration processes for SAP data and documents.

You may manage and monitor every aspect of the migration while necessary steps are being executed in the background.

System Requirements

For the system requirements please see: Prerequisites for KGS Software Components

If the migration is used in combination with the proxy and you want to use the same database for both products, then two different users with different schemas for the database must be provided for both products.

Licensing

In order to use KGS Migration4ArchiveLink follow the guide for requesting licences: KGS Software licensing

Migration Modes

KGS Migration4ArchiveLink supports migration runs in two different modes:

  • Online Migration

  • Offline Migration

Both migration modes have in common, that you may define a list of identifying data which determines which documents have to be migrated. The difference is, how this identifying data is being obtained.

Online Migration

This feature is no longer available from version 3.2.6

When setting up an online migration, the KGS Migration4ArchiveLink uses an RFC (Remote Function Call) session to obtain all document references  visible to your SAP system.

At this point, only basic metadata such as content repositories and object categories (we currently support the following: Images, Print Lists, Data Objects) are being read from the SAP configuration tables.

This information will be stored in the KGS Migration4ArchiveLink repository.

Please note: The table BDS_BAR_EX will not be automatically part of an online migration and has to be exported manually. You may use SAP transaction SE16

SAP tables being used

SAP tables being used

TOA01

TOA02

TOA03

TOAHR

TOADL

ADMI_FILES

Offline Migration

When setting up an offline migration the KGS Migration4ArchiveLink doesn't connect to your SAP system at all.

Instead you'll have to manually add the repositories which should be included in the migration run. You'll also have to provide a list with the Archive Document IDs, representing all documents that are going to be migrated.

You may either create this kind of list by an SAP transaction or through SQL statemets. This approach has the advantage that the user will be able to exclude documents from the migration process (e.g.: if the documents are too old or unused).



Installation

KGS Migration4ArchiveLink is being shipped as a web archive container (WAR file). Depending on your webserver the installation procedure might differ.

Sample installation for Apache Tomcat 7 via WebUI

Open your tomcat's "Manager App", go to section WAR file to deploy, select "KGSAdmin-MIG.war" and click on the button Deploy.

After the deployment procedure has been completed a new web application called KGSAdmin-MIG will appear in the list of the installed web applications.

Please note: If the name of the *.war-file was changed, that the name of the deployed web application has been changed as well.



Sample installation via webapps-folder

After downloading KGS Migration4ArchiveLink you unzip the contents of the downloaded zip-archive to <Webserver-installation-folder>/webapps.

The zip-archive contains KGS Migration4ArchiveLink in form of a war-container, which will be automatically decompressed by Tomcat Webserver.

After tomcat has finished decompressing the war-container you may restart Tomcat webserver one time.

Please note: Depending on the hardware and system Tomcat Webserver is being executed on it might take some time to decompress the content of the war-archive.

Setting up a migration process with an external SQL database

KGS Migration4Archivelink is being shipped with an integrated database (H2 database). If you intend to use an external database (i.e.: Oracle, Microsoft SQL Server, etc.), you'll have to define and configure a database connection to the external database ( Main → Edit Configuration → Database).

If you intend to use the database which has been shipped with KGS Migration4ArchiveLink you may skip this step.

Additional Requirements for Online Migrations

In order to be able to perform online migrations an SAP connection has to be setup in the KGS SAP Connector (Main → KGS SAP Connector).

Please find additional information about the configuration of KGS SAP Connector here: KGS SAP Connector.