Hello, 
I have been reading that the only possibility to Migrating from BPM Standard 8.5.6 to BAW 21.x is to upgrade the current environment, with the option to clone it to a new machine and than upgrade in the new machine to keep the current environment untouched. 
I would like to install a complete new BAW 21.x and than some way to migrate the data from BPM. 
Some tool to export the configuration and import in the new one. I believe that the database can be cloned and be used in the new BAW with no problems.
Is not this really possible?

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

From infrastructure upgrade standpoint the approach seems fine. But the major problem happens with the application artifacts compatibility.
It's good to take backup of the product DB or if possible the whole VM for easy rollback.

------------------------------
Atanu Roy
Solution Architect
Salient Process
------------------------------

Hello Atanu,
I will start with the Test environment, and I expect the Developers to test the applications before passing to the Staging environment and by the end the Production one. 
I also do not do any change to the current environment, it will be always available while I create the new one, and upgrade it.
If any change to the applications is needed they will detect it in the test phase. (I hope) :-)

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

Original Message:
Sent: Tue January 11, 2022 03:00 AM
From: Atanu Roy
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

From infrastructure upgrade standpoint the approach seems fine. But the major problem happens with the application artifacts compatibility.
It's good to take backup of the product DB or if possible the whole VM for easy rollback.

------------------------------
Atanu Roy
Solution Architect
Salient Process
------------------------------

Yes, that should be the ideal approach, upgrade the Process Center at last.

------------------------------
Atanu Roy
Solution Architect
Salient Process
------------------------------

Original Message:
Sent: Tue January 11, 2022 04:53 AM
From: JOAO PEDRO ALEXANDRE
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hello Atanu,
I will start with the Test environment, and I expect the Developers to test the applications before passing to the Staging environment and by the end the Production one. 
I also do not do any change to the current environment, it will be always available while I create the new one, and upgrade it.
If any change to the applications is needed they will detect it in the test phase. (I hope) :-)

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


Original Message:
Sent: Tue January 11, 2022 03:00 AM
From: Atanu Roy
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

From infrastructure upgrade standpoint the approach seems fine. But the major problem happens with the application artifacts compatibility.
It's good to take backup of the product DB or if possible the whole VM for easy rollback.

------------------------------
Atanu Roy
Solution Architect
Salient Process

Hello Joao, 
You're right, the only support way if you want to keep the data (apps + inflight/historical process instances) is to upgrade. You are also right when saying that you can combine this with a move to new hardware. Unfortunately the remote migration that we knew until 8.5.0 is not applicable. 

If keeping the process instances is not important to you, then another option could be to start from scratch on a new environment and import any process applications and toolkits you need. This however requires some preparation to keep the dependencies clean and maybe some scripting for the export/import if you have a large number of applications. 

Hope that helps! 
You can find a summary article on upgrade/migration here.

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

Hi Matthias,
thanks for your explanation.
Yes , it helped.
Yes I was also thinking in installing from scratch in a test environment , and import/export the applications and toolkits. I always prefer to create clena environments and configure exactly what I need. For the BPM files, like 100Custom.xml and others, I can copy from their current location, but I am afraid that I can miss other BPM configurations like Filenet integration and others' that I do not know.
There would be good to have an export script that gets all the configuration and import it in the new environment.
I will try to collect the most information I can about the environment to know exactly what I have to define in the new environment.

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

Original Message:
Sent: Tue January 11, 2022 03:44 AM
From: Matthias Benda
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hello Joao, 
You're right, the only support way if you want to keep the data (apps + inflight/historical process instances) is to upgrade. You are also right when saying that you can combine this with a move to new hardware. Unfortunately the remote migration that we knew until 8.5.0 is not applicable. 

If keeping the process instances is not important to you, then another option could be to start from scratch on a new environment and import any process applications and toolkits you need. This however requires some preparation to keep the dependencies clean and maybe some scripting for the export/import if you have a large number of applications. 

Hope that helps! 
You can find a summary article on upgrade/migration here.

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

Hi Joao, 
You can always use BPMConfig -export to export the BPM configuratin, which might be a good starting point for your new environment.
Also, there is a WAS tooling to export / import any WebSphere configuration, which is helpful when you have a lot of custom data sources, JMS and other resources configured in your environment. 

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

Original Message:
Sent: Tue January 11, 2022 04:45 AM
From: JOAO PEDRO ALEXANDRE
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hi Matthias,
thanks for your explanation.
Yes , it helped.
Yes I was also thinking in installing from scratch in a test environment , and import/export the applications and toolkits. I always prefer to create clena environments and configure exactly what I need. For the BPM files, like 100Custom.xml and others, I can copy from their current location, but I am afraid that I can miss other BPM configurations like Filenet integration and others' that I do not know.
There would be good to have an export script that gets all the configuration and import it in the new environment.
I will try to collect the most information I can about the environment to know exactly what I have to define in the new environment.

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


Original Message:
Sent: Tue January 11, 2022 03:44 AM
From: Matthias Benda
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hello Joao, 
You're right, the only support way if you want to keep the data (apps + inflight/historical process instances) is to upgrade. You are also right when saying that you can combine this with a move to new hardware. Unfortunately the remote migration that we knew until 8.5.0 is not applicable. 

If keeping the process instances is not important to you, then another option could be to start from scratch on a new environment and import any process applications and toolkits you need. This however requires some preparation to keep the dependencies clean and maybe some scripting for the export/import if you have a large number of applications. 

Hope that helps! 
You can find a summary article on upgrade/migration here.

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

Thanks again,
yes, I know the tool to export WAS resources I will use it, because I noticed that tree are definitions of another business DB datasources and jca connections.

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

Original Message:
Sent: Tue January 11, 2022 06:20 AM
From: Matthias Benda
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hi Joao, 
You can always use BPMConfig -export to export the BPM configuratin, which might be a good starting point for your new environment.
Also, there is a WAS tooling to export / import any WebSphere configuration, which is helpful when you have a lot of custom data sources, JMS and other resources configured in your environment. 

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


Original Message:
Sent: Tue January 11, 2022 04:45 AM
From: JOAO PEDRO ALEXANDRE
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hi Matthias,
thanks for your explanation.
Yes , it helped.
Yes I was also thinking in installing from scratch in a test environment , and import/export the applications and toolkits. I always prefer to create clena environments and configure exactly what I need. For the BPM files, like 100Custom.xml and others, I can copy from their current location, but I am afraid that I can miss other BPM configurations like Filenet integration and others' that I do not know.
There would be good to have an export script that gets all the configuration and import it in the new environment.
I will try to collect the most information I can about the environment to know exactly what I have to define in the new environment.

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


Original Message:
Sent: Tue January 11, 2022 03:44 AM
From: Matthias Benda
Subject: Migrating from BPM Standard 8.5.6 to BAW 21.x

Hello Joao, 
You're right, the only support way if you want to keep the data (apps + inflight/historical process instances) is to upgrade. You are also right when saying that you can combine this with a move to new hardware. Unfortunately the remote migration that we knew until 8.5.0 is not applicable. 

If keeping the process instances is not important to you, then another option could be to start from scratch on a new environment and import any process applications and toolkits you need. This however requires some preparation to keep the dependencies clean and maybe some scripting for the export/import if you have a large number of applications. 

Hope that helps! 
You can find a summary article on upgrade/migration here.

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