Created On:  30 July 2012

Problem:

How to bind Naming service to multiple network interfaces on a multi-home host?

Resolution:

A typical scenario would be:
SE proxy_tp is used for customer's network architecture.
They have a naming service on their local network in which all the program locate can access it.
They also have a NAT firewall locating between the local network and the wide area network. It map the local network IP address and port number of the machine in which the naming server reside to a outside WAN IP and port in order to let the user in WAN access the naming service.
Because the naming service must be accessed from both inside and outside network, an extra SE and proxyHost and proxyPort must be applied.

VisiBroker support multiple default server engines which can be bound to different network interfaces. 


Start the name service: nameserv -config naming.properties
Here is the sample content of naming.properties:
##################################
vbroker.se.default=iiop_tp,proxy_tp

vbroker.se.iiop_tp.scms=iiop_tp
vbroker.se.iiop_tp.scm.iiop_tp.listener.port=10001

vbroker.se.proxy_tp.host=192.168.0.59
vbroker.se.proxy_tp.proxyHost=192.168.0.1
vbroker.se.proxy_tp.scms=proxy_tp
vbroker.se.proxy_tp.scm.proxy_tp.listener.giopVersion=1.2
vbroker.se.proxy_tp.scm.proxy_tp.connection.tcpNoDelay=true
vbroker.se.proxy_tp.scm.proxy_tp.manager.type=Socket
vbroker.se.proxy_tp.scm.proxy_tp.listener.type=IIOP
vbroker.se.proxy_tp.scm.proxy_tp.listener.port=10002
vbroker.se.proxy_tp.scm.proxy_tp.listener.proxyPort=8888
vbroker.se.proxy_tp.scm.proxy_tp.manager.connectionMax=100
vbroker.se.proxy_tp.scm.proxy_tp.manager.connectionMaxIdle=300
vbroker.se.proxy_tp.scm.proxy_tp.dispatcher.type=ThreadPool
vbroker.se.proxy_tp.scm.proxy_tp.dispatcher.threadMax=100
vbroker.se.proxy_tp.scm.proxy_tp.dispatcher.threadMin=5
vbroker.se.proxy_tp.scm.proxy_tp.dispatcher.threadMaxIdle=300
###################################
Incident #00014860