Chapter 32. Process instance migration

Procedure

1. Download the rhpam-7.13.5-add-ons.zip file from the Software Downloads page for Red Hat Process Automation Manager 7.13.
2. Extract the rhpam-7.13.5-add-ons.zip file.
3. Extract the rhpam-7.13.5-process-migration-service.zip file.

4. Enter the following commands to create the database tables. Replace <user> with your user name and <host> with the name of the local host:

   $ psql -U <user> -h <host> -d rhpam7 -f ~/process-migration/ddl-scripts/postgres/postgresql-quartz-schema.sql
   $ psql -U <user> -h <host> -d rhpam7 -f ~/process-migration/ddl-scripts/postgres/postgresql-pim-schema.sql

   Copy to Clipboard Toggle word wrap
5. Change directory to the process-migration directory.

6. Use a text editor to create the servers.yaml configuration file with the following content and save in the process-migration directory. In this example, replace <user_name> and <password> with the credentials to log in to the KieServer.

   kieservers:
     - host: http://localhost:8080/kie-server/services/rest/server
       username: <user_name>
       password: <password>

   Copy to Clipboard Toggle word wrap

7. Use a text editor to create the datasource.yaml configuration file with the following content datasource.yaml and save in the process-migration directory. In this example, replace <user_name> and <password> with the credentials to log in to the database:

   quarkus:
     datasource:
       db-kind: postgresql
       jdbc:
         url: jdbc:postgresql://localhost:5432/rhpam7
       username: <user_name>
       password: <password>

   Copy to Clipboard Toggle word wrap

8. Rebuild the quarkus-run.jar file to include the PostgreSQL driver:

   $ java -jar -Dquarkus.launch.rebuild=true -Dquarkus.datasource.db-kind=postgresql quarkus-app/quarkus-run.jar

   Copy to Clipboard Toggle word wrap

   The output of this command should be similar to the following example:

   INFO [io.qua.dep.QuarkusAugmentor] (main) Quarkus augmentation completed in 2657ms

   Copy to Clipboard Toggle word wrap

9. Run the quarkus-app JAR file:

   $ java -jar -Dquarkus.http.port=8090 -Dquarkus.config.locations=servers.yaml,datasource.yaml quarkus-app/quarkus-run.jar

   Copy to Clipboard Toggle word wrap

   This command returns output similar to the following example:

   __  ____  __  _____   ___  __ ____  ______
    --/ __ \/ / / / _ | / _ \/ //_/ / / / __/
    -/ /_/ / /_/ / __ |/ , _/ ,< / /_/ /\ \
   --\___\_\____/_/ |_/_/|_/_/|_|\____/___/
   2022-03-11 13:04:18,261 INFO  [org.fly.cor.int.lic.VersionPrinter] (main) Flyway Community Edition 7.14.0 by Redgate
   2022-03-11 13:04:18,262 INFO  [org.fly.cor.int.dat.bas.BaseDatabaseType] (main) Database: jdbc:postgresql://localhost:5432/rhpam7 (PostgreSQL 13.4)
   2022-03-11 13:04:18,280 INFO  [org.fly.cor.int.com.DbMigrate] (main) Current version of schema "public": 1.0
   2022-03-11 13:04:18,281 INFO  [org.fly.cor.int.com.DbMigrate] (main) Schema "public" is up to date. No migration necessary.
   2022-03-11 13:04:18,601 INFO  [org.qua.imp.jdb.JobStoreCMT] (main) Freed 0 triggers from 'acquired' / 'blocked' state.
   2022-03-11 13:04:18,603 INFO  [org.qua.imp.jdb.JobStoreCMT] (main) Recovering 0 jobs that were in-progress at the time of the last shut-down.
   2022-03-11 13:04:18,603 INFO  [org.qua.imp.jdb.JobStoreCMT] (main) Recovery complete.
   2022-03-11 13:04:18,603 INFO  [org.qua.imp.jdb.JobStoreCMT] (main) Removed 0 'complete' triggers.
   2022-03-11 13:04:18,603 INFO  [org.qua.imp.jdb.JobStoreCMT] (main) Removed 0 stale fired job entries.
   2022-03-11 13:04:18,624 INFO  [org.kie.ser.api.mar.MarshallerFactory] (main) Marshaller extensions init
   2022-03-11 13:04:18,710 INFO  [org.kie.pro.ser.imp.KieServiceImpl] (main) Loaded kie server configuration for: org.kie.processmigration.model.config.KieServers$KieServer9579928Impl@4b6b5352
   2022-03-11 13:04:18,715 INFO  [org.kie.pro.ser.RecoveryService] (main) Resuming ongoing migrations ...
   2022-03-11 13:04:18,856 INFO  [io.quarkus] (main) process-migration-service 7.59.0.Final-redhat-00006 on JVM (powered by Quarkus 2.2.3.Final-redhat-00013) started in 1.443s. Listening on: http://0.0.0.0:8090
   2022-03-11 13:04:18,857 INFO  [io.quarkus] (main) Profile prod activated.
   2022-03-11 13:04:18,857 INFO  [io.quarkus] (main) Installed features: [agroal, cdi, config-yaml, flyway, hibernate-orm, hibernate-orm-panache, jdbc-db2, jdbc-h2, jdbc-mariadb, jdbc-mssql, jdbc-mysql, jdbc-oracle, jdbc-postgresql, narayana-jta, quartz, resteasy, resteasy-jackson, scheduler, security, security-jdbc, security-ldap, security-properties-file, smallrye-context-propagation, smallrye-health]

   Copy to Clipboard Toggle word wrap
10. To access the Process Instance Migration application, enter http://localhost:8090/ in a web browser .
11. When prompted, enter the user name admin and the password admin1!. The Process Instance Migration console appears.

Procedure

1. To add passwords to anew or existing keystore file for the PIM Keystore Vault, use the keytool command. For example:

   $ keytool -importpass -alias pimdb -keystore pimvault.p12 -storepass password -storetype PKCS12
   $ keytool -importpass -alias kieserver -keystore pimvault.p12 -storepass password -storetype PKCS12
   $ keytool -importpass -alias cert -keystore pimvault.p12 -storepass password -storetype PKCS12
   $ keytool -importpass -alias keystore -keystore pimvault.p12 -storepass password -storetype PKCS12
   $ keytool -importpass -alias truststore -keystore pimvault.p12 -storepass password -storetype PKCS12

   Copy to Clipboard Toggle word wrap

2. Configure the PIM Keystore Vault to use the keystore file. For example:

   quarkus:
     file:
       vault:
         provider:
           pim:
             path: pimvault.p12
             secret: ${vault.storepassword} # This will be provided as a property

   Copy to Clipboard Toggle word wrap

3. Configure your application to use the credentials from the vault. For example:

   quarkus:
     datasource:
       credentials-provider: quarkus.file.vault.provider.pim.pimdb
   kieservers:
     - host: http://localhost:18080/kie-server/services/rest/server
       credentials-provider: quarkus.file.vault.provider.pim.kieserver

   Copy to Clipboard Toggle word wrap

4. To start PIM with the configured credentials, specify the credentials as an environment variable or as a system property. For example:

   • As an environment variable:

     VAULT_STOREPASSWORD=mysecret java -jar quarkus-app/quarkus-run.jar

     Copy to Clipboard Toggle word wrap

   • As a system property:

     java -Dvault.storepassword=password -jar quarkus-app/quarkus-run.jar

     Copy to Clipboard Toggle word wrap

Procedure

1. Enter http://localhost:8080 in a web browser.
2. Log in to the PIM service.
3. In the upper right corner of the Process Instance Migration page, from the KIE Service list select the KIE Service you want to add a migration plan for.
4. Click Add Plan. The Add Migration Plan Wizard window opens.
5. In the Name field, enter a name for the migration plan.
6. Optional: In the Description field, enter a description for the migration plan.
7. Click Next.
8. In the Source ContainerID field, enter the source container ID.
9. In the Source ProcessId field, enter the source process ID.
10. Click Copy Source To Target.
11. In the Target ContainerID field, update the target container ID.

12. Click Retrieve Definition from backend and click Next.

    

    View larger image

    
13. From the Source Nodes list, select the source node you want to map.
14. From the Target Nodes list, select the target node you want to map.
15. If the Source Process Definition Diagram pane is not displayed, click Show Source Diagram.
16. If the Target Process Definition Diagram pane is not displayed, click Show Target Diagram.

17. Optional: To modify the view in the diagram panes, perform any of the following tasks:

    • To select text, select the icon.
    • To pan, select the icon.
    • To zoom in, select the icon.
    • To zoom out, select the icon.
    • To fit to viewer, select the icon.
18. Click Map these two nodes.
19. Click Next.
20. Optional: To export as a JSON file, click Export.
21. In the Review & Submit tab, review the plan and click Submit Plan.
22. Optional: To export as a JSON file, click Export.
23. Review the response and click Close.

Procedure

1. Enter http://localhost:8080 in a web browser.
2. Log in to the PIM service.
3. On the Process Instance Migration page, select the Edit Migration Plan icon on the row of the migration plan you want to edit. The Edit Migration Plan window opens.
4. On each tab, modify the details you want to change.
5. Click Next.
6. Optional: To export as a JSON file, click Export.
7. In the Review & Submit tab, review the plan and click Submit Plan.
8. Optional: To export as a JSON file, click Export.
9. Review the response and click Close.

Procedure

1. Enter http://localhost:8080 in a web browser.
2. Log in to the PIM service.
3. On the Process Instance Migration page, select the Export Migration Plan icon on the row of the migration plan you want to execute. The Export Migration Plan window opens.
4. Review and click Export.

Procedure

1. Enter http://localhost:8080 in a web browser.
2. Log in to the PIM service.
3. On the Process Instance Migration page, select the Execute Migration Plan icon on the row of the migration plan you want to execute. The Execute Migration Plan Wizard window opens.
4. From the migration plan table, select the check box on the row of each running process instance you want to migrate, and click Next.
5. In the Callback URL field, enter the callback URL.

6. To the right of Run migration, perform one of the following tasks:

   • To execute the migration immediately, select Now.
   • To schedule the migration, select Schedule and in the text field, enter the date and time, for example 06/20/2019 10:00 PM.
7. Click Next.
8. Optional: To export as a JSON file, click Export.
9. Click Execute Plan.
10. Optional: To export as a JSON file, click Export.
11. Check the response and click Close.

Procedure

1. Enter http://localhost:8080 in a web browser.
2. Log in to the PIM service.
3. On the Process Instance Migration page, select the Delete icon on the row of the migration plan you want to delete. The Delete Migration Plan window opens.
4. Click Delete to confirm deletion.