Hello,
I have this plan to upgrade from BPM 8.5.6 to BAW 21.0.0.3. (in summary, do not worry with the details now) 

1. Clone the existing development environment
2. Follow the instructions in Migrating Process Center artifacts - IBM Documentation
3.  Clone DB
4. Start new Dev and test it
5. Upgrade to BAW 21.0.0.3 the new Dev.
6. Do the same in Staging and by the end Production environment.

My doubt here is when I have to repeat the some steps in Quality and Production I am worried with the following. We know that the artifacts are not migrated as it is said in Cloning the deployment environment - IBM Documentation:
The databases and customer applications are not replicated to the new environment. For instructions to replicate the complete environment, see Migrating IBM BPM to new hardware.
The issue is that I do not find in the documentation how to Export existing process applications and toolkits in the Process Server as it is done above in the Process Center. The new environment must have exactly the same snapshots (some names /ids , information, ...)
Imagine that I have Human Tasks running at certain workflows / Processes, with the clone of the databases the data (process status) is not lost, but what about the apps / snapshots?! Shouldn't they be exported and imported in the new environment somehow to allow the Human Tasks to continue their workflow in the new environment?

------------------------------
JOAO PEDRO ALEXANDRE
------------------------------

Hello, 
Let me clarify what is meant by the terms cloning and migrating to new hardware are a bit misleading here. 
From the documentation point-of-view, cloning means recreating the exact same type of configuration but somewhere else, as a new environment, i.e. new DB.
Migrating means you keep the same environment with its database. All process applications snapshots are stored in the database together with the process instances so they are migrated in a consistent way.
Hope that helps.

------------------------------
Matthias Benda
------------------------------

Hello, yes it helps. I thought that the applications had to be exported from the old environment and imported in the new, as it happens with WAS applications, or I would need to deploy again the snapshots. So a BPM application / snapshot is not in the file system, it is in DB, now I understand.

------------------------------
JOAO PEDRO ALEXANDRE
------------------------------

Original Message:
Sent: Tue February 01, 2022 03:43 AM
From: Matthias Benda
Subject: Cloning BPM 8.5.6

Hello, 
Let me clarify what is meant by the terms cloning and migrating to new hardware are a bit misleading here. 
From the documentation point-of-view, cloning means recreating the exact same type of configuration but somewhere else, as a new environment, i.e. new DB.
Migrating means you keep the same environment with its database. All process applications snapshots are stored in the database together with the process instances so they are migrated in a consistent way.
Hope that helps.

------------------------------
Matthias Benda
------------------------------

Hello again, 
the same applies to Process Center, right? 
So the sentence "... customer applications are not replicated to the new environment" is wrong. It should be more clear. I believe they mean BLA Applications or other applications that were deployed as normal WAS applications. 

------------------------------
JOAO PEDRO ALEXANDRE
------------------------------

Original Message:
Sent: Tue February 01, 2022 03:43 AM
From: Matthias Benda
Subject: Cloning BPM 8.5.6

Hello, 
Let me clarify what is meant by the terms cloning and migrating to new hardware are a bit misleading here. 
From the documentation point-of-view, cloning means recreating the exact same type of configuration but somewhere else, as a new environment, i.e. new DB.
Migrating means you keep the same environment with its database. All process applications snapshots are stored in the database together with the process instances so they are migrated in a consistent way.
Hope that helps.

------------------------------
Matthias Benda
------------------------------