How can two IDM3 eDirectory drivers talk to each other on a multi-instance eDirectory box

  • 3948482
  • 08-Jan-2008
  • 26-Apr-2012

Environment

Novell Identity Manager 3.0
Novell Identity Manager 3.5
Novell Identity Manager 3.5.1

Situation

How can two Identity Manager (IDM) 3 eDirectory drivers talk to each other on a multi-instance eDirectory box?

With IDM 3 running on multi-instance eDirectory (for example, SLES 9/10, Solaris, etc.) how can two eDirectory drivers talk to each other? In the past, you would set the ports for the IDM engines to talk to each other on port 8196 (default) or increment them together on both sides of the connection. With multi-instance eDirectory though, 8196 is owned by the first process to get started which means the second instance of IDM cannot hook onto the same port and make the connection properly. Setting one to 8196 and the other to 8197 does not work because then they are both trying to talk to the other on the port where the other is not listening.

Connection refused error - eDir Driver Between Multiple Instances of eDirectory
java.net.ConnectException: Connection refused

Resolution

You can specify two different ports; one is for the subscriber channel and one is for the publisher channel. The subscriber channel of one driver connects to the publisher channel of the other driver and vice versa. The complete connection information is specified as follows:

[:][[:]:]

Note that "port", if no "publisher port" is specified, is used as the port number to connect to the remote publisher and as the listening port number for the local publisher. If "publisher port" is specified then "port" is only used as the port number to connect to the remote publisher.

So, you probably want to specify something like:

localhost:8196:8197 on the first driver, and localhost:8197:8196 on the second machine.

It is also possible to use different IP addresses instead of different ports though using different ports it the recommended option.

Additional Information

The single port specification is not only "where IDM looks for the remote connection" but also "where IDM listens for an inbound connection".

Formerly known as TID# 10099917

Feedback service temporarily unavailable. For content questions or problems, please contact Support.