| Author |
Message
|
| Caket |
 Posted: Sun May 12, 2013 2:22 am Post subject: mb8.0.0.1 to mb8.0.0.2 fixpack upgrade |
 |
|
Novice
Joined: 07 Aug 2010
Posts: 10
|
Darn it,
resubbing post again.
Installed original MB8 which included fp1 and used default values where install dir was MQSI\8.0.0.1.
windows service starts pointing to fp 1 runtime.
Installed mb8 fp2 into MQSI\8.0.0.2. Windows service still points to 8.0.0.1 directory.
apart from recreating broker, uninstalling fp2 and reinstalling into fp1 location, how would one install fp2 so that it does exists in a different location and windows service points to new runtime. |
|
| Back to top |
|
 |
| mqjeff |
| Posted: Sun May 12, 2013 6:42 am Post subject: |
|
|
Grand Master
Joined: 25 Jun 2008
Posts: 17447
|
| The service is specific to the broker, not to the install. |
|
| Back to top |
|
|
| Caket |
| Posted: Sun May 12, 2013 7:02 am Post subject: |
|
|
Novice
Joined: 07 Aug 2010
Posts: 10
|
Jeff, if service is specific to broker, then I should have installed fp at same point all the time. So the different directories should be used for Broker versions not for fixpacks.
Guess i muddled the version's and fixpacks statements up.
Strange then MQ install defaulted to MQSI\8.0.0.1 directory. It should have been MQSI\8. |
|
| Back to top |
|
|
| Vitor |
| Posted: Sun May 12, 2013 7:38 am Post subject: |
|
|
Grand High Poobah
Joined: 11 Nov 2005
Posts: 26093
Location: Texas, USA
|
| Caket wrote: |
| Jeff, if service is specific to broker, then I should have installed fp at same point all the time. So the different directories should be used for Broker versions not for fixpacks. |
What I think my most worthy associate is getting at is that the service running broker FOO is distinct from the service running broker BAR. It's perfectly acceptable (and under some circumstances reasonable) to have 2 brokers at 2 different levels.
| Caket wrote: |
| Strange then MQ install defaulted to MQSI\8.0.0.1 directory. It should have been MQSI\8. |
If it did that, how could you maintain separate brokers at different levels?
_________________
Honesty is the best policy.
Insanity is the best defence. |
|
| Back to top |
|
|
| mgk |
| Posted: Sun May 12, 2013 7:57 am Post subject: |
|
|
Padawan
Joined: 31 Jul 2003
Posts: 1642
|
| Quote: |
| how would one install fp2 so that it does exists in a different location and windows service points to new runtime |
When you start a broker, the runtime automatically changes the windows service definition to point to the runtime which is starting it (assuming it points somewhere else). It happens automatically, you don't have to do anything...
Kind regards,
_________________
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 |
|
|
| ramires |
| Posted: Sun May 12, 2013 3:10 pm Post subject: |
|
|
Knight
Joined: 24 Jun 2001
Posts: 523
Location: Portugal - Lisboa
|
This broker fixpack installation can confuse users. Initially we have <mqsipath>\8.0.0.1
after a fixpack and others we have
<mqsipath>\8.0.0.2
<mqsipath>\8.0.0.3
<mqsipath>\8.0.0.4
<mqsipath>\8.0.0.n
and we can choose the fixpack to start? MQ is really more simple, install a fix pack, a backup is made and if necessary a roolback can be done.
I prefer to use only one directory for broker binaries.
_________________
Obrigado / Thanks you |
|
| Back to top |
|
|
| Caket |
| Posted: Sun May 12, 2013 10:56 pm Post subject: |
|
|
Novice
Joined: 07 Aug 2010
Posts: 10
|
You are all right.
Profiled to fp 2 at the command line
My broker had the start as MQ service as "defined".
I undefined it and started broker from commandline.
It started,
Checked windows and Broker service was now pointing to FP2 runtime.
thank you all. |
|
| Back to top |
|
|
|
|
