Skip to main content

         This documentation site is for previous versions. Visit our new documentation site for current releases.      

Installing the command-line tool

Updated on August 25, 2021

Install the command-line tool from the file, which is in the ResourceKit folder on the Pega Platform distribution media.

  1. Copy and extract the file. The extracted folder structure contains:
    • logs folder: Logs of the command-line tool. The rolling file appender creates one file per day, and the latest log file has no time stamp on its name.
    • productMigrationResources/lib folder: The JAR files that are required to run the tool.
    • file: The configuration file that you can use to set properties for invoking each of the available parameters.
    • prlog4j2.xml file: The log4j configuration file that you can use to configure logging for the tool.
    • productMigration.bat file: The Windows bat file that you can use to invoke the tool.
    • file: The bash script that you can use to run the tool on Linux or UNIX.
    • ProductMigration-Readme.txt file: A text file that describes the available parameters.
  2. Set the JAVA_HOME environment variable to a valid JDK 6, JDK 7 or JDK 8 directory.
  3. Based on your environment, run the productMigration.bat or file to use the actions described in the Command-line tool actions topic. You can invoke the tool by performing one of the following actions:
    • Specify the parameters in the file.
    • Use the command line arguments.
    • Specify some parameters in the file and others from the command line.
    Note: The command line arguments take precedence over the parameters specified in the file.
  • Previous topic Migrating products and applications from the command line
  • Next topic Configuring the source and target systems

Have a question? Get answers now.

Visit the Support Center to ask questions, engage in discussions, share ideas, and help others.

Did you find this content helpful?

Want to help us improve this content?

We'd prefer it if you saw us at our best. is not optimized for Internet Explorer. For the optimal experience, please use:

Close Deprecation Notice
Contact us