Moving applications between systems
You can migrate rules and data between instances of Pega Platform by using interactive tools in Dev Studio or by using command-line tools. You can develop rules on one system and deploy them on other systems. As a best practice, use Deployment Manager to promote applications.
Check this list of available tools and supported operations to choose the appropriate tool for your purpose.
| Task | Tool | Interactive | Command line | Export | Import | Migrate |
| As a best practice, use Deployment Manager to promote an application from one system to another. | See Getting started with Deployment Manager | |||||
| Create a product rule that can be used for exporting or migrating an application. | Application Packaging wizard | X | ||||
| Migrate a product or an application from a source system to one or more target systems or export to a file system. | Product Migration wizard | X | X | X | ||
| Export an application, a ruleset, a product, or a patch to a file system or repository. | Export gadget | X | X | |||
| Create or modify a product rule and optionally download an export file to your local file system. | Product rule form | X | X | |||
| Create a product rule that can be used for exporting or migrating work items. | Package Work wizard | X | ||||
| Import rules and data from a file system or repository to your system. | Import wizard | X | X | |||
| Migrate a product or an application from a source system to a target system or export to a file system. | Product Migration command-line tool | X | X | X | ||
| Use scripting to export rules and data to a file system or repository, or import from a file system or repository by using a web service to connect to an active instance. | prpcServiceUtils command-line tool | X | X | X | ||
| Use scripting to export rules and data to a file system, or import from a file system by using a direct connection to the database. | prpcUtils command-line tool | X | X | X |
- IBM Db2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name
If you plan to import an application with schema changes and a separate DB-Admin-DB-Name and you are using IBM Db2 for z/OS, follow these instructions to configure the import parameters before you import the application, or the import fails.
- Preparing to package and move applications
Before you move your application, prepare the source and target system.
- Packaging your application in a product rule
Use product rules to migrate or deliver an application to another Pega Platform systems. Product rules identify the rulesets and versions, rules and data objects, and other parts of an application. Define a product rule to specify what to include in the archive. Then use one of the other tools to create the product rule.
- Packaging an application from App Studio
Package your application to create an archive on your local system that you can import to another system.
- Exporting an application, product rule, or ruleset to an archive or repository by using the Export wizard
Export rules from a Pega Platform system into an product rule, archive file, or repository by using the export wizard. An archive is useful for sharing rulesets between instances of Pega Platform.
- Importing rules and data by using the Import wizard
Import rules and data instances from your file system or repository into your Pega Platform instance by using the Import wizard. Rules, data, and other artifacts in the imported file are added to the rules that are already in this system. Use the Import wizard to upload archives up to 1 GB in size; for larger files, use File Transfer Protocol (FTP) or another means to place the file into the ServiceExport directory.
- Importing the legacy ruleset from the Resource Kit
Applications that require deprecated rules that are no longer included in the Pega Platform distribution need to import those legacy rules from the Resource Kit.
- Updating dependent applications with the latest versions of built-on applications
You can automatically update dependent applications so that they are built on the latest versions of the applications that you import.
- Using restore points to enable error recovery
Restore points mark a significant point in time for your system. You can roll back to a restore point later to return the rules and data of the system to that point in time. For example, if importing an application caused problems, you might want to roll it back.
- Distributing product rules to multiple systems by using the Product Migration wizard
Use the Product Migration wizard to push your product rule to multiple systems in a single step from the user interface. The wizard simplifies the management of rule assets across Pega Platform systems.
- Distributing an application from command line
For complex application distribution tasks, use the command-line tools to export, import, and migrate rules and data. If you have a running Pega Platform node, need to run asynchronous operations, or you do not have a direct connection to the database, use the prpcServiceUtils tool. If you do not have a running Pega Platform node, use the prpcUtils tool.
- Reviewing migration results
After you move your application, review the results of the move.
Previous topic On-premises only: Running the static assembler from the command line Next topic IBM Db2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name