| Author |
Message
|
| lawrence |
 Posted: Wed Jul 10, 2002 10:36 pm Post subject: Migrate Workflow server 3.3.0 to 3.3.2 |
 |
|
Novice
Joined: 04 Jun 2002
Posts: 13
|
Dear All,
Currently, my development server is version 3.3. I like to set up a new production server using the latest Workflow server version 3.3.2. I like to synchronize the buildtime and runtime databases between development and production server. My existing Workflow design processes, staff defintions etc are at the development Workflow server. Is it sufficient by exporting the fdl definitions from the development server's Workflow builtime and importing it into the new production server's Workflow buildtime and also import it into production runtime using fmcibie?
Thank you.
regards, |
|
| Back to top |
|
 |
| jmac |
| Posted: Thu Jul 11, 2002 4:34 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Lawrence:
You can migrate everything exactyly as you say, except for in-flight instances in your existing Runtime database.
After you set up the new system, export all from old runtime, then import into the new runtime DB, and new Buidtime DB
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| steinra |
| Posted: Thu Jul 11, 2002 2:48 pm Post subject: |
|
|
Apprentice
Joined: 23 May 2002
Posts: 28
Location: USA
|
I have not had a chance to look at all the steps needed to do an upgrade.
In the case of a production server can you migrate the in-flight processes as well?
Thanks!
Randy |
|
| Back to top |
|
|
| jmac |
| Posted: Thu Jul 11, 2002 4:43 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
Randy:
In the past IBM has provided a mechanism for this, but you generally need to ask about it directly. I.E. I don't think there is a single command for all environments, process models etc.
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
| lawrence |
| Posted: Thu Jul 11, 2002 6:25 pm Post subject: |
|
|
Novice
Joined: 04 Jun 2002
Posts: 13
|
Thanks, so the first step is to do an export of runtime database of the development server and do an import into the new server's buildtime and runtime. But I suppose we could also use an export of old buildtime database, import into the new buildtime database and so on.
By the way, anyone knows whats the meaning of in-flight instances? |
|
| Back to top |
|
|
| jmac |
| Posted: Fri Jul 12, 2002 4:55 am Post subject: |
|
|
Jedi Knight
Joined: 27 Jun 2001
Posts: 3081
Location: EmeriCon, LLC
|
An "In-flight" instance is an instance in your runtime database that has been started, and not yet completed.
By far the easiest way to migrate to a new version of MQWF, is to let all the in-flight instances complete, but start new instances on your updated platform. This is fine as long as you dont have long-running instances. For example if you had instances that ran for say 6 months, you'd need to maintain both systems (old and new versions of MQWF for that period of time), in that case you'd want to investigate migrating the in-flight instances
_________________
John McDonald
RETIRED |
|
| Back to top |
|
|
|
|
