|   | 
	 
  
    | 
RSS Feed - WebSphere MQ Support
 | 
RSS Feed - Message Broker Support
 |   
 
  
	     | 
	 | 
   
 
  
	|  ODM Configurable Service issue | 
	« View previous topic :: View next topic »  | 
   
  
  	
	  
		
		
		  | Author | 
		  Message
		 |  
		
		  | kash3338 | 
		  
		    
			  
				 Posted: Mon Apr 02, 2018 8:19 am    Post subject: ODM Configurable Service issue | 
				     | 
			   
			 
		   | 
		 
		
		   Shaman
 
 Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India 
  | 
		  
		    
			  
				Hi,
 
 
We are implementing a Decision Service by retrieving business rules at run time from ODM repository. Its done by using the Decision Service configurable service.
 
 
We have run the below set of mqsi commands to setup the configurable service:
 
   
	| Code: | 
   
  
	mqsicreateconfigurableservice <<BROKER_NAME>> -c JDBCProviders -o ODMConfigSrc -n connectionUrlFormat
 
connectionUrlFormatAttr1
 
connectionUrlFormatAttr2
 
connectionUrlFormatAttr3
 
connectionUrlFormatAttr4
 
connectionUrlFormatAttr5
 
databaseName
 
databaseSchemaNames
 
databaseType
 
databaseVersion
 
description
 
environmentParms
 
jarsURL
 
jdbcProviderXASupport
 
maxConnectionPoolSize
 
portNumber
 
securityIdentity
 
serverName
 
type4DatasourceClassName
 
type4DriverClassName 
 
 
-v 
 
"jdbc:db2://[serverName]:[portNumber]/[databaseName]:user=[user];password=[password];"
 
""
 
""
 
""
 
""
 
""
 
ABCDB
 
ABC
 
"DB2 Universal Database"
 
10.1.0
 
default_Description
 
default_none
 
"C:\Program Files\IBM\SQLLIB\java"
 
true
 
0
 
50000
 
DB2SecurityIdentity
 
<<Remote_IP>>
 
com.ibm.db2.jcc.DB2XADataSource
 
com.ibm.db2.jcc.DB2Driver | 
   
 
 
 
   
	| Code: | 
   
  
	| mqsichangeproperties <<BROKER_NAME>> -c DecisionServiceRepository -o Default -n JDBCProviderName,resManagementHost,resManagementPort,resManagementProfiling  -v ODMConfigSrc,<<RES_Server_IP>>,<<RES_Server_Port>>,false | 
   
 
 
 
   
	| Code: | 
   
  
	| mqsisetdbparms <<BROKER_NAME>> -n jdbc::DB2SecurityIdentity -u <<user_name>> -p <<password>> | 
   
 
 
 
I have checked the "Use DecisionServiceRepository configurable service" in the Decision service node.
 
 
The error we get when trying to run this is,
 
 
   
	| Quote: | 
   
  
	
 
RecoverableException
 
					File:CHARACTER:DecisionServiceNode.java
 
					Line:INTEGER:311
 
					Function:CHARACTER:evaluate
 
					Type:CHARACTER:
 
					Name:CHARACTER:
 
					Label:CHARACTER:
 
					Catalog:CHARACTER:BIPmsgs
 
					Severity:INTEGER:3
 
					Number:INTEGER:4324
 
					Text:CHARACTER:Decision Service not found in repository
 
					Insert
 
							Type:INTEGER:5
 
							Text:CHARACTER:Decision Service
 
					Insert
 
							Type:INTEGER:5
 
							Text:CHARACTER:ODM_Test_Sample
 
					Insert
 
							Type:INTEGER:5
 
							Text:CHARACTER:Sample
 
					Insert
 
							Type:INTEGER:5
 
							Text:CHARACTER:
 
					Insert
 
							Type:INTEGER:5
 
							Text:CHARACTER:tbtNrfbCheckrules
 
					Insert
 
							Type:INTEGER:5
 
							Text:CHARACTER:tbtnrfbCheclapptest
 
 | 
   
 
 
 
In the RES server info log, we see the below log,
 
   
	| Quote: | 
   
  
	| Info: Connection from "<<Broker_Server_Host_Name>> | 
   
 
 
 
The user trace gives below info,
 
   
	| Quote: | 
   
  
	RecoverableException  BIP4324E: The DecisionService node ''Decision Service'' in message flow ''ODM_Test_Sample'' cannot locate the ruleset ''tbtNrfbCheckrules'' in the remote repository that is defined by the DecisionServiceRepository configurable service. 
 
The DecisionService node ''Decision Service'' in message flow ''ODM_Test_Sample'' (application ''Sample'', library '''') is configured to use a DecisionServiceRepository configurable service. The ruleset ''tbtNrfbCheckrules'' with namespace ''tbtnrfbCheclapptest'' cannot be located in the remote decision service repository as defined by the configurable service. 
 
Check that the DecisionServiceRepository configurable service properties are correct. Check that the JDBCProviders configurable service properties are correct. Check that the ruleset ''tbtNrfbCheckrules'' with namespace ''tbtnrfbCheclapptest'' is deployed to the remote repository. | 
   
 
 
 
But the Decision Service is deployed and running in RES server. We are able to test that locally in ODM as well. 
 
 
 
What could be the reason for this error? We tried searching this error and dont find any clue.[/img] | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | Vitor | 
		  
		    
			  
				 Posted: Mon Apr 02, 2018 8:57 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Grand High Poobah
 
 Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA 
  | 
		  
		    
			  
				Are you sure that the ruleset is in the correct namespace? _________________ Honesty is the best policy.
 
Insanity is the best defence. | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | fjb_saper | 
		  
		    
			  
				 Posted: Tue Apr 03, 2018 8:06 pm    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		    Grand High Poobah
 
 Joined: 18 Nov 2003 Posts: 20768 Location: LI,NY 
  | 
		  
		    
			  
				And did you check the spelling for the rules asked for? (tbtnrfbCheclapptest)   _________________ MQ & Broker admin | 
			   
			 
		   | 
		 
		
		  | Back to top | 
		  
		  	
		   | 
		 
		
		    | 
		 
		
		  | kash3338 | 
		  
		    
			  
				 Posted: Fri Apr 06, 2018 12:23 am    Post subject:  | 
				     | 
			   
			 
		   | 
		 
		
		   Shaman
 
 Joined: 08 Feb 2009 Posts: 709 Location: Chennai, India 
  | 
		  
		    
			  
				Thanks for the inputs. We had the correct namespace and spelling specified. (The spelling of tbtnrfbCheclapptest was same at both Broker and ODM). But later we changed the name of namespace in ODM and reran the setup, things started working. Some strange reason!!
 
 
But now what we notice is another issue. As per documentation, 
 
   
	| Quote: | 
   
  
	By default, the hot deployment from business console will not reflect immediately to the execution group. You need to configure the Rule execution server for TCP/IP monitoring.
 
 
If you have not configured this, the rules will not reflect immediately. You need to restart the execution group to get the latest rules. | 
   
 
 
 
We have not configured the TCP/IP monitoring in RES server. Hence we are not seeing the changes made in RES reflect in Broker. The problem is, even with a EG or Broker restart we are not seeing the changes reflected in Broker. 
 
 
So the doubt is how does this work and how to get the changes reflected in Broker from RES (without enabling the TCP?IP monitoring in RES)? | 
			   
			 
		   | 
		 
		
		  | 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
  | 
  		 
	   
	 | 
   
 
  	 | 
	  |