ASG
IBM
Zystems
Cressida
Icon
Netflexity
 
  MQSeries.net
Search  Search       Tech Exchange      Education      Certifications      Library      Info Center      SupportPacs      LinkedIn  Search  Search                                                                   FAQ  FAQ   Usergroups  Usergroups
 
Register  ::  Log in Log in to check your private messages
 
RSS Feed - WebSphere MQ Support RSS Feed - Message Broker Support

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsisetdbparms...

Post new topic  Reply to topic
 mqsisetdbparms... « View previous topic :: View next topic » 
Author Message
broker_new
PostPosted: Wed Mar 18, 2009 10:50 am    Post subject: mqsisetdbparms... Reply with quote

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
Whenever we change the password for the Application database we issue mqsisetdbparms to get it reflected on the broker.
So before that we stop the broker and execute it, can we see broker 7.0 it not to bounce.

The reason why i am asking you is....
1) We have 200 message flows deployed on broker which are business critical deployed on the same broker.

nearly 100 flows(TCP protocol) talks to database and 50 flows are exposed as web services and other 50 we are calling the web services.

These 50 web services which we exposed are like the wrappers on the oracle database which message flow calls a stored procedure..

When the database password changes for one of the flow and bounce the broker for changing it , it is impacting the other flows( Broker web services will be down for a while).

In this way we are not able to provide the SOA applications upto the max extent...
_________________
IBM ->Let's build a smarter planet
Back to top
View user's profile Send private message
PeterPotkay
PostPosted: Wed Mar 18, 2009 1:11 pm    Post subject: Reply with quote

Poobah

Joined: 15 May 2001
Posts: 7722
I agree, this is a pain.

MQ 5.3 finally figured it out and let us issue REFRESH SECURITY so we didn't have to bounce the QM to pick up O/S security changes. Its time WMB did the same for mqsisetdbparms.

"Just bounce the broker." It is not an easy thing to do in the real world!
_________________
Peter Potkay
Keep Calm and MQ On
Back to top
View user's profile Send private message
broker_new
PostPosted: Wed Mar 18, 2009 5:50 pm    Post subject: Reply with quote

Yatiri

Joined: 30 Nov 2006
Posts: 614
Location: Washington DC
Our policy in the company is change the databases regularly between 3 to 6 months which might be a best practice to them this is causing us to use separate brokers for each application which uses different app databases.

This is leading us to face the memory limitations and its hard to digest that we are deploying only 3-4 message flows(exposed as web service) in each broker

There is no problem at all for message flows which are mq based as it has no impact of bouncing the broker.

If our experts consider these things and take it as a challenging requirement for the new version release it would be very nice
_________________
IBM ->Let's build a smarter planet
Back to top
View user's profile Send private message
Display posts from previous:   
Post new topic  Reply to topic Page 1 of 1

MQSeries.net Forum Index » WebSphere Message Broker (ACE) Support » mqsisetdbparms...
Jump to:  



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
Protected by Anti-Spam ACP
  
 


Theme by Dustin Baccetti
Powered by phpBB © 2001, 2002 phpBB Group

Copyright © MQSeries.net. All rights reserved.