<http://data.openlinksw.com/oplweb/faq/UDA/HowcanIdeterminewhichportstheMulti-TierRequestBrokerusesAnswer#this>	<http://www.w3.org/2007/05/powder-s#describedby>	<https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/DAV/data/turtle/general/uda-faq.ttl> .
<http://data.openlinksw.com/oplweb/faq/UDA/HowcanIdeterminewhichportstheMulti-TierRequestBrokerusesAnswer#this>	<http://www.w3.org/2007/05/powder-s#describedby>	<https://www.openlinksw.com/about/id/entity/https/www.openlinksw.com/data/turtle/general/uda-faq.ttl> .
<http://data.openlinksw.com/oplweb/faq/UDA/HowcanIdeterminewhichportstheMulti-TierRequestBrokerusesAnswer#this>	<http://www.w3.org/1999/02/22-rdf-syntax-ns#type>	<http://schema.org/Answer> .
<http://data.openlinksw.com/oplweb/faq/UDA/HowcanIdeterminewhichportstheMulti-TierRequestBrokerusesAnswer#this>	<http://schema.org/answerExplanation>	"The Request Broker port appears in the Session Rules Book. This is the oplrqb.ini file that appears in the /bin sub-directory of the user's server components installation. Users need to open this file with a text editor and locate the following section:\n\n[Protocol TCP]\nPingWatchdog = No\nPingInterval = 600\nListen         = 5000\nPortLow      = 5000\nPortHigh     = 5099\nIPAddress      = 127.0.0.1\n\nOpenLink's 4.x and 5.x Brokers listen on the port passed by the Listen parameter. OpenLink's 1.x and 3.x Brokers listen on the initial port as specified by the PortLow parameter." .