| Author |
Message
|
| halbe01 |
 Posted: Tue Mar 29, 2005 4:59 am Post subject: View database username in v5 Broker |
 |
|
Novice
Joined: 02 Feb 2005
Posts: 16
|
Hi,
I have a broker which accesses a remote Oracle database using an ODBC connection, plus a username and password combination which I have set using mqsisetdbparms.
However, I would like to verify which user the database is connecting with (i.e. what must have been put in the mqsisetdbparms command). I can find no way to view this information from the broker. Is there a way?
Obviously I can work this from the other side (i.e. run the flow and look at the Oracle logs to see who is connecting at that point) but that means getting our Oracle dba's involved and is somewhat long winded.
So, does anyone know if it's possible to find out what the mqsisetdbparms parameters were (I'm assuming the password won't be readable, but that's ok).
Many thanks for any help,
Regards,
Ben. |
|
| Back to top |
|
 |
| JT |
| Posted: Tue Mar 29, 2005 6:52 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
What OS?
On the Solaris platform (and probably most UNIX systems), the database id can be found at:
/var/mqsi/registry/broker_name/DSN/database_name/Userid
As you surmised the password is encrypted in the Password file. |
|
| Back to top |
|
|
| halbe01 |
| Posted: Wed Mar 30, 2005 2:26 am Post subject: |
|
|
Novice
Joined: 02 Feb 2005
Posts: 16
|
| Sorry - forgot to mention - this is on a Windows platform. I suspect then it's in the windows registry somewhere...? |
|
| Back to top |
|
|
| JT |
| Posted: Wed Mar 30, 2005 5:48 am Post subject: |
|
|
Padawan
Joined: 27 Mar 2003
Posts: 1564
Location: Hartford, CT.
|
|
| Back to top |
|
|
| halbe01 |
| Posted: Thu Mar 31, 2005 1:38 am Post subject: |
|
|
Novice
Joined: 02 Feb 2005
Posts: 16
|
Got it - nice one, thanks!
Ben. |
|
| Back to top |
|
|
| SAFraser |
| Posted: Thu Mar 31, 2005 2:21 pm Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
Just learned this undocumented command when I opened a WMQI ticket recently:
| Code: |
| mqsiservice <brokername> |
It works on Solaris just dandy, summarizing a lot of what's in the registry files. I don't know about Windows -- maybe someone can try it and let us know? |
|
| Back to top |
|
|
| bower5932 |
| Posted: Thu Mar 31, 2005 2:51 pm Post subject: |
|
|
Jedi Knight
Joined: 27 Aug 2001
Posts: 3023
Location: Dallas, TX, USA
|
From my windows machine:
| Code: |
C:\support>mqsiservice wbi_broker
BIPv500 en US
ucnv Console CCSID 437 dft ucnv CCSID 5348
OS cp1252 ICUW ibm-5348_P100-1997 ICUA ibm-5348_P100-1997
Install Path = C:/WBIMB
Working Path = C:/WBIMB
Component UUID = 63095a76-fd00-0000-0080-c5f6e1828f8f
process id = 0
broker db name = WBRKBKDB
broker db userId = bower
broker db password =
queue manager = wbi_qmgr
pubsub migration = no
fastpath Queue Manager = yes
configuration timeout = 300
configuration delay timeout = 60
statistics major interval = 60
Trace, bipservice, bipbroker, bipconfigmgr, bipuns = debug
TraceSize = 50000000
executionGroupTraceOverrideLevel = debug
BIP8071I: Successful command completion. |
|
|
| Back to top |
|
|
| SAFraser |
| Posted: Fri Apr 01, 2005 10:56 am Post subject: |
|
|
Shaman
Joined: 22 Oct 2003
Posts: 742
Location: Austin, Texas, USA
|
It's good to know it works in Windows, too. Thanks for trying it, bower.
ALSO -- this does work on WMQI v2.1 also.
Shirley |
|
| Back to top |
|
|
|
|
