| Author | 
		  Message
		 | 
		
		  | sshaker | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 10:40 am    Post subject: User name to access remote database | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				Hi 
 
I am trying to access a remote oracle db from my copute node. The target database needs username guest and password for authentication. My broker runs on db2admin/db2admin. How can my compute node/broker access the remote database. Do I have any options to set at my end. ur inputs highly appreciated.
 
 
regards
 
shaker _________________ shaker | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | lbrett | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 10:51 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 24 Jan 2002 Posts: 20
  
  | 
		  
		    
			  
				| Thru the compute node, MQSI will connect to the database using the userid that the broker runs under.  Your only other option is to write a custom node that establishes its own connection to the db. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sshaker | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 11:03 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				hi thnx for the reply,
 
i even changed the service userid and changed the username under which the windows service is running to guest (the target userid / pw required).. looks it is only taking the userid that is used to create the broker..  i am not looking at a custom node.. is there any simple way to use the user id required by target system (db).
 
 
regards,
 
shaker _________________ shaker | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kirani | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 11:27 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Jedi Knight
 
 Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA 
  | 
		  
		    
			  
				shaker,
 
 
There are two user-id's related to WMQI
 
1) service user-id - This id is used to start the service.
 
2) db user-id - This id is used to access remote or local database. 
 
 
So you need to change db user-id of your broker to guest. 
 
I would recommend that you grant permissions to existing db user-id on oracle database. _________________ Kiran
 
 
 
IBM Cert. Solution Designer & System Administrator - WBIMB V5
 
IBM Cert. Solutions Expert - WMQI
 
IBM Cert. Specialist - WMQI, MQSeries
 
IBM Cert. Developer - MQSeries
 
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sshaker | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 11:37 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				hi kiran
 
thnx for the reply.. i am aware of the user ids..but 
 
how to change the db user id once the broker is created with db2admin username and password.. i dont see a way to modify the broker data source user name.. where as i can change the name/pw of service user id.. and i dont want to force changes at database.. ur effort is appreciated.. 
 
 
regards,
 
shaker _________________ shaker | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kirani | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 11:57 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Jedi Knight
 
 Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA 
  | 
		  
		    
			  
				I don't think you can change db user-id directly for the broker/configmgr. You might have to recreate the broker for this. There is no option to change dbuser-id in mqsichangebroker/mqsichangeconfigmgr commands. 
 
That's why i said, I would prefer to define new user-id into database. It is much more simpler than recreating the broker. _________________ Kiran
 
 
 
IBM Cert. Solution Designer & System Administrator - WBIMB V5
 
IBM Cert. Solutions Expert - WMQI
 
IBM Cert. Specialist - WMQI, MQSeries
 
IBM Cert. Developer - MQSeries
 
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sshaker | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 12:03 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				thnx kiran,
 
i wanted to make sure that i am really at the end of the tunnel.. dont u think there should be some mechanism to accommodate such requirements? We end-up talking to so many databases and each time we force to add username.. think of adding db2admin on oracle? 
 
 
thnx again for ur effort
 
 
regards
 
shaker _________________ shaker | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kirani | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 1:05 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Jedi Knight
 
 Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA 
  | 
		  
		    
			  
				shaker,
 
 
I think it is more of a design issue. When you design mqsi broker domain, you should create db-user-id and service-user-id globally (like domain user). db2admin is not a global user-id, instead you can have some meaningful user name related to your application. 
 
 
I think it is not that simple to chage db-user-id, that's why IBM didn't expose this option. In worst case the command might end up deleting and recreating all broker table, which is same as mqsideletebroker.     _________________ Kiran
 
 
 
IBM Cert. Solution Designer & System Administrator - WBIMB V5
 
IBM Cert. Solutions Expert - WMQI
 
IBM Cert. Specialist - WMQI, MQSeries
 
IBM Cert. Developer - MQSeries
 
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sshaker | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 1:12 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				Ya.. u may be right.. there must be some issue in exposing the db user. And I was mentioning db2admin as an example .. in real time we will have different users for different databases.. and each time we are accessing a new database.. we need to 'request' to add a user name (what ever it may be) to that database. May be we have to live with it. 
 
 
regards
 
shaker _________________ shaker | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | AlexeiSkate | 
		  
		    
			  
				 Posted: Mon Oct 07, 2002 5:37 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Centurion
 
 Joined: 10 Apr 2002 Posts: 123
  
  | 
		  
		    
			  
				Hi,
 
 
I just want to get some clarification on which user-id the broker will use to access an external database. Let say my WMQI service user id and password are "myuserid/password2002". When I installed DB2 I used the userid and password of "db2admin/password2002".  When I created my broker, I don't think I specify a datasource userid and password. So when the broker tries to access an external database, it will use the servicer user id and password "myuserid/password2002", correct ?  I would have to define the service id/password to the external database in order for the broker to access its tables ? 
 
 
Thanks,
 
Alex | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | kirani | 
		  
		    
			  
				 Posted: Mon Oct 07, 2002 7:52 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Jedi Knight
 
 Joined: 05 Sep 2001 Posts: 3779 Location: Torrance, CA, USA 
  | 
		  
		    
			  
				Alex,
 
 
Yes, the broker will use myuserid/password2002 to connect to external databases, so you will have to define this userid/pwd into your database with appropriate authorizations. _________________ Kiran
 
 
 
IBM Cert. Solution Designer & System Administrator - WBIMB V5
 
IBM Cert. Solutions Expert - WMQI
 
IBM Cert. Specialist - WMQI, MQSeries
 
IBM Cert. Developer - MQSeries
 
 
 | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | wolstek | 
		  
		    
			  
				 Posted: Tue Oct 08, 2002 5:48 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Acolyte
 
 Joined: 25 Jun 2001 Posts: 52 Location: Bristol, UK 
  | 
		  
		    
			  
				  I am not sure if this is relevant but I was thinking that you could set the userid/password at datasource or odbc level. In the Administration Manual (Chapter 2 ...DB Setup and config) it gives an example of .odbc.ini entries for Oracle. In the 2.0.2 manual this includes user/password
 
   
	| Code: | 
   
  
	
 
[ORACLEDB]
 
Driver=/usr/opt/mqsi/merant/lib/UKor816.so
 
Description=Oracle8
 
ServerName=YourServerName
 
LogonId=scott
 
Password=tiger
 
EnableDescribeParam=1
 
OptimizePrepare=1
 
 | 
   
 
 
whereas in 2.1 manual the loginid and password are no longer there
 
   
	| Code: | 
   
  
	
 
[ORACLEDB]
 
Driver=/usr/opt/mqsi/merant/lib/UKor816.so
 
Description=Oracle8
 
ServerName=YourServerName
 
EnableDescribeParam=1
 
OptimizePrepare=1
 
WorkArounds=536870912
 
WorkArounds2=2
 
 | 
   
 
 
Maybe some use could be made of this. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | zpat | 
		  
		    
			  
				 Posted: Wed Oct 09, 2002 3:54 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Jedi Council
 
 Joined: 19 May 2001 Posts: 5867 Location: UK 
  | 
		  
		    
			  
				| I understand that CSD 3 for WMQI 2.1 has introduced more options for Database authentication. | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |