| Author |
Message
|
| prabhuoist |
 Posted: Tue Nov 14, 2017 10:12 pm Post subject: MB 7008 to IIB 10 migration |
 |
|
Apprentice
Joined: 10 Oct 2017
Posts: 39
|
Hi Friends,
Could you please advise if message broker 7008 backup can directly restore in IIB 10.
Or do we need to create all execution group and deploy each and every code again. |
|
| Back to top |
|
 |
| zpat |
| Posted: Wed Nov 15, 2017 12:19 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
What does the IBM documentation say?
I would expect you would need to run mqsimigratecomponents command at the v10 level before a backup and restore will work.
Are these versions on different hosts?
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| prabhuoist |
| Posted: Wed Nov 15, 2017 12:48 am Post subject: |
|
|
Apprentice
Joined: 10 Oct 2017
Posts: 39
|
| Yes, both MB7 and IIB are on different host. |
|
| Back to top |
|
|
| zpat |
| Posted: Wed Nov 15, 2017 1:17 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You will have to upgrade the broker to v10 on the first host before moving it to the other host if you want to use mqsibackup / restorebroker.
You can always downgrade it again on the first host afterwards.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| prabhuoist |
| Posted: Thu Nov 23, 2017 2:25 am Post subject: |
|
|
Apprentice
Joined: 10 Oct 2017
Posts: 39
|
Hi There,
Thanks for the suggestion.
We have now successfully restore the broker backup. However whenever we start the broker, there are multiple errors being print in user.log as below :
Nov 22 12:50:28 SVHJ0117 user:err|error IIB[10617074]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP33) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.eclipse.ui.plugin.AbstractUIPlugin was thrown while loading Java user-defined node class log4jxmlconfignode.Activator.
Nov 22 12:50:31 SVHJ0117 user:err|error IIB[10551368]: IBM Integration Bus v100010 (EAIMBP1.SRI) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.eclipse.ui.plugin.AbstractUIPlugin was thrown while loading Java user-defined node class log4jxmlconfignode.Activator.
Nov 22 12:50:31 SVHJ0117 user:err|error IIB[16122006]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP14) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.eclipse.ui.plugin.AbstractUIPlugin was thrown while loading Java user-defined node class log4jxmlconfignode.Activator.
Nov 22 12:50:33 SVHJ0117 user:err|error IIB[14221334]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP28) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.eclipse.ui.plugin.AbstractUIPlugin was thrown while loading Java user-defined node class log4jxmlconfignode.Activator.
Nov 22 12:50:56 SVHJ0117 user:err|error IIB[10617074]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP33) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.osgi.framework.BundleActivator was thrown while loading Java user-defined node class com.ibm.ws.ClientServicesBundleActivator.
Nov 22 12:50:56 SVHJ0117 user:err|error IIB[10617074]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP33) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.osgi.framework.BundleActivator was thrown while loading Java user-defined node class com.ibm.ws.EMFClientServicesBundleActivator.
Nov 22 12:50:56 SVHJ0117 user:err|error IIB[10617074]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP33) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.osgi.framework.BundleActivator was thrown while loading Java user-defined node class com.ibm.ws.FFDCBundleActivator.
Nov 22 12:50:56 SVHJ0117 user:err|error IIB[10617074]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP33) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.osgi.framework.BundleActivator was thrown while loading Java user-defined node class com.ibm.ws.JavaxRpcBundleActivator.
Nov 22 12:50:56 SVHJ0117 user:err|error IIB[10617074]: IBM Integration Bus v100010 (EAIMBP1.MBP1_EXC_GRP33) [Thread 1] (Msg 1/1) BIP4512S: java.lang.NoClassDefFoundError: org.osgi.framework.BundleActivator was thrown while loading Java user-defined node class com.ibm.ws.RASBundleActivator.
And we are not able to telnet any of the port(though firewall access is there).
Also broker commands(mqsilist, mqsireportproperties etc) output is very very slow.
We have checked the permission on the file system with existing broker server and given same permission.
Any suggestion, what could be the issue here.
So is there anything |
|
| Back to top |
|
|
| abhi_thri |
| Posted: Fri Nov 24, 2017 12:15 am Post subject: |
|
|
Knight
Joined: 17 Jul 2017
Posts: 516
Location: UK
|
| The integration node is not able to find the user-defined jars/classes...please crosscheck whether all jars used by the v7 node is copied to the v10 one and see. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Nov 24, 2017 1:39 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
Probably some flows using the log4j nodes support pac.
Don't just blindly copy user defined node jar files. Look to see if they are compatible with v10, there may be a later version.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
| prabhuoist |
| Posted: Fri Nov 24, 2017 2:01 am Post subject: |
|
|
Apprentice
Joined: 10 Oct 2017
Posts: 39
|
There are two broker running on same server. While broker 1 is having this issue, broker 2 is working fine. We are able to run all integration deployed on broker 2.
Broker 2 also uses same jar files on same path. |
|
| Back to top |
|
|
| zpat |
| Posted: Fri Nov 24, 2017 3:31 am Post subject: |
|
|
Jedi Council
Joined: 19 May 2001
Posts: 5866
Location: UK
|
You should check the origin of user defined node jar files for later versions that are compatible with v10.
Just because the old ones "seem" to work, is not a reason to leave them alone if there are later v10 compatible ones.
It's just the standard professional approach to do this.
_________________
Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
| Back to top |
|
|
|
|
