| Author |
Message
|
| pratuluv |
 Posted: Wed Dec 25, 2013 11:30 pm Post subject: Migration from WMB v8 to IB v9.0 |
 |
|
Acolyte
Joined: 25 May 2011
Posts: 53
|
Hi,
We are currently working on WMB v8. We have around 100 main flows that in turn calls around 500 subflows running on v8.0, mostly on MQ protocol.
If I want to migrate to version 9, how feasible would that be at this given point. Please advice. |
|
| Back to top |
|
 |
| Simbu |
| Posted: Thu Dec 26, 2013 3:04 am Post subject: |
|
|
Master
Joined: 17 Jun 2011
Posts: 289
Location: Tamil Nadu, India
|
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Dec 27, 2013 9:05 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
Migrating from WMB v8 to IIB v9 is pretty much the same as migrating from WMB v7 to WMB v8. Is there any particular reason why you thought it would be a problem?
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| emiddleware |
| Posted: Wed Dec 10, 2014 3:32 am Post subject: IIB migration v9 |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi
I want to do cross platform migration. The MQ version is 7.0 and MB artifacts are in v 6.1 in Unix platform.
I have downloaded IIB v9 and MQ 7.5 trial version in Windows ..
Is there any document for cross-platform migration ?
I was thinking of connecting to Unix via Win scp and getting the components and importing it into my IIB v9
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| smdavies99 |
| Posted: Wed Dec 10, 2014 3:55 am Post subject: |
|
|
Jedi Council
Joined: 10 Feb 2003
Posts: 6076
Location: Somewhere over the Rainbow this side of Never-never land.
|
I'm currently runnnig a test VM where ALL the flows etc that are deployed
were built on 7.0.0.4. By that I mean that the .bar files were created using a V7.0.0.4 tooklit.
The Test VM is running IBM MQ 8.0.0.1 and IIB 9.0.0.2
Ok, so this is all on (boo hiss) Windows but there really wasn't a big problem with the migration once I'd sorted out a get little gotchas (as documented here - sigh)
All the scripts that were used for the V7 build only required a few tweaks for the V9 build. These were mainly to do with the making it all work nicely in an MSCS environment.
_________________
WMQ User since 1999
MQSI/WBI/WMB/'Thingy' User since 2002
Linux user since 1995
Every time you reinvent the wheel the more square it gets (anon). If in doubt think and investigate before you ask silly questions. |
|
| Back to top |
|
|
| emiddleware |
| Posted: Tue Dec 16, 2014 9:47 pm Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi Simbu,
The above link is not opening . Can u share anyother document . I want to migrate artifacts from MB v6 (unix) to IIB v9 (Windows) and MB v6 (unix) to IIB v9 (Unix).
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| JosephGramig |
| Posted: Wed Dec 17, 2014 11:56 am Post subject: |
|
|
Grand Master
Joined: 09 Feb 2006
Posts: 1244
Location: Gold Coast of Florida, USA
|
Well, you cannot migrate "artifacts" from one broker to another (especially on a different platform). You will need to redeploy them. You will probably need to migrate the source code from Toolkit 6.0.?.? to 7.0.0.7 and then to 9.0.0.2.
For your UNIX broker, are you looking to upgrade the software on the same UNIX box for the upgrade or is this to another box?
I would suggest going to a new box as a "Co-exist" migration just to be sure the new environment is clean.
I'm sure you've read the KC all about migrating from 6.0 to 7.0 and 7.0 to 9.0... |
|
| Back to top |
|
|
| emiddleware |
| Posted: Fri Jan 02, 2015 3:08 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
[quote="JosephGramig"]Well, you cannot migrate "artifacts" from one broker to another (especially on a different platform). You will need to redeploy them. You will probably need to migrate the source code from Toolkit 6.0.?.? to 7.0.0.7 and then to 9.0.0.2.
| Quote: |
For your UNIX broker, are you looking to upgrade the software on the same UNIX box for the upgrade or is this to another box?
|
I would suggest going to a new box as a "Co-exist" migration just to be sure the new environment is clean.
I'm sure you've read the KC all about migrating from 6.0 to 7.0 and 7.0 to 9.0...
Hi Joseph,
Yes I want to import the artifacts to my local environment in Windows . The current message flows are running in Unix. I tried importing the flows .. The only issue is that IIB v9 is not recognizing the subflows .
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| kimbert |
| Posted: Fri Jan 02, 2015 3:34 am Post subject: |
|
|
Jedi Council
Joined: 29 Jul 2003
Posts: 5542
Location: Southampton
|
| Quote: |
| The current message flows are running in Unix. I tried importing the flows |
Did you take the BAR files that were deployed to the Unix machine and redeploy them on the Windows machine?
If not, then what exactly did you do?
_________________
Before you criticize someone, walk a mile in their shoes. That way you're a mile away, and you have their shoes too. |
|
| Back to top |
|
|
| emiddleware |
| Posted: Mon Jan 05, 2015 12:14 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
| kimbert wrote: |
| Quote: |
| The current message flows are running in Unix. I tried importing the flows |
Did you take the BAR files that were deployed to the Unix machine and redeploy them on the Windows machine?
If not, then what exactly did you do? |
Hi Kimbert,
I took the project files from svn repository and saved in my local system in windows.
The project files contain message flows , subflows, common flows and message set that were developed in v6.1 and are currently deployed in unix environment.
I have installed IIB v9 and MQ v7.5 in my Windows system. I created a new project and imported the artifacts into the new project in the workspace.
I could have re-deployed the flows in my current EG in Windows . But I see many errors. One of the error is that its not recognizing the subflows .. It says unable to "locate the input terminal of subflow ".
I created a separate project for subflows and tried giving this as a reference to the main message flow project. I rebuild the workspace. But still I see red cross marks.
I am not interested to re-deploy the bar file . I just want to import the flows manually and re-build them in my workspace and deploy the flow in my EG.
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| emiddleware |
| Posted: Mon Jan 05, 2015 3:30 am Post subject: |
|
|
Centurion
Joined: 03 Apr 2006
Posts: 120
|
Hi !!
I managed to remove the errors related to subflows .
I am getting two main errors.
Circular project dependency and
Flow with duplicate name found in referenced project.
For Circular project dependency I checked http://www.mqseries.net/phpBB2/viewtopic.php?p=245926/.
I first checked my jvm strength.. So I ran the following command and the result too.
Before executing the command I first wanted to check the properties first.
C:\Program Files\IBM\MQSI\9.0.0.2>mqsireportproperties IB9NODE -b agent -o ComIb
mJVMManager -r
ComIbmJVMManager
uuid='ComIbmJVMManager'
jvmVerboseOption='none'
jvmDisableClassGC='false'
jvmEnableIncGC='false'
jvmNativeStackSize='-1'
jvmMinHeapSize='16777216'
jvmMaxHeapSize='393216000'
jvmDebugPort='0'
As I am convinced that there is enough memory allocated to JVM , I did not alter anything.
I don't understand the duplicate name... I have done the project references ... I have not created any project name with duplicate name .. Why am I getting this ?
K 
_________________
Best Regards,
E-MiddleWare |
|
| Back to top |
|
|
| fjb_saper |
| Posted: Mon Jan 05, 2015 5:37 am Post subject: |
|
|
Grand High Poobah
Joined: 18 Nov 2003
Posts: 20756
Location: LI,NY
|
| emiddleware wrote: |
I don't understand the duplicate name... I have done the project references ... I have not created any project name with duplicate name .. Why am I getting this ?
K |
You are getting this because you have a duplicate flow name that is not in a different broker schema.
Say you have flow name abc in default schema in lib A and flow name abc in default schema in lib B. Now if applicaton app1 references both lib A and lib B you have a flow naming conflict...
So your problem might still be related to your circular reference problem... 
_________________
MQ & Broker admin |
|
| Back to top |
|
|
|
|
