| Author | 
		  Message
		 | 
		
		  | asajnani | 
		  
		    
			  
				 Posted: Sun Sep 29, 2002 2:36 am    Post subject: MQSI Deployment Issues | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 04 Mar 2002 Posts: 21
  
  | 
		  
		    
			  
				I have created a workflow and messageset and assingned the broker with the message set and work flow in the control centre. After I delpoy fromf ile deploy normal i get a success message BIP15201. After that there is no messages in log tab or any graphical messages flows in the organisation tab. 
 
 
I have checked the following:
 
 
1. Config manager running
 
2. Broker running
 
3. Queue Manager running 
 
4. Listenener for Queue Manager running.
 
 
Is there any kind of channel I need to create? Please help me here people
 
 
Thanks Anant | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | Lisa | 
		  
		    
			  
				 Posted: Sun Sep 29, 2002 9:01 am    Post subject: MQSI Deploy Issue | 
				     | 
			   
			 
		   | 
		
		
		   Master
 
 Joined: 07 Jun 2002 Posts: 287 Location: NJ 
  | 
		  
		    
			  
				Hi,
 
Please explain your configuration.
 
Is it like this?
 
Configmgr --> QM1
 
Broker1 --> QM1
 
 
or
 
 
Configmgr --> QM1
 
Broker1 --> QM2
 
 
You will need channels if your broker and configmgr do not share the same qmgr. 
 
 
Hope this helps,
 
Lisa | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sam_mq | 
		  
		    
			  
				 Posted: Mon Sep 30, 2002 7:33 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 22 Aug 2002 Posts: 24
  
  | 
		  
		    
			  
				Hi,
 
 
  If your broker and configmgr share the same QM, i guess u need to refresh your view...
 
still if u have pbs... let us know what's happening exactly...
 
 
Sam | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | sshaker | 
		  
		    
			  
				 Posted: Mon Sep 30, 2002 8:33 am    Post subject:  | 
				     | 
			   
			 
		   | 
		
		
		    Disciple
 
 Joined: 20 Sep 2002 Posts: 185
  
  | 
		  
		    
			  
				anant
 
the information u have provided is not sufficient to really understand ur problem.. i suggest u follow the flow chart in installation guide.. the link:
 
http://publibfp.boulder.ibm.com/epubs/pdf/bipyac05.pdf 
 
 
ref to ch4 and 5 .. that makes sure that ur config is right..
 
then u may test a simple flow with one input and one output node.. where u send a message to input node queue and it should reach the output node queue.. 
 
 
and when ur referring to workflow... i hope ur referring to message flows.. 
 
 
regards
 
shaker _________________ shaker | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | asajnani | 
		  
		    
			  
				 Posted: Tue Oct 01, 2002 2:46 am    Post subject: Emergency Esql Problem Compute Node | 
				     | 
			   
			 
		   | 
		
		
		   Novice
 
 Joined: 04 Mar 2002 Posts: 21
  
  | 
		  
		    
			  
				Solved the issue. My bad.  I have this issue now if you can help me out 
 
 
 
I just want to put my recordset into a string and assign it to the output root but I do not know how to change a list to a string to be assigned to a scalar value. Is there a function of recordset to assign it's data in string like visualbasic? So ,I want to return a field name to the output root and when i do this it does not work. I am using a compute node.
 
 
input-->Compute-->output
 
 
SET Environment.Variables.RecordSet.data[] =PASSTHRU('SELECT * FROM stacey.project');SET OutputRoot=Environment.Variables.ResultSet.Record[1]."projno" ; 
 
 
 
There is a failure doing and using the debugger all error messages i get is in the output node that no message data. I have tried hardcoding outputroot='test' and same error message. THis is strange when i assign outpoot root to the input root it works fine Can anyone advise me?
 
 
I know that that the select statement is being executed correctly. I assigned a output root xml to it and saw it using the debugger. 
 
 
 
 
Thanks Anant | 
			   
			 
		   | 
		
		
		  | Back to top | 
		  
		  	
		   | 
		
		
		    | 
		
		
		  | 
		    
		   |