Author |
Message
|
hiiib |
Posted: Thu Nov 10, 2016 11:14 pm Post subject: How can we change URL Registration url property |
|
|
Newbie
Joined: 10 Nov 2016 Posts: 1
|
Hello experts,
I would like to change the url property under URLRegistration
dynamically using mqsichange properties for below , Kindly suggest how would i can change this
Code: |
HTTPConnector
uuid='HTTPConnector'
userTraceLevel='none'
traceLevel='none'
userTraceFilter='none'
traceFilter='none'
port='7080'
address=''
maxPostSize=''
acceptCount=''
compressableMimeTypes=''
compression=''
connectionLinger=''
connectionTimeout=''
maxHttpHeaderSize=''
maxKeepAliveRequests=''
maxThreads=''
minSpareThreads=''
noCompressionUserAgents=''
restrictedUserAgents=''
socketBuffer=''
tcpNoDelay=''
explicitlySetPortNumber=''
enableLookups=''
enableMQListener=''
shutdownDelay=''
allowCrossConnectorPolling=''
autoRespondHTTPHEADRequests=''
Connector
port='7080'
type='Broker'
URLRegistration
url='/rbl/api/test2
UsedBySOAPNNodes='FALSE'
UsedByHTTPNNodes='TRUE'
nodeLabel='HTTP Input'
URLRegistration
url='/rbl/api/test'
UsedBySOAPNNodes='FALSE'
UsedByHTTPNNodes='TRUE'
nodeLabel='HTTP Input' |
Regards, |
|
Back to top |
|
 |
fjb_saper |
Posted: Fri Nov 11, 2016 5:49 am Post subject: |
|
|
 Grand High Poobah
Joined: 18 Nov 2003 Posts: 20756 Location: LI,NY
|
Have you thought about using a bar override file and redeploying?
That's the way I would do it...
Moved to Broker Topic  _________________ MQ & Broker admin |
|
Back to top |
|
 |
Craig B |
Posted: Mon Nov 14, 2016 3:55 am Post subject: |
|
|
Partisan
Joined: 18 Jun 2003 Posts: 316 Location: UK
|
You cannot directly change the URL of HTTPInput/SOAPInput nodes after deployment using any of the commands or APIs. As ther previous response has mentioned you will need to update this either through BAR file overrides or the message flow needs to be updated in the Toolkit. Both of these approaches will need a redeploy. _________________ Regards
Craig |
|
Back to top |
|
 |
zpat |
Posted: Mon Nov 14, 2016 6:35 am Post subject: |
|
|
 Jedi Council
Joined: 19 May 2001 Posts: 5866 Location: UK
|
You can design flows to set the URLs dynamically and store them in a User Defined Configurable service, UDP, global cache, message queue, DB or any other means of storing them that a message flow can access.
This is certainly possible for web service calls made from a flow. I don't know if the same principle can be applied to inbound calls. _________________ Well, I don't think there is any question about it. It can only be attributable to human error. This sort of thing has cropped up before, and it has always been due to human error. |
|
Back to top |
|
 |
Vitor |
Posted: Mon Nov 14, 2016 7:27 am Post subject: |
|
|
 Grand High Poobah
Joined: 11 Nov 2005 Posts: 26093 Location: Texas, USA
|
zpat wrote: |
This is certainly possible for web service calls made from a flow. I don't know if the same principle can be applied to inbound calls. |
Best bet would be to redesign as a gateway flow, and store the URL as you describe so that a Route node (or similar) can be used.
That's a lot of work & code. I'd just override it. _________________ Honesty is the best policy.
Insanity is the best defence. |
|
Back to top |
|
 |
|