The Broadcast Repeater utility (dbns12) allows SQL Anywhere clients to find SQL Anywhere database servers running on other subnets and through firewalls where UDP broadcasts normally do not reach, without using the Host connection parameter or LDAP.
There are no prerequisites for this task.
Context and remarks
Any number of DBNS processes can communicate with each other. Each DBNS process connects to every other DBNS that it is aware of, and the different DBNS processes share their lists of DBNS processes. For example, suppose you start two DBNS processes, A and B. If you start a third DBNS process, C, in a third subnet, passing the address of B to C, then B tells C about A, and C then connects to A.
Running more than one DBNS process in a single subnet is generally not necessary, and is not recommended.
If you must run multiple DBNS processes in a single subnet, then you must specify a different port for each DBNS process. A single DBNS process can only listen on one port. Use the -ap parameter in the Broadcast Repeater utility (dbns12).
If either the Host connection parameter or the HOST protocol option is used, then the Broadcast Repeater utility is not needed.
Start a DBNS (database name service) process on any computer in a subnet.
Start a DBNS process on any computer in a different subnet and pass the computer name or IP address of the first computer as a parameter.
The two DBNS processes make a TCP/IP connection to each other.
The DBNS processes now listen for broadcasts on each of their own subnets. Each DBNS process forwards requests over the TCP/IP connection to the other DBNS process, which re-broadcasts the requests on its subnets and also forwards responses back to the originating DBNS process, which sends them to the original client.
Discuss this page in DocCommentXchange.
|Copyright © 2012, iAnywhere Solutions, Inc. - SQL Anywhere 12.0.1|