|  | 
 
  
    | RSS Feed - WebSphere MQ Support | RSS Feed - Message Broker Support |  
 
  
	|    |  |  
  
	| WMB version & connection with WMB toolkit | « View previous topic :: View next topic » |  
  	| 
		
		
		  | Author | Message |  
		  | schau31 | 
			  
				|  Posted: Tue Jan 27, 2015 8:53 am    Post subject: WMB version & connection with WMB toolkit |   |  |  
		  | Novice
 
 
 Joined: 22 Jan 2015Posts: 10
 
 
 | 
			  
				| Hi, 
 I used till today WMB V8.0.0.1 and Toolkit on a windows environment. Fine.
 I tried to update both to V8.0.0.3. The toolkit updated itself like a charm, but when I installed WMB Fix pack V8.0.0.3, it installed new binaries next to already existing ones, so I'm a bit confused about which version is running "behind the scene"...I mean when I run (for instance) a command like "mqsilist" in both "bin" directories, I get the same output, listing my previously used broker instance...
 
 So my question is : what do I have to perform to switch everything to the new version of the broker ? Do I have to create a new queue manager + local broker ? More than that ... ?
 
 Thank you for your help
 
 Sebastien
 |  |  
		  | Back to top |  |  
		  |  |  
		  | Vitor | 
			  
				|  Posted: Tue Jan 27, 2015 9:06 am    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 11 Nov 2005Posts: 26093
 Location: Texas, USA
 
 | 
			  
				| An mqsichangebroker to pick up the new version? _________________
 Honesty is the best policy.
 Insanity is the best defence.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | mgk | 
			  
				|  Posted: Tue Jan 27, 2015 1:31 pm    Post subject: |   |  |  
		  |  Padawan
 
 
 Joined: 31 Jul 2003Posts: 1647
 
 
 | 
			  
				| For a "side by side" install, to run a Broker at 8.0.0.1 run the profile that comes with 8.0.0.1. To run a Broker at 8.0.0.3, run the profile that comes with 8.0.0.3. Starting a Broker with from a given profile will automatically start the Broker at that level. So if you run the start from an 8.0.0.3 profile then you will running the 8.0.0.3 code and pick up all the APAR fixes in 8.0.0.3. 
 You do not need to run the mqsichangebroker -f command unless you want to set the function level to 8.0.0.3 as well (which means that you can use any new 8.0.0.1 (and .2 and .3) function as well as any APAR fixes).
 
 I hope this helps...
 _________________
 MGK
 The postings I make on this site are my own and don't necessarily represent IBM's positions, strategies or opinions.
 |  |  
		  | Back to top |  |  
		  |  |  
		  | schau31 | 
			  
				|  Posted: Wed Jan 28, 2015 7:33 am    Post subject: |   |  |  
		  | Novice
 
 
 Joined: 22 Jan 2015Posts: 10
 
 
 | 
			  
				| Thank you mgk & Vitor for your help, 
 As I am not familiar with MQ/WMB/Toolkit stuff, I'm still fighting with my problem.
 The thing is that IBM support site indicates that this defect has been fixed in V8.0.0.3 of the product, so I would like to check that this version actually fix my problem.
 
 How I tested so far :
 At the begining, I installed WMB Toolkit (V8.0.0.1) & WMB (V8.0.0.1) on top on MQ (V7.0.1.3) on my laptop.
 Using "MQ Explorer" tool, I configured my environment like this :
 I created a Queue manager "MYQM"
 I created a Local Broker "MYBK" referencing this queue manager.
 
 Then, using "WMB Toolkit", I was able to deploy my flow to this local broker, debug it and ... see that there is a defect in the mapping node management.
 Great. AS the support site indicated that this issue had been fixed by a newer release, I decided to run my flow with WMB v8.0.0.3
 => I updated my WMB Toolkit (thanks to IBM installation manager), and ran the V8.0.0.3 of the WMB installer.
 It installed the binaries of this new version next to the previous one (in my "MQSI" folder, I now have two folders : 8.0.0.1 & 8.0.0.3).
 Then I tried to create a new local broker, and the wizard asked me to select the installation version to create it.
 I chose v8.0.0.3, but could not select the same queue manager as before, so I had to create first a new QM and create this new local broker.
 I stopped my first QM & local broker (v8.0.0.1) and performed a new test of my flow, but the problem is still there, so I doubt the right version is running...
 
 Do you have an idea to see at runtime which version is currently operating my flow ?
 
 Thank in advance
 
 Sebastien
 |  |  
		  | Back to top |  |  
		  |  |  
		  | fjb_saper | 
			  
				|  Posted: Wed Jan 28, 2015 8:21 am    Post subject: |   |  |  
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| Stop the broker. Use the broker command line environment for V 8.0.0.3 and run the mqsistart  (broker) command from there. Your broker will run in the 8.0.0.3 environment with all the corresponding fixes. New features may not be available yet, they depend on the "effective" version of your broker. (see mqsireportbroker)
 
 Have fun
  _________________
 MQ & Broker admin
 |  |  
		  | 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
 
 |  |  |  |