| |
|
RSS Feed - WebSphere MQ Support
|
RSS Feed - Message Broker Support
|
  |
|
| MQSI 2.02 --> 2.1, can't see anything in Control Center |
« View previous topic :: View next topic » |
| Author |
Message
|
| Jari |
 Posted: Thu Sep 18, 2003 8:04 am Post subject: MQSI 2.02 --> 2.1, can't see anything in Control Center |
 |
|
Novice
Joined: 09 Oct 2001
Posts: 16
|
Hi,
I upgraded MQSI from 2.02 to 2.1 CSD05. MQ Series is 5.2.0.7 CSD07.
Now I'm not able to see any flows, assignments etc.
I had to delete the config mgr database when upgrading and had to create the config manager again. After this I was not able to see the flows anymore. Before upgrade they were available. The flows are there and work fine when testing.
I've tried setting up the security domain stuff according to administration guide to no avail. I DO NOT have the domain level groups set up (Domain mqbrasgn etc.). Shoul I set these up ? I only have the local groups and the user I'm using is admin of the machine and is in all the local mq groups.
Any help greatly appreciated!
Kind Regards,
Jari Pakarinen |
|
| Back to top |
|
 |
| EddieA |
| Posted: Thu Sep 18, 2003 9:05 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Did you use the -n -m flags when deleting the configmgr. If so, then you deleted all the tables in the database. That means you lost everything. And I hope you had a backup. 
Did you follow, to the letter, the instructions in the Administration Guide.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Jari |
| Posted: Thu Sep 18, 2003 9:38 pm Post subject: |
|
|
Novice
Joined: 09 Oct 2001
Posts: 16
|
Hi,
| EddieA wrote: |
Did you use the -n -m flags when deleting the configmgr. If so, then you deleted all the tables in the database. That means you lost everything. And I hope you had a backup.
Did you follow, to the letter, the instructions in the Administration Guide.
Cheers, |
I did use the -n -m. What did I actually lose ? The stuff that was deployed still work. I do have exports of the flows, but not of the assignments and subscriptions. I can however get these from the production system but it's going to be a bit of work... 
Is there going to be problems if I add new assignments that are different from the ones I had before ?
I'm able to create new flows. The old flows still show up in the left hand window where the IBMPrimitives are but I'm not able to see their contents. I think I should see these flows ?
I can't see the brokers in the topology or assignments view. Are they lost or is it the security stuff that is wrong here ?
I did follow through the Administration guide part "Scenario 3: operation on a stand-alone machine" on page 72. I have not however added the domain groups "Domain mqbrasgn" etc as I thought they are not needed.
If I add these domain groups, should I add them to the domain where the users are or to the domain where the server is registered ? Users logon to USERS domain and the server is in CITY domain.
Lots of questions  Thanks for your help!
Jari |
|
| Back to top |
|
|
| Craig B |
| Posted: Fri Sep 19, 2003 10:35 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003
Posts: 316
Location: UK
|
Hi,
As Eddie pointed out, if you used the -n -m options on the mqsideleteconfigMgr command then this would have deleted any resources belonging to this configMgr from your configMgr database and the MRM database. So, in affect you have deleted your message flows, messageSets, assignment information, topology and broker information. This is why you cannot see these anymore in your Control Centre.
You mentioned that you can still see flows in your Control Centre, but you cannot see the contents of these flows. This is because your workspace that this control centre has, has references to these message flows when you added them to your workspace at some point. But when you click on them, it uses the reference (a uuid) to look up the flow contents in the configMgr database, and in this case, they are not their because you have deleted them.
Your broker will still be running fine, because when you delete the configmgr you have not affected anything on a broker machine. The broker will still have its Broker database, where it has all the flows and messageSets that were ever deployed to it.
However, this means that your configMgr and Broker are no longer in synch, and so the next time you deploy to this broker, you will have to do a complete deploy.
Hopefully you have a backup of your MRM and ConfigMgr databases or you have the exports of all your flows and messageSets. If you do have backups of these databases then you should be able to re-instate them. If you only have exports, then you will need to go through the lengthy process of importing them all again. It would be worth removing the old flows references from your workspace so that you can import the new flows.
You will then have to go through the process of setting up your broker in the topology, creating executions grouop, assigning all your flows and messageSets. You may encounter problems between mismatches between what the broker thinks yours brokers UUID is and what the configMgr believes it is.
_________________
Regards
Craig |
|
| Back to top |
|
|
| Jari |
| Posted: Wed Sep 24, 2003 3:55 am Post subject: |
|
|
Novice
Joined: 09 Oct 2001
Posts: 16
|
Hi Craig,
Thanks for the reply.
Am I correct in thinking that I will have to recreate the brokers (we have two of them on one config manager) again ? Or will mqsichangebroker do the job ?
Thanks again!
Regards,
Jari |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Sep 24, 2003 8:31 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
You might get away with just re-connecting the brokers in the topology. But as Craig pointed out:
| Quote: |
| You may encounter problems between mismatches between what the broker thinks yours brokers UUID is and what the configMgr believes it is. |
But, also:
| Quote: |
| However, this means that your configMgr and Broker are no longer in synch, and so the next time you deploy to this broker, you will have to do a complete deploy. |
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| Back to top |
|
|
| Jari |
| Posted: Wed Sep 24, 2003 9:33 am Post subject: |
|
|
Novice
Joined: 09 Oct 2001
Posts: 16
|
Thanks Eddie,
I don't see the brokers in the topology or assignments. Do I have to recreate the brokers to be able to see them again ?
Regards,
Jari |
|
| Back to top |
|
|
| EddieA |
| Posted: Wed Sep 24, 2003 11:31 am Post subject: |
|
|
Jedi
Joined: 28 Jun 2001
Posts: 2453
Location: Los Angeles
|
Yes, because that's what 'inserts' the information into the ConfigMgr.
Cheers,
_________________
Eddie Atherton
IBM Certified Solution Developer - WebSphere Message Broker V6.1
IBM Certified Solution Developer - WebSphere Message Broker V7.0 |
|
| 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
|
|
|
|
