Configuring the source and target systems

Configure the source and target systems to migrate products from the command line.

1. Set up users on the source and target systems. The users must have product export( zipMoveImport ) and import ( zipMoveExport ) privileges, and SchemaImport privileges if you want to migrate schema changes. The systems use these users for authentication, and to invoke the services.
2. Add target systems on the source system:

   From the user interface

   1. From the Application Explorer, navigate to the Data-Admin-System-Targets class.

   2. Click the class node type with the icon. The Designer Studio work area displays a list of target system instances.
   3. Click Create to create a new instance.
   4. Enter a Short description and a Unique Name of Target System, and click Create and open.
   5. In the rule form, enter:

      • Https? : Select this check box if you want to use HTTP with Secure Sockets Layer protocol for product migration.

      • Host Name : Enter a target server host name. This can be a machine name or an IP address.

      • Port Number : Enter a target server port number, such as 8080.

      • Context Root : Enter a target server context root name, such as prweb or prweb.war.

   6. Click Save to save the rule.
   Note: If you add target systems from the user interface, the system prompts you for the login credentials during migration.

   From the command line

   Add target systems from the command line by using the addTarget action under the Manage target systems category in the Command-line tool actions topic.

3. Configure the PegaDiagnosticUser security role on the source system:
   1. Create an instance of Data-Admin-System-Security as PegaDiagnosticUser on the source system. Specify the system granting the access as the source from which migration will be initiated.
   2. Add the same role and user to the tomcat-users.xml file:

      <role rolename="PegaDiagnosticUser"/>
      <user username="pega" password="pega" roles="PegaDiagnosticUser"/>

   3. Restart Tomcat for the changes to take effect. This user is used by the target system to authenticate and download the products for migration.