Migrate data from ALM/PC to SaaS

This section provides instructions about how to migrate ALM/PC data from on-premises to SaaS.

Every ALM/PC project has its own database schema and file repository. Perform all the steps in this topic for every project you want to migrate to SaaS.

In this topic:

Obtain file repository size

Follow the step below to obtain the size of the file repository from the file server.

1. Open ALM Site Administration.

2. Select the project you want to migrate. In the Project Details tab, under Project Directory, find the file repository path of the project.

3. On the file server machine, go to the repository path of the project and run the following command.

   UNIX

   To summarize the directory and all sub-directories and display size values in a human-readable format, use:

   Copy code

   du –sh <directory name>

   For example,

   Copy code

   root@ubuntu# du -sh /usr/ X11R6
   4.0K /usr/X11

   If you find all your path repositories follow the same path, use the following command to show the summary of only the first level of the sub-directories within the folder. This summary lets you know the size of all the file repositories folders on the same path.

   For example,

   Copy code

   root@ubuntu# du -sh /usr/*
   
   4.0K /usr/X11R6
   96M /usr/bin
   24K /usr/games
   12M /usr/include
   164M /usr/lib
   0 /usr/lib64
   96K /usr/local
   25M /usr/sbin
   197M /usr/share
   4.0K /usr/src

   Linux

   To summarize the directory and all sub-directories and display size values in a human-readable format, use:

   Copy code

   du –sh

   For example,

   Copy code

   $ du -sh svn/ports
   
   6.2M svn/ports

   Windows

   Right-click the folder and select Properties to view the size of the folder.

Back to top

Obtain database schema size

Follow the steps below to obtain the size of the database schema.

1. Open ALM Site Administration.

2. Select the project you want to migrate. In the Project Details tab, under Database Name, find the database schema of the project. Under Database Server, find the server where the schema is located.

3. On the database server, run the following command to obtain the size of the database schema.

   Oracle

   To obtain the size of the DB_USER_SCHEMA schema, connect to the Oracle instance and run the following SQL query.

   • To obtain the size of each database schema, run:

     Copy code

     SELECT SUM(BYTES)/1024/1024 "MB" FROM DBA_SEGMENTS WHERE owner='<SCHEMA>';

   • To obtain the size of all database schemas at one time, run:

     Copy code

     SELECT owner, SUM(BYTES)/1024/1024 "MB" FROM DBA_SEGMENTS group by owner 

   SQL Server

   Run the following command to print a summary of space used in the current database.

   Copy code

   sp_spaceused

   Output:

   Copy code

   database_name database_size
   --------------- ---------------------------
   master 5 MB
   reserved data index_size unused
   --------- --------- ----------- --------
   2176 KB 1374 KB 72 KB 730 KB

   Note: The database_size metric shows the size of the current database in megabytes, including both data and log files.

Back to top

Export database schema

Export the database schema of each project you want to migrate.

Prerequisites

Consider the following prerequisites before you export the database schema.

MD5 software	For example, md5.
FTP server	An FTP server location provided by your CSM during the migration process.

To export the database schema:

Perform one of the following export actions, depending on your database type:

Back to top

Export file repository

Follow the steps below to export the file repository.

1. Open ALM Site Administration.

2. Select the project you want to migrate. In the Project Details tab, under Project Directory, find the file repository path of the project.

3. Connect to the application server, go to the project directory path, and compress the entire file repository folder.

4. Run md5sum.

5. Open a command window, go to the location where the md5.zip file was extracted, and run the following command:

   Copy code

   md5.exe -generate <compressed folder path><compressed folder name.zip>

   For example,

   Copy code

   md5.exe – generate C:\”Documents and Settings”\Desktop\ project1_filereposiotry.zip

   The command returns the md5sum output. For example,

   Copy code

   24BCED0C939DD7E61C6E4CCE252687BE db_schemas.zip

6. Copy the output to a text file.

7. Upload the compressed file repository and the text file to the FTP server.

8. Repeat the above steps for each project you want to migrate.

Back to top

Migrate users to SaaS

Follow the steps below to migrate users from on-premises to SaaS.

1. From the ALM server, search for the site admin schema name.

   1. Log in to the ALM server.

   2. Go to the directory where ALM is installed.

   3. Go to the directory where the siteadmin.xml file is saved.

   4. Open the file and search for the site admin schema name using the DBNAME tags. For example,

      Copy code

      <DbName>qc_sa_esar_db</DbName>

2. Contact the DBAs to search for the users tables on the site admin schema. The DBAs need to then perform a select all query from the users tables.

   For example:

   Copy code

   select * from td.users

3. Copy the results of the select all query into an Excel spreadsheet and upload it to the FTP server.

Back to top

See also:

• Export a project from ALM/PC to SaaS
• Migrate LoadRunner Enterprise to SaaS