This article provides an overview of what is involved in migrating data and or configuration settings from FootPrints Service Core version 11.6.01 (or a later service pack) to FootPrints 12.1.XX - 20.XX.
There are several tools available to assist in the migration process. The Migration Advisor tool runs on your FootPrints version 11.6.01+ installation, and provides a report and analysis of your existing FootPrints system to use when planning the migration.
Check Footprints Support site for latest version of Migration Advisor tool. Once you have run the Migration Advisor tool and created your report, contact BMC Technical Support to review the report and learn about next steps and the other tools.

• When you run the tool, a Migration Advisor Report link is created which links to a MigrationAdvisorReports\Analysis_yyyy-mm-dd-hh-mm.html file in the "base install folder" of where FootPrints 11.6.01+ is installed. Example: C:\FootPrintsServiceCore\MigrationAdvisorReports\Analysis_2014-04-13-16-44.html NOTE: An older version of the utility places the files in C:\FootPrintsServiceCore\UpgradeAdvisorReports Open this file in any of the suggested browsers:
  • Internet Explorer 9+
  • Firefox
  • Chrome
• The report displays estimated times needed to perform a migration of your system to version 12.1.XX - 20.XX, as well as information about items found in your FootPrints 11.6.01+ install with links to knowledge base articles that provide information and guidance in mitigating the differences in functionality between FootPrints 11.6.01+ and FootPrints 12.1.XX - 20.XX and assist in proper configuration of the FootPrints 12 feature referenced in the report. Review each item in the report thoroughly and view the knowledge base articles linked to from the report.
• The Migration Advisor can be run as many times as needed.
• The Migration Advisor does not make any changes to the existing system.

Please follow the instructions below to run the Migration Advisor.

There are certain scenarios for migrating from footprints 11 to footprints 12.1.XX - 20.XX. User has to replace a file basename.pm in FP11 location "C:\FootPrintsServiceCore\bin\Perl\lib\File" before starting with migration process. PFA: basename.pm.
 

Footprints 11 Version	Footprints 12 Version	Steps to be performed before starting the migration process
11.6.09/11.6.10.001/11.6.10.002	20.19.02/20.19.03	This scenario is not possible The user has to migrate FP11 mentioned versions to 20.19.01 or lower version and then upgrade to 20.19.02.
11.6.09/11.6.10.001/11.6.10.002	20.18.03/20.19.01	No Need to replace the file in FP11 install folder
11.6.11	20.19.01	Need to replace file basename.pm in FP11 install folder location "C:\FootPrintsServiceCore\bin\Perl\lib\File"
11.6.11	20.19.02/20.19.03	Need to replace file basename.pm in FP11 install folder location "C:\FootPrintsServiceCore\bin\Perl\lib\File"

 

1. Download the Migration tool.  The download is available from this article:  Download the FootPrints Service Core 12 Migration Advisor
2. Once the Migration Advisor tool is obtained, follow the steps below for either Windows or Linux.

Windows

1. Place it on the FootPrints 11.6.01+ application server in a folder outside the FootPrints install folder.
2. Unpack the footprints-service-core-migration-advisor-12.x-nn.nn.zip file into the folder where it was placed.
3. Navigate to that folder and run the setup.cmd file to start the Migration Advisor.
4. Once started, the Migration Advisor displays information in a command prompt window before displaying the wizard's Welcome message. Do not close the command prompt window. It closes when the Cancel button or the Done button on the last screen of the wizard is pressed.
5. Press the Next button.
6. Enter or browse for the location of the "base install folder" where FootPrints 11 is installed. Examples: C:\FootPrintsServiceCore or D:\Footprints
7. Press Next. Note the amount of time estimated to run.
8. Press Next again to start the analysis of the system.

Linux NOTE: It is highly recommended to run the Migration Advisor on Linux logged into the graphical desktop environment as a user that has the following permissions:

• a user that has read and write permission in the "base install directory" (i.e. /usr/local/footprintsservicecore) of the FootPrints 11.6.01+ install.
• a user that has write permissions in the /tmp directory on the server.

The "root" user of the server automatically has these permissions. However, testing indicates if the Migration Advisor is run using su privileges, the graphical Migration Advisor tool does not start. Therefore, logging into the desktop environment as root resolves the issue.

1. Be sure to download the correct footprints-service-core-migration-advisor-NNbit-12.x-nn.nn.tar.gz file (where NN is 32 or 64 for the bitness of the FootPrints 11 application server. For example:
   32 bit - footprints-service-core-migration-advisor-32bit-12.x-nn.nn.tar.gz 64 bit - footprints-service-core-migration-advisor-64bit-12.x-nn.nn.tar.gzIf it is unknown as to whether the system is 32 or 64 bit, run the uname -m command. If it is a 32 bit system, the output will be (one of): i386, i486, i586 or i686. If it is 64 bit the output will be: x86_64.
2. Create a directory (named such as MigrationAdvisor or MA) and move the footprints-service-core-migration-advisor-NNbit-12.x-nn.nn.tar.gz file in it.
3. cd into the newly-created directory.
4. Unpack the footprints-service-core-migration-advisor-NNbit-12.x-nn.nn.tar.gz file using a command such as:
   tar xzvf footprints-service-core-migration-advisor-NNbit-12.x-nn.nn.tar.gz
5. Make the setup.bin file executable as well as the jre/bin/java file.
6. Export the display using a command such as:
   export DISPLAY=:0.0 OR export DISPLAY=localhost:0.0
7. Run the setup.bin script:
   ./setup.bin
8. Once started, the Migration Advisor displays information in the shell window before displaying the wizard's Welcome message. Do not close the shell window.
9. Press the Next button.
10. Enter or browse for the location of the "base install directory" where FootPrints 11.6.01+ is installed. Examples: /usr/local/footprintsservicecore or /opt/footprints
11. Press Next. Note the amount of time estimated to run.
12. Press Next again to start the analysis of the system.