Posted: Thu Jan 09, 2014 12:39 am Post subject: Changing Broker Name -Migration from 7.0.0.5 - IIB 9
Disciple
Joined: 27 Oct 2005 Posts: 185 Location: South Africa
We are in the process of migrating our Broker 7 environment to IIB9.
So we want to ultimately end up on IIB9 with a new Broker name.
So this is the process we want to follow:
We will do a backup of 7.0.0.3, and then change the Broker name (maybe in the script or with a command), and then 'restore' the Broker again on 7.0.0.3 with the new Broker name;
Then we want to migrate this (new Broker name) Broker to IIB9;
The issue we have is - we don't have a way of changing the Broker name to a new name and we don't want to re-create all of the artefacts from scratch in a new environment, deploying all bar files....
So the question is - is there a way (command perhaps) that we can use to re-name the Broker in 7.0.0.3 and restore the Broker with this new name?
Joined: 10 Feb 2003 Posts: 6076 Location: Somewhere over the Rainbow this side of Never-never land.
It seems that you don't have scripts that can create a new broker to your desired config at your site.
IMHO this is a big problem. If for some reason you needed to re-create your prod broker on another system that is identical but only has a different name then you are stuck.
There is an RFE for being able to extract the broker contents as an XML file thus making it editable and to then be able to subsequently build a new broker with that config but that does not help you here.
Perhaps this might be a good time to create those scripts and save them away in your source control system along with the bar files just for that 'rainy day'. _________________ 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.
Even scripts won't re-create deployed objects unless you deploy the bar files again.
mqsibackup/restorebroker is very useful, but it can't change the broker name.
It's really the same problem as if you wanted to change the broker name where it is now.
You could try messing about with the components and registry directories to copy deployed objects onto a new broker from the old one - but this would be entirely at your own risk. There might be broker name or Qm name refererences all over the place. _________________ 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.
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