In a multiple Content Server environment, sometimes ACS/JMS may fail with an Exception since it tries to connect to the remote Content Server projected to Docbroker.

Cause
ACS/JMS connects to Content Server with a trusted login, but it only works locally. If it tries to connect to remote Content Server, it fails.

Resolution
The user can configure additional docbrokers used only internally. Below is a sample configuration with two Content Server and two Docbrokers each.

Suppose on each Content Server, Docbroker 1 is using port 1489 and Docbroker 2 is using port 1491 (port 1490 is used for secure communication by first Docbroker and port 1492 by second Docbroker, since each Docbroker should be assigned with two consecutive ports).

Content Server 1

server.ini
[DOCBROKER_PROJECTION_TARGET]
host = host1
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_1]
host = host2
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_2]
host = host1
port = 1491
proximity = 1
[DOCBROKER_PROJECTION_TARGET_3]
host = host2
port = 1491
proximity = 10

dfc.properties
#only put the docbroker on port 1491
host = host1
port = 1491

Content Server 2
server.ini
[DOCBROKER_PROJECTION_TARGET]
host = host2
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_1]
host = host1
port = 1489
proximity = 5
[DOCBROKER_PROJECTION_TARGET_2]
host = host2
port = 1491
proximity = 1
[DOCBROKER_PROJECTION_TARGET_3]
host = host1
port = 1491
proximity = 10

dfc.properties
#only put the docbroker on port 1491
host = host2
port = 1491

Application server
dfc.docbroker.host[0]= host1
dfc.docbroker.port[0]=1489
dfc.docbroker.host[1]= host2
dfc.docbroker.port[1]=1489

On each machine, the second docbroker is used internally by the clients installed on the CS (ACS, JMS, IDQL, etc). In this way, it prevents the system to try to connect to remote CS with trusted login when it actually is unable to.