[RESOLVED] Migration and update process

Submitted by 3Fred9 on Thu, 09/08/2016 - 11:41
1
0
-1

Hi,

I'm going to migrate the engine to Bonita 7.3.0, it was before in 6.3.7.

Since no modifications are necessary for my process, I undestand that no update for them are necessary in Bonita studio.
But when it will be necessary to change one of them (and then change version for example 1.0 to 2.0), will it be necessary to update process (in Bonita 7.3.0) which are dependant of the one to be modified ?

In other words, a process modified in Bonita 7.3.0 could continue to call (by callling activity or by message) process create in Bonita 6.3.7 ?

Thanks for response

migration
update
Process

Comments

Submitted by maxime.baranowski on Thu, 09/08/2016 - 12:08

Hello 3Fred9,

A Bonita 7.3 process can't call a 6.3 process without migrating the 6.3 one.
To migrate it, you just have to import the 6.3 one in Bonita Studio 7.3.

Hope I helped you,

Maxime.

Permalink
Submitted by 3Fred9 on Thu, 09/08/2016 - 12:12

Hello Maxime,

Yes you do.

Thanks you very much for your response.

Permalink
Submitted by 3Fred9 on Thu, 09/08/2016 - 12:15

and a little more...

Every migration of bonita needs conversion of process ? For example betwwen 7.3.2 and 7.3.4 too ?

How can we know when conversion is necessary ?

Thanks

Permalink
Submitted by romualdo.s.rs on Mon, 01/22/2018 - 14:44

Were you able to use the migration tool correctly? I use it however it is not migrating my engine to the requested version.

I even tried to migrate to version 7.4.3 but it still did not work, I even asked a question for that, but still did not get anything, if you can give me a hint how you did, I would be very grateful

Permalink
1 answer

Submitted by Sean McP on Mon, 09/12/2016 - 02:19
1
+1
-1
This one is the BEST answer!

I take it you've read the migration guides?
http://documentation.bonitasoft.com/?page=migrate-from-an-earlier-versio...

You must migrate from 6.x.x to 7.0.0 first and then to 7.3.x

Now as to your question:

But when it becomes necessary to change one of them (and then change version for example 1.0 to 2.0), will it be necessary to update process (in Bonita 7.3.0) which are dependent on the one to be modified? In other words, a process modified in Bonita 7.3.0 could continue to call (by calling activity or by message) process create in Bonita 6.3.7 ?

It depends on the process and the subprocess, we've had to modify some, but not all.

The thing to remember is after the migration the process is not a 6.3.7 process but a 7.3.x process.

The other thing is, you don't actually have to change the subprocess, if you just open the subprocess in Studio 7.3.x, Export the BAR file with a .1 increment and then import it to the production system replacing the previous one.

Now - interesting question:

(does) Every migration of bonita needs conversion of process ? For example between 7.3.2 and 7.3.4 too ?

Yes.

BUT! For Production do you actually need to do this?

Our view is 7.3.x to 7.3.y should only be implemented if you are experiencing a specific issue that is fixed in 7.3.y.

We tend to migrate 7.2 to 7.3 and will do 7.3 to 7.4. it is safer and much easier...

regards
Seán

PS: As this reply answers your question, please mark as resolved by ticking the tick mark on the left of this reply.

Comments

Submitted by 3Fred9 on Mon, 09/12/2016 - 09:26

Hi Sean,

The thing to remember is after the migration the process is not a 6.3.7 process but a 7.3.x process

==> What do this ? The migration tool ? If this really occurs, this answer to my question... Since after the migration, all process already deploy are in 7.3.x, the calling process (which must to be modified) will allready call the subprocess migrated to 7.3.x. So the new version of process after modification continue to call the subprocess in it's older version and migrated and so don't need to be migrated in studio (and then changed of version). Is it really this ?

The other thing is, you don't actually have to change the subprocess, if you just open the subprocess in Studio 7.3.x, Export the BAR file with a .1 increment and then import it to the production system replacing the previous one

==> Of course, this doen't represent to much work... but if this process is a central subprocess which is called by many other process, we must change the new version in all calling activity of process which call him... and then redeploy the new version for all of them...

We tend to migrate 7.2 to 7.3 and will do 7.3 to 7.4. it is safer and much easier...

==> All right...

Regards

Permalink
Submitted by Sean McP on Mon, 09/12/2016 - 12:32

1) Yes, the Migration tool should do this.

2) With 1) above working correctly there is no need to do 2)

And as long as you say in your process Use the latest version of the subprocess there is no need to change any process. It will just use the latest.

regards

Permalink
Submitted by 3Fred9 on Mon, 09/12/2016 - 12:40

Thanks Sean for all these responses.

Permalink
Submitted by romualdo.s.rs on Mon, 01/22/2018 - 14:42

Were you able to use the migration tool correctly? I use it however it is not migrating my engine to the requested version.

I even tried to migrate to version 7.4.3 but it still did not work, I even asked a question for that, but still did not get anything, if you can give me a hint how you did, I would be very grateful

Permalink
Notifications