| Author | Message | 
		
		  | murared | 
			  
				|  Posted: Wed Apr 23, 2014 7:19 am    Post subject: Websphere Application Server Shipping with WMQ |   |  | 
		
		  | Novice
 
 
 Joined: 16 Jan 2014Posts: 17
 
 
 | 
			  
				| Hello Team, 
 We are going to apply the fix pack on WMQ 7.0.1.14 and the Websphere Application Server is running on 7.0.0.29. When i checked for IBM site,
 
 http://www-304.ibm.com/support/docview.wss?rs=171&uid=swg21248089#7dotx
 
 It is showing the shipping versions.
 
 Please suggest me that if i want to apply fix pack on MQ, DO i need to install the websphere application server first?
 
 Thanks,
 Murali.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Wed Apr 23, 2014 7:32 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| If you want to keep in sync, are you sure you don't need to upgrade to WAS 8? _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | murared | 
			  
				|  Posted: Wed Apr 23, 2014 9:20 pm    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 16 Jan 2014Posts: 17
 
 
 | 
			  
				| Hi fjb_saper, 
 We have so many Websphere Applications configured int he environment and we are not moving to upgrade websphere instead we are going to do it for WMQ. Please suggest us.
 
 Thanks,
 Reddy.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | zpat | 
			  
				|  Posted: Wed Apr 23, 2014 9:51 pm    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| Applying the WMQ fixpack may not upgrade the imbedded MQ client in WAS. _________________
 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 |  | 
		
		  |  | 
		
		  | murared | 
			  
				|  Posted: Thu Apr 24, 2014 1:26 am    Post subject: |   |  | 
		
		  | Novice
 
 
 Joined: 16 Jan 2014Posts: 17
 
 
 | 
			  
				| Hi Zpat, 
 Yes, that is the only reason i have posted this. I have gone through so many IBM sites for this topic but not found any related one. Please let me know if anybody tried this out in the environments?
 
 Thanks,
 Murali.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | fjb_saper | 
			  
				|  Posted: Thu Apr 24, 2014 5:59 am    Post subject: |   |  | 
		
		  |  Grand High Poobah
 
 
 Joined: 18 Nov 2003Posts: 20767
 Location: LI,NY
 
 | 
			  
				| You can upgrade MQ and leave WAS as is. Just be aware that the features accessible to you on WAS may be limited to the set provided by the level of your WAS MQ Client...  _________________
 MQ & Broker admin
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  | zpat | 
			  
				|  Posted: Thu Apr 24, 2014 6:20 am    Post subject: |   |  | 
		
		  |  Jedi Council
 
 
 Joined: 19 May 2001Posts: 5867
 Location: UK
 
 | 
			  
				| If you want to upgrade the imbedded MQ client - upgrade the WAS installation. 
 IBM test the WAS version and the imbedded MQ version together - I don't think it's wise to upgrade one without the other.
 
 Applying a MQ fixpack will only upgrade the MQ installation if it was installed separately to WAS.
 
 Fairly sure the MQ fixpack will have no interaction with the imbedded client, unless you were to manually copy over jar files etc.
 _________________
 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 |  | 
		
		  |  | 
		
		  | JosephGramig | 
			  
				|  Posted: Thu Apr 24, 2014 7:20 am    Post subject: |   |  | 
		
		  |  Grand Master
 
 
 Joined: 09 Feb 2006Posts: 1244
 Location: Gold Coast of Florida, USA
 
 | 
			  
				| 
   
	| zpat wrote: |  
	| ... unless you were to manually copy over jar files etc. |   That's asking for trouble for sure! 
 Apply maintenance to WAS to get the desired level of MQ Client. Do this first and then apply maintenance to MQ. I had a weird issue with WAS 7.0 where even the maintenance didn't take affect and the MQ Client was still at MQ 7.0.0.0 and when I upgraded the Qmgr the WAS application broke because MQ fixed a bug. I posted the link on this site several months ago about this one off issue.
 |  | 
		
		  | Back to top |  | 
		
		  |  | 
		
		  |  |