You are here: Designer Studio > Landing pages > Application > Importing a file by using the Import wizard

Importing a file by using the Import wizard

Import rules and data instances from your file system or repository into your current Pega Platform instance. Use the Import wizard to upload artifacts 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.

  1. ClosedFor IBM DB2 for z/OS, configure the import properties.

    If you are importing an application with schema changes and a separate DB-Admin-DB-Name and you are using IBM DB2 for z/OS, configure the import parameters before you import the application, or the import will fail. For more information about configuring the import parameters, see IBM DB2 for z/OS: Preparing to import an application with schema changes and a separate DB-Admin-DB-Name. For more information about your application, see your database administrator.

  2. Click Designer Studio > Application > Distribution > Import.
  3. Import a file in one of the following ways:
    ClosedFrom a local file system:
    1. Browse to the local file.
    2. Click Next.
    ClosedFrom a repository:
    1. Enter the Repository name.
    2. Select the Artifact type from the list. The listed artifact types depend on the repository definition.
    3. Select the artifact Name.
    4. Click Next.
    ClosedFrom a file on server:

    This option displays files that are in the service export directory.

    1. Select the file from the Select a file from the server to import list.
    2. Click Next.

  4. Optional: To view the components of the file and select individual instances to load, click Show content details.

  5. Optional: To display a detailed view of the contents of the imported file, select the Enable advanced mode to provide more granular control over the import process check box.

  6. Optional: To limit import time, select Do not set restore point or save metadata. If you do not set a restore point, you cannot roll back to the current state of your system.

  7. Optional: If you are importing a code archive, a default Codeset name and Codeset version are displayed. You can override the default values.

  8. Click Next to begin the import. If you selected the check box in step 4, click Next again.

    During the import, the system confirms that each imported ruleset version has the same or a higher ruleset version identified as a prerequisite. For example, you cannot import a product archive exported from a Pega Platform 05-03-01 system into a Pega Platform 04-02-60 system.

  9. ClosedIf applicable, respond to missing dependency error messages:

    If a dependency is missing from the target system, an error message is displayed. You can either stop the import or continue with missing dependencies. The best practice depends on the specific missing item and your system:

    • If the only error message refers to missing hotfix dependencies and recommends that you ignore the missing dependencies:
      1. Select Allow import with missing dependencies.
      2. Click Next to continue the import.
    • For production systems, if you see any other error message:
      1. Cancel the import.
      2. Correct the missing dependency.
      3. Repeat the import.
    • For testing or development systems, if you see any other error message, you can either cancel the import or allow the import to continue with missing dependencies. If there are missing dependencies and you continue with the import, some rules might not work correctly.

  10. To close the form, click Done.

Related information

Open topic with navigation