| **
If I understand the question correctly, this is the
work-around solution for ARS 5.1 from the SupportWeb KB. A
single ARDBC plugin instance can connect to any number of LDAP data
sources, the LDAP URL just has to be modified when creating the vendor
form. The only issue is that the plugin will attempt to bind to the LDAP
directory using the info stored in the ARDBC LDAP Configuration form (which only
allows one entry). If the primary ARDBC connection is configured with a
blank Distinguished Name and Password, then you should be able to connect to any
other LDAP source that accepts anonymous connections by simply modifying the URL
when creating the vendor form. Otherwise, it is necessary to run a
separate instance of the arplugin server, which reads from its own
ar.cfg/ar.conf to obtain the login info for the ARDBC plugin (as described in
the KB below).
HTH,
Thomas
# KM-000000012275
Can you communicate with more than one directory service when using
ARDBC LDAP?
ARS 5.1 Categories
P R O B L E M I would like to create multiple vendor forms that point to 3 or 4 LDAP Servers. Can this be done? S O L U T I O N The URL associated with the form properties can reference a directory service running on any host (and at any port number). The ARDBC LDAP plug-in will connect to that host (and at a specific port number if specified). There are two constraints (when using only a single Plugin server) : The User DN and password (or certificate if using SSL) used to access all directory servers is the same. The list of table names (i.e. LDAP URL's) that the Admin Tool provides when creating a vendor form will be from the host name and port number identified in the configuration. This basically means that you have to enter the LDAP URL by hand when creating a vendor form . Once you have done this, however, the list of attributes available to which you can attach to fields will appear in the Admin Tool. You can get around these limitations by running multiple instances of the plugin server , each with its own configuration - thus addressing the two points above. Granted, this takes some administrative/setup effort. It does not require coding. It uses documented functionality. Basically, you run additional instances of arplugin.exe, each pointing to a different ar.cfg. You would do the following: Create a second AR System install directory with a copy of your 'conf' directory with ar.cfg. You don't need armonitor.cfg in this copy. In your copy of the AR System install directory, modify the ar.cfg to represent the configuration you want for the 2nd instance of arplugin.exe. This second instance of arplugin will need to listen on a different port number than the 1st instance of arplugin, so you'll need to set "Plugin-Port" in ar.cfg to some port number - e.g. "Plugin-Port: 64001" Copy the line in the armonitor.cfg in your primary AR System install directory (the one you made the copy from) that starts arplugin.exe. In the new copy, modify the path specified with the -i option to represent the AR System install directory that contains your 2nd instance of conf/ar.cfg. In the primary instance of ar.cfg, add an alias for the 2nd instance. E.g., Server-Plugin-Alias: ARSYS.ARDBC.LDAP2 ARSYS.ARDBC.LDAP localhost:64001 Once you restart your server you should see "ARSYS.ARDBC.LDAP2" in addition to "ARSYS.ARDBC.LDAP" appear in the Admin Tool when you create a vendor form. The attached white paper goes over this functionality too. __20060125_______________________This posting was submitted with HTML in it___ |
Title: RE: Many ARDBC connections
