| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| Workflow Migration Question |
« View previous topic :: View next topic » |
| Author |
Message
|
| MaheshPN |
 Posted: Wed Jul 19, 2006 11:08 am Post subject: Workflow Migration Question |
 |
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi,
We have a scenario where we need to move the application running on WF 3.4 to a new box, on which we are going to have 3.6.
Idea is to not to disturb the old environment. Just backup the db, restore on newsystem and migrate using mig_360 utility.
I was going through the command and I saw that, we need to provide the configuration name during migration, which makes it not to work on new box.
couple of option I thought of..
1. Backup 3.4, migrate and restore the backup again (Risky of production)
2. Setup 3.4 environment on new box, migrate and then upgrade.
Do you guys think of any workable solution, with a minimal or no affect on the 3.4 box?
Thanks,
-Mahesh |
|
| Back to top |
|
 |
| koko |
| Posted: Wed Jul 19, 2006 11:36 am Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
You can *copy* data to the new server. Once the whole data is moved to the new place, you can turn on all the feeders into workflow.
I would give two weeks to see if everything else is going to be fine for the move from 3.4 on old box to 3.6 on new box. Once I gain confidence that everything is fine, would clean up the data on the new server and copy the latest data from 3.4 system.
| Quote: |
| I was going through the command and I saw that, we need to provide the configuration name during migration, which makes it not to work on new box. |
I didnt quite understand this. Can you not have a clean workflow environment and the same old configi d on the newer box?
_________________
Thanks
Koko |
|
| Back to top |
|
|
| MaheshPN |
| Posted: Wed Jul 19, 2006 12:38 pm Post subject: |
|
|
Master
Joined: 21 May 2003
Posts: 245
Location: Charlotte, NC
|
Hi Koko,
If I understood the migration stuff, first we need to migrate the database to make it compatible with WF 3.6 in order to work properly.
We don't have "power" to do so on 3.4 box. So, I thought of copying the old data on newbox and migrate it to 3.6 before doing the configuration.
Since, its a new box, there won't be any configuration which migration utility looks for.
I just spoke to IBM and they said "IBM does not recommend to move the data from one hardware to another".
Which brings a new question, does anybody moved their WF database to new box once installed?
Thanks,
-Mahesh |
|
| Back to top |
|
|
| koko |
| Posted: Wed Jul 19, 2006 1:27 pm Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
| Quote: |
| does anybody moved their WF database to new box once installed? |
We did.
We basically copied over data from one machine to another. I am not very sure if we have incremented the version or not but I am thinking we did move from 3.4 to 3.5.
Its a very simple thing for the DBAs. They do the data copy. From a WF stand point once the data is copied over we did a rebinds and everything was fine.
basically we created an exact replica of old configuration in the new env but without any data. so its a clean new env. Once the data is copied over, we were up and running. But its been a long time since we did this so some other experts may chip in and prove me wrong. 
_________________
Thanks
Koko |
|
| Back to top |
|
|
| koko |
| Posted: Wed Jul 19, 2006 1:41 pm Post subject: |
|
|
Master
Joined: 26 Sep 2003
Posts: 206
|
| Quote: |
| I just spoke to IBM and they said "IBM does not recommend to move the data from one hardware to another". |
Also IBM claims that MQ workflow is horizontally and vertically scalable. So I guess what you are trying to do should be feasilble 
_________________
Thanks
Koko |
|
| Back to top |
|
|
| hos |
| Posted: Fri Jul 21, 2006 1:37 am Post subject: |
|
|
Chevalier
Joined: 03 Feb 2002
Posts: 470
|
Mahesh,
I suggest the following approach:
1. Copy the 3.4 database to the new box.
2. Install 3.6 on the new box.
3. Now configure the 3.4 configID on the 3.6 box using the following options:
- use existing DB (the 3.4 DB is OK at this point in time)
- unselect to import the initial date into this DB during configuration
4. Migrate the DB to 3.6
All of this should not impact your production system at all.
After sufficient sanity checking you can move production to the 3.6 box.
Good Luck! |
|
| Back to top |
|
|
|
|
|
| |
|
Page 1 of 1 |
|
You cannot post new topics in this forum
You cannot reply to topics in this forum
You cannot edit your posts in this forum
You cannot delete your posts in this forum
You cannot vote in polls in this forum
|
|
|
|
